Alarm synchronization method, device, medium and product

Abstract

Provided in the present disclosure is an alarm synchronization method. The method comprises: acquiring alarm information sent by a network element device; acquiring an alarm synchronization table from a preset storage space; and on the basis of the alarm synchronization table and the alarm information, synchronizing the alarm information, wherein the alarm synchronization table is stored in the preset storage space by the network element device, and comprises information used for indicating alarm synchronization. The present disclosure further provides an electronic device, a computer-readable medium and a computer program product.

Description

Alarm synchronization methods, equipment, media and products

[0001] Cross-references to related applications

[0002] This patent application claims priority to Chinese Patent Application No. 202411527395.0, filed on October 29, 2024, with the State Intellectual Property Office of China, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to the field of communication technology, and in particular to an alarm synchronization method, electronic device, computer-readable medium, and computer program product. Background Technology

[0004] Because the Simple Network Management Protocol (SNMP) is based on the User Datagram Protocol (UDP), and UDP is a connectionless communication protocol, it does not guarantee the reliability of data transmission. Therefore, in a communication management system based on SNMP, information loss may occur. Summary of the Invention

[0005] This disclosure provides an alarm synchronization method, an electronic device, a computer-readable medium, and a computer program product.

[0006] In a first aspect, embodiments of this disclosure provide an alarm synchronization method, the method comprising: acquiring alarm information sent by a network element device; acquiring an alarm synchronization table from a preset storage space; and synchronizing the alarm information according to the alarm synchronization table and the alarm information, wherein the alarm synchronization table is stored by the network element device in the preset storage space and includes information for indicating alarm synchronization.

[0007] Secondly, embodiments of this disclosure provide an alarm synchronization method, the method comprising: generating alarm information; storing an alarm synchronization table including information for indicating alarm synchronization into a preset storage space; and reporting the alarm information to a network management device.

[0008] Thirdly, embodiments of this disclosure provide an electronic device, including: one or more processors; and a memory storing one or more programs thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any of the alarm synchronization methods in the embodiments of this disclosure.

[0009] Fourthly, embodiments of this disclosure provide a readable storage medium storing a computer program that, when executed by a processor, implements any of the alarm synchronization methods described in the embodiments of this disclosure.

[0010] Fifthly, embodiments of this disclosure provide a computer program product, which includes a computer program that, when executed by a processor, implements any of the alarm synchronization methods in embodiments of this disclosure. Attached Figure Description

[0011] In the accompanying drawings of the embodiments disclosed herein:

[0012] Figure 1 is a flowchart illustrating an alarm synchronization method provided in an embodiment of this disclosure;

[0013] Figure 2 is a flowchart illustrating an alarm synchronization method provided in an embodiment of this disclosure;

[0014] Figure 3 is a block diagram of an alarm synchronization system provided in an embodiment of this disclosure;

[0015] Figure 4 is a schematic diagram of the working method of an alarm synchronization system provided in an embodiment of this disclosure;

[0016] Figure 5 is a schematic diagram of the working method of an alarm synchronization system provided in an embodiment of this disclosure;

[0017] Figure 6 is a block diagram of a network management device provided in an embodiment of this disclosure;

[0018] Figure 7 is a block diagram of a network element device provided in an embodiment of this disclosure;

[0019] Figure 8 is a block diagram of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0020] To enable those skilled in the art to better understand the technical solutions of this disclosure, the embodiments of this disclosure will be described in detail below with reference to the accompanying drawings.

[0021] The present disclosure will be described more fully below with reference to the accompanying drawings; however, the embodiments shown may be embodied in different forms, and the present disclosure should not be construed as limited to the embodiments set forth below. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will enable those skilled in the art to fully understand the scope of the disclosure.

[0022] The accompanying drawings of the embodiments disclosed herein are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the detailed embodiments to explain this disclosure and do not constitute a limitation thereof. The above and other features and advantages will become more apparent to those skilled in the art from the description of the detailed embodiments with reference to the accompanying drawings.

[0023] Where there is no conflict, the various embodiments of this disclosure and the features thereof in the embodiments may be combined with each other.

[0024] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the disclosure. The term "and / or" as used in this disclosure includes any and all combinations of one or more of the associated enumerated entries. The singular forms "a" and "the" as used in this disclosure are also intended to include the plural forms, unless the context clearly indicates otherwise. The terms "comprising," "made of," etc., as used in this disclosure specify the presence of the stated feature, integral, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof.

