Fault locating method, apparatus, device, medium, and program product

CN122993816APending Publication Date: 2026-10-27CHINA UNITED NETWORK COMM GRP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611132712.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-28
Publication Date
2026-10-27

AI Technical Summary

Technical Problem

[0004]然而,按照上述方法,在对海底光缆故障进行定位时,需要较长的信号采样与处理时间,监测频率受限,无法实现分钟级甚至秒级的实时在线监测

Benefits of technology

[0007]本申请提供的技术方案至少带来以下有益效果:在对海底光缆故障进行定位时,可以先基于实时方差和历史基准均值生成路由异常告警信号,然后再响应于该路由异常告警信号,对目标AS邻接对标识关联的目标IP及多海底光缆接口IP进行并行探测处理,以得到目标海底光缆对应的故障定位信息。从而无需较长的信号采样与处理时间,可以实现分钟级甚至秒级的实时在线监测。如此可以在故障发生的第一时间探测异常及捕捉瞬态故障,能够及时定位海底光缆故障。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122993816A_ABST
    Figure CN122993816A_ABST
Patent Text Reader

Abstract

The application provides a fault positioning method, device, equipment, medium and program product, relates to the technical field of communication, and is used for positioning a submarine cable fault. The specific technical scheme is as follows: based on topology information of at least one submarine cable, filtering and processing BGP data flow to obtain an observation data set of a target submarine cable; performing stream processing on the observation data set to obtain a withdrawal count statistical variance and a change count statistical variance of each path associated with the target submarine cable; generating a routing anomaly alarm signal based on the withdrawal count statistical variance of each path and a historical withdrawal count reference mean value, and / or the change count statistical variance of each path and a historical change count reference mean value; and in response to the routing anomaly alarm signal, performing parallel detection processing on a target IP and a multi-submarine cable interface IP associated with a target AS adjacent pair identifier, and outputting fault positioning information corresponding to the target submarine cable. The application is applied to a scene of positioning a submarine cable fault.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a fault location method, apparatus, device, medium, and program product. Background Technology

[0002] As a core infrastructure carrying cross-border data traffic, the operational reliability of submarine optical cables directly affects the normal operation of international internet services, cloud computing interconnection, and other businesses. However, submarine optical cables are located in the deep-sea environment and are susceptible to interruptions due to natural and human factors. Therefore, locating submarine optical cable faults has become an important research topic for ensuring international communication security.

[0003] Currently, the location of faults in submarine optical cables typically employs a physical layer detection scheme based on the principle of Optical Time Domain Reflectometer (OTDR). Specifically, a pulsed laser is injected into the cable under test, and then the backscattered and Fresnel reflected signals returning along the fiber are collected. Based on the round-trip time of the collected signals and the refractive index of the fiber, the physical distance to the fault point is calculated, thereby enabling the location of the fault in the submarine optical cable.

[0004] However, the above method requires a long signal sampling and processing time to locate submarine optical cable faults, limiting the monitoring frequency and making it impossible to achieve real-time online monitoring at the minute or even second level. This results in the inability to locate submarine optical cable faults in a timely manner. Summary of the Invention

[0005] This application provides a fault location method for timely locating faults in submarine optical cables.

[0006] In a first aspect, embodiments of this application provide a fault location method, which includes: filtering a Border Gateway Protocol (BGP) data stream based on the topology information of at least one submarine optical cable to obtain an observation dataset of the target submarine optical cable; wherein the topology information includes Autonomous System (AS) adjacency pairs and interface Internet Protocol (IP) pairs corresponding to each submarine optical cable; the observation dataset includes a portion of the packets in the BGP data stream; performing streaming processing on the observation dataset to obtain the statistical variance of cancellation counts and statistical variance of change counts for each path associated with the target submarine optical cable; generating a routing anomaly alarm signal based on the statistical variance of cancellation counts and the historical average of cancellation counts for each path, and / or the statistical variance of change counts and the historical average of change counts for each path; wherein the routing anomaly alarm signal includes a target AS adjacency pair identifier; and responding to the routing anomaly alarm signal, performing parallel detection processing on the target IP associated with the target AS adjacency pair identifier and multiple submarine optical cable interface IPs to output fault location information corresponding to the target submarine optical cable.

[0007] The technical solution provided in this application offers at least the following advantages: When locating faults in submarine optical cables, a routing anomaly alarm signal can be generated first based on real-time variance and historical benchmark mean. Then, in response to this routing anomaly alarm signal, parallel detection processing is performed on the target IP associated with the target AS adjacency pair identifier and multiple submarine optical cable interface IPs to obtain the fault location information corresponding to the target submarine optical cable. This eliminates the need for lengthy signal sampling and processing time, enabling real-time online monitoring at the minute or even second level. This allows for the detection of anomalies and the capture of transient faults at the first moment of fault occurrence, enabling timely location of submarine optical cable faults.

[0008] One possible implementation involves performing parallel detection processing on the target IP associated with the target AS adjacency pair identifier and the multiple submarine optical cable interface IPs, and outputting the fault location information corresponding to the target submarine optical cable. This includes: obtaining the first path feature corresponding to the target IP and the second path feature corresponding to the multiple submarine optical cable interface IPs; and performing route detection on the multiple submarine optical cable interface IPs when the first path feature matches the second path feature to obtain the fault location information.

[0009] Another possible implementation, which involves filtering the BGP data stream based on the topology information of at least one submarine optical cable to obtain an observation dataset of the target submarine optical cable, includes: performing source AS matching filtering on the BGP data stream based on the topology information of the at least one submarine optical cable to obtain an initial observation dataset; and performing fingerprint inclusion matching filtering on the initial observation dataset to obtain the observation dataset.

[0010] Another possible implementation involves performing streaming processing on the aforementioned observation dataset to obtain the statistical variance of the cancellation count and the statistical variance of the change count for each path associated with the target submarine optical cable. This includes: performing streaming processing on the aforementioned observation dataset to obtain the cancellation count sequence and the change count sequence for each path associated with the target submarine optical cable; and determining the statistical variance of the cancellation count and the statistical variance of the change count for each path based on the cancellation count sequence and the change count sequence for each path using a variance standard calculation module.

[0011] Another possible implementation involves generating a routing anomaly alarm signal based on the statistical variance of the cancellation count and the historical average cancellation count for each path, and / or the statistical variance of the change count and the historical average change count for each path. This includes generating the routing anomaly alarm signal when a first condition is met; wherein the first condition includes at least one of the following: the statistical variance of the cancellation count for each path is greater than the historical average cancellation count; and the statistical variance of the change count for each path is greater than the historical average change count.

[0012] Secondly, embodiments of this application provide a fault location device, comprising: a processing module and a generation module; the processing module is configured to filter BGP data streams based on topology information of at least one submarine optical cable to obtain an observation dataset of the target submarine optical cable; wherein the topology information includes AS adjacency pairs and interface IPs corresponding to each submarine optical cable; the observation dataset includes a portion of the packets in the BGP data stream; the processing module is further configured to perform streaming processing on the observation dataset to obtain the statistical variance of cancellation counts and statistical variance of change counts for each path associated with the target submarine optical cable; the generation module is configured to generate a routing anomaly alarm signal based on the statistical variance of cancellation counts and the historical average of cancellation counts for each path, and / or the statistical variance of change counts and the historical average of change counts for each path; wherein the routing anomaly alarm signal includes a target AS adjacency pair identifier; the processing module is further configured to, in response to the routing anomaly alarm signal, perform parallel detection processing on the target IPs associated with the target AS adjacency pair identifiers and multiple submarine optical cable interface IPs, and output fault location information corresponding to the target submarine optical cable.

[0013] One possible implementation is that the above processing module is specifically used to: obtain the first path feature corresponding to the target IP and the second path feature corresponding to the multiple submarine optical cable interface IPs; when the first path feature matches the second path feature, perform route detection on the multiple submarine optical cable interface IPs to obtain the fault location information.

[0014] Another possible implementation, the above processing module is specifically used to: perform source AS matching filtering on the BGP data stream based on the topology information of at least one submarine optical cable to obtain an initial observation dataset; and perform fingerprint inclusion matching filtering on the initial observation dataset to obtain the observation dataset.

