Method, device, storage medium and electronic device for diagnosing network failure

Abstract

The present application discloses a method, device, storage medium and electronic device for diagnosing network failures. The method includes: the operator network management device obtains the alarm information of the client network management device; determines the target alarm category to which the alarm information belongs, and obtains the network operation status of the operator network management device; determines the network interruption scenario corresponding to the client network management device according to at least one of the target alarm type and the network operation status; determines the cause of the network failure and the treatment measures according to the network interruption scenario. The present application solves the technical problem that the fault cannot be handled in time after the network fails because the optoelectronic transceiver does not have the network management capability and the customer does not open the monitoring platform due to information security considerations.

Description

Technical Field

[0001] The present application relates to the field of networks, and in particular to a method, device, storage medium and electronic device for diagnosing network failures. Background Art

[0002] With the all-optical transformation of communication networks, operators' networks have basically become all-optical, but a large number of government and enterprise user devices have not yet been fully transformed to optical, and there are still a large number of electrical port devices. Therefore, the government and enterprise dedicated lines opened by operators for customers need to be converted by optical transceivers, but optical transceivers do not have network management capabilities, and there are monitoring blind spots.

[0003] Therefore, customer network interruptions often occur, while the operator monitors that the customer network is running normally and does not raise an alarm. In addition, customers usually do not open the monitoring platform to the operator for information security reasons, resulting in the inability to handle the fault in a timely manner after the customer equipment has a network failure.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present application provide a method, device, storage medium and electronic device for diagnosing network faults, so as to at least solve the technical problem that the fault cannot be handled in time after a network fault occurs because the optoelectronic transceiver does not have network management capabilities and the customer does not open a monitoring platform due to information security considerations.

[0006] According to one aspect of an embodiment of the present application, a method for diagnosing network failures is provided, including: an operator network management device obtains alarm information from a client network management device; determines a target alarm category to which the alarm information belongs, and obtains the network operation status of the operator network management device; determines a network interruption scenario corresponding to the client network management device based on at least one of the target alarm type and the network operation status; and determines a cause of the network failure and a handling measure based on the network interruption scenario.

[0007] Optionally, the network interruption scenario corresponding to the client network management device is determined based on at least one of the target alarm type and the network operation status, including: when the target alarm category of the alarm information is the first alarm information category, detecting whether the intranet address of the client network management device is interrupted, and whether the outbound gateway address of the client network management device is normal; when the intranet address of the client network management device is interrupted, and the outbound gateway address of the client network management device is normal, determining that the network interruption scenario is an intranet failure.

[0008] Optionally, determining the cause of the network failure and a handling measure according to the network interruption scenario includes: when the network interruption scenario is an intranet failure, determining that the cause of the network failure is an intranet failure, and the handling measure is that the first object self-checks the intranet.

[0009] Optionally, the network interruption scenario corresponding to the client network management device is determined according to at least one of the target alarm type and the network operation status, including: judging whether the intranet address of the client network management device is normal, and whether the outbound gateway address of the client network management device is interrupted; when the intranet address of the client network management device is normal, and the outbound gateway address of the client network management device is interrupted, determining that the network interruption scenario of the client network management device is a network interruption.

[0010] Optionally, the cause of the network failure and the handling measures are determined according to the network interruption scenario, including: when the network interruption scenario of the client network management device is network interruption, detecting whether the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in abnormal status; when the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in abnormal status, determining that the network interruption scenario is an access layer network interruption of the operator network management device; when the access layer network of the operator network management device is interrupted, determining that the cause of the network failure is a transceiver failure, an access layer network failure or an access layer network device failure, and the handling measures are that the second object checks the transceiver, access layer network and equipment.

[0011] Optionally, the method also includes: when the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in normal status, determining that the access layer network of the operator network management device is normal; and determining that the cause of the network failure is a failure from the client network management device to the transceiver, and the processing measure is that the first object self-checks the network optical path and port between the client network management device and the transceiver.

[0012] Optionally, the network interruption scenario corresponding to the client network management device is determined according to at least one of the target alarm type and the network operation status, including: when the target alarm category is the third alarm information, judging whether the intranet address of the client network management device is normal, and whether the outbound gateway address of the client network management device is normal; when the intranet address of the client network management device is normal, and the outbound gateway address of the client network management device is normal, and the application, service and Internet portal of the client network management device are interrupted, determining that the network interruption scenario of the client network management device is that the network cannot be connected.

[0013] Optionally, determine the cause of the network failure and the handling measures based on the network interruption scenario, including: when the network of the client network management device cannot be connected, detect whether the access layer network downlink port, the uplink port and the upper layer network downlink port of the operator network management device are in abnormal status, and detect whether the optical power of the access layer network uplink port, the downlink port optical power and the upper layer network downlink port of the operator network management device are in abnormal range; determine the cause of the network failure and the handling measures based on the detection results.