[0025] Unless otherwise specified, all terms used in this disclosure (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this disclosure, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined in this disclosure.

[0026] In a communication management system based on SNMP, the Network Management Station (NMS) is the network management center of the entire system, responsible for managing multiple network elements. Each network element interacts with the NMS through its internal Management Agent process to receive management commands from the NMS and report important events generated by the network element to the NMS.

[0027] In some related technologies, agent processes running on network elements interact with the Network Management System (NMS) via the SNMP protocol. The agent process sends alarm information to the NMS, enabling the NMS to detect operational anomalies in the network elements. This allows network maintenance personnel to make timely adjustments to the network elements based on the information displayed on the NMS, ensuring their normal operation.

[0028] However, since NMS does not verify the integrity of the alarm information it receives, and the alarm information is an unacknowledged access message sent by the agent process on the network element device using the User Datagram Protocol (UDP), NMS cannot verify the integrity of the alarm information when it receives it. This may cause it to miss important alarm information generated by the network element device, thus reducing the effectiveness of monitoring the network element device.

[0029] To address the aforementioned issues, this disclosure provides an alarm synchronization method, an electronic device, a computer-readable medium, and a computer program product.

[0030] Figure 1 is a flowchart illustrating an alarm synchronization method provided in an embodiment of this disclosure. This alarm synchronization method is applied to network management devices, such as servers and base stations. As shown in Figure 1, the alarm synchronization method includes, but is not limited to, the following steps.

[0031] Step S101: Obtain alarm information sent by network element devices.

[0032] Alarm information indicates that an anomaly has occurred in a network element device. For example, an alarm message may indicate that an interface of the network element device is faulty, or that the communication link between the network element device and other devices has failed.

[0033] By obtaining alarm information sent by network element devices, it is possible to identify the specific anomalies existing in the network element devices, so as to promptly repair and manage the network element devices and ensure their normal operation.

[0034] Step S102: Obtain the alarm synchronization table from the preset storage space.

[0035] The alarm synchronization table is stored in a preset storage space by the network element device and includes information used to indicate alarm synchronization.

[0036] The pre-defined storage space stores multiple data tables (e.g., a data table storing configuration information, an alarm synchronization table storing information including instructions for alarm synchronization, etc.). Each data table is implemented using a different data structure, and each table records multiple columns of different fields, with each column corresponding to a physical meaning.

[0037] In some embodiments, the preset storage space is implemented using a Management Information Base (MIB). The MIB includes an alarm synchronization table, which stores information that indicates whether the network management device has obtained all the alarm information generated by the network element device. This allows the network management device to match the received alarm information with the alarm synchronization table and synchronize the alarm information.

[0038] Step S103: Synchronize alarm information according to the alarm synchronization table and alarm information.

[0039] The network management device compares the received alarm information with the information stored in the alarm synchronization table to determine whether all alarm information stored in the alarm synchronization table has been received. When the network management device confirms that the received alarm information is all the alarm information stored in the alarm synchronization table based on the comparison result, it can be determined that the network management device has achieved alarm information synchronization. When the network management device confirms that the received alarm information is not all the alarm information stored in the alarm synchronization table based on the comparison result, and some alarm information in the alarm synchronization table has not been obtained by the network management device, it can be determined that the network management device has not achieved alarm information synchronization. In this case, the network management device needs to further obtain the lost alarm information from the network element device.

[0040] In the alarm synchronization method of this embodiment, when a network element sends alarm information, it also stores an alarm synchronization table, which includes information for indicating alarm synchronization, in a preset storage space. Thus, after receiving alarm information from a network element, the network management device can confirm whether the received alarm information is all the alarm information generated by the network element based on the alarm synchronization table in the preset storage space. This facilitates alarm information synchronization by the network management device, reduces the risk of alarm information loss, ensures that the network management device can obtain all alarm information from the network element, and improves the effectiveness of monitoring the network element.

[0041] In some exemplary embodiments, obtaining alarm information sent by the network element device in step S101 includes: parsing the data packet in response to receiving the data packet sent by the network element device; and separating the alarm information from the data packet in response to obtaining the alarm identifier through parsing.

[0042] An alarm identifier indicates that the information carried in a data packet is an alarm message. For example, if the alarm identifier is set to A, then when the preset identifier A is parsed from a data packet, it can be determined that the information carried in the data packet is an alarm message.

[0043] When a network management device receives a data packet from a network element, it performs initial parsing of the data packet to obtain information corresponding to a preset identifier in the data packet, so as to clarify the type of information carried by the data packet. When the preset identifier is parsed as an alarm identifier, it can be determined that the information carried by the data packet is alarm information, so that the network management device can manage all alarm information in a unified manner and improve the processing speed of alarm information.

[0044] Furthermore, after determining that the information carried in the data packet is alarm information, the network management device parses the data packet again to obtain the alarm information. This alarm information indicates that there is an anomaly in the network element device, so that the network management device can clearly identify the anomaly in the network element device, and then repair the network element device according to the anomaly, so that the network element device can resume normal operation.

[0045] In some embodiments, the network management device can count the number of alarm messages it receives based on alarm identifiers to clarify the number of alarm messages it receives, thereby facilitating unified management of alarm messages.

[0046] In some exemplary embodiments, the information used to indicate alarm synchronization includes: a preset number of alarms and a preset reporting identifier, wherein the preset reporting identifier represents the alarm type of the alarm information.

[0047] Step S103, which synchronizes alarm information based on the alarm synchronization table and alarm information, includes: comparing the first number of acquired alarm information with a preset alarm number to obtain a number comparison result; comparing the pending confirmation reporting identifier in the acquired alarm information with a preset reporting identifier to obtain an identifier comparison result; if both the number comparison result and the identifier comparison result are the same, alarm synchronization is determined to have been achieved; if at least one of the number comparison result and the identifier comparison result is different, alarm synchronization is determined to have not been achieved. At this point, the network management device needs to further retrieve the lost alarm information from the network element device.

[0048] The preset reporting identifier can be a predefined alarm type for different alarm information. For example, the preset reporting identifier for the link down alarm is 1.3.6.1.6.3.1.1.5.3, and the preset reporting identifier for the OSPFv3 neighbor state change alarm is 1.3.6.1.2.1.191.0.2.

[0049] OSPFv3 is an Open Shortest Path First (OSPF) routing protocol that runs on Internet Protocol Version 6 (IPv6).

[0050] When the network management device receives an OSPFv3NbrStateChange alarm message from a network element, it can know that the state of the OSPFv3 neighbor of the network element may have changed due to a change in the state of the interface where the neighbor is located, or the alarm may have been caused by a change in the content of the received initial message.

[0051] The above examples of preset reporting identifiers are merely illustrative. Different preset reporting identifiers can be set for different alarm information according to actual needs, so that the device can distinguish between different types of alarm information. This disclosure does not impose any limitations on this, and will not elaborate further here.

[0052] The data comparison results include whether the first quantity is the same as the preset alarm quantity, or whether the first quantity is less than the preset alarm quantity. When the first quantity is the same as the preset alarm quantity, it indicates that the number of alarm messages received by the network management device is the same as the number of alarm messages generated by the network element device; when the first quantity is less than the preset alarm quantity, it indicates that the alarm messages received by the network management device are not all the alarm messages generated by the network element device, suggesting that alarm messages are lost during the alarm reporting process on the network element device.

[0053] The identification comparison results include whether the identification to be confirmed and reported is the same as the preset reporting identification, or whether the identification to be confirmed and reported is different from the preset reporting identification. When the identification to be confirmed and reported is the same as the preset reporting identification, it indicates that the alarm information received by the network management device is an alarm information generated by the network element device; when the identification to be confirmed and reported is different from the preset reporting identification, it indicates that the alarm information received by the network management device is not an alarm information generated by the network element device (for example, the alarm information received by the network management device is other interference information, etc.).

[0054] By matching the quantity and type of alarm information received by the network management device with the preset alarm quantity and preset reporting identifier in the alarm synchronization table, it can be determined whether the alarm information received by the network management device is all the alarm information generated by the network element device. If both the quantity comparison result and the identifier comparison result are the same, it is determined that the network management device has received all the alarm information generated by the network element device, i.e., alarm synchronization has been achieved. Otherwise, if at least one of the quantity comparison result and the identifier comparison result is different, it indicates that the alarm information received by the network management device is not all the alarm information generated by the network element device, i.e., alarm synchronization has not been achieved. The network management device needs to further obtain the required alarm information from the network element device to comprehensively understand the possible anomalies of the network element device, achieve accurate management of the network element device, and thus ensure the normal operation of each network element device.

[0055] In some exemplary embodiments, after synchronizing the alarm information according to the alarm synchronization table and the alarm information, the method further includes: querying the alarm synchronization table to obtain data structure information; and parsing the alarm information according to the data structure information to obtain the alarm parameter values ​​in the alarm information.

[0056] The alarm synchronization table also includes data structure information. After confirming that alarm synchronization has been achieved, the network management device can also parse the alarm information according to the data structure information in the alarm synchronization table to obtain the alarm parameter values ​​and thus know the specific content of the alarm information.

[0057] For example, the alarm synchronization table can be searched using the pending confirmation reporting identifier as an index to obtain the data structure information corresponding to the pending confirmation reporting identifier stored in the alarm synchronization table, thereby understanding the specific data structure of the alarm information corresponding to the pending confirmation reporting identifier. Then, based on the data structure information corresponding to the pending confirmation reporting identifier, the obtained alarm information is parsed to extract the alarm parameter values ​​of each alarm parameter corresponding to the data structure information in the alarm information.

[0058] For example, if the data structure information corresponding to the reporting identifier to be confirmed includes two alarm parameters, with the first alarm parameter occupying 16 bits of data and the second alarm parameter occupying 8 bits of data, then the first 16 bits in the alarm information can be used to represent the value of the first alarm parameter, and the 17th to 25th bits in sequence can represent the value of the second alarm parameter. In this way, the values ​​of each alarm parameter in the alarm information corresponding to the reporting identifier to be confirmed can be accurately obtained to determine the content of the alarm information.

[0059] By parsing the alarm information based on the data structure information stored in the alarm synchronization table, the alarm information can be parsed quickly without having to look up the data structure information corresponding to the pending confirmation reporting identifier stored in the cache, thereby speeding up the processing of alarm information.

[0060] In some exemplary embodiments, after determining that alarm synchronization has not been achieved, the alarm synchronization method further includes: requesting the lost alarm information from the network element device according to the alarm synchronization table.

[0061] The second number of lost alarm messages is the difference between the preset alarm number and the first number. For example, if the preset alarm number is set to 5, and the first number of alarm messages actually received by the network management device is 3, then the number of lost alarm messages is 5-3=2. That is, there are 2 alarm messages that were generated by the network element device but were not received by the network management device, which means that the alarm messages received by the network management device are incomplete.

[0062] Based on the alarm synchronization table, the number of lost alarm messages is determined, i.e., the difference between the preset alarm number and the first number. Then, based on the alarm synchronization table, the preset reporting flag for the unreceived lost alarm messages is determined, and then the network element device is requested to retrieve the lost alarm messages. This is to facilitate finding the lost alarm messages reported by the network element device and to make the network element device resend the lost alarm messages. This allows the network management device to obtain all the alarm messages generated by the network element device, enabling the network management device to have a comprehensive understanding of the possible anomalies of the network element device and to achieve accurate management of the network element device.

[0063] In some exemplary embodiments, requesting lost alarm information from a network element device according to an alarm synchronization table includes: determining a preset reporting identifier in the alarm synchronization table that is different from the reporting identifier to be confirmed as a target reporting identifier; generating an alarm request message according to the target reporting identifier and sending the alarm request message to the network element device; and obtaining the alarm information corresponding to the target reporting identifier in response to the alarm request response sent by the network element device.

[0064] The network management device compares the received pending-acknowledgment reporting identifiers sequentially with the preset reporting identifiers stored in the alarm synchronization table. It can obtain preset reporting identifiers that are different from the pending-acknowledgment reporting identifiers and uses them as target reporting identifiers. That is, the target reporting identifier represents alarm information that has been generated by the network element device but has not been received by the network management device.

[0065] An alarm request message including the target reporting identifier is sent to the network element device, so that the network element device can resend the alarm information with the target reporting identifier as the alarm type to the network management device. This allows the network management device to obtain the alarm information corresponding to the target reporting identifier, thus completing the alarm information lost by the network management device. Based on the complete alarm information it obtains, the network management device can determine the working status of the network element device, perform timely maintenance and management of the network element device, and enable the network element device to quickly return to normal operation.

[0066] Figure 2 is a flowchart illustrating an alarm synchronization method provided in an embodiment of this disclosure. This alarm synchronization method is applied to network element devices, such as terminals. As shown in Figure 2, the alarm synchronization method includes, but is not limited to, the following steps.

[0067] Step S201: Generate alarm information.

[0068] Alarm information indicates abnormalities in network elements. For example, an alarm may indicate an interface malfunction in a network element, or a failure in the communication link between the network element and other devices.

[0069] Step S202: Store the alarm synchronization table, which includes information for indicating alarm synchronization, into a preset storage space.

[0070] After generating alarm information, the network element device will store the relevant information of the generated alarm information in the alarm synchronization table, which includes information used to indicate alarm synchronization.

[0071] In some embodiments, the alarm synchronization table stores at least one of the following information: the number of alarm messages generated by the network element device, the alarm type of the alarm message, and the data structure information corresponding to the alarm message.

[0072] For example, if a network element generates 3 alarm messages within a preset time period, then the number of alarm messages stored in the alarm synchronization table will be 3. Correspondingly, the alarm type of each alarm message (such as interface abnormal alarm, communication link alarm, configuration parameter abnormal alarm, etc.) and the data structure information corresponding to each alarm message will be stored in the alarm synchronization table, so that the network management device can obtain the alarm synchronization table through the preset storage space and then synchronize the alarm messages according to the alarm synchronization table.

[0073] By storing the information used to indicate alarm synchronization in a table format in a preset storage space, the network management device can obtain the alarm synchronization table in a timely manner through the preset storage space, and then determine the integrity of the alarm information it receives based on the alarm synchronization table.

[0074] Step S203: Report the data packet carrying alarm information to the network management device.

[0075] Data packets are packets that include alarm information. Network elements send data to network management devices in the form of data packets. The format of these data packets can be predefined according to actual needs.

[0076] For example, the data message includes an alarm identifier, and / or, information indicating alarm synchronization includes a preset reporting identifier.

[0077] An alarm identifier indicates that the information in a data packet sent to the network management device is an alarm message. This allows the network management device to identify the information in the data packet as an alarm message when it receives a data packet containing both an alarm identifier and alarm message, and to manage the alarm message in a unified manner, thereby improving the efficiency of the network management device in managing alarm messages.

[0078] A preset reporting identifier indicates the alarm type of the alarm information. When a network management device receives a data packet containing an alarm identifier, a preset reporting identifier, and alarm information, it can first identify the information carried in the data packet as alarm information through the alarm identifier. Then, the alarm information is separated from the data packet and further parsed to obtain the preset reporting identifier that can represent the alarm type of the alarm information. This clarifies the alarm type of the alarm information, facilitating the network management device to classify and manage the alarm information according to the alarm type, thereby improving the efficiency of the network management device in managing alarm information.

[0079] When the data packets received by the network management device include preset reporting identifiers and alarm information, the network management device can determine the alarm type based on the preset reporting identifiers, thereby speeding up the processing of alarm information.

[0080] By reporting data packets carrying alarm information to the network management device, the network management device can obtain the alarm information generated by the network element, so that the network management device can manage or repair the network element device in a timely manner based on the alarm information, reducing the risk that the network element device cannot work normally due to abnormality (or failure).

[0081] In this embodiment, when a network element generates an alarm, it not only needs to report a data packet carrying the alarm information to the network management device so that the network management device can obtain the alarm information, but also needs to store an alarm synchronization table, including information for indicating alarm synchronization, in a preset storage space. This allows the network management device to retrieve the alarm synchronization table from the preset storage space and then confirm the received alarm information according to the alarm synchronization table to determine whether the received alarm information is all the alarm information generated by the network element. This achieves alarm information synchronization, reduces the risk of alarm information loss, and enables the network management device to more accurately confirm the status of the network element through the synchronized alarm information, thereby managing and maintaining the network element and ensuring its normal operation.

[0082] In some exemplary embodiments, the method further includes: obtaining a target reporting identifier in response to an alarm request message sent by the network management device; generating an alarm request response based on the target reporting identifier and the alarm information corresponding to the target reporting identifier; and sending the alarm request response to the network management device.

[0083] The alarm request message includes a target reporting identifier, which identifies the alarm information that the network management device expects to obtain. This alarm information is alarm information that the network management device has not received, and may be lost in the process of the network element device reporting the alarm information it generates to the network management device.

[0084] After obtaining the target reporting identifier, the network element device finds the alarm information corresponding to the target reporting identifier. Then, it encapsulates the target reporting identifier and its corresponding alarm information into an alarm request response and sends the alarm request response to the network management device so that the network management device can obtain its lost alarm information and thus realize the synchronization of alarm information.

[0085] In other words, by sending the alarm information corresponding to the target reporting identifier to the network management device in the above manner, the network management device can obtain all the alarm information generated by the network element device. This allows the network management device to analyze the status of the network element device based on the synchronized alarm information, and to maintain and manage the network element device based on the analysis results. This enables the network element device to work better and reduces the risk of network element device downtime.

[0086] Figure 3 is a block diagram of an alarm synchronization system provided in an embodiment of this disclosure. As shown in Figure 3, the alarm synchronization system includes, but is not limited to, the following devices: network management device 301, network element device 302, and management information database 303.

[0087] Network management device 301 is used to obtain alarm information sent by network element devices; obtain alarm synchronization table from management information database 303; and synchronize alarm information according to alarm synchronization table and alarm information.

[0088] The alarm synchronization table is stored in the management information database 303 by the network element device and includes information for indicating alarm synchronization.

[0089] Network element device 302 is used to generate alarm information; store an alarm synchronization table, which includes information for indicating alarm synchronization, in management information database 303; and report data packets carrying alarm information to network management device.

[0090] The Management Information Database 303 can be implemented using the MIB library.

[0091] The alarm synchronization table stored in the MIB library includes: the preset number of alarms, the preset reporting identifier, and the data structure information corresponding to the preset reporting identifier.

[0092] For example, the preset reporting identifier is represented by an object identifier (OID). The data structure information corresponding to the preset reporting identifier can be encoded using preset encoding rules (such as Abstract Syntax Notation One (ASN.1) encoding rules) to obtain the numerical value.

[0093] For example, the following data structure can be used to represent the structure of the data stored in the alarm synchronization table:

[0094] 1) alarmSyncTable OBJECT-TYPE

