Passenger-dedicated line fault root cause positioning method and device, electronic equipment and storage medium

Abstract

The application relates to the communication technical field and provides a passenger special line fault root cause positioning method and device, electronic equipment and a storage medium, the method comprises the following steps: receiving a fault alarm of a passenger special line, determining the service type of the passenger special line; according to the service type, determining a target fault root cause positioning strategy; and according to the target fault root cause positioning strategy, positioning the fault root cause of the passenger special line. After receiving the fault alarm of the passenger special line, the service type of the passenger special line can be determined, so that the corresponding fault root cause positioning strategy can be further determined as the target fault root cause positioning strategy according to the service type, and then the fault root cause of the passenger special line can be quickly and accurately positioned according to the target fault root cause positioning strategy, thereby avoiding the problem that the positioning speed is slow and the accuracy is insufficient caused by fault analysis by the on-duty personnel, and the fault root cause positioning efficiency of the passenger special line can be improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a method, apparatus, electronic device, and storage medium for locating the root cause of faults in dedicated customer lines. Background Technology

[0002] Private line services are a significant revenue source for the telecommunications industry, and after-sales service is subject to clear time limits based on Service Level Agreements (SLAs). However, the monitoring room handles a massive volume of traffic, and currently, upon receiving a fault alarm, on-duty personnel are required to analyze the data to identify the root cause. However, due to the limitations of manual processing, fault analysis by on-duty personnel is slow and inaccurate, resulting in low efficiency in locating the root cause of private line faults. Summary of the Invention

[0003] This application provides a method, apparatus, electronic device, and storage medium for locating the root cause of faults in passenger dedicated lines, in order to solve the problem of low efficiency in locating the root cause of faults in passenger dedicated lines.

[0004] In a first aspect, embodiments of this application provide a method for locating the root cause of faults in a dedicated passenger transport line, including:

[0005] Upon receiving a fault alarm from the dedicated customer service line, determine the service type of the dedicated customer service line.

[0006] Based on the business type, determine the target fault root cause localization strategy;

[0007] Based on the target fault root cause localization strategy, locate the root cause of the fault in the customer service line.

[0008] In one embodiment, the target fault root cause localization strategy includes a first root cause localization strategy; the step of localizing the root cause of the fault in the dedicated passenger line according to the target fault root cause localization strategy includes:

[0009] If the target fault root cause localization strategy is the first root cause localization strategy, then determine whether the customer service line is in an engineering state. If it is in an engineering state, then output the fault root cause of the customer service line based on the engineering state.

[0010] If it is not in the engineering state, determine whether there are alarms in the starting end network element / ending end network element of the customer-accessible dedicated line;

[0011] If there is an alarm at the starting end network element / ending end network element, the root cause of the fault of the dedicated customer line is output based on the alarm at the starting end network element / ending end network element.

[0012] If there are no alarms at the starting / ending network element, then determine whether there are alarms at intermediate network elements in the dedicated customer line;

[0013] If an intermediate network element alarm exists, the root cause of the fault in the dedicated customer line will be output based on the intermediate network element alarm.

[0014] If no intermediate network element alarm is found, then it is determined whether the dedicated customer line has a service router network element alarm.

[0015] If a service router network element alarm exists, the root cause of the fault in the dedicated customer line will be output based on the service router network element alarm.

[0016] If there are no alarms in the service router network element, the root cause of the fault in the dedicated customer line is output as an abnormality on the customer side.

[0017] In one embodiment, the target fault root cause localization strategy includes a second root cause localization strategy; the step of localizing the root cause of the fault in the dedicated passenger line according to the target fault root cause localization strategy further includes:

[0018] If the target fault root cause localization strategy is the second root cause localization strategy, then determine whether the customer service line is in an engineering state. If it is in an engineering state, then output the fault root cause of the customer service line based on the engineering state.

[0019] If the line is not in an engineering state, determine whether the outage of the fiber optic terminal equipment is caused by a power failure; if the outage of the fiber optic terminal equipment is caused by a power failure, output the root cause of the fault of the line.

[0020] If the outage of the fiber optic line terminal equipment is not caused by a power failure, then determine whether the outage of the fiber optic line terminal equipment is caused by a hardware failure of the fiber optic line terminal equipment; if the outage is caused by a hardware failure of the fiber optic line terminal equipment, then output the root cause of the fault of the fiber optic line terminal equipment.

[0021] If the outage of the fiber optic line terminal equipment is not caused by a hardware failure, then determine whether the power failure of the fiber optic line terminal equipment board is causing undervoltage. If the power failure is causing undervoltage, then output the root cause of the fault of the fiber optic line terminal equipment.

[0022] If the undervoltage of the fiber optic line terminal equipment board is not caused by a power failure, then it is determined whether there is a hardware failure of the fiber optic line terminal equipment in the customer service line; if there is a hardware failure of the fiber optic line terminal equipment, then the root cause of the failure of the customer service line is output.

[0023] If there is no hardware fault in the fiber optic line terminal equipment, then determine whether there is a fiber optic cable fault in the customer service line; if there is a fiber optic cable fault in the fiber optic line terminal equipment, then output the root cause of the fault in the customer service line.

[0024] If there is no optical cable fault in the fiber optic line terminal equipment, then determine whether the power outage of the optical network user terminal equipment is caused by a regional power outage; if the power outage of the optical network user terminal equipment is caused by a regional power outage, then output the root cause of the fault in the customer dedicated line.

[0025] If a non-regional power outage causes a power failure in the optical network user terminal equipment, then determine whether there is a dedicated line segment alarm on the dedicated customer line; if there is a dedicated line segment alarm, then output the root cause of the fault on the dedicated customer line.

[0026] If there is no alarm on the dedicated line segment, then determine whether there is an abnormal optical power of the fiber optic line terminal equipment on the customer dedicated line; if there is an abnormal optical power of the fiber optic line terminal equipment, then output the root cause of the fault of the customer dedicated line.

[0027] If there is no optical power abnormality in the fiber optic line terminal equipment, then determine whether there is a service router network element alarm in the dedicated customer line; if there is a service router network element alarm, then output the root cause of the fault in the dedicated customer line based on the service router network element alarm.

[0028] If there are no alarms in the service router network element, the root cause of the fault in the dedicated customer line is output as an abnormality on the customer side.

[0029] In one embodiment, the target fault root cause localization strategy includes a third root cause localization strategy; the step of locating the root cause of the fault in the dedicated passenger line according to the target fault root cause localization strategy further includes:

[0030] If the target fault root cause localization strategy is the third root cause localization strategy, then determine whether the customer service line is in an engineering state. If it is in an engineering state, then output the fault root cause of the customer service line based on the engineering state.

[0031] If it is not in the engineering state, determine whether there are alarms in the starting end network element / ending end network element of the customer-accessible dedicated line;

[0032] If there is an alarm at the starting end network element / ending end network element, the root cause of the fault of the dedicated customer line is output based on the alarm at the starting end network element / ending end network element.

[0033] If there are no alarms at the starting / ending network element, then determine whether there are alarms at intermediate network elements in the dedicated customer line;

[0034] If an intermediate network element alarm exists, the root cause of the fault in the dedicated customer line will be output based on the intermediate network element alarm.

[0035] If there is no intermediate network element alarm, the root cause of the fault in the dedicated customer line is output as an abnormality on the customer side.

[0036] In one embodiment, the starting / ending network element alarm and the intermediate network element alarm each include at least one of the following: disconnection alarm, environmental monitoring alarm, optical signal loss alarm, single board alarm, optical power alarm, and bit error alarm.

[0037] In one embodiment, determining the service type of the customer acquisition line includes:

[0038] Obtain the service identifier of the customer acquisition line;

[0039] The service type of the dedicated customer line is determined based on the first association information between the service identifier and the service type, as well as the service identifier of the dedicated customer line; the service type is an Internet dedicated line, an Internet gigabit passive optical network dedicated line, or a non-Internet dedicated line.

[0040] In one embodiment, determining the target fault root cause localization strategy based on the service type includes:

[0041] Obtain the second correlation information between the fault root cause localization strategy and the business type of the dedicated customer line;

[0042] Based on the second association information and the business type, a target fault root cause localization strategy is determined from each preset fault root cause localization strategy.