[0014] Optionally, the cause of the network failure and the handling measures are determined based on the detection results, including: when the detection results indicate that the status of the access layer network downstream port and the upstream port are normal, the optical power of the access layer network upstream port and the range of the optical power of the downstream port are normal, and the status of the upper layer network downstream port is abnormal, and the optical power range of the upper layer network downstream port is abnormal, then it is determined that the access layer network of the operator's network management equipment is normal and the upper layer network is interrupted; when the access layer network of the operator's network management equipment is normal and the upper layer network is interrupted, it is determined that the cause of the network failure is an upper layer network failure, and the handling measure is to check the upper layer network with the second object.

[0015] Optionally, the cause of the network failure and the treatment measures are determined based on the detection results, including: when the detection results indicate that the status of the access layer network downstream port and the upstream port are normal, the optical power of the access layer network upstream port and the range of the optical power of the downstream port are normal, and the status of the upper layer network downstream port is normal, and the range of the optical power of the upper layer network downstream port is normal, then it is determined that the access layer network of the operator's network management equipment is normal and the upper layer network is normal; when the access layer network of the operator's network management equipment is normal and the upper layer network is normal, the cause of the network failure is determined to be an access address failure; and the treatment measure is that the second object and the first object jointly check the server.

[0016] Optionally, the cause of the network failure and the treatment measures are determined based on the detection results, including: when the detection results indicate that the status of the access layer network downstream port and the status of the upstream port are abnormal, and the range of the access layer network upstream port optical power and the downstream port optical power is abnormal, determining that the access layer network of the operator's network management equipment is abnormal; when the access layer network of the operator's network management equipment is abnormal, determining that the cause of the network failure is an access layer network failure, and the treatment measure is to check the access layer network with the second object.

[0017] According to another aspect of an embodiment of the present application, a device for diagnosing network failures is also provided, including: an acquisition module, used for an operator's network management device to acquire alarm information of a client's network management device; a first determination module, used to determine a target alarm category to which the alarm information belongs, and to acquire the network operation status of the operator's network management device; a second determination module, used to determine a network interruption scenario corresponding to the client's network management device based on at least one of the target alarm type and the network operation status; and a third determination module, used to determine the cause of the network failure and handling measures based on the network interruption scenario.

[0018] According to another aspect of an embodiment of the present application, a non-volatile storage medium is also provided, including: the storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute any method for diagnosing a network fault.

[0019] According to another aspect of an embodiment of the present application, there is also provided an electronic device, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute instructions to implement any one of the methods for diagnosing a network fault.

[0020] In the embodiment of the present application, a method of determining a network interruption scenario based on alarm information, thereby determining the cause of the fault and the treatment measures is adopted, and the alarm information of the client network management device is obtained through the operator's network management device; the target alarm category to which the alarm information belongs is determined, and the network operation status of the operator's network management device is obtained; the network interruption scenario corresponding to the client network management device is determined according to at least one of the target alarm type and the network operation status; the cause of the network fault and the treatment measures are determined according to the network interruption scenario, thereby achieving the purpose of improving the efficiency of handling faults, thereby achieving the technical effect of avoiding undiscovered faults due to the existence of monitoring blind spots in transceivers, and further solving the technical problem that the fault cannot be handled in time after a network fault occurs due to the fact that the optoelectronic transceiver does not have network management capabilities and the customer does not open the monitoring platform due to information security considerations. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0022] Figure 1 is a flowchart of a method for diagnosing network failures according to an embodiment of the present application;

[0023] Figure 2 is a schematic diagram of an optional process of diagnosing a network fault according to an embodiment of the present application;

[0024] Figure 3 is a schematic diagram of an alarm message according to an embodiment of the present application;

[0025] Figure 4 is a schematic diagram of fault information according to an embodiment of the present application;

[0026] Figure 5 is a flowchart of processing a network failure according to an embodiment of the present application;

[0027] Figure 6 is a schematic diagram of a networking diagram according to an embodiment of the present application;

[0028] Figure 7 is a schematic diagram of the structure of a device for diagnosing network failures according to an embodiment of the present application;

[0029] Figure 8is a schematic block diagram of an exemplary electronic device 800 according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0031] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0032] According to an embodiment of the present application, an embodiment of a method for diagnosing network faults is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0033] Figure 1 A method for diagnosing a network fault according to an embodiment of the present application is as follows: Figure 1 As shown, the method comprises the following steps:

[0034] Step S102, the operator's network management device obtains alarm information from the client's network management device;

[0035] Step S104, determining the target alarm category to which the alarm information belongs, and obtaining the network operation status of the operator's network management equipment;

[0036] Step S106, determining a network interruption scenario corresponding to the client network management device according to at least one of the target alarm type and the network operation status;