[0095] 2) alarmSyncEntry OBJECT-TYPE

[0096] 3)AlarmSyncEntry::=

[0097] The data structure of AlarmSyncIndex is as follows:

[0098] Based on the above data structure, the network management device 301 constructs a query message to query the alarm synchronization table stored in the MIB library; then, based on the queried data structure (i.e., AlarmSyncVarBindList), it parses the corresponding alarm information to obtain the values ​​of the alarm parameters in the alarm information.

[0099] In some embodiments, different data structures are set in the alarm synchronization table stored in the MIB library for different alarm information.

[0100] For example, for a linkDown alarm message, the format of its corresponding trap message can be set as follows:

[0101] The above structure allows setting the Trap OID for link fault alarm information to 1.3.6.1.6.3.1.1.5.3; alarm parameters include ifIndex, ifAdminStatus, and ifOperStatus.

[0102] For example, for the ospfv3NbrStateChange alarm message, the format of its corresponding trap message can be set as follows:

[0103] For example, the above structure can be used to set the Trap OID of the ospfIfStateChange alarm information to 1.3.6.1.2.1.191.0.2, and its corresponding alarm parameters include ospfv3RouterId and ospfv3NbrState.

[0104] Figure 4 is a schematic diagram of the operation method of an alarm synchronization system provided in an embodiment of this disclosure. As shown in Figure 4, the operation method of the alarm synchronization system includes, but is not limited to, the following steps.