[0043] Secondly, embodiments of this application provide a fault root cause location device for a passenger dedicated line, comprising:

[0044] The receiving module is used to receive fault alarms from the dedicated customer line and determine the service type of the dedicated customer line.

[0045] The determination module is used to determine the target fault root cause localization strategy based on the business type.

[0046] The positioning module is used to locate the root cause of the fault in the customer service line according to the target fault root cause positioning strategy.

[0047] Thirdly, embodiments of this application provide an electronic device, including a processor and a memory storing a computer program, wherein the processor executes the program to implement the root cause localization method for customer dedicated line faults as described in the first aspect.

[0048] Fourthly, embodiments of this application provide a storage medium, which is a computer-readable storage medium including a computer program. When the computer program is executed by a processor, it implements the root cause localization method for customer dedicated line faults as described in the first aspect.

[0049] The enterprise dedicated line fault root cause localization method, device, electronic device, and storage medium provided in this application embodiment can determine the service type of the enterprise dedicated line after receiving a fault alarm. This allows for the determination of a corresponding fault root cause localization strategy as a target fault root cause localization strategy based on the service type. Subsequently, the root cause of the enterprise dedicated line fault can be quickly and accurately located based on the target fault root cause localization strategy. This avoids the problem of slow localization speed and insufficient accuracy caused by fault analysis by on-duty personnel, thereby improving the efficiency of enterprise dedicated line fault root cause localization. Attached Figure Description

[0050] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0051] Figure 1 This is a flowchart illustrating the root cause localization method for customer dedicated line faults provided in this application embodiment;

[0052] Figure 2 This is one of the flowcharts illustrating the root cause of a fault in the customer-dedicated line fault location method provided in this application embodiment;

[0053] Figure 3 This is the second flowchart illustrating the root cause of a fault in the customer-dedicated line fault location method provided in this application embodiment;

[0054] Figure 4 This is the third flowchart illustrating the root cause of a fault in the customer-dedicated line fault location method provided in this application embodiment;

[0055] Figure 5 This is a functional module diagram of an embodiment of the customer-dedicated line fault root cause location device of this application;

[0056] Figure 6 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0057] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0058] The following describes in detail the root cause localization method, apparatus, electronic equipment and storage medium for customer dedicated line faults provided in this application, with reference to the embodiments.

[0059] Based on this, this application provides a method for locating the root cause of faults in a dedicated passenger line.

[0060] Figure 1 This is one of the flowcharts illustrating the root cause localization method for customer service line faults provided in this application embodiment. (Refer to...) Figure 1 This application provides a method for locating the root cause of faults in a dedicated passenger line, which may include:

[0061] Step 100: Receive a fault alarm from the customer service dedicated line and determine the service type of the customer service dedicated line;

[0062] It should be noted that the execution subject of the customer dedicated line fault root cause localization method provided in this application embodiment can be a computer device, such as a mobile phone, tablet computer, laptop computer, handheld computer, vehicle electronic device, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc.

[0063] In this application, the enterprise customer dedicated line is a dedicated network connection service provided by an operator, which is typically used to meet the high-speed and secure network transmission needs of enterprise customers.

[0064] The service types of corporate leased lines in this application may include Internet leased lines, Gigabit Passive Optical Network (GPON) leased lines, and non-Internet leased lines.

[0065] Non-Internet leased lines can be further divided into non-Internet leased lines and non-Internet GPON leased lines.

[0066] The fault alarms received in this application for the dedicated customer lines can be obtained through network management monitoring or customer fault reporting.

[0067] In this application, each customer-dedicated line can be assigned a service identifier, and each service identifier can represent a service type.

[0068] Step 200: Determine the target fault root cause localization strategy based on the business type;

[0069] After obtaining the business type of the customer-dedicated line, the root cause location strategy corresponding to the current customer-dedicated line's business type can be determined as the target root cause location strategy based on the correlation between the business type and the root cause location strategy.

[0070] The fault root cause localization strategy pre-defined in this application may include at least a first fault root cause localization strategy, a second fault root cause localization strategy, and a third fault root cause localization strategy.

[0071] Among them, the first fault root cause location strategy can be the fault root cause location strategy for Internet leased lines; the second fault root cause location strategy can be the fault root cause location strategy for Internet GPON leased lines; and the third fault root cause location strategy can be the fault root cause location strategy for non-Internet leased lines.

[0072] Therefore, the target fault root cause localization strategy can be a first fault root cause localization strategy, a second fault root cause localization strategy, or a third fault root cause localization strategy.

[0073] Step 300: Locate the root cause of the fault in the customer service line according to the target fault root cause localization strategy.

[0074] After obtaining the target fault root cause localization strategy, this application can execute the target fault root cause localization strategy to locate the fault root cause of the dedicated passenger line and obtain the fault root cause of the dedicated passenger line.

[0075] The fault root cause localization method for customer dedicated lines provided in this application embodiment can determine the service type of the customer dedicated line after receiving a fault alarm. This allows for the determination of a corresponding fault root cause localization strategy as a target fault root cause localization strategy based on the service type. Then, based on the target fault root cause localization strategy, the fault root cause of the customer dedicated line can be quickly and accurately located. This avoids the problem of slow localization speed and insufficient accuracy caused by fault analysis by on-duty personnel, and can improve the efficiency of fault root cause localization for customer dedicated lines.

[0076] In one embodiment, determining the business type of the corporate dedicated line includes:

[0077] Step 101: Obtain the business identifier for the customer acquisition dedicated line;

[0078] This application can extract the service identifier carried in the customer-dedicated line. The service identifier can be a specific identifier or tag.

[0079] Step 102: Determine the business type of the customer-customer dedicated line based on the first association information between the business identifier and the business type, as well as the business identifier of the customer-customer dedicated line.

[0080] It should be noted that the association between business identifier and business type can be pre-set in this application and determined as the first association information.

[0081] For example, business identifier 1 is associated with business type 1, and business identifier 2 is associated with business type 2, etc.

[0082] Therefore, after obtaining the business identifier, the business type corresponding to the business identifier can be queried based on the first association information, and the business type can be identified as the business type of the customer-customer dedicated line.

[0083] This embodiment can quickly and accurately determine the service type of the customer-dedicated line based on the service identifier in the customer-dedicated line. Based on the service type, a corresponding fault root cause localization strategy is determined as the target fault root cause localization strategy. Then, based on the target fault root cause localization strategy, the fault root cause of the customer-dedicated line can be quickly and accurately located. This avoids the problem of slow localization speed and insufficient accuracy caused by fault analysis by on-duty personnel, and can improve the efficiency of fault root cause localization of customer-dedicated lines.

[0084] In one embodiment, determining a target fault root cause localization strategy based on the business type includes:

[0085] Step 201: Obtain the second correlation information between the fault root cause localization strategy and the business type of the customer dedicated line;

[0086] It should be noted that in this application, each type of customer-dedicated line can be pre-associated with a fault root cause localization strategy, and the association between each type of business and each fault root cause localization strategy can be determined as a second association relationship.

[0087] Therefore, after determining the service type of the customer-dedicated line, this application can obtain the second correlation information between the pre-set fault root cause localization strategy and the service type of the customer-dedicated line, so as to determine the target fault root cause localization strategy based on the correlation relationship.

[0088] Step 202: Based on the second association information and the business type, determine the target fault root cause localization strategy from each preset fault root cause localization strategy.

[0089] Furthermore, this application can use the business type as a search term, query through the second associated information, and determine the preset fault root cause localization strategy associated with the business type in the second associated information as the target fault root cause localization strategy.

[0090] This embodiment can quickly and accurately determine the target fault root cause localization strategy based on the business type of the customer service line, and then quickly and accurately locate the fault root cause of the customer service line based on the target fault root cause localization strategy. This avoids the problem of slow localization speed and insufficient accuracy caused by fault analysis by on-duty personnel, and can improve the efficiency of fault root cause localization of customer service lines.

[0091] Figure 2 This is one of the flowcharts illustrating the root cause of a fault in the customer-dedicated line fault location method provided in this application embodiment. (Refer to...) Figure 2In one embodiment, locating the root cause of a fault in a dedicated customer service line according to a target fault root cause localization strategy includes:

