CN109450527B

CN109450527B - Fault determination method and device, computer equipment and storage medium

Info

Publication number: CN109450527B
Application number: CN201811241366.2A
Authority: CN
Inventors: 李忠谕; 迟景升
Original assignee: Guangdong Transmission Network Operation Center of China Telecom Corp Ltd
Current assignee: Guangdong Transmission Network Operation Center of China Telecom Corp Ltd
Priority date: 2018-10-24
Filing date: 2018-10-24
Publication date: 2020-09-08
Anticipated expiration: 2038-10-24
Also published as: CN109450527A

Abstract

The invention relates to a fault determining method and device, computer equipment and a storage medium, and belongs to the technical field of networks. The method comprises the following steps: when receiving the reporting information, determining reporting equipment corresponding to the reporting information; determining a first running state of the reporting device, and acquiring a second running state of each candidate device on a network line where the reporting device is located when the fault of the reporting device cannot be determined according to the first running state; and determining the fault of the reporting equipment according to the second operation state. By the technical scheme, the problem that the fault which cannot be detected through alarming still needs to be manually checked and the fault point is located after the user declares the service fault is solved. The method and the device can realize active detection and position the fault of the optical access network according to the triggering of the reporting information, determine the fault which cannot be detected by alarm detection, and effectively improve the determination efficiency of the network access fault.

Description

Fault determination method and device, computer equipment and storage medium

Technical Field

The present invention relates to the field of network technologies, and in particular, to a method and an apparatus for determining a fault, a computer device, and a storage medium.

Background

When a network access fault occurs in an existing network, a network manager often needs to locate the network access fault and determine the cause of the fault. At present, the detection of network faults mainly depends on network management alarms. In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: due to the reasons of software and hardware (such as network management version, compatibility between equipment and a terminal, transmission loss between systems, messy codes of alarm information and the like), the alarm is incomplete, which shows that the existing network has a fault but does not generate a corresponding network management alarm. For the part of faults which can not be detected through alarming, the user still needs to declare the service fault and then manually troubleshoot and locate the fault point, which causes the waste of manpower and material resources for determining the fault.

Disclosure of Invention

Based on this, the embodiment of the invention provides a fault determination method, a fault determination device, computer equipment and a storage medium, which can effectively reduce manpower and improve fault determination efficiency.

The content of the embodiment of the invention is as follows:

a method of fault determination comprising the steps of: when receiving reporting information, determining reporting equipment corresponding to the reporting information; determining a first operation state of the reporting device, and acquiring a second operation state of each candidate device on a network line where the reporting device is located when the fault of the reporting device cannot be determined according to the first operation state; and determining the fault of the reporting equipment according to the second operation state.

In one embodiment, the step of determining the first operating state of the reporting device comprises: determining whether an in-transit fault corresponding to the reporting information exists in an in-transit fault list; the on-the-road fault list comprises on-the-road faults analyzed according to the network management alarm; when there is an in-transit fault corresponding to the reporting information, determining the in-transit fault corresponding to the in-transit fault list as the fault of the reporting equipment; when the in-transit fault corresponding to the reporting information does not exist, determining whether the OLT corresponding to the reporting equipment Ping is connected or not; if the Ping is not successful, determining that the fault of the reporting equipment is an OLT pipe disconnection fault; and if Ping leads, determining a first operation state of the reporting equipment, and determining the fault of the reporting equipment according to the first operation state.

In one embodiment, the step of determining the fault of the reporting device according to the second operation state comprises: determining whether online candidate equipment exists under the OBD where the reporting equipment is located according to the second running state; when an online candidate device exists under the OBD where the reporting device is located, determining the fault of the reporting device according to the type of the reporting device; when no online candidate device exists under the OBD where the reporting device is located, determining whether an online candidate device exists under the PON port where the reporting device is located according to the second running state; when no online candidate equipment exists under the PON port where the reporting equipment is located, determining the fault of the reporting equipment according to the state of each branch of the network line; when an online candidate device exists under the PON port where the reporting device is located, determining whether the candidate device which is offline after the reporting device is offline exists under the OBD where the reporting device is located according to the second running state; when candidate equipment which is offline after a preset time period exists, determining the fault of the reporting equipment according to the type of the reporting equipment; when the candidate equipment which is offline after the time period exceeds the preset time period does not exist, determining the number of first candidate equipment which is powered down in the preset effective time under the OBD, and determining the fault of the reporting equipment according to the number of the first candidate equipment.

In one embodiment, the step of determining the fault of the reporting device according to the first candidate device number comprises: when the number of the first candidate devices is more than or equal to 1, determining the fault of the reporting device according to the type of the reporting device; and when the first candidate equipment quantity is equal to 0, determining the fault of the reporting equipment according to a second candidate equipment quantity offline in the effective time under the OBD.

In one embodiment, the step of determining the fault of the reporting device according to the state of each branch of the network line includes: determining the number of third candidate devices with power failure in the effective time under the PON port; when the number of the third candidate devices is more than or equal to 1, determining the fault of the reporting device according to the type of the reporting device; when the number of the third candidate devices is equal to 0, determining whether the candidate devices offline within the valid time under the PON port are under the same OBD; if the reporting equipment is in the same OBD, determining the fault of the reporting equipment according to the number of second candidate equipment which are offline in the effective time under the OBD; if the number of the fourth candidate devices of the PON port which are off-line in the effective time is not in the same OBD, determining the fault of the reporting device according to the type of the reporting device when the number of the fourth candidate devices is equal to 1, and determining the fault of the reporting device as the fault of the main optical path when the number of the fourth candidate devices is greater than 1.

In one embodiment, the step of determining the failure of the reporting device according to the second number of candidate devices offline in the valid time under the OBD includes: when the number of the second candidate devices is larger than 1, determining that the failure of the reporting device is a branch optical path failure; and when the number of the second candidate devices is equal to 1, determining the fault of the reporting device according to the type of the reporting device.

