Heterogeneous link monitoring method, device and equipment and readable storage medium

Abstract

The invention discloses a heterogeneous link monitoring method, device and equipment and a readable storage medium, and the method comprises the steps: carrying out the network monitoring of a heterogeneous equipment networking link through different network monitoring protocols; performing normalization processing on the monitored performance parameters to obtain target performance parameters; calculating an average performance score corresponding to a target path in the heterogeneous equipment networking link and a comprehensive performance score of a target link section in the target path by using the target performance parameter; determining a dynamic threshold value of the target link section by using the average performance score; and under the condition that the comprehensive performance score reaches a dynamic threshold value, determining that the target link section has a performance bottleneck. In the application, network monitoring is carried out in combination with different network monitoring protocols, and comprehensive and accurate target performance parameters can be obtained. Then, scores corresponding to the paths and the link sections and a dynamic threshold value of the target link section are calculated based on the target performance parameters, and the link sections with performance bottlenecks can be rapidly and accurately positioned.

Description

Technical Field

[0001] The present application relates to the field of network technology, and in particular to a heterogeneous link monitoring method, apparatus, device, and readable storage medium. Background Art

[0002] As networks continue to expand and their architectures become increasingly complex, backbone networks, as the core of the network, carry a significant amount of data transmission. The stability and performance of backbone networks directly impact the overall network efficiency and user experience. Backbone networks contain a variety of heterogeneous devices using different technologies and protocols. While the heterogeneity of these networks improves network flexibility and scalability to a certain extent, it also presents numerous challenges, particularly in network performance monitoring and bottleneck identification.

[0003] Traditional network performance monitoring methods primarily rely on single technical means. While simple and easy to use, these methods often struggle to provide comprehensive and accurate performance data in complex, heterogeneous network environments. Particularly in networking environments with multi-vendor devices, due to compatibility issues between different vendors' equipment, traditional monitoring methods often fail to effectively obtain end-to-end link performance data, making it difficult for network administrators to fully grasp the network's operational status. In particular, link bottleneck location methods typically rely on manual troubleshooting and empirical judgment based on operational status collected using a single technical means. This approach is not only inefficient but also prone to errors. In complex, heterogeneous network environments, locating bottlenecks becomes even more difficult, as link bottlenecks can occur on any link or device, and traditional troubleshooting methods often fail to quickly and accurately locate bottlenecks.

[0004] In summary, how to effectively solve problems such as network performance monitoring in heterogeneous networks is a technical problem that those skilled in the art urgently need to solve. Summary of the Invention

[0005] The purpose of this application is to provide a heterogeneous link monitoring method, device, equipment and readable storage medium, which can monitor the performance of complex heterogeneous device networking links and quickly and accurately locate bottlenecks.

[0006] To solve the above technical problems, this application provides the following technical solutions:

[0007] A method for detecting links in a heterogeneous device network, comprising:

[0008] Use different network monitoring protocols to monitor the networking links of heterogeneous devices;

[0009] Normalize the performance parameters obtained from monitoring to obtain target performance parameters;

[0010] Calculating, using the target performance parameters, an average performance score corresponding to a target path in the heterogeneous device networking link and a comprehensive performance score of a target link segment in the target path;

[0011] determining a dynamic threshold of the target link segment using the average performance score;

[0012] When the comprehensive performance score reaches the dynamic threshold, it is determined that a performance bottleneck exists in the target link segment.

[0013] Preferably, determining the dynamic threshold of the target link segment using the average performance score includes:

[0014] Obtaining an amplification factor and a sensitivity, and amplifying the sensitivity using the amplification factor;

[0015] The average performance score and the amplified sensitivity are superimposed to obtain the dynamic threshold.

[0016] Preferably, determining the dynamic threshold of the target link segment using the average performance score includes:

[0017] Obtaining an amplification factor and a sensitivity, and amplifying the sensitivity using the amplification factor;

[0018] Obtaining the packet loss rate and jitter of the target link segment from the target performance parameters;

[0019] Calculating a packet loss penalty value corresponding to the packet loss rate using a packet loss rate penalty function;

[0020] Calculating a jitter penalty value corresponding to the jitter using a jitter penalty function;

[0021] The average performance score, the packet loss penalty value, the jitter penalty value, and the amplified sensitivity are superimposed to obtain the dynamic threshold.

[0022] Preferably, different network monitoring protocols are used to perform network monitoring on heterogeneous device networking links, including:

[0023] The network monitoring is performed on the heterogeneous device networking link by utilizing a bidirectional active measurement protocol, a network quality analyzer and a flow-based network performance monitoring protocol.

[0024] Preferably, before performing network monitoring on heterogeneous device networking links using different network monitoring protocols, the following steps are included:

[0025] Identifying the device type of the network device in the heterogeneous device networking link;

[0026] Configuring a corresponding network monitoring protocol for the network device according to the device type;

[0027] Based on the Border Gateway Protocol Link State Protocol, dynamic perception of the entire network topology is performed to build a topology database;

[0028] Accordingly, after normalizing the performance parameters obtained from monitoring to obtain the target performance parameters, the following steps are also included:

[0029] Overlaying the target performance parameters on the topological database to obtain a performance analysis view;

[0030] The performance analysis view is output.

[0031] Preferably, different network monitoring protocols are used to perform network monitoring on heterogeneous device networking links, including:

[0032] Different network monitoring protocols are used to perform end-to-end or hop-by-hop network monitoring on the heterogeneous device networking links.

[0033] Preferably, performing end-to-end or hop-by-hop network monitoring on the heterogeneous device networking link includes:

[0034] Perform end-to-end network monitoring on the heterogeneous device networking links;

[0035] If the packet loss rate or jitter exceeds the monitoring threshold, hop-by-hop network monitoring is performed on the heterogeneous device networking link.

[0036] A heterogeneous link monitoring device, comprising:

[0037] The network monitoring module is used to monitor the networking links of heterogeneous devices using different network monitoring protocols;