[0015] Another possible implementation is that the above processing module is specifically used to: perform streaming processing on the above observation dataset to obtain the cancellation count sequence and change count sequence for each path associated with the above target submarine optical cable; and determine the statistical variance of the cancellation count and the statistical variance of the change count for each path based on the cancellation count sequence and change count sequence for each path through the variance standard calculation module.

[0016] Another possible implementation is that the above-mentioned generation module is specifically used to: generate the above-mentioned routing anomaly alarm signal when the first condition is met; wherein the above-mentioned first condition includes at least one of the following: the statistical variance of the cancellation count of each path is greater than the historical cancellation count baseline mean; the statistical variance of the change count of each path is greater than the historical change count baseline mean.

[0017] Thirdly, this application provides an electronic device comprising: a processor and a memory; the memory stores a program or instructions executable on the processor, wherein the program or instructions, when executed by the processor, implement the method of the first aspect described above.

[0018] Fourthly, this application provides a readable storage medium on which a program or instructions are stored, which, when executed by a computer, implement the method of the first aspect described above.

[0019] Fifthly, this application provides a computer program product stored in a storage medium, which, when executed by a computer, implements the method described in the first aspect.

[0020] In a sixth aspect, embodiments of this application provide a chip including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect.

[0021] The beneficial effects of the second to sixth aspects mentioned above are described in the corresponding description of the first aspect and will not be repeated here. Attached Figure Description

[0022] Figure 1 A schematic diagram of the network architecture for an application of a fault location method provided in this application embodiment;

[0023] Figure 2 A flowchart illustrating a fault location method provided in an embodiment of this application;

[0024] Figure 3 A flowchart illustrating another fault location method provided in an embodiment of this application;

[0025] Figure 4 A flowchart illustrating another fault location method provided in an embodiment of this application;

[0026] Figure 5 A flowchart illustrating another fault location method provided in an embodiment of this application;

[0027] Figure 6 A flowchart illustrating another fault location method provided in an embodiment of this application;

[0028] Figure 7 A flowchart illustrating the implementation process of a fault location method provided in this application embodiment;

[0029] Figure 8 This is a schematic diagram of the structure of a fault location device provided in an embodiment of this application;

[0030] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0031] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0032] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0033] The terms "at least one," "at least one of," etc., used in the specification and claims of this application refer to any one, any two, or a combination of two or more of the included items. For example, at least one of a, b, and c can mean: "a," "b," "c," "a and b," "a and c," "b and c," and "a, b, and c," where a, b, and c can be single or multiple. Similarly, "at least two" refers to two or more items, and its meaning is similar to that of "at least one."

[0034] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0035] The following explains some concepts and terms involved in the fault location method provided in the embodiments of this application.

[0036] I. Submarine Optical Cables

[0037] Submarine optical cables are the core infrastructure for intercontinental communication on the global internet. They mainly consist of trunk optical cables, branch optical cables, submarine branching units (BUs), submarine landing stations, and repeaters. The trunk section is typically deployed in deep-sea areas to carry high-capacity intercontinental backbone communications. Branch optical cables are responsible for connecting trunk signals to multiple coastal cities or regions. Repeaters are periodically deployed on the seabed based on the attenuation characteristics of optical fibers to amplify long-distance propagating optical signals. Submarine landing stations are located at the land endpoints and are key nodes for interconnecting the submarine optical cable system with the terrestrial fiber optic network, undertaking important functions such as signal terminal processing, power supply, and monitoring.

[0038] As the primary medium for international communication links, submarine optical cables handle over 95% of global cross-border data traffic, playing an irreplaceable role in international internet services, cloud computing interconnection, and cross-border data center synchronization. Compared to satellite communication, submarine optical cables offer lower latency, higher bandwidth, and more stable transmission performance, thus becoming the most critical intercontinental transmission method in modern information infrastructure.

[0039] However, submarine optical cables, operating in the deep-sea environment, are susceptible to various external factors that can lead to interruptions or performance degradation. Common causes include: natural events such as submarine earthquakes, geological activity, and tsunamis causing cable breakage; mechanical damage from human activities such as ship anchoring and trawling; and equipment problems such as cable aging, amplifier failures, or power system malfunctions. Statistics show that over 70% of submarine optical cable failures globally each year are related to human activity. When submarine optical cables are interrupted, they typically have a significant impact on cross-border communications. Typical phenomena include: a sharp drop in international link bandwidth, cross-border traffic being forced to detour through other intercontinental links leading to increased congestion, a significant increase in transoceanic communication round-trip time (RTT), and large-scale BGP routing jitter and AS-level path changes. In severe cases, it can trigger a chain reaction of regional network unavailability and a decline in international internet service quality, affecting multiple regions.

[0040] Geographically, submarine optical cables typically employ a "trunk line + multiple branches" structure, with most cables laid along specific trenches or continental shelf edges to avoid areas of intense geological activity. Furthermore, submarine cable landing stations are usually concentrated in coastal cities or port areas with stable power supply, low geological risk, and international network exchange capabilities. These landing stations are often directly associated with a small number of ASs (Autonomous Systems), resulting in a significant concentration of their geographical locations and AS distribution. If a landing station fails, its impact can spread to multiple related countries or intercontinental links.

[0041] In conclusion, although submarine optical cable systems constitute the core of the global communication network, their vulnerability makes the detection and location of submarine optical cable breaks an important research topic for ensuring international communication security.

[0042] II. Autonomous System

[0043] An Autonomous System (AS) is a collection of networks that publish internet routes under the control of a single technical management authority and using a unified routing policy. The global internet is composed of tens of thousands of interconnected ASs, each with a unique Autonomous System Number (ASN), typically representing entities such as telecommunications operators, internet service providers, content delivery networks (CDNs), large data centers, or cross-border communication hubs. ASs form the physical and logical connectivity structure of the internet by establishing peering or switching relationships with other ASs.

[0044] In cross-border communication scenarios, there is a natural mapping relationship between Autonomous Systems (AS) and submarine fiber optic cable infrastructure. Most international communication traffic must enter or leave a specific area through a small number of key ASs where submarine fiber optic cable landing stations are located; therefore, these ASs often serve as intercontinental exits or entry points. Due to the limited number of landing stations and the high concentration of cross-border links, once the submarine fiber optic cable upon which the relevant AS depends is interrupted, its routing announcements will exhibit abnormal characteristics such as path convergence failure, loss of reachability of cross-border prefixes, and sudden changes in the Autonomous System Path (AS_PATH). Furthermore, the importance of Autonomous Systems in the global routing propagation process is reflected in:

[0045] (1) The topology between different ASes determines the reachability of the global Internet;

[0046] (2) The geographical location of AS is closely related to the landing point of submarine optical cable, and can be used to infer the cross-border path of traffic;

[0047] (3) The interconnection method between ASs (private interconnection, shared interconnection, public network interconnection) directly affects the traffic flow and link redundancy.

[0048] Therefore, understanding the structural characteristics of autonomous systems is crucial for inferring submarine fiber optic cable outages based on route observation data.

[0049] III. Border Gateway Protocol

[0050] BGP is the core protocol in the Internet used for exchanging routing reachability information between autonomous systems. As the control plane protocol of the global Internet, BGP is responsible for maintaining the Internet's AS-level topology and propagating reachable paths for each prefix through an incremental update mechanism, enabling different autonomous systems to dynamically select paths and exit points.

[0051] BGP routing information mainly includes key fields such as prefix, AS_PATH, next-hop, and community attribute. Among these, AS_PATH explicitly identifies the sequence of autonomous systems a data packet traverses during transmission and is the core basis for inferring link reachability. When a physical link fails, such as a submarine fiber optic cable break, the corresponding autonomous system will be unable to continue advertising the reachability of a specific prefix, leading to BGP prefix withdrawal, path hopping, AS_PATH extension, or switching.

[0052] In actual operation, BGP propagation has the following characteristics:

[0053] (1) High real-time performance: Route updates will be rapidly propagated to global monitoring points after link changes;

[0054] (2) Significant cross-border dependence: Topological changes in international links are directly reflected in BGP update behavior;