In one embodiment, the step of determining the fault of the reporting device according to the type of the reporting device includes: when the reporting equipment is an MDU, determining that the fault of the reporting equipment is an MDU fiber breakage fault; and when the reporting equipment is not the MDU, determining that the fault of the reporting equipment is a sheath fiber fault.

Correspondingly, an embodiment of the present invention provides a device for determining a fault, including: the reporting device determining module is used for determining the reporting device corresponding to the reporting information when the reporting information is received; the operation state determining module is used for determining a first operation state of the reporting device, and acquiring a second operation state of each candidate device on a network line where the reporting device is located when the fault of the reporting device cannot be determined according to the first operation state; and the fault determining module is used for determining the fault of the reporting equipment according to the second running state.

After determining the reporting equipment, the method and the device for determining the fault determine a first operation state of the reporting equipment, and determine the fault of the reporting equipment according to the first operation state; and when the fault of the reporting device cannot be determined according to the first operation state, acquiring a second operation state of each candidate device on the network line where the reporting device is located, and determining the fault of the reporting device according to the second operation state. The method and the device can realize active detection and positioning of the network access fault according to the triggering of the reporting information, determine the fault which cannot be detected by alarm detection, and effectively improve the determination efficiency of the network access fault.

A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program: when receiving reporting information, determining reporting equipment corresponding to the reporting information; determining a first operation state of the reporting device, and acquiring a second operation state of each candidate device on a network line where the reporting device is located when the fault of the reporting device cannot be determined according to the first operation state; and determining the fault of the reporting equipment according to the second operation state.

The computer equipment can realize active detection and positioning of the network access fault according to the triggering of the reporting information, determine the fault which cannot be detected by alarm detection, and effectively improve the determination efficiency of the network access fault.

A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of: when receiving reporting information, determining reporting equipment corresponding to the reporting information; determining a first operation state of the reporting device, and acquiring a second operation state of each candidate device on a network line where the reporting device is located when the fault of the reporting device cannot be determined according to the first operation state; and determining the fault of the reporting equipment according to the second operation state.

The computer readable storage medium can realize active detection and positioning of the network access fault according to the triggering of the reporting information, determine the fault which cannot be detected by alarm detection, and effectively improve the determination efficiency of the network access fault.

Drawings

FIG. 1 is a diagram of an application environment of a method for determining a failure in one embodiment;

FIG. 2 is a flow diagram illustrating a method for fault determination in one embodiment;

FIG. 3 is a schematic diagram of a two-stage optical splitter network according to an embodiment;

FIG. 4 is a schematic illustration of a main process in one embodiment;

FIG. 5 is a schematic flow chart diagram of a method for determining a fault in another embodiment;

FIG. 6 is a schematic diagram of a backbone failure analysis sub-process in one embodiment;

FIG. 7 is a diagram illustrating a branch fault analysis sub-flow in one embodiment;

FIG. 8 is a schematic diagram of the MDU fiber break/sheath fiber sub-flow in one embodiment;

FIG. 9 is a block diagram showing the structure of a failure determination device in one embodiment;

FIG. 10 shows an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The method for determining the fault can be applied to an application environment as shown in fig. 1, and the application scenario can be in an optical internet. The application environment includes a reporting device 101 and a server 102. When the service use of the reporting device 101 is affected, the user reports a fault to the server 102, and the server analyzes reporting information of the fault report performed by the user and determines a corresponding reporting device; the server 102 determines the fault of the reporting device based on the first operation state of the reporting device 101 and the second operation state of the candidate device. The reporting device 101 may refer to various devices connected in a network, for example: ONU (Optical Network Unit), MDU (Multiple dwelling Unit, which refers To FTTB (Fiber To The Building) type ONU), and The like. The server 102 refers to a device provided by a network manager and used for maintaining a network, and may be implemented by a separate server or a server cluster composed of a plurality of servers.

The embodiment of the invention provides a fault determination method and device, computer equipment and a storage medium. Hereinafter, the reporting facilities are described in detail as an example.

In one embodiment, a method of fault determination is provided, as shown in FIG. 2. Taking the application of the method to the server side in fig. 1 as an example for explanation, the method comprises the following steps:

s201, when receiving reporting information, determining a reporting device corresponding to the reporting information.

The reporting information refers to failure reporting information sent to the server by the user when the network fails. The reporting information may include a fault description, corresponding reporting device information (service access number), and the like. In addition, the user can report the fault to the server through a channel such as a network service hotline (for example, number 10000) and WeChat, and the server uses the service access number when the user reports the fault to locate the reporting equipment where the service is located.

In the fault analysis process, for an ONU which can be queried by an OLT (Optical Line Terminal); if the following conditions are met: inquiring ONU with current state value as online; and until now, at the time point of fault analysis, ONU recorded by off-line or power failure exists. The corresponding ONU is considered to be a valid ONU and included in the object of this failure analysis.

S202, determining a first running state of the reporting device, and acquiring a second running state of each candidate device on the network line where the reporting device is located when the fault of the reporting device cannot be determined according to the first running state.

The operation state (including the first operation state and the second operation state) may be an online state, a power-down state, a power-off state, a network line where the device is located, and the like of the device. The server can preliminarily determine the fault of the reporting device according to the first operation state, and when the fault of the reporting device cannot be determined according to the first operation state, the server determines the fault of the reporting device by combining the operation states (second operation states) of other devices on the same network line. It should be noted that the candidate device in the embodiment of the present invention may include the reporting device itself.