[0038] A normalization processing module is used to normalize the performance parameters obtained by monitoring to obtain target performance parameters;

[0039] a performance scoring module, configured to calculate, by using the target performance parameters, an average performance score corresponding to a target path in the heterogeneous device networking link and a comprehensive performance score of a target link segment in the target path;

[0040] a dynamic threshold determination module, configured to determine a dynamic threshold of the target link segment using the average performance score;

[0041] The performance bottleneck locating module is configured to determine that a performance bottleneck exists in the target link segment when the comprehensive performance score reaches the dynamic threshold.

[0042] An electronic device, comprising:

[0043] Memory for storing computer programs;

[0044] A processor is configured to implement the steps of the above-mentioned heterogeneous link monitoring method when executing the computer program.

[0045] A readable storage medium stores a computer program, which implements the steps of the above-mentioned heterogeneous link monitoring method when executed by a processor.

[0046] By applying the method provided in the embodiments of the present application, network monitoring is performed on heterogeneous device networking links using different network monitoring protocols; the performance parameters obtained from the monitoring are normalized to obtain target performance parameters; the target performance parameters are used to calculate the average performance score corresponding to the target path in the heterogeneous device networking link, and the comprehensive performance score of the target link segment in the target path; the average performance score is used to determine the dynamic threshold of the target link segment; and when the comprehensive performance score reaches the dynamic threshold, it is determined that a performance bottleneck exists in the target link segment.

[0047] In this application, in order to effectively monitor the networking links of heterogeneous devices, different network monitoring protocols are used for network monitoring. Taking into account the differences in the data collected by different network monitoring protocols, the performance parameters obtained by monitoring can be normalized to obtain target performance parameters. In order to quickly and accurately find link segments with performance bottlenecks. The average performance score corresponding to the target path and the comprehensive performance score of the target link segment in the target path can be calculated based on the target performance parameters. Then, a dynamic threshold is set for the target link segment. When the comprehensive performance score of the target link segment reaches the dynamic threshold, it is determined that the target link segment has a performance bottleneck.

[0048] In other words, in this application, by combining different network monitoring protocols for network monitoring and normalizing the performance parameters obtained from the monitoring, more comprehensive and accurate performance parameters can be obtained. Then, based on the performance parameters, the scores corresponding to the path and the link segments in the path are calculated. Combined with the dynamic threshold of the target link segment, the link segment with performance bottlenecks can be quickly and accurately located.

[0049] Accordingly, the embodiments of the present application also provide a heterogeneous link monitoring device, equipment and readable storage medium corresponding to the above-mentioned heterogeneous link monitoring method, which have the above-mentioned technical effects and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0051] Figure 1 This is a flowchart of an implementation method of a heterogeneous link monitoring method in an embodiment of the present application;

[0052] Figure 2 This is a schematic diagram of a collaborative detection network of NQA and TWAMP in an embodiment of the present application;

[0053] Figure 3 This is a data collection diagram in an embodiment of the present application;

[0054] Figure 4 This is a schematic diagram of a data collection mode in an embodiment of the present application;

[0055] Figure 5 This is a specific implementation flow chart of a heterogeneous link monitoring method in an embodiment of the present application;

[0056] Figure 6 This is a schematic structural diagram of a heterogeneous link monitoring device according to an embodiment of the present application;

[0057] Figure 7 This is a schematic structural diagram of another heterogeneous link monitoring device in an embodiment of the present application;

[0058] Figure 8 This is a schematic structural diagram of an electronic device according to an embodiment of the present application;

[0059] Figure 9 This is a schematic diagram of the specific structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0060] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below in conjunction with the accompanying drawings and specific embodiments. Obviously, the embodiments described are only a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without making any creative efforts are within the scope of protection of the present application.

[0061] Please refer to Figure 1 , Figure 1 This is a flow chart of a heterogeneous link monitoring method according to an embodiment of the present application, which includes the following steps:

[0062] S101. Perform network monitoring on heterogeneous device networking links using different network monitoring protocols.

[0063] Considering that a single network monitoring protocol cannot meet the requirements of network detection of heterogeneous device networking links in actual applications, different network monitoring protocols are used in this embodiment to perform network monitoring on heterogeneous device networking links.

[0064] Specifically, when selecting different network monitoring protocols, you can try to select a network monitoring protocol that can cover the entire detection link for network monitoring. Figure 2 Figure 2 shows the collaborative detection network of NQA and TWAMP in a heterogeneous vendor scenario.

[0065] In a specific embodiment of the present application, different network monitoring protocols are used to perform network monitoring on heterogeneous device networking links, including: using a bidirectional active measurement protocol, a network quality analyzer and a flow-based network performance monitoring protocol to perform network monitoring on heterogeneous device networking links.

[0066] The Two-Way Active Measurement Protocol (TWAMP) is a protocol used to measure network performance. It evaluates network performance by sending test packets and measuring their round-trip time (RTT). TWAMP's advantage lies in its ability to provide end-to-end performance data.

[0067] A Network Quality Analyzer (NQA) assesses network performance by sending test packets and analyzing their response times. NQA's advantage lies in its support for multiple protocols and technologies, making it suitable for diverse network environments.

[0068] The In-situ Flow Information Telemetry (IFIT) protocol collects network performance data in real time by inserting monitoring information into data streams. IFIT's advantage lies in its ability to provide highly accurate hop-by-hop performance data.

[0069] That is, in this embodiment, if Figure 3 As shown, by integrating the strengths of three monitoring protocols, NQA, TWAMP, and IFIT, a layered and coordinated monitoring system can be constructed. NQA is responsible for end-to-end performance baseline measurement across vendor links, TWAMP focuses on high-precision latency acquisition between devices from the same vendor, and IFIT performs refined traffic marking and compensation calibration on key links. Through unified scheduling by the controller, spatiotemporal alignment and fusion of multi-source monitoring data (NQA, TWAMP, and IFIT) is achieved, forming a comprehensive link performance profile (data) covering the entire path. This mechanism effectively addresses the accuracy drift and data fragmentation issues associated with single-protocol monitoring, providing multi-dimensional data support for the precise location of link bottlenecks.