[0055] (3) Available from the public network: Platforms such as IP Network Routing Information Service (RIPE RIS) provide global BGP observation points, which facilitates open monitoring;

[0056] (4) Logical expression of physical layer events: Physical link failures will manifest as identifiable routing anomalies at the BGP layer.

[0057] Therefore, BGP plays the role of "logic layer early warning" in submarine optical cable outage events: when a submarine optical cable or landing station is interrupted, the resulting symptoms such as path unreachability, international link detours, withdrawals, and AS path reconstruction will manifest through BGP in a short period of time. By analyzing BGP update behavior, combined with the geographical distribution of autonomous systems and submarine optical cable topology information, the possible scope and location of submarine optical cable faults can be inferred without requiring internal data from the submarine optical cable operator.

[0058] IV. Routing Interruption

[0059] Routing outages refer to abnormal changes in the reachability of routes between autonomous systems on the Internet within a short period of time, resulting in specific prefixes becoming unreachable, withdrawn, or experiencing path jumps globally. Routing outages are typically caused by factors such as link failures, equipment malfunctions, and changes in routing policies. Among these, the interruption of cross-border links or submarine optical cables is one of the most typical causes of widespread routing anomalies.

[0060] In intercontinental communications, submarine optical cables bear the primary responsibility for data transmission. Their breakage or damage directly impacts the cross-border connectivity of related ASs (Autonomous Systems). When a submarine optical cable is interrupted, the critical ASs at both ends of the connection will be unable to continue advertising reachable paths for certain prefixes, forcing these prefixes to be withdrawn from the BGP routing table. Simultaneously, traffic throughout the region may be passively redirected to other optical cables or links, resulting in numerous abrupt changes in AS_PATH, including significantly longer paths, exit point switching, and AS sequence reconstruction.

[0061] In actual operation, routing interruptions have the following characteristics:

[0062] (1) Prefix withdrawals are highly concentrated: a large number of Withdrawals usually occur within a few minutes;

[0063] (2) Wide range of impact: It involves multiple regions, multiple operators, and even multiple intercontinental exports;

[0064] (3) High synchronicity of path changes: Multiple BGP observation points will simultaneously observe AS path jumps;

[0065] (4) Cross-border link sensitivity is prominent: Link interruption has the most significant impact on BGP inter-domain paths.

[0066] Especially in incidents involving submarine optical cables, physical layer failures can lead to logical layer routing outages exhibiting significant cross-domain synchronization anomalies. For example, when a submarine optical cable breaks, the affected ASs cannot maintain their original effective cross-border connections, resulting in path interruptions, route convergence failures, and the disappearance of numerous prefixes from the global routing view within a short period. Simultaneously, traffic in the affected area will be diverted to backup submarine optical cables or terrestrial cross-border lines, causing increased path latency, routing oscillations, and AS switching. Because submarine optical cables are deployed in deep waters and have long maintenance cycles, actual recovery times are often lengthy. Therefore, the abnormal behavior of routing outages at the BGP layer is persistent and can have a cascading impact on global network performance. Timely detection and location of routing outages are crucial for identifying potential submarine optical cable faults and ensuring the quality of cross-border communication. Therefore, how to discover and locate routing outages caused by submarine optical cable faults based on publicly available internet routing data, without relying on internal operator monitoring methods, has become a key issue in current research and engineering practice.

[0067] The fault location method, apparatus, equipment, medium, and program product provided in this application embodiment can be applied to scenarios such as optical cable fault location, path visualization, and routing anomaly notification detection.

[0068] As a core infrastructure carrying cross-border data traffic, the operational reliability of submarine optical cables directly affects the normal operation of international internet services, cloud computing interconnection, and other businesses. However, submarine optical cables are located in the deep-sea environment and are susceptible to interruptions due to natural and human factors. Therefore, locating submarine optical cable faults has become an important research topic for ensuring international communication security.

[0069] Currently, the most widely used optical cable fault detection and localization scheme in submarine optical cable location technology is OTDR (Optical Time Domain Reflectometry) technology based on the principle of optical time domain reflectometry. This scheme typically consists of a pulsed laser, an optical directional coupler or circulator, a photodetector, a signal processing unit, and a display and control module to perform detection and localization. Its core working principle is based on the backscattering and reflection characteristics of light propagating in optical fibers: the light source sends a high-power light pulse to the fiber under test. When the light pulse propagates within the fiber, Rayleigh scattering occurs due to the microscopic inhomogeneities in the fiber's density. When the light pulse encounters a point of abrupt change in refractive index, such as a fiber break, a moving connector, or a mechanical joint, Fresnel reflection occurs. Some of the scattered and reflected light returns along the original path, is separated by the optical directional coupler, and then enters the photodetector.

[0070] The specific implementation steps typically include: First, the system drives a laser to generate optical pulses of specific wavelengths and pulse widths via a pulse generator and injects them into the optical fiber under test; second, a detector receives the backlight signals returned along the fiber in real time, converts them into electrical signals, and amplifies them; third, a signal processing unit samples and averages the acquired signals to improve the signal-to-noise ratio, and uses the formula... (in At the speed of light, For signal round-trip time, The physical distance to the fault point or event point is calculated (using the fiber refractive index); finally, by analyzing the reflection amplitude and the slope of the scattering curve, the fault type (such as breakpoint, fusion splice loss or macrobend) is determined and the link status curve is output.

[0071] Another existing technology utilizes BGP data for control plane analysis and fault reasoning, typically consisting of BGP data acquisition probes distributed across key global nodes, a data preprocessing module, a routing event analysis engine, and a topology mapping database. Its core operating principle is based on the convergence mechanism of the BGP protocol: when an underlying physical link or logical connection is interrupted, the affected router broadcasts BGP update messages to its neighboring nodes to revoke unreachable routes or advertise new paths. The system infers underlying faults by analyzing the characteristics of these massive amounts of messages.

[0072] Key implementation steps typically include: First, the system establishes BGP connections with multiple core routers globally, passively receiving and storing full routing table snapshots and incremental update messages based on the Routing Information Base (RIB) in real time; second, it parses key attributes in the messages, such as network prefixes, AS paths, and next hops; third, it constructs AS-level interconnection topology using graph theory algorithms to identify common failure edges where multiple routing paths are simultaneously interrupted; finally, combined with time window correlation analysis, when a large-scale route cancellation or path detour is detected between specific AS pairs within a short period, it determines that the logical link is faulty.

[0073] However, traditional OTDR technology still has significant drawbacks and limitations in practical applications. This technology is highly dependent on physical access resources; detection requires intrusive connections to the fiber optic cable terminal or the deployment of dedicated hardware monitoring stations. This results in critical monitoring data such as submarine cable routing information and optical power changes being confined to the operator's internal system. Third-party research institutions or non-directly connected entities cannot obtain relevant data, making it difficult to detect anomalies from an external perspective immediately after an event occurs. OTDR's measurement mechanism requires long signal sampling and averaging times, limiting monitoring frequency. It typically only supports periodic scanning or manually triggered tests, failing to achieve real-time online monitoring at the minute or even second level, and making it difficult to capture transient faults. Furthermore, due to the inherent contradiction between the saturation recovery time and dynamic range of photodetectors, existing technologies also suffer from inherent physical limitations such as large blind zones at short distances, low resolution at long distances, and difficulty in penetrating submarine cable repeaters for end-to-end detection.

[0074] Anomaly detection techniques based on routing protocols also have significant drawbacks and limitations in practical applications. The granularity of fault location is relatively coarse, only able to pinpoint logical connection interruptions at the autonomous system level, unable to precisely map to specific physical fiber optic cable segments or geographical coordinates, and difficult to distinguish between physical fiber optic cable cuts and path changes caused by human adjustments to routing strategies. The inherent path hiding mechanism and convergence delay of the BGP protocol result in detection lag; there is typically a time difference of several seconds to several minutes between the occurrence of a physical fault and the complete convergence of the BGP route and its observation by the data collection points, failing to meet the millisecond-level real-time detection requirements for high-frequency oscillations or transient faults. This technology is highly susceptible to noise interference from path exploration phenomena during fault reasoning, leading to numerous false alarms during route oscillations. Furthermore, for stub networks or private interconnection links lacking redundant paths, monitoring blind spots often exist due to incomplete coverage of data collection points.

[0075] To address the aforementioned technical problems, this application provides a fault location method, apparatus, device, medium, and program product. When locating faults in submarine optical cables, a routing anomaly alarm signal can first be generated based on real-time variance and historical benchmark mean. Then, in response to this routing anomaly alarm signal, parallel detection processing is performed on the target IP associated with the target AS adjacency pair identifier and multiple submarine optical cable interface IPs to obtain the fault location information corresponding to the target submarine optical cable. This eliminates the need for lengthy signal sampling and processing time, enabling real-time online monitoring at the minute or even second level. This allows for the detection of anomalies and the capture of transient faults at the first moment of fault occurrence, enabling timely location of submarine optical cable faults.

[0076] The following description, in conjunction with the accompanying drawings, details the fault location methods, apparatus, devices, media, and program products provided in the embodiments of this application.

[0077] Figure 1 The network architecture of a fault location method provided in an embodiment of this application is illustrated. For example... Figure 1 As shown, the network architecture includes a fault location device 101 and a terminal device 102. The fault location device 101 and the terminal device 102 are interconnected.

[0078] In some embodiments, the fault location device 101 may be a server, a computer, or a processor or processing unit within a server or computer. The server may be a single server or a server cluster consisting of multiple servers. It should be noted that the specific device form of the fault location device 101 is not limited in the embodiments of this application. Figure 1 The fault location device 101 is used as an example of a single server.

[0079] In some embodiments, the terminal device may be a mobile phone, tablet computer, laptop computer, handheld computer, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, personal computer (PC), ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc., and the embodiments of this application do not specifically limit it. Figure 1 The example shown is a mobile phone, with terminal device 102 as an example.

[0080] In some embodiments, the fault location device 101 filters the BGP data stream based on the topology information of at least one submarine optical cable to obtain an observation dataset of the target submarine optical cable; the fault location device 101 streams the observation dataset to obtain the statistical variance of the cancellation count and the statistical variance of the change count for each path associated with the target submarine optical cable; the fault location device 101 generates a routing anomaly alarm signal based on the statistical variance of the cancellation count and the historical mean of the cancellation count for each path, and / or the statistical variance of the change count and the historical mean of the change count for each path; in response to the routing anomaly alarm signal, the fault location device 101 performs parallel detection processing on the target IP associated with the target AS adjacency pair identifier and the IPs of multiple submarine optical cable interfaces, and outputs the fault location information corresponding to the target submarine optical cable.

[0081] Then, the fault location device 101 can send the fault location information to the terminal device 102. After receiving the fault location information, the terminal device 102 can submit a work order to the corresponding Internet service provider to report the fault, providing the specific target IP and the timestamp of the abnormal fault; at the same time, if there is multi-line BGP access, the terminal device 102 can manually adjust the egress weight to urgently transfer user traffic to the normal path.

[0082] It should be noted that the network architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As network architectures evolve, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0083] See Figure 2 This is a flowchart illustrating a fault location method provided in an embodiment of this application. Figure 2 As shown, the fault location method provided in this application embodiment can be implemented by the above-mentioned fault location device, specifically including the following steps 201 to 204.