[0092] Step 301a: If the target fault root cause localization strategy is the first root cause localization strategy, then determine whether the customer service line is in the engineering state. If it is in the engineering state, then output the fault root cause of the customer service line based on the engineering state.

[0093] In this application, if the target fault root cause localization strategy is determined to be the first root cause localization strategy, i.e., the fault root cause localization strategy for internet leased lines, then it is possible to query whether the triggering event has an "engineering status" alarm. If it does, then it is determined that the fault root cause of the enterprise leased line is caused by engineering reasons, and a prompt message can be output asking maintenance personnel to verify the engineering status. Specifically, it is possible to query whether there is a flag on the enterprise leased line indicating that the leased line is undergoing engineering. If it exists, it is determined that it is in an engineering status; otherwise, it is determined that it is not in an engineering status.

[0094] Step 301b: If not in the engineering state, determine whether there are alarms in the starting / ending network element of the customer dedicated line;

[0095] The dedicated customer line in this application may include at least the starting network element, intermediate network elements, service router (SR) network element and the ending network element, wherein the starting network element or the ending network element is also referred to as the A / Z end network element.

[0096] Among them, intermediate network elements can be firewalls, load balancers, etc.

[0097] Therefore, if it is determined that the dedicated customer line is not in the engineering phase, it can be further determined whether there are alarms at the starting or ending network elements of the dedicated customer line.

[0098] It should be noted that the alarms of the starting / ending network element in this application may include at least one of the following: disconnection alarm, environmental alarm, loss of signal (LOS) alarm, single board alarm, optical power alarm, and bit error alarm.

[0099] Step 301c: If there is an alarm at the starting end network element / ending end network element, output the root cause of the fault of the customer dedicated line based on the alarm at the starting end network element / ending end network element.

[0100] Therefore, this application can first query whether there are any disconnection alarms in the A / Z end network elements. Specifically, the query can be performed by querying the name of the A / Z end network element, a specified time period, and the alarm range. For example, the query can be performed by querying the name of the A / Z end network element, 15 minutes before the fault occurred, and the alarm range (NE_NOT_LOGIN (not logged in), NE_COMMU_BREAK (communication interruption), network element link failure, bearer network management system alarm, network element link failure, etc.) to determine whether there are any disconnection alarms in the network element.

[0101] If a disconnection alarm is confirmed, further investigation is needed to determine if any environmental alarms exist on the A / Z network elements. Specifically, the A / Z network element can be queried to its associated data center, and further information such as data center name, alarm title, and fault occurrence time minus 4 hours can be used to check for environmental alarms. Alarm titles may include, but are not limited to, mains power failure, mains power outage, rectifier module failure, AC input failure, input interruption alarm, output interruption alarm, AC input power failure alarm, DC input interruption alarm, low battery total voltage, low total voltage, low voltage disconnection, secondary low voltage disconnection, and low DC output voltage.

[0102] If an environmental alarm exists, the alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the following can be output: "At XX time, in XX data center, alarm title: Fault caused. Please have maintenance personnel verify the external power supply and environmental conditions of the data center." Here, XX is determined based on the information in the query results.

[0103] If there is no environmental alarm, the disconnection alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0104] If no disconnection alarm is found, it can be determined whether there is an optical signal loss alarm on the A / Z end network element. Specifically, information such as the A / Z end network element, tributary, and alarm range can be used to query whether there were any alarms in the 15 minutes prior to the fault occurrence. The alarm range can include, for example, Ethernet physical interface signal loss, signal loss, Ethernet physical optical interface signal loss, Synchronous Digital Hierarchy (SDH) port signal loss, Ethernet physical interface (ETPI) signal loss, SDH port signal loss, 155 Ethernet port signal loss, and other optical signal loss alarms.

[0105] If an optical signal loss alarm exists, the alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the names of the network elements involved, and the events that triggered the alarm can be output. Furthermore, a message can be output indicating a customer-side fault, requesting maintenance personnel to contact the customer for joint troubleshooting.

[0106] If no optical signal loss alarm exists, it can be determined whether there are board alarms in the A / Z network elements. Specifically, the presence of board alarms can be queried by checking the name of the A / Z network element, the time 15 minutes prior to the fault occurrence, and the scope of board alarms. The scope of board alarms may include, but is not limited to, BD_STATUS (board status), HARD_BAD (hardware failure), OUT_PWR_ABN (output power abnormality), COMMUN_FAIL (communication failure), LSR_NO_FITED (line selector not installed), and LSR_WILL_DIE (line selector about to fail).

[0107] If a single board alarm exists, the single board alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0108] If no single-board alarm exists, it can be determined whether there is an optical power alarm in the A / Z end network element. Specifically, the presence of an optical power alarm can be queried by the port name of the A / Z end network element, the low optical power alarm range (IN_PWR_LOW (input power low voltage), MS_RDI (master station remote indication)), and information such as 15 minutes before the fault occurred.

[0109] If an optical power alarm exists, the optical power alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0110] If no optical power alarm exists, it can be determined whether there is a bit error alarm in the A / Z network element. Specifically, the presence of a bit error alarm can be checked by the port name of the A / Z network element, the bit error alarm range (MAC_FCS_SD (data frame check sequence error), MS_REI (master station bit error indication), B1_EXC (bit error rate measurement unit 1 channel abnormality), B2_EXC (bit error rate measurement unit 2 channel abnormality)), and information from 15 minutes prior to the fault occurrence.

[0111] If a bit error alarm exists, the bit error alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0112] If there are no error alarms, it can be determined that there are no alarms at the starting / ending network element.

[0113] Step 301d: If there are no alarms at the starting end network element / ending end network element, then determine whether there are alarms at intermediate network elements in the dedicated customer line.

[0114] The intermediate network element alarms in this application may include at least one of the following: disconnection alarm, environmental monitoring alarm, optical signal loss alarm, single board alarm, optical power alarm, and bit error alarm.

[0115] It should be noted that intermediate network element alarms can also include bandwidth utilization alarms.

[0116] Therefore, if it is determined that there are no alarms at the starting / ending network element, then it is determined whether there are alarms at intermediate network elements in the dedicated customer line.

[0117] Step 301e: If an intermediate network element alarm exists, output the root cause of the fault in the dedicated customer line based on the intermediate network element alarm.

[0118] Furthermore, one can first check whether there are any disconnection alarms in the intermediate network element. Specifically, this can be done by querying the name of the intermediate network element, a specified time period, and the alarm range. For example, one can query whether a network element has a disconnection alarm by the name of the intermediate network element, 15 minutes before the fault occurred, and the alarm range (NE_NOT_LOGIN (not logged in), NE_COMMU_BREAK (communication interruption), network element link failure, bearer network management system alarm, network element link failure, etc.).

[0119] If a disconnection alarm is confirmed, further investigation is needed to determine if any environmental alarms exist on the intermediate network element. Specifically, the data center to which the intermediate network element belongs can be queried, and further information such as data center name, alarm title, and fault occurrence time minus 4 hours can be used to check for environmental alarms. Alarm titles may include, but are not limited to, mains power failure, mains power outage, rectifier module failure, AC input failure, input interruption alarm, output interruption alarm, AC input power failure alarm, DC input interruption alarm, low battery total voltage, low total voltage, low voltage disconnection, secondary low voltage disconnection, and low DC output voltage.

[0120] If an environmental alarm exists, the alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the following can be output: "At XX time, in XX data center, alarm title: Fault caused. Please have maintenance personnel verify the external power supply and environmental conditions of the data center." Here, XX is determined based on the information in the query results.

[0121] If there is no environmental alarm, the disconnection alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0122] If no disconnection alarm is found, it can be determined whether there is an optical signal loss alarm in the intermediate network element. Specifically, information such as the intermediate network element, tributary, and alarm range can be used to query whether there were any alarms in the 15 minutes prior to the fault occurrence. The alarm range may include, for example, Ethernet physical interface signal loss, signal loss, Ethernet physical optical interface signal loss, SDH port signal loss, Ethernet physical interface (ETPI) signal loss, SDH port signal loss, 155 Ethernet port signal loss, and other optical signal loss alarms.

[0123] If an optical signal loss alarm exists, the alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the names of the network elements involved, and the events that triggered the alarm can be output. Furthermore, a message can be output indicating a customer-side fault, requesting maintenance personnel to contact the customer for joint troubleshooting.