[0070] S102: Normalize the performance parameters obtained through monitoring to obtain target performance parameters.

[0071] After network monitoring using different network monitoring protocols, performance parameters can be obtained.

[0072] Because performance parameters are obtained using different network monitoring protocols, which often have different recording methods and accuracy, these performance parameters can be normalized to obtain target performance parameters in a unified form. Specifically, the performance parameters can be parsed and converted based on the different network monitoring protocols to obtain the target performance parameters.

[0073] For example, to integrate data collected from three different technologies—NQA, TWAMP, and iFit—and transform it into a unified data model for comprehensive analysis of network-wide link performance, this integrated approach not only overcomes the limitations of individual tools in heterogeneous network environments but also provides a more comprehensive and accurate view of network performance. This module implements targeted preprocessing steps for the raw data collected from NQA, TWAMP, and iFit. NQA primarily covers end-to-end performance metrics across vendor devices, such as latency, jitter, and packet loss rate; TWAMP focuses on high-precision latency measurement within a vendor's equipment; and iFit provides detailed hop-by-hop performance information, including but not limited to actual packet loss rate and latency parameters. Each technology has distinct data formats and content, requiring specialized parsing and transformation logic to ensure data consistency and comparability. All preprocessed data is then mapped into a common data model. This unified data model defines a set of standardized performance metrics and measurement units, enabling data from different sources to be compared and analyzed within a common framework. For example, all latency data will be converted to a uniform time unit (milliseconds), and all packet loss rate data will be presented as a percentage.

[0074] S103: Calculate the average performance score corresponding to the target path in the heterogeneous device networking link and the comprehensive performance score of the target link segment in the target path using the target performance parameter.

[0075] After obtaining unified target performance parameters, the average performance score of the target parts and the comprehensive performance score of the target link segments in the target path can be calculated based on these target performance parameters.

[0076] The target path can be any path in a heterogeneous device network. A path may contain multiple links. In this embodiment, each link segment is referred to as a target link segment. Each target link segment can be scored individually, and a dynamic threshold can be determined to ultimately determine whether a performance bottleneck has occurred. Alternatively, a unified dynamic threshold can be used.

[0077] Specifically, (1) suppose represents the i-th link, A set of performance indicators on the link, including but not limited to latency , packet loss rate , jitter For each link Li, its comprehensive performance score can be defined as ,as follows:

[0078] ;in, These are the weight coefficients corresponding to latency, packet loss rate, and jitter, reflecting the importance of each factor on link performance. These weights can be adjusted based on specific network requirements and service level agreements (SLAs).

[0079] (2) Consider that the entire path consists of multiple link segments, that is, In order to locate the performance bottleneck, the average performance score of the entire path can be calculated :

[0080] .

[0081] S104: Determine a dynamic threshold of the target link segment using the average performance score.

[0082] In a specific embodiment of the present application, determining a dynamic threshold of a target link segment using an average performance score includes:

[0083] Obtaining the amplification factor and sensitivity, and amplifying the sensitivity using the amplification factor;

[0084] The average performance score and the amplified sensitivity are superimposed to obtain the dynamic threshold.

[0085] In this application, the sensitivity and amplification factor can be pre-set. Of course, in actual application, the sensitivity and amplification factor can also be adjusted. The amplification factor can amplify the sensitivity.

[0086] After the sensitivity is amplified, the average performance score and the amplified sensitivity may be superimposed, and the superimposed result may be used as the dynamic threshold.

[0087] In a specific embodiment of the present application, determining a dynamic threshold of a target link segment using an average performance score includes:

[0088] Obtaining the amplification factor and sensitivity, and amplifying the sensitivity using the amplification factor;

[0089] Obtaining the packet loss rate and jitter of the target link segment from the target performance parameters;

[0090] Calculate the packet loss penalty value corresponding to the packet loss rate using the packet loss rate penalty function;

[0091] Calculate the jitter penalty value corresponding to the jitter using the jitter penalty function;

[0092] The average performance score, packet loss penalty value, jitter penalty value, and amplified sensitivity are superimposed to obtain a dynamic threshold.

[0093] In this embodiment, if it is necessary to locate the performance bottleneck more accurately, the jitter and packet loss rate may be combined to amplify the average performance score, thereby reflecting the serious impact of the packet loss rate and jitter on the link quality.

[0094] Specifically, a penalty function for packet loss rate and jitter can be used to amplify their impact on the final score. These two penalty parameters are nonlinear functions that reflect the severity of packet loss rate and jitter on link quality. In this way, the dynamic threshold is not only related to the current average performance score, but also closely related to the specific packet loss rate and jitter.

[0095] S105: When the comprehensive performance score reaches a dynamic threshold, it is determined that a performance bottleneck exists in the target link segment.

[0096] When the comprehensive performance score of the target link segment reaches the dynamic threshold, it indicates that the target link segment has a performance bottleneck.

[0097] Example 1: You can define a sensitivity (For example, 5ms can be described as ), if a link Overall performance score Exceed The sum of (where k is the amplification factor, used to adjust the sensitivity), then Potential performance bottlenecks are: .

[0098] Example 2: To more accurately locate performance bottlenecks, a dynamic threshold expressed by the following formula can be introduced: , which is adjusted according to the specific conditions of the current link:

[0099] ;

[0100] in, These are penalty functions for packet loss rate and jitter, respectively, used to amplify their impact on the final score. These two penalty parameters are nonlinear functions that reflect the serious impact of packet loss rate and jitter on link quality:

[0101] That is, with this design, when the packet loss rate or jitter exceeds a certain threshold, its impact on link performance will increase dramatically.

[0102] If a link Overall performance score Exceeded the dynamic threshold , then it is believed that Potential performance bottlenecks are: .