[0037] It should be noted that the network interruption scenarios include three scenarios, specifically: the first network interruption scenario: customer intranet failure: internal network failure of the client device; the second network interruption scenario: customer network interruption: network failure from client device to transceiver; the third network interruption scenario: customer network cannot be connected: the network from client device to transceiver is normal, but cannot be connected.

[0038] Step S108: determining the cause of the network failure and the treatment measures according to the network interruption scenario.

[0039] It is understandable that the three network interruption scenarios correspond to different alarm information, that is, the alarm information includes three types of information, specifically:

[0040] First warning message:

[0041]

Telecom Level 3 Network

Alarm

[0042] X month X day XX hour XX minute XX second, detected XX.XXX.XXX.XX [address XX-XX],

[0043] RemotePing status [srcIP:XX.XXX.XXX.X, target IP address:XX.XXX.XXX.X] triggers an alarm.

[0044] The current RemotePing status [srcIP:XX.XXX.XXX.X, target IP address:XX.XXX.XXX.X] is that the intranet of the address XX-XX Telecom Level 3 network dedicated line customer is interrupted.

[0045] The client network management system sets the ping test frequency and ping test IP address (intranet address, outbound gateway, customer application or Internet portal web page) according to the network demand. The client network management system then obtains the ping test result (i.e. network connectivity) based on the packet loss rate of the ping test. Finally, the client network management system analyzes the ping test result to obtain the network interruption scenario to which the current alarm information belongs.

[0046] It should be noted that the first warning SMS corresponds to the first network interruption scenario, wherein the condition for determining that the intranet is interrupted is that the ping of the intranet address is interrupted and the outbound gateway address is normal.

[0047] Second warning message:

[0048]

Telecom Level 3 Network

Alarm

[0049] Detected XX.XXX.XXX.XX [address XX-XX] at XX:XX:XX on X:X.

[0050] RemotePing status [srcIP:XX.XXX.XXX.X, target IP address:XX.XXX.XXX.X] triggers an alarm.

[0051] The current RemotePing status [srcIP:XX.XXX.XXX.X, target IP address:XX.XXX.XXX.X] is that the address XX-XX Telecom's third-level network dedicated line customer network is interrupted.

[0052] It should be noted that the second warning SMS corresponds to the second network interruption scenario, wherein the conditions for determining the network interruption are: pinging the intranet address is normal and the outbound gateway address is interrupted.

[0053] The third warning message:

[0054]

Telecom Level 3 Network

Alarm

[0055] Detected XX.XXX.XXX.XX [address XX-XX] at XX:XX:XX on X:X.

[0056] RemotePing status [srcIP:XX.XXX.XXX.X, target IP address:XX.XXX.XXX.X] triggers an alarm.

[0057] The current RemotePing status [srcIP:XX.XXX.XXX.X, target IP address:XX.XXX.XXX.X] is that the address XX-XX Telecom Level 3 network dedicated line customer network cannot be connected.

[0058] It should be noted that the third warning SMS corresponds to the third network interruption scenario, in which the condition for judging that the network cannot be connected is: pinging the intranet address is normal and the outbound gateway address is normal, but the customer application, service or Internet portal is interrupted.

[0059] In the embodiment of the present application, a method of determining a network interruption scenario based on alarm information, thereby determining the cause of the fault and the treatment measures is adopted, and the alarm information of the client network management device is obtained through the operator's network management device; the target alarm category to which the alarm information belongs is determined, and the network operation status of the operator's network management device is obtained; the network interruption scenario corresponding to the client network management device is determined according to at least one of the target alarm type and the network operation status; the cause of the network fault and the treatment measures are determined according to the network interruption scenario, thereby achieving the purpose of improving the efficiency of handling faults, thereby achieving the technical effect of avoiding undiscovered faults due to the existence of monitoring blind spots in transceivers, and further solving the technical problem that the fault cannot be handled in time after a network fault occurs due to the fact that the optoelectronic transceiver does not have network management capabilities and the customer does not open the monitoring platform due to information security considerations.

[0060] In an exemplary embodiment of the present application, the network interruption scenario corresponding to the client network management device is determined according to at least one of the target alarm type and the network operation status, including: when the target alarm category of the alarm information is the first alarm information category, detecting whether the intranet address of the client network management device is interrupted, and whether the outbound gateway address of the client network management device is normal; when the intranet address of the client network management device is interrupted, and the outbound gateway address of the client network management device is normal, determining that the network interruption scenario is an intranet failure.

[0061] As an optional implementation, determining the cause of the network failure and the handling measures according to the network interruption scenario includes: when the network interruption scenario is an intranet failure, determining that the cause of the network failure is an intranet failure, and the handling measure is that the first object self-checks the intranet.