[0084] Step 201: The fault location device filters the BGP data stream based on the topology information of at least one submarine optical cable to obtain the observation dataset of the target submarine optical cable.

[0085] In some embodiments of this application, the topology information of the submarine optical cable is a submarine optical cable topology mapping dictionary, which includes the AS adjacency pair and interface IP corresponding to each submarine optical cable. The AS adjacency pair represents a combination of two ASNs corresponding to the IP addresses at both ends of adjacent submarine optical cables.<ASN_A,ASN_B> The interface IP represents the physical interface address of the submarine optical cable at the IP layer, and is marked as the near-end interface IP and the far-end interface IP respectively.

[0086] In some embodiments of this application, the aforementioned BGP data stream refers to user service traffic affected by BGP routing decisions. Traffic refers to the collection of all packets passing through a network link or device interface within a certain period, and a packet refers to a single data block transmitted in the network. The fault location device sequentially reads each packet in the BGP data stream using the RIPE RIS update file. In some embodiments of this application, the aforementioned at least one submarine optical cable can be one or more submarine optical cables within a certain geographical area set.

[0087] In some embodiments of this application, the target submarine optical cable is one or more of the above-mentioned submarine optical cables.

[0088] In some embodiments of this application, the above-mentioned observation dataset includes a portion of the messages obtained by filtering the BGP data stream. This portion of the messages contains an AS adjacency pair that is consistent with the ASN of the source AS and one AS adjacency pair in the submarine cable AS adjacency pair set. The observation dataset serves as the input data source for the subsequent step S202 fault location device to perform streaming processing.

[0089] In some embodiments of this application, combined with Figure 2 ,like Figure 3 As shown, step 201 can be implemented through steps 201a and 201b below.

[0090] Step 201a: The fault location device performs source AS matching filtering on the BGP data stream based on the topology information of at least one submarine optical cable to obtain the initial observation dataset.

[0091] In some embodiments of this application, the specific process of the above-mentioned source AS matching and filtering includes: the fault location device checks whether the rightmost ASN of the AS-PATH attribute in each message is consistent with the set source AS. If a message is inconsistent, the fault location device discards the message. If a message is consistent, the initial observation data is obtained. The initial observation dataset is constructed from multiple initial observation data.

[0092] In some embodiments of this application, the aforementioned initial observation dataset represents a portion of the packets in the BGP data stream that are consistent with the ASN of the source AS, and can be matched with the source IP that passes through the submarine optical cable during the traceroute detection process.

[0093] Step 201b: The fault location device performs fingerprint inclusion matching filtering on the initial observation dataset to obtain the observation dataset.

[0094] In some embodiments of this application, the specific process of the fingerprint matching and filtering process includes: the fault location device checks whether any AS adjacency pair in the submarine optical cable AS adjacency pair set exists in the AS-PATH sequence of each message; if a message does not exist, the fault location device discards the message; if a message exists, the message is stored in the submarine optical cable observation dataset.

[0095] In this way, the fault location device performs source AS matching and fingerprint inclusion matching filtering on the BGP data stream to obtain the observation dataset. This filters out the ASNs that do not match the source AS and the AS adjacency pairs in the submarine cable AS adjacency pair set from the BGP data stream, enabling the quick identification of the matching observation dataset from the massive BGP data stream and reducing storage costs.

[0096] Step 202: The fault location device performs streaming processing on the observation dataset to obtain the statistical variance of the cancellation count and the statistical variance of the change count for each path associated with the target submarine optical cable.

[0097] In some embodiments of this application, the above-described streaming processing is a real-time data computation processing mode.

[0098] In some embodiments of this application, the aforementioned cancellation count statistical variance represents the statistical variance of the number of prefix cancellations (also known as prefix withdrawals) that occur on each path of a target submarine optical cable AS adjacency pair within a certain period of time. Prefix cancellation is one of the abnormal changes in the route reachability between ASs in a short period of time when the submarine optical cable is interrupted.

[0099] In some embodiments of this application, the aforementioned change count statistical variance represents the statistical variance of the number of path changes that occur on each path of a target submarine optical cable AS adjacency pair within a certain period of time. When the path change is due to the interruption of the submarine optical cable, one of the phenomena is that the routing reachability between ASs changes abnormally in a short period of time.

[0100] For example, the aforementioned time period could be 0.5 hours, 1 hour, or 1.5 hours, etc.

[0101] In some embodiments of this application, combined with Figure 2 ,like Figure 4 As shown, step 202 can be implemented through steps 202a and 202b below.

[0102] Step 202a: The fault location device performs streaming processing on the observation dataset to obtain the cancellation count sequence and change count sequence for each path associated with the target submarine optical cable.

[0103] In some embodiments of this application, the above-mentioned revocation count sequence is a plurality of numerical sequences corresponding to the prefix revocation count of each path of the target submarine optical cable AS adjacency pair.