[0103] By applying the method provided in the embodiments of the present application, network monitoring is performed on heterogeneous device networking links using different network monitoring protocols; the performance parameters obtained from the monitoring are normalized to obtain target performance parameters; the target performance parameters are used to calculate the average performance score corresponding to the target path in the heterogeneous device networking link, and the comprehensive performance score of the target link segment in the target path; the average performance score is used to determine the dynamic threshold of the target link segment; and when the comprehensive performance score reaches the dynamic threshold, it is determined that a performance bottleneck exists in the target link segment.

[0104] In this application, in order to effectively monitor the networking links of heterogeneous devices, different network monitoring protocols are used for network monitoring. Taking into account the differences in the data collected by different network monitoring protocols, the performance parameters obtained by monitoring can be normalized to obtain target performance parameters. In order to quickly and accurately find link segments with performance bottlenecks. The average performance score corresponding to the target path and the comprehensive performance score of the target link segment in the target path can be calculated based on the target performance parameters. Then, a dynamic threshold is set for the target link segment. When the comprehensive performance score of the target link segment reaches the dynamic threshold, it is determined that the target link segment has a performance bottleneck.

[0105] In other words, in this application, by combining different network monitoring protocols for network monitoring and normalizing the performance parameters obtained from the monitoring, more comprehensive and accurate performance parameters can be obtained. Then, based on the performance parameters, the scores corresponding to the path and the link segments in the path are calculated. Combined with the dynamic threshold of the target link segment, the link segment with performance bottlenecks can be quickly and accurately located.

[0106] It should be noted that, based on the above embodiments, the embodiments of the present application also provide corresponding improved solutions. In the preferred / improved embodiments, the same steps or corresponding steps as those in the above embodiments can be referenced to each other, and the corresponding beneficial effects can also be referenced to each other, and will not be described in detail in the preferred / improved embodiments of this document.

[0107] In a specific embodiment of the present application, before performing network monitoring on heterogeneous device networking links using different network monitoring protocols, the following steps are included:

[0108] Identify the device types of network devices in heterogeneous device networking links;

[0109] Configure corresponding network monitoring protocols for network devices according to device types;

[0110] Based on the Border Gateway Protocol Link State Protocol, dynamic perception of the entire network topology is performed to build a topology database;

[0111] Accordingly, after normalizing the performance parameters obtained from monitoring to obtain the target performance parameters, the following steps are also included:

[0112] Overlay target performance parameters on the topology database to obtain a performance analysis view.

[0113] Outputs the performance analysis view.

[0114] In this embodiment, a configuration process / module is set up to automatically deliver configurations and monitor status for heterogeneous devices, enabling multi-vendor device compatibility management through the NETCONF / YANG model. It supports TWAMP / NQA / IFIT protocol configuration template management for devices from different vendors, automatically identifying device types and matching corresponding configuration templates. Configuration version management, delivery verification, and rollback mechanisms are provided, synchronizing device configuration status with the controller database in real time.

[0115] Based on the Border Gateway Protocol (BGP) Link State Protocol, the system dynamically detects the entire network topology and builds a topology database that includes device vendors, interface attributes, and protocol status. It parses NLRI information to identify adjacencies between PE devices from the same vendor (vendor ID matching) and automatically annotates links from different vendors. It supports subscription and real-time notification of topology change events, providing topology data support for link policy delivery.

[0116] The Telemetry Management module can be configured. In addition to implementing the Telemetry data gateway function of the GRPC protocol stack, this module also handles the unified reception and parsing of iFit data from devices from different vendors. It provides dynamic subscription management, adjusting the sampling frequency (adjustable from 1 second to 5 minutes) based on business needs. A built-in streaming data processing engine performs threshold compression and time alignment on high-concurrency Telemetry data, ensuring real-time and accurate data processing. For iFit data in heterogeneous environments, this module implements a series of predefined data conversion rules to ensure that all collected data is formatted and semantically consistent before entering the analysis phase, providing a reliable data foundation for subsequent performance analysis.

[0117] A full-network link topology display module can also be configured. Based on a spatiotemporal correlation engine between topology data and performance indicators, it enables multi-level, multi-precision visualization. It supports layered topology rendering (physical layer, logical layer, and service layer), presents link latency distribution via heat maps, and uses dynamic traffic coloring to highlight abnormal links. A topology drill-down function is provided, allowing users to drill down to view a joint TWAMP / NQA / IFIT analysis view for specific links.

[0118] In a specific embodiment of the present application, network monitoring is performed on heterogeneous device networking links using different network monitoring protocols, including:

[0119] Utilize different network monitoring protocols to conduct end-to-end or hop-by-hop network monitoring on heterogeneous device networking links.

[0120] Among them, end-to-end or hop-by-hop network monitoring of heterogeneous device networking links includes:

[0121] Conduct end-to-end network monitoring of heterogeneous device networking links;

[0122] If the packet loss rate or jitter exceeds the monitoring threshold, hop-by-hop network monitoring is performed on the heterogeneous device networking link.

[0123] In this embodiment, if Figure 4 As shown, you can configure intelligent switching strategies between end-to-end and hop-by-hop detection modes. When the network's end-to-end latency or packet loss rate exceeds a preset threshold, the system automatically triggers hop-by-hop detection mode. Using dye flow marking technology, it tracks traffic hop by hop along the target path, quickly identifying abnormal nodes. When link quality stabilizes, it automatically reverts to low-overhead end-to-end monitoring mode. This mechanism overcomes the limitations of traditional static detection modes, which suffer from low efficiency and high resource consumption. While ensuring detection accuracy, it significantly reduces device load and achieves a balanced optimization between fault location efficiency and resource consumption.

[0124] To facilitate those skilled in the art to better implement the heterogeneous link monitoring method provided in the embodiment of the present application, the heterogeneous link monitoring method is described in detail below with reference to a specific application scenario as an example.