[0124] If no optical signal loss alarm exists, it can be determined whether there are board alarms in the intermediate network element. Specifically, the presence of board alarms can be queried by checking the name of the intermediate network element, the time 15 minutes prior to the fault occurrence, and the scope of board alarms. The scope of board alarms may include, but is not limited to, BD_STATUS (board status), HARD_BAD (hardware failure), OUT_PWR_ABN (output power abnormality), COMMUN_FAIL (communication failure), LSR_NO_FITED (line selector not installed), and LSR_WILL_DIE (line selector about to fail).

[0125] If a single board alarm exists, the single board alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0126] If there is no single-board alarm, it can be determined whether there is an optical power alarm in the intermediate network element. Specifically, the presence of an optical power alarm can be queried by the port name of the intermediate network element, the low optical power alarm range (IN_PWR_LOW (input power low voltage), MS_RDI (master station remote indication)), and information such as 15 minutes before the fault occurred.

[0127] If an optical power alarm exists, the optical power alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0128] If there is no optical power alarm, it can be determined whether there is a bit error alarm in the intermediate network element. Specifically, the presence of bit error alarms can be checked by the port name of the A / Z end network element, the bit error alarm range (MAC_FCS_SD (data frame check sequence error), MS_REI (master station bit error indication), B1_EXC (bit error rate measurement unit 1 channel abnormality), B2_EXC (bit error rate measurement unit 2 channel abnormality)), and information such as 15 minutes before the fault occurred.

[0129] If a bit error alarm exists, the bit error alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0130] If no bit error alarms are detected, it can be determined that there are no intermediate network element alarms. Further investigation can be conducted to determine if there are bandwidth utilization alarms. Specifically, if the bandwidth utilization is greater than or equal to a specified threshold, such as 90%, a bandwidth utilization alarm conclusion can be output as the root cause of the fault in the dedicated line. Further, a message suggesting that the bandwidth utilization is too high and recommending capacity expansion can be output.

[0131] If the bandwidth utilization is less than the specified threshold, it can be determined that there are no intermediate network element alarms.

[0132] Step 301f: If there is no intermediate network element alarm, determine whether there is a service router network element alarm on the enterprise customer dedicated line.

[0133] If no intermediate network element alarms are found, this application can further determine whether there are service router network element alarms on the enterprise leased line. The service router network element can be a router, switch, or other network device.

[0134] Step 301g: If there is a service router network element alarm, output the root cause of the fault in the customer dedicated line based on the service router network element alarm.

[0135] Specifically, queries can be performed using the network element name of the service router, the 15 minutes prior to the fault, and the SR alarm range.

[0136] The scope of SR alarms can include: device board failure, device board performance failure, service board failure, board sub-board alarm, forwarding anomaly, device offline alarm, physical entity failure, physical port DOWN (closed or disconnected), physical entity unplugged, single board overall function failure, physical entity exiting primary status and other alarm situations.

[0137] If there is an alarm in the service router network element, the alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0138] In step 301h, if there are no alarms in the service router network element, the root cause of the fault in the dedicated customer line is output as an abnormality on the customer side.

[0139] If it is determined that there are no alarms in the business router network element, the root cause of the fault in the enterprise customer dedicated line can be directly output as an abnormality on the customer side, that is, a problem on the customer side caused the fault.

[0140] Figure 3 This is the second flowchart illustrating the root cause of a fault in the customer-dedicated line fault location method provided in this application embodiment. (Refer to...) Figure 3 In one embodiment, locating the root cause of a fault in a dedicated customer service line according to a target fault root cause localization strategy includes:

[0141] Step 302a: If the target fault root cause localization strategy is the second root cause localization strategy, then determine whether the customer service line is in the engineering state. If it is in the engineering state, then output the fault root cause of the customer service line based on the engineering state.

[0142] If this application determines that the target fault root cause localization strategy is the second root cause localization strategy, namely the root cause localization strategy for Internet GPON leased lines, it can query whether the triggering event has an "engineering status" alarm. If it does, it determines that the root cause of the fault in the enterprise leased line is caused by engineering reasons, and can output a prompt message asking maintenance personnel to verify the engineering status. Specifically, it can query whether there is a flag on the enterprise leased line indicating that the leased line is under engineering. If it exists, it is determined that the line is in engineering status; otherwise, it is determined that the line is not in engineering status.

[0143] Step 302b: If not in engineering status, determine whether the outage of the fiber optic line terminal equipment is caused by a power failure; if the outage of the fiber optic line terminal equipment is caused by a power failure, output the root cause of the fault of the customer service line.

[0144] If it is determined that the dedicated customer line is not under construction, then it can be determined whether the optical line terminal (OLT) equipment is out of service due to a power failure.

[0145] Specifically, it can be determined whether there is a fiber optic line terminal equipment alarm as the main alarm in the customer-dedicated line. If there is a main alarm, it can be further determined whether there is a data center environmental alarm as a related alarm. If there is a data center environmental alarm, it can be determined that the root cause of the fault in the customer-dedicated line is a power failure that caused the fiber optic line terminal equipment to go out of service.

[0146] Among them, alarms for fiber optic line terminal equipment may include network management and equipment communication failures, International Organization for Standardization (ISO) alarms, and network element link failures.

[0147] The environmental alarms in the computer room can include mains power failure, mains power outage, rectifier module failure, AC input failure, input interruption alarm, output interruption alarm, AC input power failure alarm, DC input interruption alarm, low battery pack total voltage, low total voltage, low voltage disconnection, secondary low voltage disconnection, low DC output voltage, etc.

[0148] If there are no environmental alarms in the data center, it is determined that the root cause of the fault in the dedicated customer line is not a power failure causing the fiber optic line terminal equipment to go out of service.

[0149] Step 302c: If the outage of the fiber optic line terminal equipment is not caused by a power failure, determine whether the outage of the fiber optic line terminal equipment is caused by a hardware failure of the fiber optic line terminal equipment. If the outage of the fiber optic line terminal equipment is caused by a hardware failure of the fiber optic line terminal equipment, output the root cause of the fault of the fiber optic line terminal equipment.

[0150] If it is determined that the root cause of the fault in the customer service line is not a power failure leading to the outage of the fiber optic line terminal equipment, then it can be determined whether the outage was caused by a hardware failure of the fiber optic line terminal equipment.

[0151] Specifically, it can be determined whether there is a fiber optic line terminal equipment alarm as the main alarm. If there is a main alarm, it can be further determined whether there is a fiber optic line terminal equipment hardware alarm as a related alarm. If there is a related alarm, it can be determined that the root cause of the fault in the customer-dedicated line is the fiber optic line terminal equipment hardware failure that caused the fiber optic line terminal equipment to go out of service.

[0152] Among them, hardware alarms of fiber optic line terminal equipment can include single-board communication failure, single-board hardware abnormality, board software not running, board type mismatch, BDMISSING (board loss), FA (fiber optic line terminal equipment fault alarm), etc.

[0153] If no associated alarms are found, it is determined that the root cause of the fault in the dedicated customer line is not a hardware failure of the fiber optic line terminal equipment that caused the fiber optic line terminal equipment to go out of service.

[0154] Step 302d: If the fiber optic line terminal equipment out of service is not due to a hardware failure, then determine whether the customer service line is experiencing a power failure causing undervoltage on the fiber optic line terminal equipment board; if it is a power failure causing undervoltage on the fiber optic line terminal equipment board, then output the root cause of the customer service line failure.

[0155] If it is determined that the root cause of the fault in the customer service line is not a hardware failure of the fiber optic line terminal equipment that caused the fiber optic line terminal equipment to go out of service, then it can be determined whether the fault in the customer service line is due to a power failure causing undervoltage on the fiber optic line terminal equipment board.

[0156] Specifically, it can be determined whether there is a hardware alarm in the fiber optic line terminal equipment that serves as the main alarm. If there is a main alarm, it can be further determined whether there is an environmental alarm in the computer room that serves as a related alarm.

[0157] If there are associated alarms, the root cause of the fault in the dedicated customer line is determined to be a power failure causing undervoltage on the fiber optic line terminal equipment board.