[0062] In an exemplary embodiment of the present application, the network interruption scenario corresponding to the client network management device is determined according to at least one of the target alarm type and the network operation status, including: judging whether the intranet address of the client network management device is normal, and whether the outbound gateway address of the client network management device is interrupted; when the intranet address of the client network management device is normal, and the outbound gateway address of the client network management device is interrupted, determining that the network interruption scenario of the client network management device is a network interruption.

[0063] In some optional embodiments of the present application, the cause of the network failure and the handling measures are determined according to the network interruption scenario, including: when the network interruption scenario of the client network management device is network interruption, detecting whether the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in abnormal status; when the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in abnormal status, determining that the network interruption scenario is an access layer network interruption of the operator network management device; when the access layer network of the operator network management device is interrupted, determining that the cause of the network failure is a transceiver failure, an access layer network failure or an access layer network device failure, and the handling measures are that the second object checks the transceiver, access layer network and equipment.

[0064] As an optional implementation, the method also includes: when the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in normal status, determining that the access layer network of the operator network management device is normal; and determining that the cause of the network failure is a failure from the client network management device to the transceiver, and the processing measure is that the first object self-checks the network optical path and port between the client network management device and the transceiver.

[0065] In an exemplary embodiment of the present application, the network interruption scenario corresponding to the client network management device is determined according to at least one of the target alarm type and the network operation status, including: when the target alarm category is the third alarm information, judging whether the intranet address of the client network management device is normal, and whether the outbound gateway address of the client network management device is normal; when the intranet address of the client network management device is normal, and the outbound gateway address of the client network management device is normal, and the application, service and Internet portal of the client network management device are interrupted, determining that the network interruption scenario of the client network management device is that the network cannot be connected.

[0066] In some optional embodiments of the present application, the cause of the network failure and the treatment measures are determined according to the network interruption scenario, including: when the network of the client network management device cannot be connected, detecting whether the access layer network downlink port, the uplink port and the upper layer network downlink port of the operator network management device are in abnormal status, and detecting whether the optical power of the access layer network uplink port, the downlink port optical power and the upper layer network downlink port optical power of the operator network management device are in abnormal range; determining the cause of the network failure and the treatment measures according to the detection results.

[0067] As an optional implementation, determining the cause of the network failure and handling measures based on the detection results, including: when the detection results indicate that the status of the access layer network downstream port and the upstream port are normal, the optical power of the access layer network upstream port and the range of the optical power of the downstream port are normal, and the status of the upper layer network downstream port is abnormal, and the optical power range of the upper layer network downstream port is abnormal, then determining that the access layer network of the operator's network management equipment is normal and the upper layer network is interrupted; when the access layer network of the operator's network management equipment is normal and the upper layer network is interrupted, determining that the cause of the network failure is an upper layer network failure, and the handling measure is to use the second object to check the upper layer network.

[0068] As an optional implementation, determining the cause of the network failure and handling measures based on the detection results, including: when the detection results indicate that the status of the access layer network downstream port and the upstream port are normal, the optical power of the access layer network upstream port and the range of the optical power of the downstream port are normal, and the status of the upper layer network downstream port is normal, and the optical power range of the upper layer network downstream port is normal, then determining that the access layer network of the operator's network management equipment is normal and the upper layer network is normal; when the access layer network of the operator's network management equipment is normal and the upper layer network is normal, determining that the cause of the network failure is an access address failure; and the handling measures are that the second object and the first object jointly check the server.

[0069] As an optional implementation, determining the cause of the network failure and the handling measures based on the detection results, including: when the detection results indicate that the status of the access layer network downstream port and the status of the upstream port are abnormal, and the range of the access layer network upstream port optical power and the downstream port optical power is abnormal, determining that the access layer network of the operator's network management equipment is abnormal; when the access layer network of the operator's network management equipment is abnormal, determining that the cause of the network failure is an access layer network failure, and the handling measures are to check the access layer network with the second object.

[0070] It can be understood that the first object is the customer and the second object is the operator.

[0071] In order to facilitate those skilled in the art to better understand the technical solution of the present application, a specific embodiment is now described.

[0072] Figure 2 is a schematic diagram of an optional process of diagnosing a network fault according to an embodiment of the present application, such as Figure 2 As shown, the process mainly includes the following steps:

[0073] (1) The three major network outage scenarios are abstracted into five propositions;

[0074] Specifically, it includes the following propositions: Proposition p: customer intranet is interrupted; Proposition q: customer network is interrupted; Proposition r: operator access layer network is interrupted; Proposition s: customer network cannot be connected; Proposition t: operator upper layer network is interrupted.

[0075] It can be understood that proposition p corresponds to the first network interruption scenario, proposition q corresponds to the second network interruption scenario, and proposition s corresponds to the third network interruption scenario.