Taking the optical internet as an example, the optical access network is a light splitting structure (which may be a primary structure, a secondary structure or even a multi-level structure), and if the uplink optical path or the uplink facility fails, all devices in the lower zone interrupt communication. Fig. 3 is a schematic structural diagram of a two-stage optical splitting network. The OLT is an operator device, and includes a plurality of boards, each board has a plurality of PON (passive optical Network) ports, and each PON port has a plurality of users (here, a user refers to an MDU or an OUN) as a light emitting source. The light source and the user are connected by an OBD (Optical Branching Device). The OBD may include two OBDs (in this case, called two-stage splitting, because the OBDs are used for splitting, splitting ratios of different OBDs are different), or may include one OBD (in this case, called one-stage splitting), although the number of the OBDs may be multiple. As shown in fig. 3, a PON port in the OLT has a first-stage optical splitter OBD1 below, an OBDl has two second-stage optical splitters OBD2 and OBD3 below, two optical network units ONUl and ONU2 below the second-stage optical splitter OBD2, and three optical network units ONU3, ONU4, and ONU5 below the second-stage optical splitter OBD 3. If the optical path between the PON port of the OLT and the OBDl is in fault, all the ONUs under the OBDl are in communication interruption; if the optical path between the OBDl and the OBD2 fails, both the ONUl and the ONU2 under the OBD2 are in communication interruption; similarly, if the optical path between OBDl to OBD3 fails, ONU3, ONU4, and ONU5 under OBD3 all have communication interruption.

The network line where the reporting device is located refers to the network line connected with the reporting device, and the candidate device refers to a device on the network line. Taking OUN1 in fig. 3 as an reporting device as an example, the candidate devices may be OUN1 and ONU2 under OBD2, or OUN1, ONU2, ONU3, ONU4 and ONU5 under OBD1, or all OUNs under OLT (there may be other OBDs under the OLT), and the determination of the candidate device is related to which branch or trunk the reporting device is located.

S203, determining the fault of the reporting device according to the second operation state.

Taking the fault of the optical access network as an example, the fault of the reporting device can be a MDU power-down fault, an MDU fiber-breaking fault, a pico-fiber fault, a branch optical path fault, a main optical path fault, a board card fault and an OLT offline fault. The MDU power failure fault refers to communication interruption caused by power supply interruption of the MDU equipment. The MDU fiber breakage failure refers to a communication interruption caused by a failure of a line connecting the MDU. The Fiber fault refers To communication interruption caused by The fault of a line of a last-stage OBD connection FTTH (Fiber To The Home Fiber To Home) type ONU. The branch optical path fault refers to communication interruption caused by the fault of a line between the primary OBD and the secondary OBD. The main optical path fault refers to communication interruption caused by the fault of a line between a PON port of the OLT and a primary OBD. And communication on-off caused by the fact that the board card of the OLT fails. An OLT outage (also referred to as an OLT network management outage) means that the network management cannot manage the device.

In an actual network fault processing process, due to software, hardware and the like, there may be a case where an alarm is incomplete. This will result in the system not being able to actively detect certain optical access network failures. The embodiment combines reporting information and a PON network light splitting structure after a user reports a service fault, can automatically analyze and position the fault of the optical access network, determines the fault which cannot be detected by alarm detection, effectively reduces manpower and material resources in the fault determination process, and improves the fault determination efficiency.

In one embodiment, the step of determining the first operational state of the reporting device comprises: determining whether an in-transit fault corresponding to the reporting information exists in an in-transit fault list; the on-the-road fault list comprises on-the-road faults analyzed according to the network management alarm; when there is an in-transit fault corresponding to the reporting information, determining the in-transit fault corresponding to the in-transit fault list as the fault of the reporting equipment; when the in-transit fault corresponding to the reporting information does not exist, determining whether the OLT corresponding to the reporting equipment Ping is connected or not; if the Ping is not successful, determining that the fault of the reporting equipment is an OLT pipe disconnection fault; and if Ping leads, determining a first operation state of the reporting equipment, and determining the fault of the reporting equipment according to the first operation state.

The process of determining the failure of the reporting device in comparison to the in-transit failure list may be as shown in fig. 4. The server determines whether a corresponding reporting device exists according to the service access number in the reporting information (S401). When there is no corresponding reporting device, the reporting information is discarded and is not processed (S402). When corresponding reporting equipment exists, reading unanalyzed in-transit fault records from the in-transit fault list (S403), inquiring whether corresponding in-transit fault records exist in the in-transit fault list or not according to reporting information (S404), and if so, indicating that the faults corresponding to the reporting equipment have been analyzed through network management alarm; if the fault affecting the reporting equipment is analyzed through the network management alarm, the fault analysis is not carried out (S405), and meanwhile, the fault of the reporting equipment is generated according to the corresponding in-transit fault. The generated fault may be: failure, diagnostic origin: and (4) in-transit fault, and conclusion: existing in-transit fault, fault ID: ****.

As shown in fig. 4, after comparing the reporting information with the in-transit fault list, a step of determining whether the equipment type of the reporting equipment is OUN may be further included (S406). Reporting information when the reporting device is not an ONU can be discarded (S407); when the reporting device is an OUN, corresponding reporting information is retained to analyze the failure of the reporting device based on the reporting information (S408). The processes involved in fig. 4 (the process of determining a reporting apparatus from reporting information, analyzing an in-transit failure, and judging an apparatus type) may be regarded as the main process of determining a failure of a reporting apparatus in the present invention. The main flow then proceeds to a sub-flow (shown in figure 5) that determines the failure of the reporting device. In the sub-flow, it is first determined whether the OLT can Ping (S501). If the Ping connection cannot be achieved, an OLT disconnection fault is generated (S502, at this time, the system can normally acquire the result of the command and think that the system is normally operated), at this time, no more information can be acquired to analyze and locate other faults, and the fault determination process can be ended. If the Ping connection can be achieved (S503), inquiring the OUN state (LIST-OUN _ STATUS) under the uplink PON port of the reporting equipment (S504); when the query is unsuccessful, generating a conclusion: the OLT can Ping pass, and the list OUN state fails (S505); and when the inquiry is successful, determining the fault of the reporting device according to the first running state of the reporting device. As shown in fig. 5, there is still a case of Ping abnormality in the process of determining whether the OLT can Ping. In this case, the Ping analysis may be performed again, or information that the Ping operation failed may be generated (S506) and the current fault determination process may be terminated (at this time, the system may be considered to be abnormal in operation).