[0104] In some embodiments of this application, the aforementioned change counting sequence is a plurality of numerical sequences corresponding to the number of path changes for each path of the target submarine optical cable AS adjacency pair.

[0105] Step 202b: The fault location device uses the variance standard calculation module to determine the statistical variance of the cancellation count and the statistical variance of the change count for each path based on the cancellation count sequence and the change count sequence for each path.

[0106] In some embodiments of this application, the variance standard calculation module is a pre-set calculation framework of the fault location device. The variance standard calculation module can determine the statistical variance of the cancellation count and the statistical variance of the change count for each path using the following formula (1):

[0107] ; (1)

[0108] in, Let represent the statistical variance, N represent the number of values ​​in the sequence, i represent the index of the value in the sequence, and x represent the number of values ​​in the sequence. i This represents the i-th value. This represents the average of N values.

[0109] In some embodiments of this application, the variance standard calculation module is started immediately after the undo count sequence and change count sequence for each path are obtained.

[0110] In some embodiments of this application, the above-mentioned variance standard calculation module can also calculate the statistical variance of all values ​​in the cancellation count sequence using the above formula (1) to obtain the cancellation count statistical variance.

[0111] In some embodiments of this application, the above-mentioned variance standard calculation module can also calculate the statistical variance of all values ​​in the change count sequence using the above formula (1) to obtain the change count statistical variance.

[0112] In this way, the fault location device performs streaming processing on the observation dataset to obtain the statistical variance of the cancellation count and the statistical variance of the change count for each path associated with the target submarine optical cable. It then determines the changing trend of abnormal BGP routing states in real time, thereby quickly identifying abnormal target submarine optical cable AS adjacency pairs. This improves the efficiency of fault location.

[0113] Step 203: The fault location device generates a routing anomaly alarm signal based on the statistical variance of the cancellation count and the historical cancellation count baseline mean for each path, and / or the statistical variance of the change count and the historical change count baseline mean for each path.

[0114] In some embodiments of this application, the aforementioned historical cancellation count benchmark mean represents the arithmetic mean of the cancellation count variance samples stored in the historical variance benchmark library.

[0115] In some embodiments of this application, the aforementioned historical change count benchmark mean represents the arithmetic mean of the change count variance samples stored in the historical variance benchmark library.

[0116] In some embodiments of this application, the above-mentioned abnormal alarm signal is used by the fault location device to facilitate quick querying of the topology mapping dictionary corresponding to the AS adjacency pair ID.

[0117] In some embodiments of this application, the above-mentioned abnormal alarm signal includes an abnormal timestamp, AS adjacency pair ID, current variance value, and baseline mean.

[0118] In some embodiments of this application, combined with Figure 2 ,like Figure 5 As shown, step 203 above can be specifically implemented through step 203a below.

[0119] Step 203a: If the first condition is met, the fault location device generates a routing anomaly alarm signal.

[0120] In some embodiments of this application, the first condition includes at least one of the following: the statistical variance of the cancellation count for each path is greater than the historical average of the cancellation count; the statistical variance of the change count for each path is greater than the historical average of the change count.

[0121] For example, assuming the target submarine optical cable is associated with paths 1, 2, and 3, the fault location device generates the aforementioned routing anomaly alarm signal if at least one of the following conditions is met:

[0122] The statistical variance of the cancellation count for Path 1 is greater than the historical baseline mean of the cancellation count for Path 1, and the statistical variance of the cancellation count for Path 2 is greater than the historical baseline mean of the cancellation count for Path 2, and the statistical variance of the cancellation count for Path 3 is greater than the historical baseline mean of the cancellation count for Path 3.

[0123] The statistical variance of change counts for path 1 is greater than the historical baseline mean of change counts for path 1, the statistical variance of change counts for path 2 is greater than the historical baseline mean of change counts for path 2, and the statistical variance of change counts for path 3 is greater than the historical baseline mean of change counts for path 3. Thus, the fault location device can quickly characterize the abnormal routing state by comparing the real-time variance with the historical variance baseline values, thereby generating a timely routing anomaly alarm signal.

[0124] Step 204: In response to the routing anomaly alarm signal, the fault location device performs parallel detection processing on the target IP associated with the target AS adjacency pair identifier and the multiple submarine optical cable interface IPs, and outputs the fault location information corresponding to the target submarine optical cable.

[0125] In some embodiments of this application, the target IP associated with the target AS adjacency pair identifier represents the key value of the submarine optical cable topology mapping dictionary corresponding to the AS adjacency pair. The key value of the submarine optical cable topology mapping dictionary also includes: submarine optical cable name, near-end interface IP list and far-end interface IP list.

[0126] In some embodiments of this application, the aforementioned multiple submarine optical cable interface IPs represent the near-end interface IPs and far-end interface IPs of multiple submarine optical cables at the IP layer.

[0127] In some embodiments of this application, the above-described parallel probing process means simultaneously probing the target IP associated with the AS adjacency pair identifier and multiple submarine optical cable interface IPs, probing whether each path of the target IP associated with the AS adjacency pair identifier and multiple submarine optical cable interface IPs is reachable.

[0128] In some embodiments of this application, the above-mentioned fault location information may also be referred to as a fault location report, including the name of the faulty submarine optical cable and the IP status information of the near and far end interfaces.

[0129] In some embodiments of this application, combined with Figure 2 ,like Figure 6 As shown, step 204 can be implemented through steps 204a and 204b below.

[0130] Step 204a: The fault location device acquires the first path characteristics corresponding to the target IP and the second path characteristics corresponding to the multiple submarine optical cable interface IPs.

[0131] In some embodiments of this application, the first path feature represents a real-time path feature, which is characterized as an AS-PATH sequence that passes through the target AS adjacency pair identifier associated with the target IP in real time.

[0132] In some embodiments of this application, the second path feature represents the historical baseline path feature, which is characterized as the optimal AS-PATH sequence (with the fewest cancellation counts and path change counts) that has historically passed through multiple submarine optical cable interface IPs.

[0133] Step 204b: If the first path feature matches the second path feature, the fault location device performs route detection on multiple submarine optical cable interface IPs to obtain fault location information.

[0134] In some embodiments of this application, the first path feature matches the second path feature, which can be understood as: the matching degree between the first path feature and the second path feature is greater than or equal to the matching degree threshold.

[0135] For example, the matching threshold mentioned above can be 85%, 90%, or 95%, etc.

[0136] In some embodiments of this application, the above-described route detection process includes: probing the complete path from the terminal device to the target IP and measuring the round-trip delay for each hop.

[0137] In some embodiments of this application, during the route detection process described above, if the target IP is reachable (the ping probe command of the route detection can be responded to), and the target IP does not contain any known near-end or far-end interface IPs of the submarine optical cable, then a path drift phenomenon is determined to have occurred. If the target IP is reachable and contains any known near-end or far-end interface IPs of the submarine optical cable, the fault location device executes an exclusive disambiguation logic rule to obtain fault location information.

[0138] In some embodiments of this application, the aforementioned exclusive disambiguation logic rule includes: if the near-end and far-end interface IP status of a specific submarine optical cable (denoted as Cable_X) is unreachable, while the near-end and far-end interface IP statuses of other submarine optical cables (Cable_Y, Cable_Z, etc.) adjacent to the same AS are reachable, then the fault location device outputs the fault location result as the physical submarine optical cable Cable_X; if all interface IP statuses in the list are unreachable, then the output fault location result is: the submarine optical cable landing station or all physical submarine optical cables are broken. The final output is submarine optical cable fault location information, including the name of the faulty submarine optical cable and the near-end and far-end interface IP status information.

[0139] In this way, the fault location device performs parallel detection processing on the target IP associated with the target AS adjacency pair identifier and multiple submarine optical cable interface IPs. When the first path feature and the second path feature match, the fault location device performs route detection on multiple submarine optical cable interface IPs, effectively distinguishing between path drift phenomenon and physical submarine optical cable interruption phenomenon, and significantly improving the accuracy of fault detection.