[0105] In step S401, the network management device 301 queries the alarm synchronization table, obtains the first alarm information recorded in the alarm synchronization table, and sends an alarm request message to the network element device 302 requesting the network element device 302 to report the first alarm information.

[0106] For example, the first alarm message is a linkDown alarm message.

[0107] In step 402, network element device 302 responds to the alarm request message sent by network management device 301, queries management information database 303 to obtain the first alarm information, and sends the alarm request response carrying the first alarm information to network management device 301.

[0108] Network element device 302 can send the alarm request response via rap message.

[0109] For example, if the first alarm message is set to a linkDown alarm message, its corresponding alarm index is 1, and the alarm parameters include: ifIndex = 100, ifAdminStatus = 1, ifOperStatus = 1, the value of AlarmSyncIndex in AlarmSyncEntry can be set to 1; the value of AlarmSyncTrapOid can be set to 1.3.6.1.6.3.1.1.5.3; and the value of AlarmSyncVarBindList can be set to the value obtained by encoding the alarm parameters (i.e., ifIndex and 100, ifAdminStatus and 1, ifOperStatus and 1) according to the ASN.1 encoding rule.

[0110] After obtaining the values ​​of the above variables, an alarm request response is generated based on each variable in AlarmSyncEntry and its corresponding value, and the alarm request response is sent to the network management device 301.