[0125] Please refer to Figure 6 , the heterogeneous link monitoring method includes the following steps:

[0126] Step 1: Import the device and distribute the configuration.

[0127] Import the new device into the backbone network controller. Based on the device's vendor, the system automatically identifies and distributes the corresponding TWAMP and iFit Telemetry configurations. This step ensures that the backbone network controller receives Telemetry monitoring data reported by the device after the network configuration is subsequently distributed.

[0128] Step 2: Obtain link topology and deliver configuration.

[0129] The backbone network controller obtains network-wide link topology information through the BGP-LS protocol. For links where PE devices at both ends are from the same vendor, the system delivers the TWAMP configuration. For links where PE devices at both ends are from different vendors, the system delivers the NQA configuration based on the vendor. This step ensures that link performance monitoring between devices from different vendors is properly configured.

[0130] Step 3: Collect link performance data.

[0131] After the configuration is delivered, link performance data collection begins. The specific process is as follows:

[0132] a. NQA collection of cross-vendor link performance: The controller obtains NQA results using the NETCONF protocol. The NQA client constructs a probe message and sends it to the destination device. The destination device responds with a response message. The NQA client measures link throughput, packet loss rate, and latency by counting the number of probe message transmissions and timestamps.

[0133] b. TWAMP performance collection for intra-vendor links: The device sends TWAMP performance packets based on the TWAMP and Telemetry configurations. TWAMP allows bidirectional measurements between two network endpoints, sending and receiving test packets to measure performance metrics such as round-trip delay, packet loss rate, and jitter.

[0134] Step 4: IFIT configuration is delivered.

[0135] Deliver end-to-end IFIT configurations based on the actual network conditions. For devices at the head and tail ends that are from different vendors, deliver compatible IFIT configurations to ensure IFIT packets can traverse these devices. IFIT is a measurement technology used in public networks, MPLS, SR-MPLS, SRv6, G-SRv6, and G-BIER transmission networks. It directly measures parameters such as the actual packet loss rate and latency of service packets, offering advantages such as easy deployment and high statistical accuracy.

[0136] Step 5: Report IFIT data.

[0137] Devices that receive iFit packets report iFit performance data through the Telemetry channel. In end-to-end mode, only data from the beginning and end is reported.

[0138] Step 6: Analyze and display link performance data.

[0139] The system analyzes BGP-LS topology information, NQA cross-vendor link performance data collected by NETCONF, and TWAMP same-vendor link data reported by Telemetry to determine the link details of the entire network topology and display them to users in real time. This step provides visualization of link performance across the entire network, facilitating user monitoring and management.

[0140] Step 7: Key business traffic performance test.

[0141] IFIT conducts end-to-end performance testing for key business and critical traffic, with devices reporting in real time via Telemetry. This ensures that the performance of critical business is prioritized and potential issues are discovered and resolved promptly.

[0142] Step 8: Detect and locate link bottlenecks.

[0143] In this step, the system performs the following operations:

[0144] a. Link performance bottleneck location: This system analyzes link performance bottlenecks based on comprehensive data and sends real-time notifications to users. This helps users quickly locate issues and reduce bottleneck recovery time.

[0145] b. IFIT Configuration Adjustment: The system automatically delivers IFIT configurations, changing IFIT end-to-end performance monitoring to hop-by-hop. This hop-by-hop performance data is displayed to customers in real time, providing granular visibility into link performance bottlenecks. This step provides more precise location capabilities and improves network reliability.

[0146] The link bottleneck detection method is as follows:

[0147] (1) Assume represents the i-th link, A set of performance indicators on the link, including but not limited to latency , packet loss rate , jitter For each link Li, its comprehensive performance score can be defined as ,as follows:

[0148] These are the weight coefficients corresponding to latency, packet loss rate, and jitter, reflecting the importance of each factor on link performance. These weights can be adjusted based on specific network requirements and service level agreements (SLAs).

[0149] (2) Consider that the entire path consists of multiple link segments, that is, In order to locate the performance bottleneck, we can first calculate the average performance score of the entire path. :

[0150] , define a sensitivity (For example, 5ms can be described as ), if a link Performance score Exceed Plus (where k is the amplification factor, used to adjust the sensitivity), then Potential performance bottlenecks are: ;

[0151] If you need to locate performance bottlenecks more accurately, introduce dynamic thresholds , which is adjusted according to the specific conditions of the current link:

[0152] ;in, These are penalty functions for packet loss rate and jitter, respectively, used to amplify their impact on the final score. These two penalty parameters are nonlinear functions that reflect the serious impact of packet loss rate and jitter on link quality:

[0153]

[0154] With this design, when the packet loss rate or jitter exceeds a certain threshold, its impact on link performance will increase dramatically.

[0155] If a link Overall performance score Exceeded the dynamic threshold , then it is believed that Potential performance bottlenecks are: .

[0156] Step 9: Link recovery and monitoring.

[0157] When all network links return to normal, IFIT switches to end-to-end mode, continuously monitoring the status of all network links. This ensures the continued healthy operation of the network and allows for the timely detection and resolution of new issues.

[0158] Specifically, this application proposes a multi-protocol collaborative monitoring and data fusion mechanism to provide positioning data support: In response to the monitoring blind spot problem caused by differences in heterogeneous network protocols, this application proposes a cross-protocol collaborative working mechanism to build a layered collaborative monitoring system by integrating the advantages of three types of monitoring protocols: NQA, TWAMP and IFIT. Among them, the NQA protocol is responsible for end-to-end performance baseline measurement of cross-vendor links, the TWAMP protocol focuses on high-precision delay acquisition between devices of the same manufacturer, and the IFIT protocol performs refined traffic marking and compensation calibration on key links. Through the unified scheduling of the controller, the spatiotemporal alignment and fusion processing of multi-source (NQA, TWAMP and IFIT three types of monitoring protocols) monitoring data are achieved to form a link performance portrait / (data) covering the entire path. This mechanism effectively solves the problems of accuracy drift and data fragmentation in traditional single-protocol monitoring, and provides multi-dimensional data support for the precise positioning of link bottlenecks.