It should be noted that "normal" and "abnormal" before the finally determined failure result in the drawings of the present invention refer to the operation state of the system (including the server and the reporting device). If the failure result can be generated normally (i.e., the result of the command can be acquired normally), it is "normal".

The embodiment first determines whether reporting information corresponds to an in-transit fault, and determines whether the OLT where the reporting device is located is Ping communication. The fault of the reporting equipment can be determined under the condition that in-transit faults and the OLT cannot realize Ping communication, and unnecessary steps in fault determination are reduced.

Under the condition that the OLT can Ping communication, whether the reporting equipment is online or not can be judged according to the first running state, if the reporting equipment is online, the reporting equipment is not faulty, and services can not be used due to the fact that a user cannot operate or account passwords are in a problem; if not, the failure is specifically analyzed. Thus, in one embodiment, the step of determining a fault in the reporting device based on the first operational state comprises: determining whether the reporting device is on-line according to the first operating state (S507); if the reporting device is on line, judging that the reporting device has no fault (S508); if the reporting device is not on-line, determining whether the reporting device is powered off or not according to the first running state (S509); when the reporting device is powered off, determining whether the reporting device is an MDU (S510) according to the first running state, and determining that the fault of the reporting device is an MDU power-off fault (S511) when the reporting device is the MDU, because the ONU is not at a user home, a corresponding fault conclusion needs to be generated, the ONU is maintained by a network manager, and if the reporting device is not the MDU, determining that the reporting device has no fault, the ONU is recommended to be powered on (S512); and when the reporting device is not powered down, judging that the fault of the reporting device cannot be determined according to the first operation state. When the fault of the reporting device cannot be determined according to the first operation state, acquiring a second operation state of each candidate device on a network line where the reporting device is located; and determining the fault of the reporting device according to the second operation state.

In the embodiment, the online state and the power-down state of the reporting device are determined according to the first running state, the fault of the reporting device can be determined according to the information, the fault of the reporting device is determined without combining other device states, and the determination process is simple and direct.

In one embodiment, the implementation method for determining the fault of the reporting device may be: in the effective time range, all ONU hung under the PON port where the reporting equipment under the same OLT is located are off-line and judged as main optical circuit disconnection. And secondly, all the ONUs under the same OBD are off-line in the effective time range, but the ONUs are on-line at the same PON port, and the branch optical path is judged to be broken. And thirdly, in the effective time range, if only one ONU is off-line, judging that the fault is a sheath fiber fault or an MDU fiber breakage fault. For reporting equipment without fault reporting capability, on the basis of the judgment, the fault obtained by analysis is marked as a suspected fault, and the current fault is judged as an optical circuit failure fault by mistake probably due to power failure.

And the ONU which has the power failure alarm reporting record within a period of time is considered to have the capability of reporting the fault. And the ONU which is in the LOS state and is simultaneously off-line or powered off in a plurality of ONUs under the same PON port is considered to have no fault reporting capability.

According to the embodiment, the fault corresponding to the reporting equipment can be accurately determined according to the first operation state of the reporting equipment and the second operation state of the candidate equipment, so that when the fault which cannot be detected through alarming exists, manual troubleshooting and fault point positioning are not needed.

Here, the effective time is defined as follows: the OFF-line or power-down TIME of the reporting device is taken as a fault analysis TIME point (LAST-OFF _ TIME, T), and 10 minutes (marked as T +10, or other TIME except 10 minutes) after the fault analysis TIME point is defined as the effective TIME of the fault analysis. The candidate devices which are off-line in the effective time are considered to be off-line simultaneously with the reporting device; the remaining candidate devices are deemed to have not been affected by the failure of the reporting device.

Further, an interruption of the uplink optical path may cause all OUNs in the downlink to go offline simultaneously. Therefore, when all OUNs (candidate devices) under the OBD of the reporting device are offline (note that offline may be caused by power failure or line disconnection), the offline within 10 minutes from T is approximately considered to be caused by the same fault as the reporting device (for example, if a device is offline, but is offline after 30 minutes of T, the reason for the offline fault of the reporting device is not the same as the offline fault of the device, and when the reporting device is offline, the device is online. The following analysis relies on this logic, if there is an online candidate device (a power-down alarm is sent to the OLT by the reporting device, which indicates that normal communication is performed from the reporting device to the PON port, and then indicates that the last-stage OBD is above normal) which is offline after T +10 or due to power-down in the device hung under the uplink optical path, then the uplink optical path is not the cause of the communication fault of the reporting device.

In one embodiment, the step of determining a fault in the reporting device based on the second operational state includes: determining whether an online candidate device exists under the OBD port where the reporting device is located according to the second operation state (S513), and when the online candidate device exists under the OBD where the reporting device is located, determining a fault of the reporting device according to the type of the reporting device (S514, wherein a process of determining the fault of the reporting device according to the type of the reporting device may be referred to as an MDU fiber breaking/skin fiber sub-process); when no online candidate device exists under the OBD where the reporting device is located, determining whether an online candidate device exists under the PON port where the reporting device is located according to the second operation state (S515), determining whether a candidate device which is offline after the reporting device is offline exists under the PON port where the reporting device is located (S516), and when the online candidate device does not exist, determining a fault of the reporting device according to the state of each branch of the network line (S517), where a process of determining the fault of the reporting device according to the state of each branch of the network line may be referred to as a main fault analysis sub-flow); if so, determining whether a candidate device which is offline after the reporting device is offline for more than a preset time period exists under the OBD where the reporting device is located according to the second operation state (S518, S519); when a candidate device which is offline after the existence of a preset time period is exceeded, determining the fault of the reporting device according to the type of the reporting device (S520); when the candidate devices which are off-line only after exceeding the preset time period do not exist, determining the number of first candidate devices which are powered down in the preset effective time under the OBD (S521), and determining the fault of the reporting device according to the number of the first candidate devices.