[0140] The fault location method provided in this application, when locating submarine optical cable faults, first generates a routing anomaly alarm signal based on real-time variance and historical benchmark mean. Then, in response to this routing anomaly alarm signal, it performs parallel detection processing on the target IP associated with the target AS adjacency pair identifier and multiple submarine optical cable interface IPs to obtain the fault location information corresponding to the target submarine optical cable. This eliminates the need for lengthy signal sampling and processing time, enabling real-time online monitoring at the minute or even second level. This allows for the detection of anomalies and the capture of transient faults at the first moment of fault occurrence, enabling timely location of submarine optical cable faults.

[0141] The fault location method of this application will be described below through specific embodiments.

[0142] like Figure 7 As shown, the implementation process of a fault location method provided in this application includes the following S1 to S3:

[0143] S1, Construction of Submarine Optical Cable Topology Observation System

[0144] Load a global key region IP set for active traceroute detection (i.e., the route detection mentioned above) to construct the original path dataset. Utilize IP-ASN mapping and a physical map of submarine optical cables to perform dual analysis of the paths, identifying the AS adjacency pairs and key interface IPs (i.e., the interface IPs mentioned above) corresponding to the physical submarine optical cables, and construct a submarine optical cable topology mapping dictionary containing logical and physical mapping relationships. Based on this dictionary, filter BGP data streams to generate a dedicated observation dataset (i.e., the observation dataset mentioned above) for specific submarine optical cables. Step S1 specifically includes:

[0145] S1a. First, data loading and preprocessing are performed. This involves loading a list of popular global website domains and a list of data center IPs from major overseas carrier DNS servers, selecting regions including North America, Europe, Asia Pacific, and Australia—areas without land borders with mainland China. The Domain Name Server (DNS) resolution service is called to convert the domain name list into a set of IP addresses, merging them to construct a global candidate target IP set. The GeoIPDatabase is loaded to establish an IP geolocation mapping table. The global candidate target IP set is iterated through. For each candidate IP, the IP geolocation mapping table is queried to extract its country / region label. If the label belongs to a preset set of key geographic regions, the IP is stored in the target IP dictionary. This dictionary is a one-dimensional dictionary where the key is the target IP address, and the values ​​are the geographic region label and carrier label to which the IP belongs.

[0146] S1b: Initialize the probe source node, configuring the source IP to a domestic probe node address. Sequentially read each target IP from the target IP dictionary and send a traceroute probe packet to that target IP. Receive and parse the probe-returned packets, extracting the routing IP address and sequence of each hop to construct the original path dataset. This dataset consists of several path records, each with a data structure defined as a five-tuple: <probe timestamp, source IP address, destination IP address, traceroute path sequence list>. Once all target IPs have been probed, the original path dataset is complete.

[0147] S1c: Load the IP-ASN mapping database, which is a one-dimensional dictionary where the key is the IP prefix and the value is the corresponding Autonomous System number. Load the Nautilus dataset, which is a lookup table recording the geographical paths of major submarine optical cables worldwide corresponding to IP links. Sequentially read each record in the raw path dataset generated in step S1b. Extract the traceroute path sequence from the record. Perform the first level of parsing: traverse each IP address in the IP path, query the IP-ASN mapping database, and convert the sequence of IPs into an ASN path sequence. Perform the second level of parsing: match the IP path with the submarine optical cable physical topology database, identify specific IP hop count segments passing through the submarine optical cable in the path, and mark the physical submarine optical cable name corresponding to the segment. Align the above ASN path sequence with the physical submarine optical cable markings. Identify the ASNs corresponding to the IP addresses at both ends of the physical submarine optical cable, extract the combination of the two adjacent ASNs, and define them as submarine optical cable AS adjacency pairs. At the same time, extract the physical interface addresses corresponding to the submarine optical cable AS adjacency pairs at the IP layer, and mark them as the near-end interface IP and the far-end interface IP, respectively. Construct a submarine optical cable topology mapping dictionary. This dictionary is a nested dictionary, where the keys in the first dimension are the submarine optical cable AS adjacency pairs.<ASN_A,ASN_B> The corresponding dictionary value is a sub-dictionary containing physical attributes. The keys of the sub-dictionary include: the destination IP address of the path entry, the submarine cable name, and a list of near-end and far-end interface IPs. Once the original path dataset has been traversed, the submarine cable topology mapping dictionary is complete.

[0148] S1d: Load the update file of the BGP data packet stream RIPE RIS, and sequentially read each packet in the BGP data stream. First, perform source AS matching: check if the rightmost ASN of the AS-PATH attribute in the packet matches the set source AS; if they do not match, discard the packet. Second, perform fingerprint inclusion matching: check if any AS adjacency pair in the AS-PATH sequence of the packet exists in the set of submarine optical cable AS adjacency pairs; if not, discard the packet. Store the filtered packets in a dedicated submarine optical cable observation dataset. This dataset is stored in time windows, with each time window containing all BGP update packets passing through a specific submarine optical cable within that time period, serving as the input data source for fault feature extraction in the subsequent step S2.

[0149] S2. Volatility-based fault detection

[0150] Streaming processing is performed on dedicated observation data for submarine optical cables to maintain a prefix state dictionary for identifying route cancellation and path detour events. A sliding window mechanism is used to calculate the statistical variance of cancellation and change counts in real time, and this variance is compared with the historical 24-hour benchmark mean for volatility overshoot. When the real-time variance significantly exceeds the historical benchmark, the route status is determined to be extremely unstable, and a route anomaly alarm signal containing AS adjacency pair IDs is generated. Step S2 specifically includes:

[0151] S2a. Receive the submarine optical cable-specific observation dataset output from step S1. Initialize the prefix path status dictionary, which is a one-dimensional dictionary where the key is the routing prefix and the value is the most recent known ASN path sequence for that prefix. Set the statistical time window. Define a routing oscillation feature dictionary to store the counting results within the current time window. This dictionary is a two-dimensional dictionary, with the first dimension as the timestamp as the key, the second dimension as the submarine optical cable AS adjacency pair as the key, and the values ​​as feature vectors containing <cancellation counts and path change counts>, all initialized to 0. Receive the submarine optical cable-specific observation dataset output from step S1 and iterate through the messages in the dataset.