[0111] Step 403: The network management device 301 responds to the alarm request response sent by the network element device 302, parses the alarm request response, and obtains the linkDown alarm information.

[0112] The network management device 301 can obtain the linkDown alarm information, including the value of AlarmSyncVarBindList, by parsing the alarm request response. Then, the network management device 301 decodes the value of AlarmSyncVarBindList according to the preset decoding rules (such as the ASN.1 decoding rule) to obtain each alarm parameter in AlarmSyncVarBindList, namely ifIndex=100, ifAdminStatus=1, and ifOperStatus=1.

[0113] In step S404, network management device 301 queries the alarm synchronization table, obtains the second alarm information recorded in the alarm synchronization table, and sends an alarm request message to network element device 302 requesting network element device 302 to report the second alarm information.

[0114] For example, the second alarm message is the ospfv3NbrStateChange alarm message.

[0115] In step 405, network element device 302 responds to the alarm request message sent by network management device 301, queries management information database 303 to obtain the second alarm information, and sends the alarm request response carrying the second alarm information to network management device 301.

[0116] Network element device 302 can send the alarm request response in the format of a rap message.

[0117] For example, if the second alarm message is set to ospfv3NbrStateChange alarm message, its corresponding alarm index is 2, and the alarm parameters include: ospfv3RouterId = 200, ospfv3NbrState = 2, the value of AlarmSyncIndex in AlarmSyncEntry can be set to 2; the value of AlarmSyncTrapOid can be set to 1.3.6.1.2.1.191.0.2; and the value of AlarmSyncVarBindList can be set to the value obtained by encoding the alarm parameters (i.e., ospfv3RouterId and 200, ospfv3NbrState and 2) according to the ASN.1 encoding rule.