The preset time period may refer to the aforementioned 10 minutes, and of course, the preset time period may be other time periods.

If the PON port has a secondary OBD, it is determined that a main optical path fault, a branch optical path fault, or a fiber fault is all possible according to the logic described above. However, if a primary OBD is provided below the PON port and only one secondary OBD is hung below the primary OBD, it is not determined that the primary optical path fails and only a unique failure is output; if only one OUN exists below the PON port, the fault of the main optical path and the fault of the branch optical path cannot be judged. Based on this, the step of determining the fault of the reporting device according to the first candidate device number comprises: when the first candidate device number is greater than or equal to 1, determining the fault of the reporting device according to the type of the reporting device (S522); when the first candidate device number is equal to 0, determining a fault of the reporting device according to a second candidate device number offline in the valid time under the OBD (S523, where a process of determining a fault of the reporting device according to the second candidate device number offline in the valid time under the OBD may be referred to as a branch fault analysis sub-process).

Wherein, S517 may be referred to as a main failure analysis sub-flow. The implementation process of the main fault analysis sub-flow can be as shown in fig. 6. The method specifically comprises the following steps: determining the number of third candidate devices powered down in the effective time under the PON port (S601); when the third candidate device number is greater than or equal to 1, determining the fault of the reporting device according to the type of the reporting device (S602); when the third candidate device number is equal to 0, determining whether the candidate devices offline within the valid time under the PON port are under the same OBD (S603); if the candidate devices are in the same OBD, determining the fault of the reporting device according to the number of second candidate devices which are off-line in the effective time under the OBD (the same OBD in which the candidate devices are located) (S604); if the number of the fourth candidate devices of the PON port which are off-line in the effective time is not in the same OBD (S605), when the number of the fourth candidate devices is larger than 1, the fault of the reporting device is determined to be a main light path fault (S606), and when the number of the fourth candidate devices is equal to 1, the fault of the reporting device is determined according to the type of the reporting device (S607).

S523 and S604 may be referred to as branch fault analysis sub-flows. The implementation process of the branch fault analysis sub-flow may be as shown in fig. 7, specifically: determining a second candidate device number (S701) of offline reporting devices in the effective time under the OBD (on-board diagnostics) of the reporting devices, and determining that the faults of the reporting devices are branch optical path faults (S702) when the second candidate device number is larger than 1; when the second candidate devices number is equal to 1, determining the fault of the reporting device according to the type of the reporting device (S703).

S514, S520, S522, S602, S607, and S703 may all be referred to as MDU fiber break/sheath sub-flow. The implementation process of the MDU fiber breaking/splitting sub-flow may be as shown in fig. 8, and specifically includes: judging the type of the reporting equipment (S801), and when the reporting equipment is an MDU, determining that the fault of the reporting equipment is an MDU fiber-breaking fault (S802); when the reporting device is not an MDU, it is determined that the failure of the reporting device is a sheath failure (S803).

According to the embodiment, the faults of the reporting device under different conditions are analyzed according to the running states of all devices on the branch and the trunk where the reporting device is located, the possibility of various faults is included, and the fault of the reporting device can be accurately and effectively determined.

It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present invention is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present invention.

Based on the same idea as the determination method of the failure in the above-described embodiment, the present invention also provides a determination device of the failure, which can be used to execute the above-described determination method of the failure. For convenience of explanation, the structure diagram of the embodiment of the fault determination device only shows the part related to the embodiment of the present invention, and those skilled in the art will understand that the illustrated structure does not constitute a limitation of the device, and may include more or less components than those illustrated, or combine some components, or arrange different components.

As shown in fig. 9, the fault determining apparatus includes a reporting device determining module 901, an operating state determining module 902, and a fault determining module 903, which are described in detail as follows:

the reporting device determining module 901 is configured to determine, when receiving the reporting information, a reporting device corresponding to the reporting information.

An operation state determining module 902, configured to determine a first operation state of the reporting apparatus, and obtain a second operation state of each candidate apparatus on the network line where the reporting apparatus is located when the failure of the reporting apparatus cannot be determined according to the first operation state.

And a fault determining module 903, configured to determine a fault of the reporting device according to the second operating state.

According to the embodiment, the active detection and the positioning of the network access fault can be realized according to the triggering of the reporting information, the fault which cannot be detected by alarm detection is determined, and the determining efficiency of the network access fault is effectively improved.

In one embodiment, the operational status determination module 902 includes: the on-road fault judgment submodule is used for determining whether on-road faults corresponding to the reporting information exist in an on-road fault list; the on-the-road fault list comprises on-the-road faults analyzed according to the network management alarm; an in-transit fault determining submodule, configured to determine, when there is an in-transit fault corresponding to the reporting information, a corresponding in-transit fault in an in-transit fault list as a fault of the reporting apparatus; the Ping on judging submodule is used for determining whether the OLT corresponding to the reporting equipment is Ping on when the in-transit fault corresponding to the reporting information does not exist; if the Ping is not successful, determining that the fault of the reporting equipment is an OLT pipe disconnection fault; and if Ping leads, determining a first operation state of the reporting equipment, and determining the fault of the reporting equipment according to the first operation state.

