Method and system for increasing and suppressing alarm number through alarm source
By constructing a real-time network topology and using a sliding time window to count the percentage of disconnected devices, and setting root cause determination conditions, the problem of alarm storms caused by network topology changes in existing technologies has been solved, achieving efficient alarm suppression and fault location, and improving operation and maintenance efficiency.
Patent Information
- Application Number
- CN202511663447.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-13
- Publication Date
- 2025-12-16
AI Technical Summary
In existing technologies, static suppression rules cannot adapt to changes in network topology in data centers, campus networks, or wide area networks. Simple topology aggregation cannot distinguish between single device failures and router failures, leading to alarm storms and difficulties in locating and repairing them.
By constructing a real-time network topology, establishing a parent-child relationship diagram between routers and downstream devices, using a sliding time window to count the percentage of disconnected devices, setting root cause determination conditions, blocking timeout alarms from downstream devices, and only issuing high-severity router fault alarms.
Significantly reduces alarm noise, improves operational efficiency, reduces broadcast storms, quickly locates and repairs network faults, and has low operating overhead.
Smart Images

Figure CN121151186A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the field of communication network operation and maintenance technology, and particularly relates to a method and system for improving the number of suppressed alarms by alarm root cause. BACKGROUND
[0002] In a data center, a campus network or a wide area network, an operation and maintenance platform usually needs to monitor thousands of terminal devices (servers, sensors, cameras, IoT nodes, etc.) at the same time. These devices are connected to the network through multiple levels of routers / switches. When a router fails, all the devices connected to it will lose their heartbeat at the same time. The traditional alarm system will treat each offline device as an independent heartbeat timeout event and send out an alarm, which can easily cause an alarm storm.
[0003] The prior art mainly uses static suppression rules or simple topology aggregation methods, which have the following defects: 1. Static rules rely on manual configuration and cannot adapt to frequent changes in network topology; 2. Simple topology aggregation cannot distinguish between "single device failure" and "router failure", which can easily cause false negatives; 3. The alarm suppression granularity is coarse and cannot provide "router-level" root causes, which is not conducive to quick positioning and repair. SUMMARY
[0004] The purpose of the present application is to provide a method for improving the number of suppressed alarms by alarm root cause to solve one or more technical problems in the prior art and at least provide a beneficial choice or create conditions.
[0005] To achieve the above technical purpose, the technical solution of the present application is as follows: In a first aspect, the present application provides a method for improving the number of suppressed alarms by alarm root cause, comprising the following steps: Step 1: Construct a real-time network topology and establish a parent-child relationship graph between routers and downstream devices; Step 2: When a heartbeat timeout alarm of a downstream device occurs in the network, the proportion of offline devices in a sliding time window with the parent router as the dimension is counted; Step 3: When the proportion of offline devices exceeds a threshold, the router is determined to be the root cause, a pre-warning containing the router meeting the root cause determinator condition is sent out, and the timeout alarms under the router are shielded.
[0006] Further, in step 1, the sub-step of constructing a real-time network topology and establishing a parent-child relationship graph between routers and downstream devices is: Step 1.1: Periodically construct and maintain a parent-child relationship graph G=(R∪D, E) of "router-downstream device" using one or more of the following methods: IP address, subnet mask, and default gateway. Here, R is the set of routers, D is the set of downstream devices, and E is a directed edge. The parent-child relationship graph G represents "router r downstream device d", where router r is an element in the set of routers R and downstream device d is an element in the set of downstream devices D. Step 1.2: Set a sliding time window. The sliding time window is used to maintain a time window of length Δt for each router r, and count the number of timeout alarms of the corresponding router's downstream devices within each time window.
[0007] Furthermore, in step 2, when a heartbeat timeout alarm occurs in the network, the sub-step of calculating the percentage of disconnected devices within a sliding time window with the parent router as the dimension is as follows: Step 2.1: Check whether the heartbeat packets periodically returned by the downstream device are correct, or whether a heartbeat packet is returned within the set interval. If the returned heartbeat packet is incorrect or no heartbeat packet is returned within the timeout, generate a timeout alarm and mark the disconnected device. The timeout alarm includes device identifier, timestamp, and event type. Step 2.2: Determine the router r corresponding to the downstream device that issued the timeout alarm based on the parent-child relationship graph G; Step 2.3: In the corresponding time window W_r, update the number of disconnected devices d_offline(r) of router r. Step 2.4, calculate the percentage of disconnected devices under router r = d_offline(r) / d_total(r); where d_offline(r) is the number of disconnected devices under router r, and d_total(r) is the total number of downstream devices under router r.
[0008] Step 3.1, set the root cause determiner conditions: The percentage of devices that are out of service is ≥θ; Where θ is the first threshold; Step 3.2: Traverse each router and determine whether it meets the root cause determination condition. If there is a router r that meets the root cause determination condition, trigger the root cause event e_root(r); otherwise, retain the timeout alarm of the original disconnected device. Step 3.3: Mark all downstream devices of router r that triggered the root cause event e_root(r) with alarm suppression flags, and issue an alert including router r that meets the root cause determiner conditions; Step 3.4: Disable all timeout warnings for all downstream devices of router r that triggered the root cause event e_root(r).
[0009] The purpose of step 3.4 is to prevent a batch failure of downstream devices of a router from impacting the entire system due to timeout warnings. Therefore, after the root cause determination condition is met, the timeout warnings of all downstream devices on the router are blocked. Instead, a warning message is displayed to remind maintenance personnel to pay attention and troubleshoot the problem. This will not impact the warning system and reduce network congestion caused by broadcast storms. If the router does not meet the root cause determination condition, the timeout warnings of the router's downstream devices are still retained, but the warning priority is lower. Manual troubleshooting will still be arranged, or the root cause determination condition will be retried after enough timeout warnings are accumulated.
[0010] Furthermore, step 3.5 is included, which involves clearing the alarm suppression flags of all downstream devices connected to router r after all downstream devices under router r have recovered.
[0011] Preferably, step 3.5 is as follows: when some downstream devices under router r cannot be restored, only the alarm suppression flag of the restored downstream devices is cleared, and the timeout warning of the faulty downstream devices is removed.
[0012] The purpose of steps 3.2 to 3.5 is to stratify faults and prioritize handling router areas with more severe faults.
[0013] Preferably, the first threshold is 0.9.
[0014] If there are many faulty downstream devices in the entire system, the first threshold can be changed to adjust the device fault tolerance.
[0015] Preferably, the first threshold, Δt, and the confidence level of the parent-child relationship are all variables.
[0016] Preferably, all undefined variables in this invention, if not explicitly defined, can be manually set thresholds.
[0017] Secondly, the present invention provides a system for increasing the number of suppressed alarms by addressing the root cause of alarms, the system comprising: Topology discovery module: Used to periodically build and maintain a parent-child relationship graph G=(R∪D, E) of "router-downstream device" using one or more of the following methods: IP address, subnet mask, and default gateway. Here, R is the set of routers, D is the set of downstream devices, and E is a directed edge. The parent-child relationship graph G represents "router r downstream device d", where router r is an element in the set of routers R and downstream device d is an element in the set of downstream devices D. Sliding Time Window Management Module: Used to set up the sliding time window manager, which maintains a time window of length Δt for each router r; Alarm access module: Used to detect whether the heartbeat packets periodically returned by the downstream device are correct, or whether a heartbeat packet is returned within a set interval. If the returned heartbeat packet is incorrect or no heartbeat packet is returned within a timeout, a timeout alarm is generated. The timeout alarm includes device identifier, timestamp, and event type; find the router r corresponding to the downstream device that triggered the timeout alarm; Root cause decision module: used to calculate the percentage of out-of-connection devices. If the percentage of out-of-connection devices is greater than the first threshold, a root cause event is triggered. Suppression and escalation module: Used to mark all downstream devices under the router r that triggered the root cause event with alarm suppression flags, and to issue an alert including the router r that meets the root cause determiner conditions; Used to block all timeout warnings from all downstream devices of router r for root cause event e_root(r); Once all downstream devices under router r have recovered, clear the alarm suppression flags of all downstream devices under router r, or clear only the alarm suppression flags of the downstream devices under router r that have recovered and remove the shielding of timeout warnings for faulty downstream devices.
[0018] Thirdly, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for increasing the number of suppressed alarms by means of alarm root causes provided in the first aspect of the present invention.
[0019] Fourthly, the present invention provides an electronic device, comprising: a memory storing a computer program thereon; and a processor for executing the computer program in the memory to implement the steps of the method for increasing the number of suppressed alarms by addressing alarm root causes provided by the present invention.
[0020] The method of this invention can dynamically identify the root cause event of "all devices connected to the same route losing connection" in the real-time alarm stream, and replace thousands of device-level heartbeat alarms with a single high-severity router fault alarm, thereby significantly reducing alarm noise and improving operation and maintenance efficiency. Low operating overhead: the algorithm complexity is O(n), and memory usage is proportional to the number of routers. This method can be extended to multi-level routing, link aggregation, and VLAN scenarios. Attached Figure Description
[0021] Figure 1 A flowchart of a method for increasing the number of suppressed alarms by addressing the root cause of alarms provided by this invention; Figure 2 This is a schematic block diagram of a system structure for increasing the number of suppressed alarms by addressing the root cause of alarms, according to an embodiment of the present invention. Detailed Implementation
[0022] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. The specific embodiments described herein are only for explaining the invention and are not intended to limit the invention.
[0023] It should also be understood that the following embodiments are only used to further illustrate the present invention and should not be construed as limiting the scope of protection of the present invention. Any non-essential improvements and adjustments made by those skilled in the art based on the above description of the present invention are within the scope of protection of the present invention. The specific process parameters, etc., in the following examples are merely examples within a suitable range; that is, those skilled in the art can make appropriate selections within the range based on the description herein, and are not intended to be limited to the specific values in the examples below.
[0024] The following exemplifies a method provided by the present invention for increasing the number of suppressed alarms by addressing the root cause of alarms.
[0025] like Figure 1 The diagram shows a flowchart of a method to increase the number of suppressed alarms by addressing the root cause of alarms. The following section will combine... Figure 1 This invention describes a method for increasing the number of suppressed alarms by addressing the root cause of alarms, comprising the following steps: Step 1: Construct the real-time network topology and establish a parent-child relationship diagram between the router and downstream devices; Step 2: When a heartbeat timeout alarm occurs in the network, the percentage of disconnected devices is counted within a sliding time window with the parent router as the dimension. Step 3: When the proportion of disconnected devices exceeds the threshold, the router is determined to be the root cause, and an early warning is issued including routers that meet the conditions of the root cause determiner, and timeout alarms under the router are blocked.
[0026] In a preferred embodiment, the downstream devices are multiple outdoor data collection devices connected wirelessly.
[0027] Furthermore, in step 1, the sub-steps for constructing the real-time network topology and establishing the parent-child relationship graph between the router and downstream devices are as follows: Step 1.1: Periodically construct and maintain a parent-child relationship graph G=(R∪D, E) of "router-downstream device" using one or more of the following methods: IP address, subnet mask, and default gateway. Here, R is the set of routers, D is the set of downstream devices, and E is a directed edge. The parent-child relationship graph G represents "router r downstream device d", where router r is an element in the set of routers R and downstream device d is an element in the set of downstream devices D. Step 1.2: Set a sliding time window. The sliding time window is used to maintain a time window of length Δt for each router r, and count the number of timeout alarms of the corresponding router's downstream devices within each time window.
[0028] Furthermore, in step 2, when a heartbeat timeout alarm occurs in the network, the sub-step of calculating the percentage of disconnected devices within a sliding time window with the parent router as the dimension is as follows: Step 2.1: Check whether the heartbeat packets periodically returned by the downstream device are correct, or whether a heartbeat packet is returned within the set interval. If the returned heartbeat packet is incorrect or no heartbeat packet is returned within the timeout, generate a timeout alarm and mark the disconnected device. The timeout alarm includes device identifier, timestamp, and event type. Step 2.2: Determine the router r corresponding to the downstream device that issued the timeout alarm based on the parent-child relationship graph G; Step 2.3: In the corresponding time window W_r, update the number of disconnected devices d_offline(r) of router r. Step 2.4, calculate the percentage of disconnected devices under router r = d_offline(r) / d_total(r); where d_offline(r) is the number of disconnected devices under router r, and d_total(r) is the total number of downstream devices under router r.
[0029] Further, in step 3, when the proportion of disconnected devices exceeds a threshold, the router is determined to be the root cause, and an alert is issued including routers that meet the root cause determination criteria. The sub-step of blocking timeout alarms under the router is as follows: Step 3.1, set the root cause determiner conditions: The percentage of devices that are out of service is ≥θ; Where θ is the first threshold; Step 3.2: Traverse each router and determine whether it meets the root cause determination condition. If there is a router r that meets the root cause determination condition, trigger the root cause event e_root(r); otherwise, retain the timeout alarm of the original disconnected device. Step 3.3: Mark all downstream devices of router r that triggered the root cause event e_root(r) with alarm suppression flags, and issue an alert including router r that meets the root cause determiner conditions; Step 3.4: Disable all timeout warnings for all downstream devices of router r that triggered the root cause event e_root(r).
[0030] Furthermore, step 3.5 is included, which involves clearing the alarm suppression flags of all downstream devices connected to router r after all downstream devices under router r have recovered.
[0031] Preferably, step 3.5 is as follows: when some downstream devices under router r cannot be restored, only the alarm suppression flag of the restored downstream devices is cleared, and the timeout warning of the faulty downstream devices is removed.
[0032] Preferably, the first threshold is 0.9.
[0033] If there are many faulty downstream devices in the entire system, the first threshold can be changed to adjust the device fault tolerance.
[0034] Preferably, the first threshold, Δt, and the confidence level of the parent-child relationship are all variable and can be set manually.
[0035] Preferably, all undefined variables in this invention, if not explicitly defined, can be manually set thresholds.
[0036] like Figure 2 The diagram shown is a schematic block diagram of a system structure for suppressing the number of alarms by increasing the source of alarms, according to an embodiment of the present invention.
[0037] Topology discovery module: Used to periodically build and maintain a parent-child relationship graph G=(R∪D, E) of "router-downstream device" using one or more of the following methods: IP address, subnet mask, and default gateway. Here, R is the set of routers, D is the set of downstream devices, and E is a directed edge. The parent-child relationship graph G represents "router r downstream device d", where router r is an element in the set of routers R and downstream device d is an element in the set of downstream devices D. Sliding Time Window Management Module: Used to set up the sliding time window manager, which maintains a time window of length Δt for each router r; Alarm access module: Used to detect whether the heartbeat packets periodically returned by the downstream device are correct, or whether a heartbeat packet is returned within a set interval. If the returned heartbeat packet is incorrect or no heartbeat packet is returned within a timeout, a timeout alarm is generated. The timeout alarm includes device identifier, timestamp, and event type; find the router r corresponding to the downstream device that triggered the timeout alarm; Root cause decision module: used to calculate the percentage of out-of-connection devices. If the percentage of out-of-connection devices is greater than the first threshold, a root cause event is triggered. Suppression and escalation module: Used to mark all downstream devices under the router r that triggered the root cause event with alarm suppression flags, and to issue an alert including the router r that meets the root cause determiner conditions; Used to block all timeout warnings from all downstream devices of router r for root cause event e_root(r); Once all downstream devices under router r have recovered, clear the alarm suppression flags of all downstream devices under router r, or clear only the alarm suppression flags of the downstream devices under router r that have recovered and remove the shielding of timeout warnings for faulty downstream devices.
[0038] The system described above, which suppresses alarm count by addressing alarm root causes, can run on computing devices such as desktop computers, laptops, PDAs, and cloud servers. The system can include, but is not limited to, processors and memory. Those skilled in the art will understand that the example described is merely an illustration of a system for suppressing alarm count by addressing alarm root causes and does not constitute a limitation on such a system. It may include more or fewer components, combinations of certain components, or different components. For example, the system may also include input / output devices, network access devices, buses, etc.
[0039] The processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. This processor is the control center of the system operating under the system that improves and suppresses the number of alarms by addressing alarm root causes, and it connects various parts of the operating system through various interfaces and lines.
[0040] The memory can be used to store the computer program and / or modules. The processor, by running or executing the computer program and / or modules stored in the memory and calling the data stored in the memory, realizes various functions of the system for increasing the number of alarms by addressing alarm root causes. The memory may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory may include random access memory (RAM), and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.
[0041] Although the invention has been described in considerable detail and particularly with regard to several of the described embodiments, it is not intended to limit itself to any of these details or embodiments or any particular embodiment, thereby effectively covering the intended scope of the invention. Furthermore, the invention has been described above with respect to embodiments foreseeable by the inventors in order to provide a useful description, and non-substantial modifications to the invention that have not yet been foreseen may still represent equivalent modifications.
[0042] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.
[0043] Although embodiments of the invention have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of the invention.
Claims
1. A method for increasing the number of suppressed alarms by addressing the root cause of alarms, characterized in that, The method includes the following steps: Step 1: Construct the real-time network topology and establish a parent-child relationship diagram between the router and downstream devices; Step 2: When a heartbeat timeout alarm occurs in the network, the percentage of disconnected devices is counted within a sliding time window with the parent router as the dimension. Step 3: When the proportion of disconnected devices exceeds the threshold, the router is determined to be the root cause, and an early warning is issued including routers that meet the conditions of the root cause determiner, and timeout alarms under the router are blocked.
2. The method for increasing the number of suppressed alarms by addressing the root cause of alarms according to claim 1, characterized in that, In step 1, the sub-steps for constructing the real-time network topology and establishing the parent-child relationship graph between the router and downstream devices are as follows: Step 1.1: Periodically construct and maintain a parent-child relationship graph G=(R∪D, E) of "router-downstream device" using one or more of the following methods: IP address, subnet mask, and default gateway. Here, R is the set of routers, D is the set of downstream devices, and E is a directed edge. The parent-child relationship graph G represents "router r downstream device d", where router r is an element in the set of routers R and downstream device d is an element in the set of downstream devices D. Step 1.2: Set a sliding time window. The sliding time window is used to maintain a time window of length Δt for each router r, and count the number of timeout alarms of the corresponding router's downstream devices within each time window.
3. The method for increasing the number of suppressed alarms by addressing the root cause of alarms according to claim 2, characterized in that, In step 2, when a heartbeat timeout alarm occurs in the network, the sub-step of calculating the percentage of disconnected devices within a sliding time window with the parent router as the dimension is as follows: Step 2.1: Check whether the heartbeat packets periodically returned by the downstream device are correct, or whether a heartbeat packet is returned within the set interval. If the returned heartbeat packet is incorrect or no heartbeat packet is returned within the timeout, generate a timeout alarm and mark the disconnected device. The timeout alarm includes device identifier, timestamp, and event type. Step 2.2: Determine the router r corresponding to the downstream device that issued the timeout alarm based on the parent-child relationship graph G; Step 2.3: In the corresponding time window W_r, update the number of disconnected devices d_offline(r) of router r. Step 2.4, calculate the percentage of disconnected devices under router r = d_offline(r) / d_total(r); where d_offline(r) is the number of disconnected devices under router r, and d_total(r) is the total number of downstream devices under router r.
4. The method for increasing the number of suppressed alarms by addressing the root cause of alarms according to claim 3, characterized in that, In step 3, when the proportion of disconnected devices exceeds a threshold, the router is determined to be the root cause, and an alert is issued including routers that meet the root cause determination criteria. The sub-step of blocking timeout alarms under the router is as follows: Step 3.1, set the root cause determiner conditions: The percentage of devices that are out of service is ≥θ; Where θ is the first threshold; Step 3.2: Traverse each router and determine whether it meets the root cause determination condition. If there is a router r that meets the root cause determination condition, trigger the root cause event e_root(r); otherwise, retain the timeout alarm of the original disconnected device. Step 3.3: Mark all downstream devices of router r that triggered the root cause event e_root(r) with alarm suppression flags, and issue an alert including router r that meets the root cause determiner conditions; Step 3.4: Disable all timeout warnings for all downstream devices of router r that triggered the root cause event e_root(r).
5. A method for increasing the number of suppressed alarms by addressing the root cause of alarms, as described in claim 4, characterized in that... In step 3, the first threshold is 0.
9.
6. A method for increasing the number of suppressed alarms by addressing the root cause of alarms, as described in claim 4, is characterized in that... Step 3 also includes: Step 3.5, after all downstream devices under router r have recovered, clear the alarm suppression flags of all downstream devices under router r.
7. A system for increasing the number of suppressed alarms by addressing the root cause of alarms, characterized in that, The system performs the steps of the method for increasing the number of suppressed alarms by addressing the root cause of alarms as described in any one of claims 1 to 6; The system includes: Topology discovery module: Used to periodically build and maintain a parent-child relationship graph G=(R∪D, E) of "router-downstream device" using one or more of the following methods: IP address, subnet mask, and default gateway. Here, R is the set of routers, D is the set of downstream devices, and E is a directed edge. The parent-child relationship graph G represents "router r downstream device d", where router r is an element in the set of routers R and downstream device d is an element in the set of downstream devices D. Sliding Time Window Management Module: Used to set up the sliding time window manager, which maintains a time window of length Δt for each router r; Alarm access module: Used to detect whether the heartbeat packets periodically returned by the downstream device are correct, or whether a heartbeat packet is returned within a set interval. If the returned heartbeat packet is incorrect or no heartbeat packet is returned within a timeout, a timeout alarm is generated. The timeout alarm includes device identifier, timestamp, and event type; find the router r corresponding to the downstream device that triggered the timeout alarm; Root cause decision module: used to calculate the percentage of out-of-connection devices. If the percentage of out-of-connection devices is greater than the first threshold, a root cause event is triggered. Suppression and escalation module: Used to mark all downstream devices under the router r that triggered the root cause event with alarm suppression flags, and to issue an alert including the router r that meets the root cause determiner conditions; Used to block all timeout warnings from all downstream devices of router r for root cause event e_root(r); Once all downstream devices connected to router r have recovered, clear the alarm suppression flags on all downstream devices connected to router r.
8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the method for increasing the number of suppressed alarms by addressing the root cause of alarms as described in any one of claims 1 to 6.
9. An electronic device, characterized in that, include: A memory on which computer programs are stored; A processor for executing the computer program in the memory to implement the steps of the method for increasing the number of suppressed alarms by means of alarm root causes as described in any one of claims 1 to 6.
Citation Information
Patent Citations
Method and device of alarm inhibition
CN102404141A
Network fault recognition method and device
CN102638375A
Distributed anti-lag-behind wireless communication devices and method
CN103714653A
Network alarm root analysis method and system, memory medium and computer equipment
CN108809734A
Cited By
Intelligent information alarm method and system based on alarm frequency
CN121462373A
Client-free private cloud full-link monitoring method and system
CN122120122A
A clientless private cloud full-link monitoring method and system
CN122120122B