[0118] After obtaining the values ​​of the above variables, an alarm request response is generated based on each variable in AlarmSyncEntry and its corresponding value, and the alarm request response is sent to the network management device 301.

[0119] Step 406: The network management device 301 responds to the alarm request response sent by the network element device 302, parses the alarm request response, and obtains the ospfv3NbrStateChange alarm information.

[0120] By parsing the alarm request response, the network management device 301 can obtain the ospfv3NbrStateChange alarm information, including the value of AlarmSyncVarBindList. Then, the network management device 301 decodes the value of AlarmSyncVarBindList according to the preset decoding rules (e.g., ASN.1 decoding rules) to obtain each alarm parameter in AlarmSyncVarBindList, namely ospfv3RouterId=200 and ospfv3NbrState=2.

[0121] In step S407, the network management device 301 queries the alarm synchronization table to obtain the kth alarm information recorded in the alarm synchronization table, and interacts with the network element device 302 to obtain the alarm parameters of the kth alarm information.

[0122] Network management device 301 uses steps similar to those described in steps S401 to 403, or steps S404 to 406, to interact with network element device 302. k is an integer greater than or equal to 2.

[0123] In step S408, if there is no alarm information in the management information database 303, the network management device 301 stops querying and confirms that the alarm information synchronization is complete.

[0124] The network management device queries the alarm synchronization table to obtain the alarm information that needs to be synchronized, and sends alarm request information to the network element device. This allows the network element device to use rap messages, with each rap message carrying the alarm information to be reported (e.g., the AlarmSyncTrapOid of the alarm information, and its corresponding alarm parameters (e.g., ospfv3RouterId=200, ospfv3NbrState=2, or ifIndex=100, ifAdminStatus=1, ifOperStatus=1, etc.)). This enables the network management device to synchronize alarm information according to the alarm synchronization table. In other words, the network management device can request all alarm information generated by the network element device based on the records in the alarm synchronization table. This ensures that the network management device obtains all alarm information generated by the network element device, reducing the risk of alarm information loss and improving the effectiveness of the network management device's monitoring of the network element device.

[0125] In some embodiments, the same alarm identifier can be used to indicate that the information carried by the trap message received by the network management device is alarm information, so that the network management device can manage the alarm information in a unified manner.

[0126] For example, the following data structure can be used to define the format of the trap message sent by the network element device:

[0127] For example, the alarm identifier is set to 1.3.6.1.4.1.3902.6001, where AlarmSyncTrapOid in alarmTrap represents the preset reporting identifier, used to characterize the alarm type; and AlarmSyncVarBindList represents the alarm parameter list.

[0128] It should be noted that the data structure of AlarmSyncVarBindList is the same as that of AlarmSyncVarBindList in Figure 3, and will not be described again here.

[0129] For example, when the alarm information carried in the trap message is a linkDown alarm, its corresponding AlarmSyncTrapOid is 1.3.6.1.6.3.1.1.5.3;

[0130] When the alarm information carried in the trap message is the ospfIfStateChange alarm information, its corresponding AlarmSyncTrapOid is 1.3.6.1.2.1.191.0.2.

[0131] Figure 5 is a schematic diagram of the operation method of an alarm synchronization system provided in an embodiment of this disclosure. As shown in Figure 5, the operation method of the alarm synchronization system includes, but is not limited to, the following steps.

[0132] In step S501, when a network element device 302 generates an alarm message, it will actively report the alarm message to the network management device 301.

[0133] Network element device 302 generates a data packet based on alarm identifier 1.3.6.1.4.1.3902.6001, preset reporting identifier and its corresponding data structure information, and sends the data packet to network management device 301.