In one embodiment, the operational status determination module 902 includes: the first online judgment sub-module is used for determining whether online candidate equipment exists under the OBD where the reporting equipment is located according to the second running state; when an online candidate device exists under the OBD where the reporting device is located, determining the fault of the reporting device according to the type of the reporting device; the second online judgment sub-module is used for determining whether an online candidate device exists under the PON port where the reporting device is located according to the second running state when the online candidate device does not exist under the OBD where the reporting device is located; the trunk fault analysis sub-module is used for determining the fault of the reporting equipment according to the state of each branch of the network line when no online candidate equipment exists under the PON port where the reporting equipment is located; the state judgment sub-module is used for determining whether candidate equipment which is offline after the reporting equipment is offline exists under the OBD of the reporting equipment according to the second running state when the candidate equipment which is online exists under the PON port of the reporting equipment; when candidate equipment which is offline after a preset time period exists, determining the fault of the reporting equipment according to the type of the reporting equipment; when the candidate equipment which is offline after the time period exceeds the preset time period does not exist, determining the number of first candidate equipment which is powered down in the preset effective time under the OBD, and determining the fault of the reporting equipment according to the number of the first candidate equipment.

In one embodiment, the offline state determining sub-module includes: a first fault determining unit, configured to determine a fault of the reporting device according to the type of the reporting device when the number of the first candidate devices is greater than or equal to 1; and the second fault determining unit is used for determining the fault of the reporting device according to the number of second candidate devices which are off-line in the effective time under the OBD when the number of the first candidate devices is equal to 0.

In one embodiment, the backbone failure analysis submodule includes: a device number determining unit, configured to determine a third candidate device number of the PON port in power down within the valid time; a third fault determining unit, configured to determine, when the number of the third candidate devices is greater than or equal to 1, a fault of the reporting device according to the type of the reporting device; a fourth fault determining unit, configured to determine, when the number of the third candidate devices is equal to 0, whether the candidate devices offline within the valid time under the PON port are under the same OBD; if the reporting equipment is in the same OBD, determining the fault of the reporting equipment according to the number of second candidate equipment which are offline in the effective time under the OBD; and if the number of the fourth candidate devices of the PON port which are off-line in the effective time is not in the same OBD, determining that the fault of the reporting device is a main optical path fault when the number of the fourth candidate devices is larger than 1.

In one embodiment, further comprising: a fifth fault determining unit, configured to determine that the fault of the reporting apparatus is a branch optical path fault when the number of the second candidate apparatuses is greater than 1; and when the number of the second candidate devices is equal to 1, determining the fault of the reporting device according to the type of the reporting device.

In one embodiment, further comprising: a sixth fault determining unit, configured to determine that the fault of the reporting device is an MDU fiber disconnection fault when the reporting device is an MDU; and when the reporting equipment is not the MDU, determining that the fault of the reporting equipment is a sheath fiber fault.

It should be noted that, the fault determining apparatus of the present invention corresponds to the fault determining method of the present invention one to one, and the technical features and the beneficial effects thereof described in the embodiments of the fault determining method are all applicable to the embodiments of the fault determining apparatus, and specific contents may refer to the description in the embodiments of the method of the present invention, which is not described herein again, and thus, the present invention is stated herein.

In addition, in the embodiment of the fault determination apparatus illustrated above, the logical division of each program module is only an example, and in practical applications, the above function distribution may be performed by different program modules according to needs, for example, due to the configuration requirements of corresponding hardware or the convenience of implementation of software, that is, the internal structure of the fault determination apparatus is divided into different program modules to perform all or part of the above described functions.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 10. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing reporting information, in-transit fault lists and other data. The network interface of the computer device is used for connecting and communicating with an external OUN terminal through a network. The computer program is executed by a processor to implement a method of fault determination.

Those skilled in the art will appreciate that the architecture shown in fig. 10 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program: when receiving reporting information, determining reporting equipment corresponding to the reporting information; determining a first operation state of the reporting device, and acquiring a second operation state of each candidate device on a network line where the reporting device is located when the fault of the reporting device cannot be determined according to the first operation state; and determining the fault of the reporting equipment according to the second operation state.

In one embodiment, the processor, when executing the computer program, further performs the steps of: determining whether an in-transit fault corresponding to the reporting information exists in an in-transit fault list; the on-the-road fault list comprises on-the-road faults analyzed according to the network management alarm; when there is an in-transit fault corresponding to the reporting information, determining the in-transit fault corresponding to the in-transit fault list as the fault of the reporting equipment; when the in-transit fault corresponding to the reporting information does not exist, determining whether the OLT corresponding to the reporting equipment Ping is connected or not; if the Ping is not successful, determining that the fault of the reporting equipment is an OLT pipe disconnection fault; and if Ping leads, determining a first operation state of the reporting equipment, and determining the fault of the reporting equipment according to the first operation state.

In one embodiment, the processor, when executing the computer program, further performs the steps of: determining whether online candidate equipment exists under the OBD where the reporting equipment is located according to the second running state; when an online candidate device exists under the OBD where the reporting device is located, determining the fault of the reporting device according to the type of the reporting device; when no online candidate device exists under the OBD where the reporting device is located, determining whether an online candidate device exists under the PON port where the reporting device is located according to the second running state; when no online candidate equipment exists under the PON port where the reporting equipment is located, determining the fault of the reporting equipment according to the state of each branch of the network line; when an online candidate device exists under the PON port where the reporting device is located, determining whether the candidate device which is offline after the reporting device is offline exists under the OBD where the reporting device is located according to the second running state; when candidate equipment which is offline after a preset time period exists, determining the fault of the reporting equipment according to the type of the reporting equipment; when the candidate equipment which is offline after the time period exceeds the preset time period does not exist, determining the number of first candidate equipment which is powered down in the preset effective time under the OBD, and determining the fault of the reporting equipment according to the number of the first candidate equipment.

In one embodiment, the processor, when executing the computer program, further performs the steps of: when the number of the first candidate devices is more than or equal to 1, determining the fault of the reporting device according to the type of the reporting device; and when the first candidate equipment quantity is equal to 0, determining the fault of the reporting equipment according to a second candidate equipment quantity offline in the effective time under the OBD.