[0159] Intelligent mode switching achieves a balance between fault location efficiency and resource consumption: Based on the dynamic perception technology of link status, this application designs an intelligent switching strategy for end-to-end and hop-by-hop detection modes. When the network end-to-end delay or packet loss rate exceeds the preset threshold, the system automatically triggers the hop-by-hop detection mode, and uses the dye flow marking technology to track the target path hop-by-hop traffic and quickly lock the abnormal node; when the link quality returns to stability, it automatically falls back to the low-overhead end-to-end monitoring mode. This mechanism breaks through the limitations of low efficiency and high resource consumption of the traditional static detection mode. While ensuring detection accuracy, it significantly reduces the equipment load pressure and achieves a balanced optimization of fault location efficiency and resource consumption.

[0160] A multi-dimensional link bottleneck comprehensive evaluation model enhances bottleneck location accuracy: To address the ambiguity of link bottleneck location in complex network scenarios, this application proposes a comprehensive evaluation method based on the integration of multiple indicators such as latency, packet loss rate, and jitter. Through a dynamic weight allocation mechanism, combined with real-time link status and historical baseline data, the performance of each node in the path is quantitatively scored, and a penalty mechanism is introduced to identify link bottlenecks. This model overcomes the one-sidedness of traditional single-metric evaluation and significantly improves location accuracy and scenario adaptability.

[0161] Corresponding to the above method embodiment, an embodiment of the present application further provides a heterogeneous link monitoring device. The heterogeneous link monitoring device described below and the heterogeneous link monitoring method described above can refer to each other.

[0162] See also Figure 6 As shown, the device includes the following modules:

[0163] The network monitoring module 101 is used to perform network monitoring on heterogeneous device networking links using different network monitoring protocols;

[0164] Normalization processing module 102 is used to normalize the performance parameters obtained by monitoring to obtain target performance parameters;

[0165] The performance scoring module 103 is used to calculate the average performance score corresponding to the target path in the heterogeneous device network link and the comprehensive performance score of the target link segment in the target path using the target performance parameter;

[0166] A dynamic threshold determination module 104 is configured to determine a dynamic threshold of a target link segment using the average performance score;

[0167] The performance bottleneck locating module 105 is configured to determine that a performance bottleneck exists in the target link segment when the comprehensive performance score reaches a dynamic threshold.

[0168] The device provided in the embodiment of the present application is applied to perform network monitoring on heterogeneous device networking links using different network monitoring protocols; the performance parameters obtained from the monitoring are normalized to obtain target performance parameters; the target performance parameters are used to calculate the average performance score corresponding to the target path in the heterogeneous device networking link, and the comprehensive performance score of the target link segment in the target path; the average performance score is used to determine the dynamic threshold of the target link segment; when the comprehensive performance score reaches the dynamic threshold, it is determined that the target link segment has a performance bottleneck.

[0169] In this application, in order to effectively monitor the networking links of heterogeneous devices, different network monitoring protocols are used for network monitoring. Taking into account the differences in the data collected by different network monitoring protocols, the performance parameters obtained by monitoring can be normalized to obtain target performance parameters. In order to quickly and accurately find link segments with performance bottlenecks. The average performance score corresponding to the target path and the comprehensive performance score of the target link segment in the target path can be calculated based on the target performance parameters. Then, a dynamic threshold is set for the target link segment. When the comprehensive performance score of the target link segment reaches the dynamic threshold, it is determined that the target link segment has a performance bottleneck.

[0170] In other words, in this application, by combining different network monitoring protocols for network monitoring and normalizing the performance parameters obtained from the monitoring, more comprehensive and accurate performance parameters can be obtained. Then, based on the performance parameters, the scores corresponding to the path and the link segments in the path are calculated. Combined with the dynamic threshold of the target link segment, the link segment with performance bottlenecks can be quickly and accurately located.

[0171] In a specific embodiment of the present application, the dynamic threshold determination module is specifically used to obtain the amplification factor and sensitivity, and amplify the sensitivity using the amplification factor;

[0172] The average performance score and the amplified sensitivity are superimposed to obtain the dynamic threshold.

[0173] In a specific embodiment of the present application, the dynamic threshold determination module is specifically used to obtain the amplification factor and sensitivity, and amplify the sensitivity using the amplification factor;

[0174] Obtaining the packet loss rate and jitter of the target link segment from the target performance parameters;

[0175] Calculate the packet loss penalty value corresponding to the packet loss rate using the packet loss rate penalty function;

[0176] Calculate the jitter penalty value corresponding to the jitter using the jitter penalty function;

[0177] The average performance score, packet loss penalty value, jitter penalty value, and amplified sensitivity are superimposed to obtain a dynamic threshold.

[0178] In a specific embodiment of the present application, the network monitoring module is specifically used to perform network monitoring on heterogeneous device networking links using a bidirectional active measurement protocol, a network quality analyzer, and a flow-based network performance monitoring protocol.

[0179] In a specific embodiment of the present application, the southbound configuration management module is used to identify the device type of the network device in the heterogeneous device networking link before performing network monitoring on the heterogeneous device networking link using different network monitoring protocols; and configure the corresponding network monitoring protocol for the network device according to the device type;

[0180] BGP-LS topology management module, used to dynamically perceive the entire network topology based on the Border Gateway Protocol Link State Protocol and build a topology database;

[0181] Correspondingly, it also includes:

[0182] The full-network link topology display module is used to normalize the performance parameters obtained from monitoring. After obtaining the target performance parameters, the target performance parameters are superimposed on the topology database to obtain a performance analysis view; and the performance analysis view is output.

[0183] In a specific embodiment of the present application, the network monitoring module is specifically used to perform end-to-end or hop-by-hop network monitoring on heterogeneous device networking links using different network monitoring protocols.