[0134] In some embodiments, the network element device 302 also uses the ASN.1 encoding rule to encode the data structure information corresponding to the preset reporting identifier to obtain the encoding value; then, according to the alarm identifier 1.3.6.1.4.1.3902.6001, the preset reporting identifier and the encoding value corresponding to the preset reporting identifier, a data packet is generated and sent to the network management device 301 to ensure the data security of the data packet during transmission and reduce the risk of the data structure information corresponding to the preset reporting identifier being leaked during transmission.

[0135] In step S502, when the network management device 301 receives the data packet sent by the network element device 302, it obtains the alarm identifier by parsing the data packet. According to the alarm identifier, it can be known that the information carried by the data packet is alarm information. Further, the alarm information is separated from the data packet.

[0136] The alarm identifier is 1.3.6.1.4.1.3902.6001; the separated alarm information includes: the preset reporting identifier and its corresponding data structure information.

[0137] In some embodiments, after parsing the preset reporting identifier, the network management device 301 will use the ASN.1 decoding rule to decode the encoded value corresponding to the preset reporting identifier to obtain the specific alarm parameters and parameter values ​​corresponding to the preset reporting identifier.

[0138] For example, when the preset reporting identifier (i.e., AlarmSyncTrapOid) is determined to be 1.3.6.1.6.3.1.1.5.3, the alarm information can be determined to be a linkDown alarm information. By decoding the encoded value corresponding to 1.3.6.1.6.3.1.1.5.3 using ASN.1, the corresponding AlarmSyncVarBindList can be obtained, which includes: ifIndex equals 100, ifAdminStatus equals 1, and ifOperStatus equals 1.

[0139] For example, when the preset reporting identifier (i.e., AlarmSyncTrapOid) is determined to be 1.3.6.1.2.1.191.0.2, the alarm information can be determined to be ospfIfStateChange alarm information. By decoding the encoded value corresponding to 1.3.6.1.2.1.191.0.2 using ASN.1, the corresponding AlarmSyncVarBindList can be obtained, which includes: ospfv3RouterId equals 200 and ospfv3NbrState equals 2.

[0140] Network elements encapsulate the alarm information they need to report using the same alarm identifier (e.g., 1.3.6.1.4.1.3902.6001) to generate data packets, which are then sent to the network management device. When the network management device receives the data packet, it can identify the information carried by the data packet as alarm information based on the alarm identifier in the data packet. This allows the network management device to manage alarm information uniformly and improve the processing speed of alarm information.

[0141] Figure 6 is a block diagram of a network management device provided in an embodiment of this disclosure. This network management device can be a server or a base station, etc., and this disclosure does not limit it.

[0142] As shown in Figure 6, the network management device 600 includes, but is not limited to, the following modules.

[0143] The first acquisition module 601 is used to acquire alarm information sent by network element devices.

[0144] The second acquisition module 602 is used to acquire the alarm synchronization table from the preset storage space.

[0145] The alarm synchronization table is stored in a preset storage space by the network element device and includes information used to indicate alarm synchronization.

[0146] The synchronization module 603 is used to synchronize alarm information based on the alarm synchronization table and alarm information.

[0147] It should be noted that the network management device in this embodiment can implement any of the alarm synchronization methods in this disclosure.

[0148] According to the network management device of this disclosure, by using a first acquisition module to acquire alarm information sent by network element devices, it can clearly identify the anomalies occurring in the network element devices, facilitating timely management and repair of the network element devices; by using a second acquisition module to retrieve an alarm synchronization table from a preset storage space, which is stored by the network element devices in the preset storage space and includes information for indicating alarm synchronization, it can characterize all alarm information generated by the network element devices. By using a synchronization module to confirm the acquired alarm information according to the alarm synchronization table, it can be determined whether the received alarm information is all the alarm information generated by the network element devices, so as to facilitate the network management device to synchronize alarm information, reduce the risk of alarm information loss, ensure that the network management device can acquire all alarm information of the network element devices, and improve the effectiveness of monitoring the network element devices.

[0149] Figure 7 is a block diagram of a network element device provided in an embodiment of this disclosure. This network element device is a terminal, or other devices in a communication network controlled by a network management device.

[0150] As shown in Figure 7, the network element device 700 includes, but is not limited to, the following modules.

[0151] The generation module 701 is used to generate alarm information.

[0152] Storage module 702 is used to store an alarm synchronization table, which includes information for indicating alarm synchronization, into a preset storage space.

[0153] The reporting module 703 is used to report alarm information to the network management device.

[0154] It should be noted that the network element device in this embodiment can implement any of the alarm synchronization methods in this disclosure.

[0155] According to the network element device of this disclosure embodiment, an alarm information is generated by a generation module. Then, the alarm information is processed simultaneously using a storage module and a reporting module. Specifically, the generation module reports a data packet carrying the alarm information to a network management device so that the network management device can obtain the alarm information. The storage module stores an alarm synchronization table, including information for indicating alarm synchronization, in a preset storage space. This allows the network management device to retrieve the alarm synchronization table from the preset storage space and then confirm the received alarm information based on the alarm synchronization table to determine whether it has received all the alarm information generated by the network element device. This achieves alarm information synchronization, reduces the risk of alarm information loss, and enables the network management device to more accurately confirm the status of the network element device through the synchronized alarm information. This allows for the management and maintenance of the network element device, ensuring its normal operation.

[0156] It should be clarified that this disclosure is not limited to the specific configurations and processes described in the foregoing embodiments and shown in the figures. For the sake of convenience and brevity, detailed descriptions of known methods are omitted here, and the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0157] Fourthly, embodiments of this disclosure provide an electronic device, a computer-readable medium, and a computer program product.