In one embodiment, the processor, when executing the computer program, further performs the steps of: determining the number of third candidate devices with power failure in the effective time under the PON port; when the number of the third candidate devices is more than or equal to 1, determining the fault of the reporting device according to the type of the reporting device; when the number of the third candidate devices is equal to 0, determining whether the candidate devices offline within the valid time under the PON port are under the same OBD; if the reporting equipment is in the same OBD, determining the fault of the reporting equipment according to the number of second candidate equipment which are offline in the effective time under the OBD; and if the number of the fourth candidate devices of the PON port which are off-line in the effective time is not in the same OBD, determining that the fault of the reporting device is a main optical path fault when the number of the fourth candidate devices is larger than 1.

In one embodiment, the processor, when executing the computer program, further performs the steps of: when the number of the second candidate devices is larger than 1, determining that the failure of the reporting device is a branch optical path failure; and when the number of the second candidate devices is equal to 1, determining the fault of the reporting device according to the type of the reporting device.

In one embodiment, the processor, when executing the computer program, further performs the steps of: when the reporting equipment is an MDU, determining that the fault of the reporting equipment is an MDU fiber breakage fault; and when the reporting equipment is not the MDU, determining that the fault of the reporting equipment is a sheath fiber fault.

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: when receiving reporting information, determining reporting equipment corresponding to the reporting information; determining a first operation state of the reporting device, and acquiring a second operation state of each candidate device on a network line where the reporting device is located when the fault of the reporting device cannot be determined according to the first operation state; and determining the fault of the reporting equipment according to the second operation state.

In one embodiment, the computer program when executed by the processor further performs the steps of: determining whether an in-transit fault corresponding to the reporting information exists in an in-transit fault list; the on-the-road fault list comprises on-the-road faults analyzed according to the network management alarm; when there is an in-transit fault corresponding to the reporting information, determining the in-transit fault corresponding to the in-transit fault list as the fault of the reporting equipment; when the in-transit fault corresponding to the reporting information does not exist, determining whether the OLT corresponding to the reporting equipment Ping is connected or not; if the Ping is not successful, determining that the fault of the reporting equipment is an OLT pipe disconnection fault; and if Ping leads, determining a first operation state of the reporting equipment, and determining the fault of the reporting equipment according to the first operation state.

In one embodiment, the computer program when executed by the processor further performs the steps of: determining whether online candidate equipment exists under the OBD where the reporting equipment is located according to the second running state; when an online candidate device exists under the OBD where the reporting device is located, determining the fault of the reporting device according to the type of the reporting device; when no online candidate device exists under the OBD where the reporting device is located, determining whether an online candidate device exists under the PON port where the reporting device is located according to the second running state; when no online candidate equipment exists under the PON port where the reporting equipment is located, determining the fault of the reporting equipment according to the state of each branch of the network line; when an online candidate device exists under the PON port where the reporting device is located, determining whether the candidate device which is offline after the reporting device is offline exists under the OBD where the reporting device is located according to the second running state; when candidate equipment which is offline after a preset time period exists, determining the fault of the reporting equipment according to the type of the reporting equipment; when the candidate equipment which is offline after the time period exceeds the preset time period does not exist, determining the number of first candidate equipment which is powered down in the preset effective time under the OBD, and determining the fault of the reporting equipment according to the number of the first candidate equipment.

In one embodiment, the computer program when executed by the processor further performs the steps of: when the number of the first candidate devices is more than or equal to 1, determining the fault of the reporting device according to the type of the reporting device; and when the first candidate equipment quantity is equal to 0, determining the fault of the reporting equipment according to a second candidate equipment quantity offline in the effective time under the OBD.

In one embodiment, the computer program when executed by the processor further performs the steps of: determining the number of third candidate devices with power failure in the effective time under the PON port; when the number of the third candidate devices is more than or equal to 1, determining the fault of the reporting device according to the type of the reporting device; when the number of the third candidate devices is equal to 0, determining whether the candidate devices offline within the valid time under the PON port are under the same OBD; if the reporting equipment is in the same OBD, determining the fault of the reporting equipment according to the number of second candidate equipment which are offline in the effective time under the OBD; and if the number of the fourth candidate devices of the PON port which are off-line in the effective time is not in the same OBD, determining that the fault of the reporting device is a main optical path fault when the number of the fourth candidate devices is larger than 1.

In one embodiment, the computer program when executed by the processor further performs the steps of: when the number of the second candidate devices is larger than 1, determining that the failure of the reporting device is a branch optical path failure; and when the number of the second candidate devices is equal to 1, determining the fault of the reporting device according to the type of the reporting device.

In one embodiment, the computer program when executed by the processor further performs the steps of: when the reporting equipment is an MDU, determining that the fault of the reporting equipment is an MDU fiber breakage fault; and when the reporting equipment is not the MDU, determining that the fault of the reporting equipment is a sheath fiber fault.

It will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by a computer program, which is stored in a computer readable storage medium and sold or used as a stand-alone product. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.

It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.

The terms "comprises" and "comprising," and any variations thereof, of embodiments of the present invention are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or (module) elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-described examples merely represent several embodiments of the present invention and should not be construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method of fault determination, comprising the steps of:

when receiving reporting information, determining reporting equipment corresponding to the reporting information;

determining a first operation state of the reporting device, and acquiring a second operation state of each candidate device on a network line where the reporting device is located when the fault of the reporting device cannot be determined according to the first operation state;

determining a fault of the reporting device according to the second operating state;

the step of determining a fault in the reporting device based on the second operating condition includes:

determining whether online candidate equipment exists under the OBD where the reporting equipment is located according to the second running state;

when an online candidate device exists under the OBD where the reporting device is located, determining the fault of the reporting device according to the type of the reporting device;