[0184] In a specific embodiment of the present application, the network monitoring module is specifically used to perform end-to-end network monitoring of heterogeneous device networking links;

[0185] If the packet loss rate or jitter exceeds the monitoring threshold, hop-by-hop network monitoring is performed on the heterogeneous device networking link.

[0186] That is, in the embodiments of the present application, TWAMP, NQA, and IFIT technologies are comprehensively utilized to achieve comprehensive monitoring of end-to-end link performance across the entire network, providing accurate data support for link bottleneck location, thereby quickly and accurately locating link performance bottlenecks. Specifically, after the device is imported into the backbone network controller, the Telemetry configuration of TWAMP and IFIT is issued according to the vendor type to receive monitoring data. After obtaining the link topology information, the PE device of the same vendor issues the TWAMP configuration, and the device of a different vendor issues the NAQ configuration. Link performance data is then collected. The NQA data of different vendors is retrieved by the controller NETCONF, and the TWAMP data of the same vendor is sent by the device. Based on the existing network conditions, the IFIT configuration is issued to ensure cross-vendor transmission, and the device reports the IFIT performance data. The topology, NQA, and TWAMP data are analyzed and displayed to the user. Critical services are detected and reported end-to-end by IFIT. When the link is abnormal or the latency exceeds the standard, IFIT switches to hop-by-hop mode and comprehensively performs fine-grained link bottleneck determination. After the link is restored, IFIT switches back to end-to-end mode. It should be noted that, in actual applications, the modules in the device can be further divided based on their functional roles.

[0187] like Figure 7 As shown, the heterogeneous link monitoring may include the following modules:

[0188] Module 1: Southbound Configuration Management, responsible for automated configuration delivery and status monitoring of heterogeneous devices, uses the NETCONF / YANG model to achieve multi-vendor device compatibility management. It supports TWAMP / NQA / IFIT protocol configuration template management for devices from major vendors such as Huawei and H3C, automatically identifying device types and matching corresponding configuration templates. It provides configuration version management, delivery verification, and rollback mechanisms, and synchronizes device configuration status with the controller database in real time.

[0189] Module 2: BGP-LS Topology Management Module, based on the BGP-Link State protocol, provides dynamic network-wide topology awareness and builds a topology database that includes device vendors, interface attributes, and protocol status. It parses NLRI information to identify adjacencies between PE devices of the same vendor (vendor ID matching) and automatically annotates inter-vendor link characteristics. It supports subscription and real-time notification of topology change events, providing topology data support for link policy delivery.

[0190] Module 3: Link performance data collection module builds a multi-protocol hybrid collection system to implement unified collection and scheduling of NQA, TWAMP, and iFit data. For cross-vendor links, an asynchronous polling mechanism is used to obtain NQA test results (latency, jitter, and packet loss rate) via NETCONF. For same-vendor links, TWAMP statistics are subscribed to via Telemetry.

[0191] Module 4: Telemetry Management. Besides implementing the Telemetry data gateway function of the GRPC protocol stack, this module also handles the unified reception and parsing of iFit data from devices from different vendors. It provides dynamic subscription management, adjusting the sampling frequency (adjustable from 1 second to 5 minutes) based on business needs. A built-in streaming data processing engine performs threshold compression and time alignment on high-concurrency Telemetry data, ensuring real-time and accurate data processing. For iFit data in heterogeneous environments, this module implements a series of predefined data conversion rules to ensure that all collected data is formatted and semantically consistent before entering the analysis phase, providing a reliable data foundation for subsequent performance analysis.

[0192] Module 5: Full-network link topology display module, based on the spatiotemporal correlation engine of topology data and performance indicators, realizes multi-level and multi-precision visualization. It supports layered topology rendering (physical layer / logical layer / business layer), presents link delay distribution through heat map, and uses dynamic traffic coloring technology to mark abnormal links. It provides topology drilling function, which can drill down to view the TWAMP / NQA / IFIT joint analysis view of specific links. Display the corresponding views separately

[0193] Module 6: iFit Management Module implements an intelligent iFit policy engine, including a dynamic switchover mechanism between end-to-end and hop-by-hop detection modes. When a detection mode switch is triggered, a cross-vendor iFit configuration sequence is automatically generated to ensure consistent transmission of packet coloring information across heterogeneous devices.

[0194] Module 7: Link Performance Analysis integrates data collected from three different technologies, NQA, TWAMP, and iFit, and transforms it into a unified data model for comprehensive analysis of network-wide link performance. This integrated approach not only overcomes the limitations of individual tools in heterogeneous network environments but also provides a more comprehensive and accurate view of network performance. This module implements targeted preprocessing steps for the raw data collected from NQA, TWAMP, and iFit. NQA data primarily covers end-to-end performance metrics across vendor devices, such as latency, jitter, and packet loss rate; TWAMP focuses on high-precision latency measurement within a vendor's equipment; and iFit provides detailed hop-by-hop performance information, including but not limited to actual packet loss rate and latency parameters. Each technology has distinct data formats and content, requiring specialized parsing and conversion logic to ensure data consistency and comparability. All preprocessed data is mapped into a common data model. This unified data model defines a set of standardized performance metrics and measurement units, enabling data from different sources to be compared and analyzed within a common framework. For example, all latency data will be converted to a uniform time unit (milliseconds), and all packet loss rate data will be presented as a percentage.

[0195] Module 8: Link Bottleneck Detection Module. This module integrates data from three technologies: NQA, TWAMP, and IFIT, to quickly and accurately locate performance bottlenecks in the backbone network. When a link anomaly is detected or latency exceeds a set threshold (such as the t interval), the system automatically triggers a detailed performance bottleneck location process. Leveraging IFIT's hop-by-hop detection capabilities, the system provides fine-grained performance analysis to pinpoint the root cause of the problem. Furthermore, IFIT configuration is dynamically adjusted based on the analysis results to optimize performance bottleneck troubleshooting strategies. Once the problem is resolved, the system returns to end-to-end detection mode to continuously monitor network health. Finally, all analysis results are presented to users through an intuitive visual interface, helping network administrators efficiently manage and maintain complex, heterogeneous network environments.