[0076] (2) First, determine whether the customer's intranet is interrupted based on the alarm information. In this case, the alarm information is the first alarm information;

[0077] Judgment condition: ifp→True;

[0078] If Proposition p: The customer's intranet is interrupted is true, then the cause of the fault can be located as a customer's intranet fault. It is recommended to send an order to let the customer check the intranet status by themselves.

[0079] (3) If the customer's intranet is not interrupted (i.e. ), it is necessary to determine whether the customer network is interrupted, and the alarm information is the second alarm information;

[0080] The first judgment condition: if q∧r→True;

[0081] Check whether the status of the carrier access layer LSW downstream port and the status of the LSW upstream port are abnormal. When the port status is "DOWN" (that is, both Proposition q: Customer network interruption and Proposition r: Carrier access layer network interruption are true), the fault cause can be located as a transceiver failure or a carrier access network or equipment failure. It is recommended to send an order to the carrier maintenance personnel to check the transceiver first, then check the carrier access network, or check the carrier equipment.

[0082] The second judgment condition:

[0083] Check that the status of the carrier access layer LSW downstream port and the status of the LSW upstream port are normal. When the port status is "UP" (that is, both proposition q: the customer network is interrupted and the non-proposition of proposition r: the carrier access layer network is not interrupted are true), the cause of the fault can be located as a fault from the customer to the transceiver. It is recommended to dispatch the customer to check the optical path and port between the client device and the transceiver.

[0084] (4) If the customer's intranet is not interrupted (i.e. ), the customer network is not interrupted (i.e. ), it is necessary to determine whether the network cannot be connected, and the alarm information is the third alarm information;

[0085] The first judgment condition:

[0086] Check the operator's access layer network, that is, the status of the switch LSW downstream port and the status of the LSW upstream port; check whether the optical power of the LSW upstream port and the optical power range of the LSW downstream port are abnormal; check the operator's upper layer network, that is, the status of the BRAS downstream port; check whether the optical power of the downstream port is abnormal.

[0087] When the operator's access layer network, i.e., the switch LSW downstream port status and LSW upstream port status are "UP"; the LSW upstream port optical power and LSW downstream port optical power are within the normal range; the operator's upper layer network, i.e., the BRAS downstream port status is "DOWN"; and the downstream port optical power is abnormal (i.e., the non-proposition of proposition r: the operator's access layer network is not interrupted, proposition s: the customer network cannot be connected, and proposition t: the operator's upper layer network is interrupted are all true), the cause of the fault can be located as a fault in the operator's upper layer network, and it is recommended to send an order to the operator's operation and maintenance department to check the operator's upper layer network.

[0088] The second judgment condition:

[0089] Check whether the status of the operator's upper-layer network, i.e., the BRAS downlink port, and the optical power of the downlink port are abnormal. When the status of the operator's upper-layer network, i.e., the BRAS downlink port, is "UP" and the optical power of the downlink port is normal (i.e., the non-proposition of proposition r: the operator's access layer network is not interrupted, proposition s: the customer network cannot be connected, and the non-proposition of proposition t: the operator's upper-layer network is not interrupted are all true), the cause of the fault can be located as a suspected customer access destination failure. It is recommended to dispatch the operator's operation and maintenance department to coordinate with the peer end to check the peer server.

[0090] The third judgment condition: ifs∧r→True;

[0091] Check the operator's access layer network, that is, the switch LSW downstream port status and LSW upstream port status, LSW upstream port optical power and LSW downstream port optical power range are abnormal. When the operator's access layer network, that is, the switch LSW downstream port status and LSW upstream port status are "DOWN", the LSW upstream port optical power and LSW downstream port optical power are in the abnormal range (that is, Proposition s: Customer network cannot be connected and Proposition t: Operator upper network interruption are both true), the cause of the fault can be located as an operator access network fault. It is recommended to send an order to the operator's operation and maintenance department to check the operator's access layer network.

[0092] For example, Figure 3 is a schematic diagram of an alarm message according to an embodiment of the present application, such as Figure 3 As shown, at 02:09 on September 17, 2022, the client's network management system pushed a text message, which included:

[0093]

Telecom Level 3 Network

Alarm

[0094] At 02:09:40 on September 17, 2022, XX.92.255.XX [XX District Zenith Group] was detected;

[0095] RemotePing status [srcIP:XX.148.72.X, target IP address:XX.148.72.X] triggers an alarm;

[0096] The current RemotePing status [srcIP:XX.148.72.X, target IP address:XX.148.72.X] is the address XX-Zhending Group dx Level 3 network dedicated line customer network interrupted.