[0152] S2b: If the message type is "withdraw," and the historical AS path of this route prefix contains monitored submarine fiber optic cable AS adjacency pairs, then in the route oscillation feature dictionary, the corresponding withdrawal count is incremented by 1, and the record for this prefix is ​​deleted from the prefix path state dictionary. If the message type is "announce," extract the route prefix and the new AS path sequence from the message (denoted as...). ). Query the prefix path status dictionary to obtain the historical AS path for that prefix (denoted as ). If the prefix record does not exist in the dictionary, it is stored directly without being counted in the oscillation. If the record exists in the dictionary, an XOR check for the existence of adjacent pairs is performed: check... Does it include monitored submarine fiber optic cable AS adjacent pairs? Also check... Does the data not include the adjacent pair of the submarine optical cable AS? Count trigger: if and only if ( (includes) and ( When the condition (excluding) is met, it is determined that a submarine optical cable path detour has occurred. The path change count for the current time window is incremented by 1, and the value corresponding to the prefix in the "Prefix Path Status Dictionary" is updated. .

[0153] S2c, for each monitored submarine optical cable AS adjacency pair, the system maintains two real-time observation queues in memory, one for storing the undo count sequence. ) and path change count sequence ( The queue length is set to... (Corresponding to a 1-hour time window, with one sampling point every 5 minutes). Whenever step S2b completes a 5-minute statistical period, a First-In-First-Out (FIFO) strategy is adopted: the oldest count value at the head of the queue is removed, and the count value for the current time window is pushed to the tail of the queue, maintaining a constant queue length of 12. After each update of the observation queue, the variance calculation module (i.e., the aforementioned variance standard calculation module) is immediately triggered. For... and Calculate the variance of each of the 12 values ​​in the dataset, denoted as . (i.e., the variance of the cancellation count statistics mentioned above) and (i.e., the change count statistical variance mentioned above). This variance value characterizes the degree of turbulence in the BGP routing status within the current 1-hour window.

[0154] S2d: Construct a historical variance benchmark library to store variance samples from the past 24 hours. This library contains variance records for 24 historical time periods (each time period corresponds to a 1-hour window). The system periodically (e.g., daily at 00:00 or on a rolling basis) calculates historical benchmark values ​​(i.e., the historical revocation count benchmark mean and the historical change count benchmark mean mentioned above): reading the set of revocation variance values ​​corresponding to the past 24 hours. and the set of changes in variance Calculate the arithmetic mean of these two sets respectively, and use it as the daily average fluctuation benchmark, denoted as . and Define the fault determination coefficient. This is used to set the tolerance range. Perform volatility overshoot comparison: determine the current withdrawal variance. Is it greater than Determine the current change in variance. Is it greater than Comprehensive Judgment: If either condition A or condition B is met, the submarine optical cable AS adjacency pair is determined to be in an extremely unstable state within the current hour. The system immediately generates a routing anomaly alarm signal, including <anomaly timestamp, AS adjacency pair ID, current variance value, and baseline mean>, and writes the signal to the message queue as input for step S3.

[0155] S3, Precise location of exclusive faults

[0156] In response to the alarm signal, parallel probing is performed on the affected target IP and its associated multiple submarine optical cable interface IPs. Path drift is identified by comparing the real-time path with the baseline path, verifying logical link interruption. Then, exclusionary disambiguation is performed based on the liveness status of the remote exclusive interface IP: if a specific submarine optical cable interface is unreachable while other submarine optical cable interfaces are active, the physical submarine optical cable is precisely located as the source of the fault. Step S3 specifically includes:

[0157] S3a. Listen to the message queue. When a BGP routing anomaly alarm signal is read, extract the faulty AS adjacency pair ID. Using this ID as an index, query the submarine fiber optic cable topology mapping dictionary constructed in step S1b, and retrieve the attribute set of the physical submarine fiber optic cable associated with this adjacency pair, including: destination IP address (i.e., the destination IP of this entry in the dictionary), and a list of remote IP addresses of the submarine fiber optic cable (containing all possible physical submarine fiber optic cables under this adjacency pair and their corresponding remote interface IPs). Initialize the active probing task, and execute traceroute and ping probing commands in parallel for the above target IP list and multiple submarine fiber optic cable interface list.

[0158] S3b: Parse the real-time traceroute path data returned in step S3a and extract the real-time IP path sequence. Execute the topology consistency comparison algorithm: First, perform a connectivity check: if the Ping response to the destination IP is lost, mark the status as Target_Unreachable. Then, perform path feature matching: if the destination IP is reachable, traverse the real-time IP hop count sequence and check if the sequence contains the near-end and far-end interface IPs recorded in the physical submarine fiber optic cable attribute set. If the destination IP is reachable and the real-time sequence does not contain any known critical submarine fiber optic cable interface IPs, then the transmission path is determined to be drifted.

[0159] S3c: Traverse each record in the list of multiple submarine optical cable interfaces. Each record has the structure <submarine optical cable name, remote exclusive interface IP>. Read the detection results for these interface IPs from step S3a and construct an interface liveness state vector. Execute the following disambiguation logic: If the near-end and far-end interface IP status of a specific submarine optical cable (denoted as Cable_X) is unreachable, while the interface IP status of other submarine optical cables (Cable_Y, Cable_Z, etc.) under the same adjacent pair is reachable, then the output location result is: Fault source: Physical submarine optical cable Cable_X. If the near-end and far-end interface IP statuses in the list are all unreachable, then the output location result is: Fault source: Submarine optical cable landing station or all physical links are interrupted. Finally, output the submarine optical cable fault location information, including the name of the faulty submarine optical cable and evidence of the unreachable interface IP status.

[0160] Thus, the fault location method provided in this application embodiment can achieve the following effects:

[0161] 1. This embodiment performs dual parsing on the original path data (logical layer parsing from IP to ASN and physical layer parsing from IP to Nautilus submarine cable), mapping the physical layer submarine cable to specific AS adjacency pairs in the BGP control plane, and generating a submarine cable mapping by combining the interface IP. This achieves logical labeling of invisible physical resources, allowing general BGP data to be used to monitor the status of specific physical submarine cables, bridging the gap between application layer monitoring and physical layer infrastructure. It can accurately identify routing convergence behavior caused by physical faults while the target IP remains reachable, effectively distinguishing between network jitter and physical outages, and significantly improving the accuracy of fault detection.

[0162] 2. This embodiment no longer relies on a single connectivity as a judgment criterion, but introduces topology consistency comparison. By comparing the real-time path with the baseline path, path drift is used as the confirmation logic for the occurrence of faults.

[0163] 3. In this embodiment, the remote interface IP unique to each submarine cable is extracted as an anchor point. After confirming path drift, the remote interface IP unique to each submarine optical cable is extracted as an anchor point, and the remote submarine optical cable interface IP under the same AS adjacent pair is detected. The determination is made based on the exclusivity principle (i.e., submarine optical cable interface IP A is unreachable, submarine optical cable interface IP B is reachable). This solves the positioning ambiguity problem when multiple submarine cables share the same logical neighbor relationship, and realizes accurate differentiation and positioning of specific physical submarine cable entities in complex load-balanced network environments.

[0164] This implementation

[0165] It should be noted that the descriptions of each step S1 to S3 in this embodiment can be found in the descriptions in the above embodiments, and will not be repeated here.

[0166] It should be noted that the above-described method embodiments, or the various possible implementations of the method embodiments, can be executed individually, or, provided there is no conflict, they can be combined with each other. The specific implementation can be determined according to actual usage requirements, and this application embodiment does not impose any restrictions on this.

[0167] As can be seen, the above mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, the embodiments of this application provide corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0168] This application embodiment can divide the fault location device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0169] In some embodiments, this application also provides a fault location device. The fault location device may include one or more functional modules for implementing the fault location method of the above method embodiments.

[0170] For example, Figure 8 This is a schematic diagram of a fault location device provided in an embodiment of this application. Figure 8 As shown, the fault location device 800 includes a processing module 801 and a generation module 802.

[0171] The processing module 801 filters the BGP data stream based on the topology information of at least one submarine optical cable to obtain an observation dataset of the target submarine optical cable. The processing module 801 also performs streaming processing on the observation dataset to obtain the statistical variance of the cancellation count and the statistical variance of the change count for each path associated with the target submarine optical cable. The generation module 802 generates a routing anomaly alarm signal based on the statistical variance of the cancellation count and the historical baseline mean of the cancellation count for each path, and / or the statistical variance of the change count for each path and the historical baseline mean of the change count. In response to the routing anomaly alarm signal, the processing module 801 performs parallel detection processing on the target IP associated with the target AS adjacency pair identifier and the IPs of multiple submarine optical cable interfaces, outputting fault location information corresponding to the target submarine optical cable.

[0172] In the fault location device 800 provided in this application, when locating a fault in a submarine optical cable, the device can first determine the routing anomaly alarm signal based on the real-time variance and the historical benchmark mean, and then perform parallel detection processing on the target IP and multiple submarine optical cable interface IPs. This eliminates the need for lengthy signal sampling and processing time, enabling real-time online monitoring at the minute or even second level. Thus, the fault location device 101 can detect anomalies from an external perspective at the first moment of a fault occurrence, accurately capture transient faults, and promptly locate submarine optical cable faults.

[0173] In some embodiments of this application, the processing module 801 is specifically used to obtain the first path feature corresponding to the target IP and the second path feature corresponding to the multiple submarine optical cable interface IPs; when the first path feature and the second path feature match, the processing module 801 performs route detection on the multiple submarine optical cable interface IPs to obtain fault location information.

[0174] In some embodiments of this application, the processing module 801 is specifically used to perform source AS matching filtering on the BGP data stream based on the topology information of at least one submarine optical cable to obtain an initial observation dataset; and to perform fingerprint inclusion matching filtering on the initial observation dataset to obtain an observation dataset.

[0175] In some embodiments of this application, the processing module 801 is specifically used to perform streaming processing on the observation dataset to obtain the cancellation count sequence and change count sequence for each path associated with the target submarine optical cable; and to determine the statistical variance of the cancellation count and the statistical variance of the change count for each path based on the cancellation count sequence and change count sequence for each path through the variance standard calculation module.

