Network maintenance method and device, computer equipment and storage medium
By receiving abnormal notifications from network nodes and using notification identifiers and event information to determine abnormal maintenance strategies, the problem of untimely network maintenance is solved, and rapid response and highly reliable RDMA traffic transmission are achieved.
Patent Information
- Application Number
- CN202511199222.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-26
- Publication Date
- 2025-11-28
AI Technical Summary
Existing technologies require a long time to trigger the notification mechanism in the event of network congestion or anomalies, resulting in untimely network maintenance and affecting timely network adjustments.
By receiving anomaly notifications from network nodes and using the notification identifiers and event information, anomaly maintenance strategies can be determined to achieve timely maintenance of network nodes.
It enables timely detection and rapid response to network anomalies, ensuring highly reliable transmission of RDMA traffic.
Smart Images
Figure CN121037221A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data communication technology, and in particular to a network maintenance method, apparatus, computer equipment, and storage medium. Background Technology
[0002] The explosive growth of large-scale artificial intelligence models has also driven a rapid increase in computing traffic. Therefore, wide area networks (WANs) need to carry RDMA traffic via end-to-end SRv6 tunnels to ensure the training efficiency of large-scale artificial intelligence models.
[0003] However, during data transmission, if network congestion or network anomalies occur, it is necessary to maintain and adjust the network status in a timely manner. However, the existing network management mechanism takes a long time to trigger the notification mechanism after network congestion or network anomalies occur, resulting in untimely anomaly notifications and affecting timely network maintenance. Summary of the Invention
[0004] Therefore, it is necessary to provide a network maintenance method, apparatus, computer equipment, and storage medium that can perform timely network maintenance to address the aforementioned technical problems.
[0005] In a first aspect, this application provides a network maintenance method applied to a processing device, the method comprising:
[0006] Receive an anomaly notification sent by a network node; wherein the anomaly notification includes a notification identifier corresponding to the anomaly notification and event information corresponding to the network node;
[0007] Based on the notification identifier and the event information, determine the abnormal maintenance strategy for the network node;
[0008] The network nodes are maintained according to the aforementioned anomaly maintenance strategy.
[0009] In one embodiment, determining the abnormal maintenance strategy for the network node based on the notification identifier and the event information includes:
[0010] Determine the anomaly type sub-identifier corresponding to the notification identifier;
[0011] Based on the anomaly type sub-identifier and the event information, the anomaly event is analyzed to obtain an anomaly maintenance strategy for the network node.
[0012] In one embodiment, determining the anomaly type sub-identifier corresponding to the notification identifier includes:
[0013] If the exception notification contains an exception type sub-identifier, extract the exception type sub-identifier corresponding to the notification identifier from the exception notification.
[0014] In one embodiment, the step of performing event analysis on the abnormal event based on the abnormality type sub-identifier and the event information to obtain an abnormality maintenance strategy for the network node includes:
[0015] Based on the anomaly type sub-identifier, at least two candidate maintenance strategies corresponding to the network node are determined, as well as the applicable parameter range for each candidate maintenance strategy.
[0016] Candidate maintenance strategies that include the event information within their applicable parameter range will be used as anomaly maintenance strategies for the network nodes.
[0017] In one embodiment, when the anomaly type corresponding to the anomaly type sub-identifier is a node failure type and a node congestion type where the port buffer size is greater than a first threshold but less than a second threshold, the processing device is an Ingress PE (Inbound Provider Edge Device); when the anomaly type corresponding to the anomaly type sub-identifier is a node congestion type where the port buffer size is greater than the second threshold, the processing device is an upstream node device.
[0018] In one embodiment, the event information includes at least one of path information, quintuple information, and node buffer state information.
[0019] Secondly, this application also provides a network maintenance device configured in a processing device, the device comprising:
[0020] A receiving module is used to receive an anomaly notification sent by a network node; wherein the anomaly notification includes a notification identifier corresponding to the anomaly notification and event information corresponding to the network node;
[0021] The determination module is used to determine the abnormal maintenance strategy for the network node based on the notification identifier and the event information;
[0022] The maintenance module is used to maintain the network nodes according to the abnormal maintenance strategy.
[0023] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:
[0024] Receive an anomaly notification sent by a network node; wherein the anomaly notification includes a notification identifier corresponding to the anomaly notification and event information corresponding to the network node;
[0025] Based on the notification identifier and the event information, determine the abnormal maintenance strategy for the network node;
[0026] The network nodes are maintained according to the aforementioned anomaly maintenance strategy.
[0027] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:
[0028] Receive an anomaly notification sent by a network node; wherein the anomaly notification includes a notification identifier corresponding to the anomaly notification and event information corresponding to the network node;
[0029] Based on the notification identifier and the event information, determine the abnormal maintenance strategy for the network node;
[0030] The network nodes are maintained according to the aforementioned anomaly maintenance strategy.
[0031] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:
[0032] Receive an anomaly notification sent by a network node; wherein the anomaly notification includes a notification identifier corresponding to the anomaly notification and event information corresponding to the network node;
[0033] Based on the notification identifier and the event information, determine the abnormal maintenance strategy for the network node;
[0034] The network nodes are maintained according to the aforementioned anomaly maintenance strategy.
[0035] The aforementioned network maintenance method, apparatus, computer equipment, and storage medium, by receiving abnormal notifications sent by network nodes, determine an abnormal maintenance strategy for the network nodes based on the notification identifier and event information contained in the abnormal notification, and then perform maintenance on the network nodes according to the abnormal maintenance strategy. As can be seen from the above, during network maintenance, network nodes proactively report abnormal notifications containing notification identifiers of the corresponding abnormal events and event information, thereby achieving timely detection of network anomalies and avoiding the time delay between the occurrence of an abnormal event and the processing device receiving the abnormal notification, preventing impact on subsequent network node maintenance. Furthermore, the processing device can determine the abnormal maintenance strategy for the network nodes through the abnormal notifications, and then maintain the network nodes according to the abnormal maintenance strategy. This application achieves proactive and rapid notification in cases of congestion, failure, etc., ensuring highly reliable transmission of RDMA traffic. Attached Figure Description
[0036] Figure 1 An application environment diagram of a network maintenance method provided in this application embodiment;
[0037] Figure 2 A flowchart illustrating the first network maintenance method provided in this application embodiment;
[0038] Figure 3 A flowchart illustrating the second network maintenance method provided in this application embodiment;
[0039] Figure 4 A schematic diagram illustrating the format of the first type of exception notification provided in this application embodiment;
[0040] Figure 5 A schematic diagram illustrating the format of the second type of exception notification provided in an embodiment of this application;
[0041] Figure 6 A schematic diagram illustrating the format of the third type of exception notification provided in this application embodiment;
[0042] Figure 7 A schematic diagram illustrating the format of the fourth type of exception notification provided in this application embodiment;
[0043] Figure 8 A schematic diagram illustrating the format of the fifth type of exception notification provided in this application embodiment;
[0044] Figure 9 A schematic diagram illustrating the format of the sixth type of exception notification provided in this application embodiment;
[0045] Figure 10 A structural block diagram of a network maintenance device provided in an embodiment of this application;
[0046] Figure 11 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation
[0047] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.
[0048] The network maintenance method provided in this application embodiment can be applied to, for example, Figure 1 In the application environment shown, processing device 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104, or it can be located in the cloud or on another network server. By receiving anomaly notifications sent by network nodes, an anomaly maintenance strategy for the network nodes is determined based on the notification identifier and event information contained in the anomaly notification, and then the network nodes are maintained according to the anomaly maintenance strategy.
[0049] In one embodiment, such as Figure 2 As shown, a network maintenance method is provided, which is applied to... Figure 1 Taking the processing device 102 as an example, the following steps are included:
[0050] S201, Receive an error notification sent by a network node.
[0051] The anomaly notification includes a notification identifier corresponding to the anomaly notification, as well as event information corresponding to the network node. The notification identifier is used to identify the identifier to which the event type to which the anomaly event belongs; the time information is used to identify the specific information of the same identifier under different event types.
[0052] Among them, the anomaly notification is sent by the network node in the event of an anomaly; the anomaly notification contains the notification identifier corresponding to the anomaly notification, as well as the event information corresponding to the network node; the event information includes at least one of path information, 5-tuple information and node buffer state information.
[0053] The identifiers include rapid notification identifiers that network nodes actively send when an abnormal event occurs or when an abnormal event ends, and regular notification identifiers that network nodes passively send.
[0054] It should be noted that, in addition to the notification identifier (i.e., TYPE) and the event information corresponding to the network node (i.e., the message body), the anomaly notification may also include a checksum.
[0055] Among them, the checksum is a mechanism for verifying data integrity. It calculates the checksum of the abnormal notification and appends it to the message. The processing device detects whether the abnormal notification has been erroneous during transmission by comparing the checksum.
[0056] S202, Based on the notification identifier and event information, determine the abnormal maintenance strategy for network nodes.
[0057] It should be noted that when it is necessary to determine the abnormal maintenance strategy for network nodes, the received notification identifiers and event information can be sent to the terminal device of the node maintenance personnel in a preset format. This allows the node maintenance personnel to formulate an abnormal maintenance strategy for network nodes based on the actual situation, as well as the notification identifiers and event information, and then send the abnormal maintenance strategy to the processing device that executes the network maintenance method.
[0058] To further clarify, when it is necessary to determine the abnormal maintenance strategy for network nodes based on the notification identifier and event information, the following may also be included: determining the abnormal type sub-identifier corresponding to the notification identifier; performing event analysis on the abnormal event based on the abnormal type sub-identifier and event information to obtain the abnormal maintenance strategy for network nodes.
[0059] S203, maintain network nodes according to the abnormal maintenance strategy.
[0060] The anomaly maintenance strategy may include at least one node parameter adjustment suggestion for network nodes; the node parameter adjustment suggestion includes suggested increases and decreases for node parameters.
[0061] It should be noted that after determining the abnormal maintenance strategy, the node parameters of the network nodes can be adjusted according to at least one node parameter adjustment suggestion included in the abnormal maintenance strategy, thereby realizing the maintenance of the network nodes according to the abnormal maintenance strategy.
[0062] The aforementioned network maintenance method, by receiving anomaly notifications sent by network nodes, determines anomaly maintenance strategies for network nodes based on the notification identifiers and event information contained in the anomaly notifications, and then performs maintenance on the network nodes according to the anomaly maintenance strategies. As can be seen from the above, during network maintenance, network nodes proactively report anomaly notifications containing notification identifiers of the corresponding anomaly events and the corresponding event information. This enables timely detection of network anomalies and avoids the time delay between the occurrence of an anomaly event and the processing device receiving the anomaly notification, preventing impact on subsequent network node maintenance. Furthermore, the processing device can determine anomaly maintenance strategies for network nodes through the anomaly notifications, and then perform maintenance on the network nodes according to the anomaly maintenance strategies. This application achieves proactive and rapid notification in cases of congestion, faults, etc., ensuring highly reliable transmission of RDMA traffic.
[0063] In one embodiment, such as Figure 3 As shown, when it is necessary to determine the abnormal maintenance policy for network nodes based on the notification identifier and event information, the following may be included:
[0064] S301, Determine the sub-identifier of the exception type corresponding to the notification identifier.
[0065] Among them, the anomaly type sub-identifier is used to characterize the further anomaly type classification of the notification identifier; when the notification identifier characterizes a rapid notification, the anomaly type sub-identifier may include, but is not limited to: rapid notification for fault protection, rapid notification for fault elimination, rapid notification for congestion control, and rapid notification for congestion elimination.
[0066] It should be noted that when the exception notification contains an exception type sub-identifier, the exception type sub-identifier corresponding to the notification identifier is extracted from the exception notification.
[0067] In one embodiment of this application, the format of the exception notification may be as follows: Figure 4 As shown, TYPE represents an 8-bit announcement identifier, which is ICMPv6 information; CODE represents an exception type sub-identifier, which indicates the purpose of the ICMPv6 message; Checksum: used for message error detection; Message Body represents event information. In the case of a node failure, the event information includes path information and a 5-tuple; in the case of a node congestion, the event information includes node buffer status information. The event information format is as follows: Figure 5 As shown, the format of the quintuple information is as follows: Figure 6 As shown, the path information and node buffer status information are formatted as follows: Figure 7 As shown.
[0068] S302, based on the anomaly type sub-identifier and event information, perform event analysis on the anomaly event to obtain the anomaly maintenance strategy for the network node.
[0069] It should be noted that when it is necessary to perform event analysis on abnormal events based on the abnormality type sub-identifier and event information to obtain an abnormal maintenance strategy for network nodes, the following may be included: based on the abnormality type sub-identifier, determine at least two candidate maintenance strategies corresponding to the network node, as well as the applicable parameter range for each candidate maintenance strategy; and take the candidate maintenance strategy whose applicable parameter range includes event information as the abnormal maintenance strategy for the network node.
[0070] To further clarify, when the anomaly type corresponding to the anomaly type sub-identifier is a node failure type, or a node congestion type where the port buffer size is greater than the first threshold but less than the second threshold, the processing device is the ingress provider edge device (Ingress PE); when the anomaly type corresponding to the anomaly type sub-identifier is a node congestion type where the port buffer size is greater than the second threshold, the processing device is the upstream node device (upstream node).
[0071] In one embodiment of this application, under a fault scenario, such as Figure 8 As shown, when a link failure occurs between R1 and R2, R1 and R2 send an anomaly notification to the ingress PE. Upon receiving the notification, the ingress PE determines an anomaly maintenance strategy; subsequently, it adjusts the service path according to the strategy to avoid the fault point. When the fault is resolved, R1 and R2 inform the ingress PE that the fault has been resolved, and path traffic is restored.
[0072] In one embodiment of this application, under congestion scenarios, such as Figure 9 As shown, when congestion occurs between 2-EgressPEs, if R2's port buffer size is greater than the first threshold but less than the second threshold, an anomaly notification is sent to the Ingress PE; if R2's port buffer size is greater than the second threshold, an anomaly notification is sent to the upstream node. Upon receiving the anomaly notification, the Ingress PE determines an anomaly maintenance strategy and re-runs the Load Balancing (LB) algorithm according to the strategy to reduce traffic on the corresponding path. Upon receiving the anomaly notification, the upstream node determines an anomaly maintenance strategy and stops sending congested traffic to R2 according to the strategy. When the congestion subsides, R2 sequentially notifies the Ingress PE and upstream node of congestion recovery, restoring path traffic.
[0073] The aforementioned network maintenance method, by determining the anomaly type sub-identifier corresponding to the notification identifier, enables event analysis of anomaly events based on the anomaly type sub-identifier and event information, thereby obtaining anomaly maintenance strategies for network nodes. This application achieves proactive and rapid notification under conditions of congestion, failure, etc., ensuring highly reliable transmission of RDMA traffic.
[0074] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.
[0075] Based on the same inventive concept, this application also provides a network maintenance apparatus for implementing the network maintenance method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more network maintenance apparatus embodiments provided below can be found in the limitations of the network maintenance method described above, and will not be repeated here.
[0076] In one embodiment, such as Figure 10 As shown, a network maintenance device is provided, comprising: a receiving module 10, a determining module 20, and a maintenance module 30, wherein:
[0077] The receiving module 10 is used to receive an anomaly notification sent by a network node; wherein the anomaly notification is sent by the network node in the event of an anomaly; the anomaly notification contains a notification identifier corresponding to the anomaly notification and event information corresponding to the network node.
[0078] The determination module 20 is used to determine the abnormal maintenance strategy for network nodes based on the notification identifier and event information.
[0079] Maintenance module 30 is used to maintain network nodes according to the abnormal maintenance strategy.
[0080] In one embodiment, an anomaly type sub-identifier corresponding to the notification identifier is determined;
[0081] Based on the anomaly type sub-identifier and event information, anomaly events are analyzed to obtain anomaly maintenance strategies for network nodes.
[0082] In one embodiment, if the exception notification contains an exception type sub-identifier, the exception type sub-identifier corresponding to the notification identifier is extracted from the exception notification.
[0083] In one embodiment, at least two candidate maintenance strategies corresponding to a network node and the applicable parameter range for each candidate maintenance strategy are determined based on the anomaly type sub-identifier.
[0084] Candidate maintenance strategies that include event information within their applicable parameter range will be used as anomaly maintenance strategies for network nodes.
[0085] In one embodiment, when the anomaly type corresponding to the anomaly type sub-identifier is a node failure type and a node congestion type where the port buffer size is greater than a first threshold but less than a second threshold, the processing device is an ingress provider edge device (Ingress PE); when the anomaly type corresponding to the anomaly type sub-identifier is a node congestion type where the port buffer size is greater than the second threshold, the processing device is an upstream node device (upstream node).
[0086] In one embodiment, the event information includes at least one of path information, quintuple information, and node buffer state information.
[0087] The aforementioned network maintenance device receives anomaly notifications sent by network nodes, determines anomaly maintenance strategies for network nodes based on the notification identifiers and event information contained in the anomaly notifications, and then performs maintenance on the network nodes according to the anomaly maintenance strategies. As can be seen from the above, during network maintenance, network nodes proactively report anomaly notifications containing notification identifiers of the corresponding anomaly events and the corresponding event information. This enables timely detection of network anomalies and avoids the time delay between the occurrence of an anomaly event and the processing device receiving the anomaly notification, preventing impact on subsequent network node maintenance. Furthermore, the processing device can determine anomaly maintenance strategies for network nodes through the anomaly notifications, and then perform maintenance on the network nodes according to the anomaly maintenance strategies. This application achieves proactive and rapid notification in cases of congestion, faults, etc., ensuring highly reliable transmission of RDMA traffic.
[0088] Each module in the aforementioned network maintenance device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.
[0089] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 11 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a network maintenance method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.
[0090] Those skilled in the art will understand that Figure 11 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0091] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:
[0092] Receive anomaly notifications sent by network nodes; where the anomaly notification is sent by the network node in the event of an anomaly; the anomaly notification contains the notification identifier corresponding to the anomaly notification, as well as the event information corresponding to the network node;
[0093] Based on the notification identifier and event information, determine the abnormal maintenance strategy for network nodes;
[0094] Network nodes are maintained according to the anomaly maintenance strategy.
[0095] In one embodiment, the processor, when executing a computer program, also performs the following steps:
[0096] Determine the anomaly type sub-identifier corresponding to the notification identifier;
[0097] Based on the anomaly type sub-identifier and event information, anomaly events are analyzed to obtain anomaly maintenance strategies for network nodes.
[0098] In one embodiment, the processor, when executing a computer program, also performs the following steps:
[0099] If the exception notification contains an exception type sub-identifier, extract the exception type sub-identifier corresponding to the notification identifier from the exception notification.
[0100] In one embodiment, the processor, when executing a computer program, also performs the following steps:
[0101] Based on the anomaly type sub-identifier, determine at least two candidate maintenance strategies for the network node, as well as the applicable parameter range for each candidate maintenance strategy;
[0102] Candidate maintenance strategies that include event information within their applicable parameter range will be used as anomaly maintenance strategies for network nodes.
[0103] In one embodiment, the processor, when executing a computer program, also performs the following steps:
[0104] When the anomaly type corresponding to the anomaly type sub-identifier is a node failure type, or a node congestion type where the port buffer size is greater than the first threshold but less than the second threshold, the processing device is the ingress provider edge device (IngressPE); when the anomaly type corresponding to the anomaly type sub-identifier is a node congestion type where the port buffer size is greater than the second threshold, the processing device is the upstream node device (upstream node).
[0105] In one embodiment, the processor, when executing a computer program, also performs the following steps:
[0106] The event information includes at least one of the following: path information, quintuple information, and node buffer state information.
[0107] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:
[0108] Receive anomaly notifications sent by network nodes; where the anomaly notification is sent by the network node in the event of an anomaly; the anomaly notification contains the notification identifier corresponding to the anomaly notification, as well as the event information corresponding to the network node;
[0109] Based on the notification identifier and event information, determine the abnormal maintenance strategy for network nodes;
[0110] Network nodes are maintained according to the anomaly maintenance strategy.
[0111] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0112] Determine the anomaly type sub-identifier corresponding to the notification identifier;
[0113] Based on the anomaly type sub-identifier and event information, anomaly events are analyzed to obtain anomaly maintenance strategies for network nodes.
[0114] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0115] If the exception notification contains an exception type sub-identifier, extract the exception type sub-identifier corresponding to the notification identifier from the exception notification.
[0116] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0117] Based on the anomaly type sub-identifier, determine at least two candidate maintenance strategies for the network node, as well as the applicable parameter range for each candidate maintenance strategy;
[0118] Candidate maintenance strategies that include event information within their applicable parameter range will be used as anomaly maintenance strategies for network nodes.
[0119] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0120] When the anomaly type corresponding to the anomaly type sub-identifier is a node failure type, or a node congestion type where the port buffer size is greater than the first threshold but less than the second threshold, the processing device is the ingress provider edge device (IngressPE); when the anomaly type corresponding to the anomaly type sub-identifier is a node congestion type where the port buffer size is greater than the second threshold, the processing device is the upstream node device (upstream node).
[0121] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0122] The event information includes at least one of the following: path information, quintuple information, and node buffer state information.
[0123] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:
[0124] Receive anomaly notifications sent by network nodes; where the anomaly notification is sent by the network node in the event of an anomaly; the anomaly notification contains the notification identifier corresponding to the anomaly notification, as well as the event information corresponding to the network node;
[0125] Based on the notification identifier and event information, determine the abnormal maintenance strategy for network nodes;
[0126] Network nodes are maintained according to the anomaly maintenance strategy.
[0127] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0128] Determine the anomaly type sub-identifier corresponding to the notification identifier;
[0129] Based on the anomaly type sub-identifier and event information, anomaly events are analyzed to obtain anomaly maintenance strategies for network nodes.
[0130] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0131] If the exception notification contains an exception type sub-identifier, extract the exception type sub-identifier corresponding to the notification identifier from the exception notification.
[0132] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0133] Based on the anomaly type sub-identifier, determine at least two candidate maintenance strategies for the network node, as well as the applicable parameter range for each candidate maintenance strategy;
[0134] Candidate maintenance strategies that include event information within their applicable parameter range will be used as anomaly maintenance strategies for network nodes.
[0135] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0136] When the anomaly type corresponding to the anomaly type sub-identifier is a node failure type, or a node congestion type where the port buffer size is greater than the first threshold but less than the second threshold, the processing device is the ingress provider edge device (IngressPE); when the anomaly type corresponding to the anomaly type sub-identifier is a node congestion type where the port buffer size is greater than the second threshold, the processing device is the upstream node device (upstream node).
[0137] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0138] The event information includes at least one of the following: path information, quintuple information, and node buffer state information.
[0139] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.
[0140] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.
[0141] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0142] The above embodiments are merely illustrative of several implementation methods of this application, and their descriptions are relatively specific and detailed. However, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.
Claims
1. A network maintenance method, characterized in that, Applied to a processing device, the method includes: Receive an anomaly notification sent by a network node; wherein the anomaly notification is sent by the network node in the event of an anomaly; the anomaly notification includes a notification identifier corresponding to the anomaly notification and event information corresponding to the network node; Based on the notification identifier and the event information, determine the abnormal maintenance strategy for the network node; The network nodes are maintained according to the aforementioned anomaly maintenance strategy.
2. The method according to claim 1, characterized in that, The step of determining the abnormal maintenance strategy for the network node based on the notification identifier and the event information includes: Determine the anomaly type sub-identifier corresponding to the notification identifier; Based on the anomaly type sub-identifier and the event information, the anomaly event is analyzed to obtain an anomaly maintenance strategy for the network node.
3. The method according to claim 2, characterized in that, The step of determining the anomaly type sub-identifier corresponding to the notification identifier includes: If the exception notification contains an exception type sub-identifier, extract the exception type sub-identifier corresponding to the notification identifier from the exception notification.
4. The method according to claim 2, characterized in that, The step of performing event analysis on the abnormal event based on the abnormal type sub-identifier and the event information to obtain an abnormal maintenance strategy for the network node includes: Based on the anomaly type sub-identifier, at least two candidate maintenance strategies corresponding to the network node are determined, as well as the applicable parameter range for each candidate maintenance strategy. Candidate maintenance strategies that include the event information within their applicable parameter range will be used as anomaly maintenance strategies for the network nodes.
5. The method according to claim 2, characterized in that, When the anomaly type corresponding to the anomaly type sub-identifier is a node failure type, or a node congestion type where the port buffer size is greater than the first threshold but less than the second threshold, the processing device is an Ingress PE (Incoming Provider Edge Device); when the anomaly type corresponding to the anomaly type sub-identifier is a node congestion type where the port buffer size is greater than the second threshold, the processing device is an upstream node.
6. The method according to claim 2, characterized in that, The event information includes at least one of path information, quintuple information, and node buffer state information.
7. A network maintenance device, characterized in that, Configured in a processing device, the apparatus includes: A receiving module is used to receive an anomaly notification sent by a network node; wherein the anomaly notification is sent by the network node in the event of an anomaly; the anomaly notification includes a notification identifier corresponding to the anomaly notification and event information corresponding to the network node; The determination module is used to determine the abnormal maintenance strategy for the network node based on the notification identifier and the event information; The maintenance module is used to maintain the network nodes according to the abnormal maintenance strategy.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.
10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.