[0158] Step 302e: If the undervoltage of the fiber optic line terminal equipment board is caused by a non-power failure, then determine whether there is a hardware failure of the fiber optic line terminal equipment in the customer service line; if there is a hardware failure of the fiber optic line terminal equipment, then output the root cause of the failure of the customer service line.

[0159] If no associated alarms are detected, it can be determined whether there is a hardware failure in the fiber optic line terminal equipment of the dedicated customer line.

[0160] Specifically, it can be determined whether there is a fault in the fiber optic line terminal equipment board, a fault in the fiber optic line terminal equipment uplink optical module, or a fault in the fiber optic line terminal equipment downlink optical module. If so, the root cause of the fault in the customer-dedicated line is determined to be a hardware fault in the fiber optic line terminal equipment.

[0161] Among them, fiber optic line terminal equipment board failures can include single-board communication failures, single-board hardware abnormalities, board software not running, board type mismatch, BDMISSING, FA, XPON MAC (XPON Media Access Control) chip failures, single-board logic software failures, etc.

[0162] Optical module failures at the inbound port of a fiber optic line terminal equipment can include optical module failure, optical module not being in place, uplink GE (Gigabit Ethernet) optical port connection failure, TXFALL (transmit line failure), optical module temperature exceeding the limit, Ethernet port optical module temperature being too high, LTTEMPEXCED (local temperature exceeding the threshold), etc.

[0163] Optical module failures at the downstream ports of fiber optic line terminal equipment can include hardware failures of GPON port optical modules, PON port optical modules not being in place, OLT optical module failures, high temperature alarms of optical modules, near-end optical transceiver parameters exceeding warning thresholds, PONCOMMFALL (PON communication link failure), etc.

[0164] If none of the above conditions are met, then there is no hardware fault in the fiber optic line terminal equipment.

[0165] Step 302f: If there is no hardware fault in the fiber optic line terminal equipment, determine whether there is a fiber optic cable fault in the customer service line; if there is a fiber optic cable fault in the fiber optic line terminal equipment, output the root cause of the fault in the customer service line.

[0166] If it is determined that there is no hardware failure in the fiber optic line terminal equipment, then it can be further determined whether there is a fiber optic cable failure in the fiber optic line terminal equipment of the dedicated customer line.

[0167] Specifically, it can be determined whether there is a fault in the upstream optical cable of the fiber optic line terminal equipment or a fault in the downstream optical cable of the fiber optic line terminal equipment.

[0168] Among them, uplink optical cable faults on fiber optic line terminal equipment may include uplink port link interruption, uplink Ethernet port connection failure or abnormal port status, loss of Ethernet optical port received signal, LINKDOWN (link interruption), etc.

[0169] Faults in the downstream optical cables of fiber optic line terminal equipment may include broken trunk optical fibers or the OLT failing to detect the expected optical signal, [GPON alarm] PON signal loss, PONLOS, etc.

[0170] If any of the above conditions are met, the root cause of the fault in the dedicated customer line is determined to be a fault in the optical fiber cable of the fiber optic line terminal equipment.

[0171] If none of the above conditions are met, then there is no optical cable fault in the fiber optic line terminal equipment.

[0172] Step 302g: If there is no optical cable fault in the fiber optic line terminal equipment, determine whether the power outage of the optical network user terminal equipment is caused by a regional power outage; if the power outage of the optical network user terminal equipment is caused by a regional power outage, output the root cause of the fault in the customer dedicated line.

[0173] If it is determined that there is no optical cable fault in the fiber optic line terminal equipment, then it can be determined whether the power outage of the optical network user terminal equipment was caused by a regional power outage.

[0174] Specifically, it can be determined whether there is a broken branch fiber, the ONT (Optical Network Terminal) failing to detect the expected optical signal, or the GPON ONT losing power.

[0175] If any of the above conditions are met, the root cause of the fault in the dedicated customer line is determined to be a power outage in the area that caused the optical network user terminal equipment to lose power.

[0176] If none of the above conditions apply, then it is determined that the power outage of the optical network user terminal equipment was not caused by a regional power outage.

[0177] Step 302h: If a non-regional power outage causes the optical network user terminal equipment to lose power, determine whether there is a dedicated line segment alarm on the dedicated customer line; if there is a dedicated line segment alarm, output the root cause of the fault on the dedicated customer line.

[0178] If it is determined that the power outage of the optical network user terminal equipment was not caused by a regional power outage, then it can be determined whether there is a dedicated line segment alarm on the customer-dedicated line.

[0179] Specifically, you can query using the following information:

[0180] First-level specialty = "customer acquisition";

[0181] Alarm titles include "Derivative Alarms" and "Service Interruption";

[0182] Customer-related dedicated line name: Event-related business resource code;

[0183] Alarm occurrence time: Take the fault occurrence time - 5 minutes;

[0184] Alarm status: Active alarm;

[0185] If the query result is not empty, then there is a dedicated line segment alarm.

[0186] Furthermore, it can output the queried alarms, alarm titles, and alarm occurrence times.

[0187] If the query result is empty, it is determined that there is no dedicated line segment alarm.

[0188] Step 302i: If there is no alarm on the dedicated line segment, determine whether there is an abnormal optical power of the fiber optic line terminal equipment on the customer dedicated line; if there is an abnormal optical power of the fiber optic line terminal equipment, output the root cause of the fault of the customer dedicated line.

[0189] If it is determined that there are no alarms on the dedicated line segment, then it can be determined whether there is an abnormal optical power in the fiber optic line terminal equipment of the customer dedicated line.

[0190] Specifically, the optical power of the OLT uplink port can be obtained from the customer system and compared with the standard value to confirm whether it meets the standard range. If it is within the standard range, the output result is that the line fault has been restored and there is no abnormal optical power of the fiber optic line terminal equipment; otherwise, the output result is that the root cause of the fault of the customer dedicated line is that the line fault has not been restored and the optical power of the OLT uplink port is abnormal.

[0191] Step 302j: If there is no abnormal optical power in the fiber optic line terminal equipment, determine whether there is a service router network element alarm in the enterprise dedicated line; if there is a service router network element alarm, output the root cause of the fault in the enterprise dedicated line based on the service router network element alarm.

[0192] If it is determined that there is no abnormal optical power in the fiber optic line terminal equipment, then it can be determined whether there is a network element alarm in the service router of the enterprise customer dedicated line.

[0193] Specifically, queries can be performed using the network element name of the service router, the 15 minutes prior to the fault, and the SR alarm range.

[0194] The scope of SR alarms can include: device board failure, device board performance failure, service board failure, board sub-board alarm, forwarding anomaly, device offline alarm, physical entity failure, physical port down, physical entity removal, single board overall function failure, physical entity exiting primary status and other alarm situations.

[0195] If there is an alarm in the service router network element, the alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0196] In step 302k, if there are no alarms in the service router network element, the root cause of the fault in the enterprise private line is output as an abnormality on the customer side.

[0197] If it is determined that there are no alarms in the business router network element, the root cause of the fault in the enterprise customer dedicated line can be directly output as an abnormality on the customer side, that is, a problem on the customer side caused the fault.

[0198] Figure 4 This is the third flowchart illustrating the root cause of a fault in the customer-dedicated line fault location method provided in this application embodiment. (Refer to...) Figure 4 In one embodiment, locating the root cause of a fault in a dedicated customer service line according to a target fault root cause localization strategy includes:

[0199] Step 303a: If the target fault root cause localization strategy is the third root cause localization strategy, then determine whether the customer service line is in the engineering state. If it is in the engineering state, then output the fault root cause of the customer service line based on the engineering state.

[0200] If the root cause localization strategy for the target fault is determined to be the third root cause localization strategy, i.e., the root cause localization strategy for non-internet leased lines, then it is possible to check whether the triggering event has an "engineering status" alarm. If it does, then the root cause of the fault in the customer leased line is determined to be due to engineering reasons, and a prompt message can be output asking maintenance personnel to verify the engineering status. Specifically, it is possible to check whether there is a flag on the customer leased line indicating that the leased line is under engineering. If it exists, then it is determined to be in engineering status; otherwise, it is determined not to be in engineering status.

[0201] Step 303b: If not in the engineering state, determine whether there are alarms in the starting / ending network element of the customer dedicated line;

[0202] If it is determined that the dedicated customer line is not in the engineering phase, it can be further determined whether there are alarms at the starting or ending network elements of the dedicated customer line.