[0176] In some embodiments of this application, the generation module 802 is specifically used to generate a routing anomaly alarm signal when a first condition is met; wherein, the first condition includes at least one of the following: the statistical variance of the cancellation count for each path is greater than the historical average of the cancellation count; the statistical variance of the change count for each path is greater than the historical average of the change count.

[0177] In some embodiments of this application, the processing module 801 is specifically used to obtain the first path feature corresponding to the target IP and the second path feature corresponding to the multiple submarine optical cable interface IPs; when the first path feature matches the second path feature, the processing module 801 performs route detection on the multiple submarine optical cable interface IPs to obtain the fault location information.

[0178] It should be noted that the fault location device can implement all the processes implemented in the above method embodiments and achieve the same beneficial effects. To avoid repetition, it will not be described again here.

[0179] In the case where the functions of the integrated modules described above are implemented in hardware, this application provides a possible structural schematic diagram of the electronic device involved in the above embodiments. For example... Figure 9 As shown, the electronic device 90 includes: a processor 92, a communication interface 93, and a bus 94. Optionally, the electronic device 90 may also include a memory 91.

[0180] Processor 92 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 92 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 92 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0181] Communication interface 93 is used to connect with other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0182] The memory 91 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0183] In one possible implementation, the memory 91 can exist independently of the processor 92. The memory 91 can be connected to the processor 92 via a bus 94 and is used to store instructions or program code. When the processor 92 calls and executes the instructions or program code stored in the memory 91, it can implement the fault location method provided in the embodiments of this application.

[0184] In another possible implementation, memory 91 can also be integrated with processor 92.

[0185] Bus 94 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 94 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 9 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0186] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the service calling device can be divided into different functional modules to complete all or part of the functions described above.

[0187] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described fault location method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0188] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0189] This application also provides a readable storage medium storing a program or instructions that, when executed by a computer, implement the fault location method provided in the above embodiments. It is understood that all or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware; the readable storage medium can be any of the foregoing embodiments or memory; the readable storage medium can also be an external storage device of the service invocation device, such as a pluggable hard drive, Smart MediaCard (SMC), Secure Digital (SD) card, flash card, etc., equipped on the service invocation device. Further, the readable storage medium can include both internal storage units of the service invocation device and external storage devices. The readable storage medium is used to store the computer program and other programs and data required by the service invocation device. The readable storage medium can also be used to temporarily store data that has been output or will be output.

[0190] This application also provides a computer program product, which is stored in a storage medium and implements the fault location method provided in the above embodiments when the computer program product is executed by a computer.

[0191] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0192] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0193] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A fault location method, characterized in that, The method includes: Based on the topology information of at least one submarine optical cable, the Border Gateway Protocol (BGP) data stream is filtered to obtain an observation dataset of the target submarine optical cable; wherein, the topology information includes the Autonomous System (AS) adjacency pairs and the Internet Protocol (IP) interface corresponding to each submarine optical cable; the observation dataset includes a portion of the packets in the BGP data stream; The observation dataset is stream-processed to obtain the statistical variance of the cancellation count and the statistical variance of the change count for each path associated with the target submarine optical cable; Based on the statistical variance of the cancellation count and the historical mean of the cancellation count for each path, and / or the statistical variance of the change count and the historical mean of the change count for each path, a routing anomaly alarm signal is generated; wherein, the routing anomaly alarm signal includes the target AS adjacency pair identifier; In response to the routing anomaly alarm signal, the target IP associated with the target AS adjacency pair identifier and the multiple submarine optical cable interface IPs are detected in parallel, and the fault location information corresponding to the target submarine optical cable is output.

2. The fault location method according to claim 1, characterized in that, The parallel detection processing of the target IP and multiple submarine optical cable interface IPs associated with the target AS adjacency pair identifier, and the output of the fault location information corresponding to the target submarine optical cable, includes: Obtain the first path feature corresponding to the target IP and the second path feature corresponding to the multiple submarine optical cable interface IPs; If the first path feature matches the second path feature, route detection is performed on the multiple submarine optical cable interface IPs to obtain the fault location information.

3. The fault location method according to claim 1, characterized in that, The BGP data stream is filtered based on the topology information of at least one submarine optical cable to obtain an observation dataset of the target submarine optical cable, including: Based on the topology information of the at least one submarine optical cable, the BGP data stream is subjected to source AS matching filtering to obtain an initial observation dataset. The initial observation dataset is subjected to fingerprint inclusion matching filtering to obtain the observation dataset.

4. The fault location method according to claim 1, characterized in that, The streaming processing of the observation dataset yields the statistical variance of the cancellation count and the statistical variance of the change count for each path associated with the target submarine optical cable, including: The observation dataset is stream-processed to obtain the undo count sequence and change count sequence for each path associated with the target submarine optical cable; The variance standard calculation module determines the statistical variance of the cancellation count and the statistical variance of the change count for each path based on the cancellation count sequence and the change count sequence for each path.

5. The fault location method according to any one of claims 1 to 4, characterized in that, The generation of a routing anomaly alarm signal based on the statistical variance of the cancellation count and the historical baseline mean of the cancellation count for each path, and / or the statistical variance of the change count and the historical baseline mean of the change count for each path, includes: If the first condition is met, the routing anomaly alarm signal is generated; The first condition includes at least one of the following: The variance of the cancellation count for each path is greater than the historical cancellation count baseline mean. The statistical variance of the change count for each path is greater than the historical change count baseline mean.

6. A fault location device, characterized in that, include: Processing module and generation module; The processing module is used to filter the Border Gateway Protocol (BGP) data stream based on the topology information of at least one submarine optical cable to obtain an observation dataset of the target submarine optical cable; wherein, the topology information includes the Autonomous System (AS) adjacency pairs and the Internet Protocol (IP) interface corresponding to each submarine optical cable; the observation dataset includes a portion of the packets in the BGP data stream; The processing module is also used to perform streaming processing on the observation dataset to obtain the statistical variance of the cancellation count and the statistical variance of the change count for each path associated with the target submarine optical cable; The generation module is used to generate a routing anomaly alarm signal based on the statistical variance of the cancellation count and the historical average of the cancellation count for each path, and / or the statistical variance of the change count and the historical average of the change count for each path; wherein, the routing anomaly alarm signal includes the target AS adjacency pair identifier; The processing module is also used to respond to the routing anomaly alarm signal, perform parallel detection processing on the target IP associated with the target AS adjacency pair identifier and the multiple submarine optical cable interface IPs, and output the fault location information corresponding to the target submarine optical cable.

7. The fault location device according to claim 6, characterized in that, The processing module is specifically used for: Obtain the first path feature corresponding to the target IP and the second path feature corresponding to the multiple submarine optical cable interface IPs; If the first path feature matches the second path feature, route detection is performed on the multiple submarine optical cable interface IPs to obtain the fault location information.

8. The fault location device according to claim 6, characterized in that, The processing module is specifically used for: Based on the topology information of the at least one submarine optical cable, the BGP data stream is subjected to source AS matching filtering to obtain an initial observation dataset. The initial observation dataset is subjected to fingerprint inclusion matching filtering to obtain the observation dataset.

9. The fault location device according to claim 6, characterized in that, The processing module is specifically used for: The observation dataset is stream-processed to obtain the undo count sequence and change count sequence for each path associated with the target submarine optical cable; The variance standard calculation module determines the statistical variance of the cancellation count and the statistical variance of the change count for each path based on the cancellation count sequence and the change count sequence for each path.

10. The fault location device according to any one of claims 6 to 9, characterized in that, The generation module is specifically used for: If the first condition is met, the routing anomaly alarm signal is generated; The first condition includes at least one of the following: The variance of the cancellation count for each path is greater than the historical cancellation count baseline mean. The statistical variance of the change count for each path is greater than the historical change count baseline mean.

11. An electronic device, characterized in that, It includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the fault location method as described in any one of claims 1 to 5.

12. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a computer, implement the fault location method as described in any one of claims 1 to 5.

13. A computer program product, characterized in that, The computer program product is stored in a storage medium, and when executed by a computer, the computer program product implements the fault location method as described in any one of claims 1 to 5.