[0196] Corresponding to the above method embodiment, an embodiment of the present application further provides an electronic device. The electronic device described below and the heterogeneous link monitoring method described above can refer to each other.

[0197] See also Figure 8 As shown, the electronic device includes:

[0198] Memory 332, for storing computer programs;

[0199] The processor 322 is configured to implement the steps of the heterogeneous link monitoring method of the above method embodiment when executing a computer program.

[0200] For details, please refer to Figure 9 , Figure 9 This is a schematic diagram of the specific structure of an electronic device provided in this embodiment. This electronic device may vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) (for example, one or more processors) and memory 332. The memory 332 stores one or more computer programs 342 or data 344. The memory 332 may be temporary storage or permanent storage. The program stored in the memory 332 may include one or more modules (not shown), each of which may include a series of instruction operations in the data processing device. Furthermore, the processor 322 may be configured to communicate with the memory 332 to execute the series of instruction operations in the memory 332 on the electronic device 301.

[0201] The electronic device 301 may further include one or more power supplies 326 , one or more wired or wireless network interfaces 350 , one or more input / output interfaces 358 , and / or one or more operating systems 341 .

[0202] The steps in the heterogeneous link monitoring method described above can be implemented by the structure of an electronic device.

[0203] Corresponding to the above method embodiment, an embodiment of the present application further provides a readable storage medium. The readable storage medium described below and the heterogeneous link monitoring method described above can refer to each other.

[0204] A readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the heterogeneous link monitoring method of the above method embodiment.

[0205] The readable storage medium may specifically be any readable storage medium capable of storing program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0206] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from the other embodiments. Reference can be made to the descriptions of the identical or similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and the relevant parts can be referred to the descriptions of the methods.

[0207] Those skilled in the art may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0208] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0209] Finally, it should be noted that, in this document, relationships such as first and second, etc., are used solely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms include, comprise, or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0210] This document uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and core ideas of this application. At the same time, for those skilled in the art, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting this application.

Claims

1. A heterogeneous link monitoring method, characterized in that: include: Use different network monitoring protocols to monitor the networking links of heterogeneous devices; Normalize the performance parameters obtained from monitoring to obtain target performance parameters; Calculating, using the target performance parameters, an average performance score corresponding to a target path in the heterogeneous device networking link and a comprehensive performance score of a target link segment in the target path; determining a dynamic threshold of the target link segment using the average performance score; When the comprehensive performance score reaches the dynamic threshold, it is determined that a performance bottleneck exists in the target link segment.

2. The heterogeneous link monitoring method according to claim 1, characterized in that: Determining a dynamic threshold of the target link segment using the average performance score includes: Obtaining an amplification factor and a sensitivity, and amplifying the sensitivity using the amplification factor; The average performance score and the amplified sensitivity are superimposed to obtain the dynamic threshold.

3. The heterogeneous link monitoring method according to claim 1, characterized in that: Determining a dynamic threshold of the target link segment using the average performance score includes: Obtaining an amplification factor and a sensitivity, and amplifying the sensitivity using the amplification factor; Obtaining the packet loss rate and jitter of the target link segment from the target performance parameters; Calculating a packet loss penalty value corresponding to the packet loss rate using a packet loss rate penalty function; Calculating a jitter penalty value corresponding to the jitter using a jitter penalty function; The average performance score, the packet loss penalty value, the jitter penalty value, and the amplified sensitivity are superimposed to obtain the dynamic threshold.

4. The heterogeneous link monitoring method according to claim 1, characterized in that: The network monitoring protocol includes at least two protocols among a bidirectional active measurement protocol, a network quality analyzer and a flow-based network performance monitoring protocol.

5. The heterogeneous link monitoring method according to claim 4, characterized in that: Before using different network monitoring protocols to monitor heterogeneous device networking links, the following must be performed: Identifying the device type of the network device in the heterogeneous device networking link; Configuring a corresponding network monitoring protocol for the network device according to the device type; Based on the Border Gateway Protocol-Link State Protocol, dynamic perception of the entire network topology is performed to build a topology database; Accordingly, after normalizing the performance parameters obtained from monitoring to obtain the target performance parameters, the following steps are also included: Overlaying the target performance parameters on the topological database to obtain a performance analysis view; The performance analysis view is output.

6. The heterogeneous link monitoring method according to claim 1, characterized in that: Use different network monitoring protocols to monitor heterogeneous device networking links, including: Different network monitoring protocols are used to perform end-to-end or hop-by-hop network monitoring on the heterogeneous device networking links.

7. The heterogeneous link monitoring method according to claim 6, characterized in that: Perform end-to-end or hop-by-hop network monitoring on the heterogeneous device networking links, including: Perform end-to-end network monitoring on the heterogeneous device networking links; If the packet loss rate or jitter exceeds the monitoring threshold, hop-by-hop network monitoring is performed on the heterogeneous device networking link.

8. A heterogeneous link monitoring device, characterized in that: include: The network monitoring module is used to monitor the networking links of heterogeneous devices using different network monitoring protocols; A normalization processing module is used to normalize the performance parameters obtained by monitoring to obtain target performance parameters; a performance scoring module, configured to calculate, by using the target performance parameters, an average performance score corresponding to a target path in the heterogeneous device networking link and a comprehensive performance score of a target link segment in the target path; a dynamic threshold determination module, configured to determine a dynamic threshold of the target link segment using the average performance score; The performance bottleneck locating module is configured to determine that a performance bottleneck exists in the target link segment when the comprehensive performance score reaches the dynamic threshold.

9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the heterogeneous link monitoring method according to any one of claims 1 to 7 when executing the computer program.

10. A readable storage medium, characterized in that: The readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the heterogeneous link monitoring method according to any one of claims 1 to 7 are implemented.

Images