[0203] Step 303c: If there is an alarm at the starting end network element / ending end network element, output the root cause of the fault of the customer dedicated line based on the alarm at the starting end network element / ending end network element.

[0204] This application can first query whether there are any disconnection alarms for network elements at the A / Z end. Specifically, it can query by the name of the A / Z end network element, a specified time period, and the alarm range. For example, it can query whether there are any disconnection alarms for network elements by the name of the A / Z end network element, 15 minutes before the fault occurred, and the alarm range (NE_NOT_LOGIN (not logged in), NE_COMMU_BREAK (communication interruption), network element link failure, bearer network management system alarm, network element link failure, etc.).

[0205] If a disconnection alarm is confirmed, further investigation is needed to determine if any environmental alarms exist on the A / Z network elements. Specifically, the A / Z network element can be queried to its associated data center, and further information such as data center name, alarm title, and fault occurrence time minus 4 hours can be used to check for environmental alarms. Alarm titles may include, but are not limited to, mains power failure, mains power outage, rectifier module failure, AC input failure, input interruption alarm, output interruption alarm, AC input power failure alarm, DC input interruption alarm, low battery total voltage, low total voltage, low voltage disconnection, secondary low voltage disconnection, and low DC output voltage.

[0206] If an environmental alarm exists, the alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the following can be output: "At XX time, in XX data center, alarm title: Fault caused. Please have maintenance personnel verify the external power supply and environmental conditions of the data center." Here, XX is determined based on the information in the query results.

[0207] If there is no environmental alarm, the disconnection alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0208] If no disconnection alarm is found, it can be determined whether there is an optical signal loss alarm on the A / Z end network element. Specifically, information such as the A / Z end network element, tributary, and alarm range can be used to query whether there were any alarms in the 15 minutes prior to the fault occurrence. The alarm range can include, for example, Ethernet physical interface signal loss, signal loss, Ethernet physical optical interface signal loss, SDH port signal loss, Ethernet physical interface (ETPI) signal loss, SDH port signal loss, 155 Ethernet port signal loss, and other optical signal loss alarms.

[0209] If an optical signal loss alarm exists, the alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the names of the network elements involved, and the events that triggered the alarm can be output. Furthermore, a message can be output indicating a customer-side fault, requesting maintenance personnel to contact the customer for joint troubleshooting.

[0210] If no optical signal loss alarm exists, it can be determined whether there are board alarms in the A / Z network elements. Specifically, the presence of board alarms can be queried by checking the name of the A / Z network element, the time 15 minutes prior to the fault occurrence, and the scope of board alarms. The scope of board alarms may include, but is not limited to, BD_STATUS (board status), HARD_BAD (hardware failure), OUT_PWR_ABN (output power abnormality), COMMUN_FAIL (communication failure), LSR_NO_FITED (line selector not installed), and LSR_WILL_DIE (line selector about to fail).

[0211] If a single board alarm exists, the single board alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0212] If no single-board alarm exists, it can be determined whether there is an optical power alarm in the A / Z end network element. Specifically, the presence of an optical power alarm can be queried by the port name of the A / Z end network element, the low optical power alarm range (IN_PWR_LOW (input power low voltage), MS_RDI (master station remote indication)), and information such as 15 minutes before the fault occurred.

[0213] If an optical power alarm exists, the optical power alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0214] If no optical power alarm exists, it can be determined whether there is a bit error alarm in the A / Z network element. Specifically, the presence of a bit error alarm can be checked by the port name of the A / Z network element, the bit error alarm range (MAC_FCS_SD (data frame check sequence error), MS_REI (master station bit error indication), B1_EXC (bit error rate measurement unit 1 channel abnormality), B2_EXC (bit error rate measurement unit 2 channel abnormality)), and information from 15 minutes prior to the fault occurrence.

[0215] If a bit error alarm exists, the bit error alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0216] If there are no error alarms, it can be determined that there are no alarms at the starting / ending network element.

[0217] Step 303d: If there are no alarms at the starting end network element / ending end network element, then determine whether there are alarms at intermediate network elements in the dedicated customer line.

[0218] If it is determined that there are no alarms at the starting / ending network element, then determine whether there are alarms at intermediate network elements in the dedicated customer line.

[0219] Step 303e: If an intermediate network element alarm exists, output the root cause of the fault in the dedicated customer line based on the intermediate network element alarm.

[0220] Furthermore, one can first check whether there are any disconnection alarms in the intermediate network element. Specifically, this can be done by querying the name of the intermediate network element, a specified time period, and the alarm range. For example, one can query whether a network element has a disconnection alarm by the name of the intermediate network element, 15 minutes before the fault occurred, and the alarm range (NE_NOT_LOGIN (not logged in), NE_COMMU_BREAK (communication interruption), network element link failure, bearer network management system alarm, network element link failure, etc.).

[0221] If a disconnection alarm is confirmed, further investigation is needed to determine if any environmental alarms exist on the intermediate network element. Specifically, the data center to which the intermediate network element belongs can be queried, and further information such as data center name, alarm title, and fault occurrence time minus 4 hours can be used to check for environmental alarms. Alarm titles may include, but are not limited to, mains power failure, mains power outage, rectifier module failure, AC input failure, input interruption alarm, output interruption alarm, AC input power failure alarm, DC input interruption alarm, low battery total voltage, low total voltage, low voltage disconnection, secondary low voltage disconnection, and low DC output voltage.

[0222] If an environmental alarm exists, the alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the following can be output: "At XX time, in XX data center, alarm title: Fault caused. Please have maintenance personnel verify the external power supply and environmental conditions of the data center." Here, XX is determined based on the information in the query results.

[0223] If there is no environmental alarm, the disconnection alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0224] If no disconnection alarm is found, it can be determined whether there is an optical signal loss alarm in the intermediate network element. Specifically, information such as the intermediate network element, tributary, and alarm range can be used to query whether there were any alarms in the 15 minutes prior to the fault occurrence. The alarm range may include, for example, Ethernet physical interface signal loss, signal loss, Ethernet physical optical interface signal loss, SDH port signal loss, Ethernet physical interface (ETPI) signal loss, SDH port signal loss, 155 Ethernet port signal loss, and other optical signal loss alarms.

[0225] If an optical signal loss alarm exists, the alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the names of the network elements involved, and the events that triggered the alarm can be output. Furthermore, a message can be output indicating a customer-side fault, requesting maintenance personnel to contact the customer for joint troubleshooting.

[0226] If no optical signal loss alarm exists, it can be determined whether there are board alarms in the intermediate network element. Specifically, the presence of board alarms can be queried by checking the name of the intermediate network element, the time 15 minutes prior to the fault occurrence, and the scope of board alarms. The scope of board alarms may include, but is not limited to, BD_STATUS (board status), HARD_BAD (hardware failure), OUT_PWR_ABN (output power abnormality), COMMUN_FAIL (communication failure), LSR_NO_FITED (line selector not installed), and LSR_WILL_DIE (line selector about to fail).

[0227] If a single board alarm exists, the single board alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0228] If there is no single-board alarm, it can be determined whether there is an optical power alarm in the intermediate network element. Specifically, the presence of an optical power alarm can be queried by the port name of the intermediate network element, the low optical power alarm range (IN_PWR_LOW (input power low voltage), MS_RDI (master station remote indication)), and information such as 15 minutes before the fault occurred.

[0229] If an optical power alarm exists, the optical power alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0230] If there is no optical power alarm, it can be determined whether there is a bit error alarm in the intermediate network element. Specifically, the presence of bit error alarms can be checked by the port name of the A / Z end network element, the bit error alarm range (MAC_FCS_SD (data frame check sequence error), MS_REI (master station bit error indication), B1_EXC (bit error rate measurement unit 1 channel abnormality), B2_EXC (bit error rate measurement unit 2 channel abnormality)), and information such as 15 minutes before the fault occurred.

[0231] If a bit error alarm exists, the bit error alarm conclusion can be output as the root cause of the fault in the dedicated customer line. Specifically, the alarm time, the name of the network element involved, and the event that triggered the alarm can be output.