[0097] The network management system on the operator side collected the SMS content and automatically determined that the interrupted dedicated line number was 80027****. The network management system checked the operator's LSW downstream port for an alarm and located the fault to be a fault in the segment from the operator's device to the transceiver or a fault in the segment from the client device to the transceiver. Based on the diagnosis results, a fault ticket was automatically triggered and sent to the maintenance unit (work order number 2022091735****), suggesting that the transceiver be checked, then the operator's access layer network, and the segment from the client device to the transceiver.

[0098] Figure 4 is a schematic diagram of a fault dispatch information according to an embodiment of the present application, such as Figure 4 As shown, the fault is caused by a fault in the transceiver device.

[0099] It is understandable that the operator's control station conducts unified scheduling and control of the fault 24 hours a day, and the maintenance unit reports the fault result as follows: transceiver equipment failure. After replacing the transceiver, the operator's network management system eliminates the alarm information, and the client's network management system pushes a recovery SMS, and the fault is resolved.

[0100] It is easy to notice that the present application adopts a method of determining the network interruption scenario according to the alarm information, thereby determining the cause of the fault and the treatment measures, which has the following beneficial effects:

[0101] (1) Collect information through instant messaging tools to solve the problem that the client network management system cannot access monitoring: The client device network management system connects with the operator's network management system via SMS or WeChat, so that fault information can be obtained in a timely manner. While meeting the customer's security needs, the customer's equipment network operation information can be obtained in a timely manner to solve the problem that the customer network management system cannot access monitoring.

[0102] (2) By utilizing the monitoring information at both ends to establish automatic fault diagnosis capabilities, the problem of blind spots in optoelectronic transceiver monitoring is solved: The operator-side network management system establishes an end-to-end fault diagnosis process for the segmented information based on the received alarm information (i.e., transceiver to client device) combined with the operator's network management system's (i.e., operator-side device to transceiver) access layer network and core layer equipment status diagnosis information, performs diagnostic tests, and automatically locates the fault point, solving the problem of blind spots in transceiver monitoring and improving the accuracy of fault diagnosis.

[0103] (3) Establish the ability to automatically generate and dispatch work orders to achieve 24 / 7 monitoring: Based on the diagnosis results, fault work orders are automatically triggered and dispatched accordingly. Work orders will also be uniformly managed according to the operator's maintenance work order requirements, achieving 24 / 7 automatic monitoring and dispatching of client network equipment.

[0104] Figure 5 is a flow chart of processing a network failure according to an embodiment of the present application, such as Figure 5 As shown, the process mainly includes the following steps:

[0105] (1) The client's network management system automatically triggers an alarm message, where the alarm message can be sent to the operator's network management system via SMS or WeChat;

[0106] (2) The network management system on the operator side receives the alarm information, determines the cause of the fault based on the alarm information, and returns the cause of the fault to the network management system on the client side;

[0107] (3) The network management system on the operator side determines the treatment measures based on the cause of the fault and dispatches a request to the technical support department;

[0108] (4) The technical support department resolves the problem and returns the results to the operator's network management system.

[0109] Figure 6 is a schematic diagram of a networking diagram according to an embodiment of the present application, such as Figure 6 As shown, the network diagram includes: operator equipment, transceivers, and government and enterprise customer equipment.

[0110] It should be noted that operator equipment includes but is not limited to: operator switches and routers; government and enterprise customer equipment includes but is not limited to: customer switches and routers;

[0111] It is understandable that the customer network failure may occur in the section from the customer device to the transceiver or in the section from the operator device to the transceiver. Since both the client and the operator are monitored by the network management, the transceiver has a monitoring blind spot. Therefore, the transceiver can be reversed through the monitoring information of the client and the operator to achieve the effect of full-process monitoring.

[0112] Figure 7 is a schematic diagram of a device structure for diagnosing network failures according to an embodiment of the present application, such as Figure 7 As shown, the device comprises:

[0113] Acquisition module 70, used for the operator's network management device to obtain the alarm information of the client's network management device;

[0114] A first determination module 72 is used to determine the target alarm category to which the alarm information belongs, and obtain the network operation status of the operator's network management equipment;

[0115] A second determination module 74, configured to determine a network interruption scenario corresponding to the client network management device according to at least one of a target alarm type and a network operation status;

[0116] The third determination module 76 is used to determine the cause of the network failure and the treatment measures according to the network interruption scenario.

[0117] In the device, an acquisition module 70 is used for the operator's network management device to obtain the alarm information of the client's network management device; a first determination module 72 is used to determine the target alarm category to which the alarm information belongs, and obtain the network operation status of the operator's network management device; a second determination module 74 is used to determine the network interruption scenario corresponding to the client's network management device according to at least one of the target alarm type and the network operation status; a third determination module 76 is used to determine the cause of the network failure and the processing measures according to the network interruption scenario, thereby achieving the purpose of improving the efficiency of handling failures, thereby achieving the technical effect of avoiding the failure to discover the failure due to the monitoring blind spot of the transceiver, and further solving the technical problem that the fault cannot be handled in time after the network fails because the optoelectronic transceiver does not have the network management capability and the customer does not open the monitoring platform due to information security considerations.