when no online candidate device exists under the OBD where the reporting device is located, determining whether an online candidate device exists under the PON port where the reporting device is located according to the second running state;

when no online candidate equipment exists under the PON port where the reporting equipment is located, determining the fault of the reporting equipment according to the state of each branch of the network line;

when an online candidate device exists under the PON port where the reporting device is located, determining whether the candidate device which is offline after the reporting device is offline exists under the OBD where the reporting device is located according to the second running state;

when candidate equipment which is offline after a preset time period exists, determining the fault of the reporting equipment according to the type of the reporting equipment;

when the candidate equipment which is offline after the time period exceeds the preset time period does not exist, determining the number of first candidate equipment which is powered down in the preset effective time under the OBD, and determining the fault of the reporting equipment according to the number of the first candidate equipment.

2. The method of claim 1, wherein the step of determining the first operational state of the reporting device comprises:

determining whether an in-transit fault corresponding to the reporting information exists in an in-transit fault list; the on-the-road fault list comprises on-the-road faults analyzed according to the network management alarm;

when there is an in-transit fault corresponding to the reporting information, determining the in-transit fault corresponding to the in-transit fault list as the fault of the reporting equipment;

when the in-transit fault corresponding to the reporting information does not exist, determining whether the OLT corresponding to the reporting equipment Ping is connected or not;

if the Ping is not successful, determining that the fault of the reporting equipment is an OLT pipe disconnection fault;

and if Ping leads, determining a first operation state of the reporting equipment, and determining the fault of the reporting equipment according to the first operation state.

3. The method of claim 1, wherein the step of determining the fault of the reporting device according to the first number of candidate devices comprises:

when the number of the first candidate devices is more than or equal to 1, determining the fault of the reporting device according to the type of the reporting device;

and when the first candidate equipment quantity is equal to 0, determining the fault of the reporting equipment according to a second candidate equipment quantity offline in the effective time under the OBD.

4. The method according to claim 1, wherein the step of determining the failure of the reporting apparatus based on the state of each branch of the network line includes:

determining the number of third candidate devices with power failure in the effective time under the PON port;

when the number of the third candidate devices is more than or equal to 1, determining the fault of the reporting device according to the type of the reporting device;

when the number of the third candidate devices is equal to 0, determining whether the candidate devices offline within the valid time under the PON port are under the same OBD;

if the reporting equipment is in the same OBD, determining the fault of the reporting equipment according to the number of second candidate equipment which are offline in the effective time under the OBD;

if the number of the fourth candidate devices of the PON port which are off-line in the effective time is not in the same OBD, determining the fault of the reporting device according to the type of the reporting device when the number of the fourth candidate devices is equal to 1, and determining the fault of the reporting device as the fault of the main optical path when the number of the fourth candidate devices is greater than 1.

5. The method of claim 3 or 4, wherein the step of determining the fault of the reporting device according to the second number of candidate devices offline in the validity time under the OBD comprises:

when the number of the second candidate devices is larger than 1, determining that the failure of the reporting device is a branch optical path failure;

and when the number of the second candidate devices is equal to 1, determining the fault of the reporting device according to the type of the reporting device.

6. The method of determining a fault according to any one of claims 2 to 4, wherein the step of determining a fault of the reporting device according to the type of the reporting device includes:

when the reporting equipment is an MDU, determining that the fault of the reporting equipment is an MDU fiber breakage fault; and when the reporting equipment is not the MDU, determining that the fault of the reporting equipment is a sheath fiber fault.

7. A fault determination apparatus, comprising:

the reporting device determining module is used for determining the reporting device corresponding to the reporting information when the reporting information is received;

the operation state determining module is used for determining a first operation state of the reporting device, and acquiring a second operation state of each candidate device on a network line where the reporting device is located when the fault of the reporting device cannot be determined according to the first operation state;

the fault determining module is used for determining the fault of the reporting equipment according to the second running state;

a fault determination module comprising: the first online judgment sub-module is used for determining whether online candidate equipment exists under the OBD where the reporting equipment is located according to the second running state; when an online candidate device exists under the OBD where the reporting device is located, determining the fault of the reporting device according to the type of the reporting device; the second online judgment sub-module is used for determining whether an online candidate device exists under the PON port where the reporting device is located according to the second running state when the online candidate device does not exist under the OBD where the reporting device is located; the trunk fault analysis sub-module is used for determining the fault of the reporting equipment according to the state of each branch of the network line when no online candidate equipment exists under the PON port where the reporting equipment is located; the state judgment sub-module is used for determining whether candidate equipment which is offline after the reporting equipment is offline exists under the OBD of the reporting equipment according to the second running state when the candidate equipment which is online exists under the PON port of the reporting equipment; when candidate equipment which is offline after a preset time period exists, determining the fault of the reporting equipment according to the type of the reporting equipment; when the candidate equipment which is offline after the time period exceeds the preset time period does not exist, determining the number of first candidate equipment which is powered down in the preset effective time under the OBD, and determining the fault of the reporting equipment according to the number of the first candidate equipment.

8. The fault determination device according to claim 7, wherein the operation state determination module includes: the on-road fault judgment submodule is used for determining whether on-road faults corresponding to the reporting information exist in an on-road fault list; the on-the-road fault list comprises on-the-road faults analyzed according to the network management alarm; an in-transit fault determining submodule, configured to determine, when there is an in-transit fault corresponding to the reporting information, a corresponding in-transit fault in an in-transit fault list as a fault of the reporting apparatus; the Ping on judging submodule is used for determining whether the OLT corresponding to the reporting equipment is Ping on when the in-transit fault corresponding to the reporting information does not exist; if the Ping is not successful, determining that the fault of the reporting equipment is an OLT pipe disconnection fault; and if Ping leads, determining a first operation state of the reporting equipment, and determining the fault of the reporting equipment according to the first operation state.

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 6 are implemented by the processor when executing the computer program.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.