[0158] Figure 8 shows a block diagram of an electronic device provided in an embodiment of the present disclosure.

[0159] As shown in Figure 8, the electronic device includes at least one processor 801, at least one memory 802, and one or more I / O interfaces 803. The processor 801, memory 802, and I / O interfaces 803 are interconnected via a bus 804. The memory 802 stores one or more computer programs, which are executed by the at least one processor 801 to enable the at least one processor 801 to implement any of the alarm synchronization methods described in the above embodiments.

[0160] The modules in the aforementioned electronic devices 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 a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0161] This disclosure also provides a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements any of the alarm synchronization methods described in the above embodiments. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium.

[0162] This disclosure also provides a computer program product, including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code, wherein when the computer-readable code is run in the processor of an electronic device, the processor in the electronic device executes the above-described alarm synchronization method.

[0163] Those skilled in the art will understand that all or some of the steps, systems, and devices disclosed above, as well as the functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components.

[0164] Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable storage medium, which may include computer storage media (or non-transitory media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer-readable program instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), flash memory or other memory technologies, portable compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer.

[0165] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0166] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to implement various aspects of this disclosure.

[0167] The computer program product described herein can be implemented specifically through hardware, software, or a combination thereof. In one alternative embodiment, the computer program product is specifically embodied in a computer storage medium; in another alternative embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0168] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0169] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0170] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0171] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, the execution order of which may be determined based on the functions involved in each block. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0172] Example embodiments have been disclosed herein, and while specific terminology has been used, it is intended and should be interpreted only in a general illustrative sense and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of this disclosure.

Claims

1. An alarm synchronization method, applied to a network management device, comprising: Obtain alarm information sent by network element devices; Retrieve the alarm synchronization table from the preset storage space; as well as Synchronize the alarm information according to the alarm synchronization table and the alarm information. The alarm synchronization table is stored by the network element device in the preset storage space and includes information for indicating alarm synchronization.

2. The method according to claim 1, wherein, The alarm information sent by the network element device is obtained, including: In response to receiving a data packet sent by the network element device, the data packet is parsed; and In response to the parsing of the alarm identifier, the alarm information is separated from the data packet, wherein the alarm identifier indicates that the information carried by the data packet is the alarm information.

3. The method according to claim 1, wherein, The information used to indicate alarm synchronization includes: a preset number of alarms and a preset reporting identifier, wherein the preset reporting identifier represents the alarm type of the alarm information; Synchronizing alarm information based on the alarm synchronization table and the alarm information includes: The first number of alarm messages obtained is compared with the preset number of alarm messages to obtain the comparison result. The pending confirmation reporting identifier in the acquired alarm information is compared with the preset reporting identifier to obtain the identifier comparison result; If both the quantity comparison result and the identifier comparison result are the same, it is determined that alarm synchronization has been achieved; and If at least one of the quantity comparison results and the identifier comparison results is different, it is determined that alarm synchronization has not been achieved.

4. The method according to claim 3, wherein, After determining that alarm synchronization has not been achieved, the method further includes: According to the alarm synchronization table, a request is made to the network element device to obtain lost alarm information, wherein the second quantity of lost alarm information is the difference between the preset alarm quantity and the first quantity.

5. The method according to claim 4, wherein, According to the alarm synchronization table, request lost alarm information from the network element device, including: The preset reporting identifier in the alarm synchronization table that is different from the reporting identifier to be confirmed is identified as the target reporting identifier. An alarm request message is generated based on the target reporting identifier, and the alarm request message is sent to the network element device; and In response to the alarm request sent by the network element device, the alarm information corresponding to the target reporting identifier is obtained.

6. The method according to claim 1, wherein, The alarm synchronization table also includes data structure information, and The method further includes, after synchronizing the alarm information according to the alarm synchronization table and the alarm information: Query the alarm synchronization table to obtain the data structure information; and Based on the data structure information, the alarm information is parsed to obtain the alarm parameter values ​​in the alarm information.

7. An alarm synchronization method, applied to network element devices, comprising: Generate alarm information; Store the alarm synchronization table, which includes information used to indicate alarm synchronization, into a preset storage space; as well as The data packet carrying the alarm information is reported to the network management device.

8. The method according to claim 7, wherein, The data message includes an alarm identifier, and / or the information used to indicate alarm synchronization includes a preset reporting identifier. The alarm identifier indicates that the information in the data packet sent to the network management device is the alarm information, and the preset reporting identifier indicates the alarm type of the alarm information.

9. The method according to claim 7, further comprising: In response to the alarm request message sent by the network management device, the target reporting identifier is obtained; Based on the target reporting identifier and the alarm information corresponding to the target reporting identifier, generate an alarm request response; as well as Send the alarm request response to the network management device.

10. An electronic device comprising a memory and a processor; the memory storing a computer program executable by the processor, the computer program, when executed by the processor, implementing the alarm synchronization method as described in any one of claims 1 to 9.

11. A computer-readable medium having a computer program stored thereon, the computer program, when executed by a processor, implementing the alarm synchronization method as described in any one of claims 1 to 9.

12. A computer program product comprising a computer program that, when executed by a processor, implements the alarm synchronization method as described in any one of claims 1 to 9.

Images