[0118] According to another aspect of an embodiment of the present application, a non-volatile storage medium is further provided, the non-volatile storage medium including a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute any method for diagnosing a network fault.

[0119] Specifically, the above storage medium is used to store program instructions for the following functions to implement the following functions:

[0120] The operator's network management device obtains the alarm information of the client's network management device; determines the target alarm category to which the alarm information belongs, and obtains the network operation status of the operator's network management device; determines the network interruption scenario corresponding to the client's network management device based on at least one of the target alarm type and the network operation status; determines the cause of the network failure and the handling measures based on the network interruption scenario.

[0121] Optionally, in this embodiment, the above-mentioned storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the above-mentioned contents. More specific examples of the above-mentioned storage medium may include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above-mentioned contents.

[0122] In an exemplary embodiment of the present application, a computer program product is further provided, including a computer program, and when the computer program is executed by a processor, any of the above methods for diagnosing a network failure is implemented.

[0123] Optionally, the computer program may implement the following steps when executed by a processor:

[0124] The operator's network management device obtains the alarm information of the client's network management device; determines the target alarm category to which the alarm information belongs, and obtains the network operation status of the operator's network management device; determines the network interruption scenario corresponding to the client's network management device based on at least one of the target alarm type and the network operation status; determines the cause of the network failure and the handling measures based on the network interruption scenario.

[0125] According to an embodiment of the present application, an electronic device is provided, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above-mentioned methods for diagnosing network faults.

[0126] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0127] Figure 8 800 is a schematic block diagram of an example electronic device 800 according to an embodiment of the present application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0128] like Figure 8 As shown, the device 800 includes a computing unit 801, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 802 or a computer program loaded from a storage unit 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the device 800 can also be stored. The computing unit 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0129] A number of components in the device 800 are connected to the I / O interface 805, including: an input unit 806, such as a keyboard, a mouse, etc.; an output unit 807, such as various types of displays, speakers, etc.; a storage unit 808, such as a disk, an optical disk, etc.; and a communication unit 809, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 809 allows the device 800 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0130] The computing unit 801 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 801 performs the various methods and processes described above, such as a method for diagnosing a network fault. For example, in some embodiments, the method for diagnosing a network fault may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 800 via the ROM 802 and / or the communication unit 809. When the computer program is loaded into the RAM 803 and executed by the computing unit 801, one or more steps of the method for diagnosing a network fault described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform a method for diagnosing a network fault in any other appropriate manner (e.g., by means of firmware).

[0131] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0132] The program code for implementing the method of the present application can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, implements the functions / operations specified in the flow chart and / or block diagram. The program code can be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0133] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0134] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0135] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0136] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0137] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0138] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0139] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0140] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0141] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0142] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0143] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for diagnosing network failures, characterized in that: include: The operator's network management device obtains the alarm information of the client's network management device; Determine the target alarm type to which the alarm information belongs, and obtain the network operation status of the operator's network management equipment; Determine a network interruption scenario corresponding to the client network management device according to at least one of the target alarm type and the network operation status; Determine the cause of the network failure and the treatment measures based on the network interruption scenario; Wherein, determining the network interruption scenario corresponding to the client network management device according to at least one of the target alarm type and the network operation status includes: judging whether the intranet address of the client network management device is normal and whether the outbound gateway address of the client network management device is interrupted; when the intranet address of the client network management device is normal and the outbound gateway address of the client network management device is interrupted, determining that the network interruption scenario of the client network management device is a network interruption; Among them, determining the cause of the network failure and the handling measures according to the network interruption scenario include: when the network interruption scenario of the client network management device is the network interruption, detecting whether the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in abnormal status; when the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in abnormal status, determining that the network interruption scenario is the access layer network interruption of the operator network management device; when the access layer network of the operator network management device is interrupted, determining that the cause of the network failure is a transceiver failure, an access layer network failure or an access layer network device failure, and the handling measure is that the second object checks the transceiver, access layer network and equipment.

2. The method according to claim 1, characterized in that Determining a network interruption scenario corresponding to the client network management device according to at least one of the target alarm type and the network operation status includes: In the case where the target alarm type of the alarm information is the first alarm information category, detecting whether the intranet address of the client network management device is interrupted, and whether the outbound gateway address of the client network management device is normal; When the intranet address of the client network management device is interrupted and the outbound gateway address of the client network management device is normal, it is determined that the network interruption scenario is an intranet failure.

3. The method according to claim 2, characterized in that Determine the cause of the network failure and the solution based on the network interruption scenario, including: In the case where the network interruption scenario is an intranet failure, it is determined that the cause of the network failure is an intranet failure, and the processing measure is that the first object self-checks the intranet.