[0232] If no bit error alarms are detected, it can be determined that there are no intermediate network element alarms. Further investigation can be conducted to determine if there are bandwidth utilization alarms. Specifically, if the bandwidth utilization is greater than or equal to a specified threshold, such as 90%, a bandwidth utilization alarm conclusion can be output as the root cause of the fault in the dedicated line. Further, a message suggesting that the bandwidth utilization is too high and recommending capacity expansion can be output.

[0233] If the bandwidth utilization is less than the specified threshold, it can be determined that there are no intermediate network element alarms.

[0234] Step 303f: If there is no intermediate network element alarm, output the root cause of the fault in the dedicated customer line as an abnormality on the customer side.

[0235] If it is determined that there are no intermediate network element alarms, the root cause of the fault in the dedicated customer line can be directly output as an abnormality on the customer side, that is, a problem on the customer side caused the fault.

[0236] In this embodiment, information such as engineering details, alarms, optical power, and bandwidth utilization are associated with the location of internet leased lines. For internet GPON leased lines, information such as engineering details, environmental alarms, OLT hardware alarms, OLT uplink / downlink transmission alarms, leased line segment alarms, OLT uplink port optical power, bandwidth utilization, and SR alarms are associated with the location of these alarms. Furthermore, by first checking AZ segment alarms, then gradually locating intermediate network element alarms, and if no equipment issues are found, the line optical power and performance bandwidth utilization are checked. Finally, it is determined whether the SR device is faulty, enabling more precise location of faults. This allows for quick and accurate identification of the cause of faults in enterprise leased lines, improving the quality and efficiency of after-sales service.

[0237] Furthermore, this application also provides a root cause location device for passenger dedicated line faults.

[0238] Reference Figure 5 , Figure 5 This is a schematic diagram of the functional modules of an embodiment of the customer service dedicated line fault root cause location device of this application.

[0239] The fault root cause location device for the passenger-carrying dedicated line includes:

[0240] The receiving module 510 is used to receive a fault alarm from the dedicated customer line and determine the service type of the dedicated customer line;

[0241] The determination module 520 is used to determine the target fault root cause localization strategy based on the service type.

[0242] The positioning module 530 is used to locate the root cause of the fault in the customer service line according to the target fault root cause positioning strategy.

[0243] The fault root cause location device for the customer service dedicated line provided in this application embodiment can determine the service type of the customer service dedicated line after receiving a fault alarm. This allows for the determination of a corresponding fault root cause location strategy as a target fault root cause location strategy based on the service type. Then, based on the target fault root cause location strategy, the fault root cause of the customer service dedicated line can be located quickly and accurately. This avoids the problem of slow location speed and insufficient accuracy caused by fault analysis by on-duty personnel, and can improve the efficiency of fault root cause location for the customer service dedicated line.

[0244] In one embodiment, the receiving module 510 is specifically used for:

[0245] Obtain the service identifier of the customer acquisition line;

[0246] The service type of the dedicated customer line is determined based on the first association information between the service identifier and the service type, as well as the service identifier of the dedicated customer line; the service type is an Internet dedicated line, an Internet gigabit passive optical network dedicated line, or a non-Internet dedicated line.

[0247] In one embodiment, the determining module 520 is specifically used for:

[0248] Obtain the second correlation information between the fault root cause localization strategy and the business type of the dedicated customer line;

[0249] Based on the second association information and the business type, a target fault root cause localization strategy is determined from each preset fault root cause localization strategy.

[0250] In one embodiment, the positioning module 530 is specifically used for:

[0251] If the target fault root cause localization strategy is the first root cause localization strategy, then determine whether the customer service line is in an engineering state. If it is in an engineering state, then output the fault root cause of the customer service line based on the engineering state.

[0252] If it is not in the engineering state, determine whether there are alarms in the starting end network element / ending end network element of the customer-accessible dedicated line;

[0253] If there is an alarm at the starting end network element / ending end network element, the root cause of the fault of the dedicated customer line is output based on the alarm at the starting end network element / ending end network element.

[0254] If there are no alarms at the starting / ending network element, then determine whether there are alarms at intermediate network elements in the dedicated customer line;

[0255] If an intermediate network element alarm exists, the root cause of the fault in the dedicated customer line will be output based on the intermediate network element alarm.

[0256] If no intermediate network element alarm is found, then it is determined whether the dedicated customer line has a service router network element alarm.

[0257] If a service router network element alarm exists, the root cause of the fault in the dedicated customer line will be output based on the service router network element alarm.

[0258] If there are no alarms in the service router network element, the root cause of the fault in the dedicated customer line is output as an abnormality on the customer side.

[0259] In one embodiment, the positioning module 530 is further configured to:

[0260] If the target fault root cause localization strategy is the second root cause localization strategy, then determine whether the customer service line is in an engineering state. If it is in an engineering state, then output the fault root cause of the customer service line based on the engineering state.

[0261] If the line is not in an engineering state, determine whether the outage of the fiber optic terminal equipment is caused by a power failure; if the outage of the fiber optic terminal equipment is caused by a power failure, output the root cause of the fault of the line.

[0262] If the outage of the fiber optic line terminal equipment is not caused by a power failure, then determine whether the outage of the fiber optic line terminal equipment is caused by a hardware failure of the fiber optic line terminal equipment; if the outage is caused by a hardware failure of the fiber optic line terminal equipment, then output the root cause of the fault of the fiber optic line terminal equipment.

[0263] If the outage of the fiber optic line terminal equipment is not caused by a hardware failure, then determine whether the power failure of the fiber optic line terminal equipment board is causing undervoltage. If the power failure is causing undervoltage, then output the root cause of the fault of the fiber optic line terminal equipment.

[0264] If the undervoltage of the fiber optic line terminal equipment board is not caused by a power failure, then it is determined whether there is a hardware failure of the fiber optic line terminal equipment in the customer service line; if there is a hardware failure of the fiber optic line terminal equipment, then the root cause of the failure of the customer service line is output.

[0265] If there is no hardware fault in the fiber optic line terminal equipment, then determine whether there is a fiber optic cable fault in the customer service line; if there is a fiber optic cable fault in the fiber optic line terminal equipment, then output the root cause of the fault in the customer service line.

[0266] If there is no optical cable fault in the fiber optic line terminal equipment, then determine whether the power outage of the optical network user terminal equipment is caused by a regional power outage; if the power outage of the optical network user terminal equipment is caused by a regional power outage, then output the root cause of the fault in the customer dedicated line.

[0267] If a non-regional power outage causes a power failure in the optical network user terminal equipment, then determine whether there is a dedicated line segment alarm on the dedicated customer line; if there is a dedicated line segment alarm, then output the root cause of the fault on the dedicated customer line.

[0268] If there is no alarm on the dedicated line segment, then determine whether there is an abnormal optical power of the fiber optic line terminal equipment on the customer dedicated line; if there is an abnormal optical power of the fiber optic line terminal equipment, then output the root cause of the fault of the customer dedicated line.

[0269] If there is no optical power abnormality in the fiber optic line terminal equipment, then determine whether there is a service router network element alarm in the dedicated customer line; if there is a service router network element alarm, then output the root cause of the fault in the dedicated customer line based on the service router network element alarm.

[0270] If there are no alarms in the service router network element, the root cause of the fault in the dedicated customer line is output as an abnormality on the customer side.

[0271] In one embodiment, the positioning module 530 is further configured to:

[0272] If the target fault root cause localization strategy is the third root cause localization strategy, then determine whether the customer service line is in an engineering state. If it is in an engineering state, then output the fault root cause of the customer service line based on the engineering state.

[0273] If it is not in the engineering state, determine whether there are alarms in the starting end network element / ending end network element of the customer-accessible dedicated line;

[0274] If there is an alarm at the starting end network element / ending end network element, the root cause of the fault of the dedicated customer line is output based on the alarm at the starting end network element / ending end network element.

[0275] If there are no alarms at the starting / ending network element, then determine whether there are alarms at intermediate network elements in the dedicated customer line;

[0276] If an intermediate network element alarm exists, the root cause of the fault in the dedicated customer line will be output based on the intermediate network element alarm.

[0277] If there is no intermediate network element alarm, the root cause of the fault in the dedicated customer line is output as an abnormality on the customer side.