4. The method according to claim 1, characterized in that The method further comprises: When the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in normal status, it is determined that the access layer network of the operator network management device is normal; and it is determined that the cause of the network failure is a failure from the client network management device to the transceiver, and the processing measure is that the first object self-checks the network optical path and port between the client network management device and the transceiver.

5. The method according to claim 1, characterized in that Determining a network interruption scenario corresponding to the client network management device according to at least one of the target alarm type and the network operation status includes: In the case where the target alarm type is the third alarm information, determining whether the intranet address of the client network management device is normal, and whether the outbound gateway address of the client network management device is normal; When the intranet address of the client network management device is normal, the outbound gateway address of the client network management device is normal, and the application, service and Internet portal of the client network management device are interrupted, it is determined that the network interruption scenario of the client network management device is that the network cannot be connected.

6. The method according to claim 5, characterized in that Determine the cause of the network failure and the solution based on the network interruption scenario, including: In the case that the network of the client network management device cannot be connected, detecting whether the access layer network downlink port, the uplink port and the upper layer network downlink port of the operator network management device are in abnormal state, and detecting whether the optical power of the access layer network uplink port, the downlink port optical power and the upper layer network downlink port of the operator network management device are in abnormal range; Determine the cause of the network failure and the treatment measures based on the test results.

7. The method according to claim 6, characterized in that Determine the cause of the network failure and the corresponding treatment measures based on the test results, including: If the detection result indicates that the status of the access layer network downlink port and the uplink port is normal, the range of the optical power of the access layer network uplink port and the downlink port optical power is normal, and the status of the upper layer network downlink port is abnormal, and the range of the optical power of the upper layer network downlink port is abnormal, it is determined that the access layer network of the operator network management device is normal and the upper layer network is interrupted; When the access layer network of the operator network management device is normal and the upper layer network is interrupted, it is determined that the cause of the network failure is the upper layer network failure, and the processing measure is that the second object checks the upper layer network.

8. The method according to claim 6, characterized in that Determine the cause of the network failure and the corresponding treatment measures based on the test results, including: If the detection result indicates that the status of the access layer network downlink port and the uplink port is normal, the range of the optical power of the access layer network uplink port and the downlink port optical power is normal, and the status of the upper layer network downlink port is normal, and the range of the optical power of the upper layer network downlink port is normal, it is determined that the access layer network and the upper layer network of the operator network management device are normal; When the access layer network of the operator network management device is normal and the upper layer network is normal, the cause of the network failure is determined to be an access address failure; and the processing measure is that the second object and the first object cooperate to check the server.

9. The method according to claim 6, characterized in that Determine the cause of the network failure and the corresponding treatment measures based on the test results, including: When the detection result indicates that the state of the downlink port and the state of the uplink port of the access layer network are abnormal, and the range of the optical power of the uplink port and the downlink port of the access layer network is abnormal, it is determined that the access layer network of the operator network management device is abnormal; In the case where the access layer network of the operator network management device is abnormal, it is determined that the cause of the network failure is an access layer network failure, and the processing measure is that the second object checks the access layer network.

10. A device for diagnosing network failures, characterized in that: include: Acquisition module, used for the operator's network management equipment to obtain the alarm information of the client's network management equipment; A first determination module is used to determine the target alarm type to which the alarm information belongs, and obtain the network operation status of the operator's network management device; The second determination module is used to determine the network interruption scenario corresponding to the client network management device according to at least one of the target alarm type and the network operation state, wherein the network interruption scenario corresponding to the client network management device according to at least one of the target alarm type and the network operation state includes: judging whether the intranet address of the client network management device is normal and whether the outbound gateway address of the client network management device is interrupted; when the intranet address of the client network management device is normal and the outbound gateway address of the client network management device is interrupted, determining that the network interruption scenario of the client network management device is a network interruption; The third determination module is used to determine the cause of the network failure and the handling measures according to the network interruption scenario, wherein the cause of the network failure and the handling measures according to the network interruption scenario are determined, including: when the network interruption scenario of the client network management device is the network interruption, detecting whether the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in abnormal states; when the access layer downlink port of the operator network management device and the access layer uplink port of the operator network management device are in abnormal states, determining that the network interruption scenario is the access layer network interruption of the operator network management device; when the access layer network of the operator network management device is interrupted, determining that the cause of the network failure is a transceiver failure, an access layer network failure or an access layer network device failure, and the handling measure is that the second object checks the transceiver, access layer network and equipment.

11. A non-volatile storage medium, characterized in that: The storage medium includes a stored program, wherein when the program is executed, the device where the storage medium is located is controlled to execute the method for diagnosing network failures as claimed in any one of claims 1 to 9.

12. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method for diagnosing network failures as claimed in any one of claims 1 to 9.

Images