[0278] Figure 6 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 6 As shown, the electronic device may include: a processor 610, a communication interface 620, a memory 630, and a communication bus 640, wherein the processor 610, the communication interface 620, and the memory 630 communicate with each other via the communication bus 640. The processor 610 can call a computer program in the memory 630 to execute the steps of the customer dedicated line fault root cause localization method, such as including:

[0279] Upon receiving a fault alarm from the dedicated customer service line, determine the service type of the dedicated customer service line.

[0280] Based on the business type, determine the target fault root cause localization strategy;

[0281] Based on the target fault root cause localization strategy, locate the root cause of the fault in the customer service line.

[0282] Furthermore, the logical instructions in the aforementioned memory 630 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0283] On the other hand, embodiments of this application also provide a medium, which is a computer-readable storage medium storing a computer program. The computer program is used to cause a processor to perform the steps of the methods provided in the above embodiments, such as including:

[0284] Upon receiving a fault alarm from the dedicated customer service line, determine the service type of the dedicated customer service line.

[0285] Based on the business type, determine the target fault root cause localization strategy;

[0286] Based on the target fault root cause localization strategy, locate the root cause of the fault in the customer service line.

[0287] The computer-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical storage (e.g., CD, DVD, BD, HVD), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0288] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0289] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0290] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for locating the root cause of faults on a passenger-dedicated railway line, characterized in that, include: Upon receiving a fault alarm from the dedicated customer service line, determine the service type of the dedicated customer service line. Based on the business type, determine the target fault root cause localization strategy; Based on the target fault root cause localization strategy, locate the fault root cause of the customer-accessible dedicated line; The target fault root cause localization strategy includes a first root cause localization strategy; The step of locating the root cause of the fault in the customer-dedicated line according to the target fault root cause localization strategy includes: If the target fault root cause localization strategy is the first root cause localization strategy, then determine whether the customer service line is in an engineering state. If it is in an engineering state, then output the fault root cause of the customer service line based on the engineering state. If it is not in the engineering state, determine whether there are alarms in the starting end network element / ending end network element of the customer-accessible dedicated line; If there is an alarm at the starting end network element / ending end network element, the root cause of the fault of the dedicated customer line is output based on the alarm at the starting end network element / ending end network element. If there are no alarms at the starting / ending network element, then determine whether there are alarms at intermediate network elements in the dedicated customer line; If an intermediate network element alarm exists, the root cause of the fault in the dedicated customer line will be output based on the intermediate network element alarm. If no intermediate network element alarm is found, then it is determined whether the dedicated customer line has a service router network element alarm. If a service router network element alarm exists, the root cause of the fault in the dedicated customer line will be output based on the service router network element alarm. If there are no alarms in the service router network element, the root cause of the fault in the dedicated customer line is output as an abnormality on the customer side.

2. The method for locating the root cause of faults on a dedicated passenger railway line according to claim 1, characterized in that, The target fault root cause localization strategy includes a second root cause localization strategy; the step of locating the root cause of the fault in the customer service line according to the target fault root cause localization strategy further includes: If the target fault root cause localization strategy is the second root cause localization strategy, then determine whether the customer service line is in an engineering state. If it is in an engineering state, then output the fault root cause of the customer service line based on the engineering state. If the line is not in an engineering state, determine whether the outage of the fiber optic terminal equipment is caused by a power failure; if the outage of the fiber optic terminal equipment is caused by a power failure, output the root cause of the fault of the line. If the outage of the fiber optic line terminal equipment is not caused by a power failure, then determine whether the outage of the fiber optic line terminal equipment is caused by a hardware failure of the fiber optic line terminal equipment; if the outage is caused by a hardware failure of the fiber optic line terminal equipment, then output the root cause of the fault of the fiber optic line terminal equipment. If the outage of the fiber optic line terminal equipment is not caused by a hardware failure, then determine whether the power failure of the fiber optic line terminal equipment board is causing undervoltage. If the power failure is causing undervoltage, then output the root cause of the fault of the fiber optic line terminal equipment. If the undervoltage of the fiber optic line terminal equipment board is not caused by a power failure, then it is determined whether there is a hardware failure of the fiber optic line terminal equipment in the customer service line; if there is a hardware failure of the fiber optic line terminal equipment, then the root cause of the failure of the customer service line is output. If there is no hardware fault in the fiber optic line terminal equipment, then determine whether there is a fiber optic cable fault in the customer service line; if there is a fiber optic cable fault in the fiber optic line terminal equipment, then output the root cause of the fault in the customer service line. If there is no optical cable fault in the fiber optic line terminal equipment, then determine whether the power outage of the optical network user terminal equipment is caused by a regional power outage; if the power outage of the optical network user terminal equipment is caused by a regional power outage, then output the root cause of the fault in the customer dedicated line. If a non-regional power outage causes a power failure in the optical network user terminal equipment, then determine whether there is a dedicated line segment alarm on the dedicated customer line; if there is a dedicated line segment alarm, then output the root cause of the fault on the dedicated customer line. If there is no alarm on the dedicated line segment, then determine whether there is an abnormal optical power of the fiber optic line terminal equipment on the customer dedicated line; if there is an abnormal optical power of the fiber optic line terminal equipment, then output the root cause of the fault of the customer dedicated line. If there is no optical power abnormality in the fiber optic line terminal equipment, then determine whether there is a service router network element alarm in the dedicated customer line; if there is a service router network element alarm, then output the root cause of the fault in the dedicated customer line based on the service router network element alarm. If there are no alarms in the service router network element, the root cause of the fault in the dedicated customer line is output as an abnormality on the customer side.

3. The method for locating the root cause of faults on a dedicated passenger railway line according to claim 1, characterized in that, The target fault root cause localization strategy includes a third root cause localization strategy; the step of locating the root cause of the fault in the dedicated passenger line according to the target fault root cause localization strategy further includes: If the target fault root cause localization strategy is the third root cause localization strategy, then determine whether the customer service line is in an engineering state. If it is in an engineering state, then output the fault root cause of the customer service line based on the engineering state. If it is not in the engineering state, determine whether there are alarms in the starting end network element / ending end network element of the customer-accessible dedicated line; If there is an alarm at the starting end network element / ending end network element, the root cause of the fault of the dedicated customer line is output based on the alarm at the starting end network element / ending end network element. If there are no alarms at the starting / ending network element, then determine whether there are alarms at intermediate network elements in the dedicated customer line; If an intermediate network element alarm exists, the root cause of the fault in the dedicated customer line will be output based on the intermediate network element alarm. If there is no intermediate network element alarm, the root cause of the fault in the dedicated customer line is output as an abnormality on the customer side.

4. The method for locating the root cause of faults on a dedicated passenger railway line according to claim 1 or claim 3, characterized in that, The alarms of the starting / ending network element and the alarms of the intermediate network element all include at least one of the following: disconnection alarm, environmental monitoring alarm, optical signal loss alarm, single board alarm, optical power alarm, and bit error alarm.

5. The method for locating the root cause of faults on a dedicated passenger railway line according to claim 1, characterized in that, Determining the business type of the customer-dedicated line includes: Obtain the service identifier of the customer acquisition line; The service type of the dedicated customer line is determined based on the first association information between the service identifier and the service type, as well as the service identifier of the dedicated customer line; the service type is an Internet dedicated line, an Internet gigabit passive optical network dedicated line, or a non-Internet dedicated line.

6. The method for locating the root cause of faults on a dedicated passenger railway line according to claim 1, characterized in that, The step of determining the target fault root cause localization strategy based on the service type includes: Obtain the second correlation information between the fault root cause localization strategy and the business type of the dedicated customer line; Based on the second association information and the business type, a target fault root cause localization strategy is determined from each preset fault root cause localization strategy.

7. A fault root cause localization device for a passenger-carrying dedicated line for executing the fault root cause localization method as described in claim 1, characterized in that, include: The receiving module is used to receive fault alarms from the dedicated customer line and determine the service type of the dedicated customer line. The determination module is used to determine the target fault root cause localization strategy based on the business type. The positioning module is used to locate the root cause of the fault in the customer service line according to the target fault root cause positioning strategy.

8. An electronic device comprising a processor and a memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the root cause localization method for passenger dedicated line faults as described in any one of claims 1 to 6.

9. A storage medium, said storage medium being a computer-readable storage medium, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the root cause localization method for passenger dedicated line faults as described in any one of claims 1 to 6.

Images