Private network bandwidth bottleneck detection method, system, equipment and medium

Abstract

The present invention relates to the field of communication technology and provides a method, system, device and medium for detecting bandwidth bottlenecks in a private network. On the one hand, a probe collector is deployed on the starting server and the ending server of the private network path, does not rely on specific network equipment, and therefore has stronger compatibility. Combined with the analysis capability of a data analyzer, it can further be compatible with complex network configurations in a multi-hop private network environment; on the other hand, the probe collector is used to perform traceroute on the target private network, and the data analyzer is used to generate a link topology based on the traceroute results. In combination with traffic injection and ping tests, the transport layer parameter changes of the round-trip delay and packet loss rate caused by traffic control are analyzed, thereby accurately identifying bandwidth-limited nodes.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method, system, device and medium for detecting a bandwidth bottleneck of a private network. Background Art

[0002] Existing bandwidth testing methods typically rely on tools like iPerf and Speedtest. While these tools can measure end-to-end maximum bandwidth, they cannot effectively identify specific routing nodes where bottlenecks occur, nor can they intuitively reflect bandwidth limitations at network nodes. Therefore, when bandwidth bottlenecks occur in private networks like enterprise intranets and data center interconnects, traditional methods struggle to accurately diagnose them.

[0003] Specifically, existing methods have the following problems:

[0004] 1. Lack of consideration of flow control factors: Existing tools fail to analyze the impact of flow control on the network transport layer;

[0005] 2. Unable to accurately locate bottleneck routes: Existing methods cannot accurately analyze which node or link is limiting bandwidth;

[0006] 3. Incompatible with complex network environments: In multi-hop private network environments, existing methods are difficult to be compatible with complex network configurations such as QoS (Quality of Service) policies and traffic shaping. Summary of the Invention

[0007] In view of the above, it is necessary to provide a private network bandwidth bottleneck detection method, system, device and medium, aiming to solve the problem of being unable to accurately locate bandwidth bottlenecks in a private network environment.

[0008] A method for detecting a private network bandwidth bottleneck is applied to a private network bandwidth bottleneck detection system. The private network bandwidth bottleneck detection system includes probe collectors deployed on a starting server and an ending server of a private network path, respectively, and a data analyzer deployed on any server in the private network path. The method includes:

[0009] In response to a bandwidth bottleneck detection instruction for a target private network, the probe collector performs traceroute on the target private network to obtain traceroute path information, and sends the traceroute path information to the data analyzer;

[0010] The data analyzer generates a link topology of the target private network according to the traceroute path information;

[0011] The probe collector performs traffic injection along the link topology, and in the process of performing traffic injection, performs a ping test on each routing node in the link topology to obtain the real-time round-trip delay and packet loss rate of each routing node, and sends the real-time round-trip delay and packet loss rate of each routing node to the data analyzer;

[0012] The data analyzer locates the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node.

[0013] According to a preferred embodiment of the present invention, the probe collector performs traceroute on the target private network to obtain traceroute path information, including:

[0014] The probe collector tracks the path of the data packet from the source end to the target end and records the delay information of each hop to obtain the traceroute path information.

[0015] According to a preferred embodiment of the present invention, after sending the traceroute path information to the data analyzer, the method further includes:

[0016] The data analyzer detects whether the last hop of the traceroute path information is the IP address of the probe collector on the terminal server;

[0017] When detecting that the last hop of the traceroute path information is not the IP address of the probe collector on the destination server, the data analyzer determines that the probe collector on the starting server cannot communicate with the probe collector on the destination server and issues an alarm.

[0018] According to a preferred embodiment of the present invention, the data analyzer generates the link topology of the target private network according to the traceroute path information, including:

[0019] The data analyzer obtains the sending network card IP address, the receiving network card IP address and the TTL value of each route from the traceroute path information;

[0020] The data analyzer uses the probe collector on the starting server as the initial node and the probe collector on the end server as the end node;

[0021] The data analyzer determines a TTL value decreasing rule according to the TTL value of each route, and determines a routing order through which the data packet passes according to the TTL value decreasing rule;

[0022] The data analyzer determines the link connection relationship between each route based on the sending network card IP address and the receiving network card IP address of each route;

[0023] The data analyzer takes each route as a node and starts from the initial node, and sequentially connects each route and the end node according to the route sequence and the link connection relationship to obtain the link topology.

[0024] According to a preferred embodiment of the present invention, the probe collector performs traffic injection along the link topology, including:

[0025] The probe collector constructs a SOCKET network data packet to generate TCP test traffic;

[0026] The probe collector transmits high-flow data from the initial node to the end node, and from the end node to the initial node based on the TCP test flow.

[0027] According to a preferred embodiment of the present invention, the data analyzer locates the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node, including:

[0028] When it is detected that the increase in the real-time round-trip delay of any routing node is greater than a first preset range, and the increase in the packet loss rate is greater than a second preset range, the data analyzer obtains the ping test direction and data transmission direction corresponding to the any routing node;

[0029] When the ping test direction corresponding to the arbitrary routing node is the same as the data transmission direction, the data analyzer determines that the sending network card of the previous routing node of the arbitrary routing node is abnormal, and determines the previous routing node of the arbitrary routing node as the failure point causing the bandwidth bottleneck; or

[0030] When the ping test direction corresponding to the arbitrary routing node is different from the data transmission direction, the data analyzer determines that the sending network card of the arbitrary routing node is abnormal, and determines the arbitrary routing node as a failure point causing a bandwidth bottleneck.

[0031] According to a preferred embodiment of the present invention, after the data analyzer locates the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node, the method further includes:

[0032] Send troubleshooting tips to the routing operations personnel corresponding to the fault point that causes the bandwidth bottleneck.

[0033] A private network bandwidth bottleneck detection system includes probe collectors deployed on a starting server and an ending server of a private network path, and a data analyzer deployed on any server in the private network path. The private network bandwidth bottleneck detection system includes:

[0034] The probe collector is configured to, in response to a bandwidth bottleneck detection instruction for a target private network, perform traceroute on the target private network to obtain traceroute path information, and send the traceroute path information to the data analyzer;

[0035] The data analyzer is configured to generate a link topology of the target private network based on the traceroute path information;

[0036] The probe collector is further used to perform traffic injection along the link topology, and in the process of performing traffic injection, perform a ping test on each routing node in the link topology to obtain the real-time round-trip delay and packet loss rate of each routing node, and send the real-time round-trip delay and packet loss rate of each routing node to the data analyzer;

[0037] The data analyzer is further used to locate the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node.

[0038] A computer device, comprising:

[0039] a memory storing at least one instruction; and

[0040] The processor executes the instructions stored in the memory to implement the private network bandwidth bottleneck detection method.

[0041] A computer-readable storage medium stores at least one instruction, and the at least one instruction is executed by a processor in a computer device to implement the private network bandwidth bottleneck detection method.

[0042] It can be seen from the above technical solutions that, on the one hand, the probe collector is deployed on the starting server and the end server of the private network path, and does not rely on specific network equipment, so it has stronger compatibility. Combined with the analysis capabilities of the data analyzer, it can further be compatible with complex network configurations in a multi-hop private network environment; on the other hand, the probe collector is used to traceroute the target private network, and the data analyzer is used to generate the link topology based on the traceroute results, and combined with traffic injection and ping tests to analyze the changes in the transport layer parameters of the round-trip delay and packet loss rate caused by traffic control, so that bandwidth-limited nodes can be accurately identified. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 It is a flow chart of a preferred embodiment of the method for detecting a bandwidth bottleneck of a private network of the present invention;

[0044] Figure 2 This is a functional module diagram of a preferred embodiment of the private network bandwidth bottleneck detection system of the present invention;

[0045] Figure 3 It is a structural diagram of a computer device according to a preferred embodiment of the present invention for implementing a method for detecting a bandwidth bottleneck in a private network. DETAILED DESCRIPTION

[0046] In order to make the objectives, technical solutions and advantages of the present invention more clear, the present invention is described in detail below with reference to the accompanying drawings and specific embodiments.

[0047] like Figure 1 FIG. 1 is a flow chart of a preferred embodiment of the method for detecting a bandwidth bottleneck in a private network according to the present invention. The order of the steps in the flow chart can be changed and some steps can be omitted according to different requirements.

[0048] The private network bandwidth bottleneck detection method is applied to at least two computer devices. The computer device is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions. Its hardware includes but is not limited to microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0049] The computer device may be any electronic product that can perform human-computer interaction with a user, such as a personal computer, a tablet computer, a smart phone, a personal digital assistant (PDA), a game console, an interactive network television (IPTV), a smart wearable device, etc.

[0050] The computer device may also include a network device and / or a user device, wherein the network device includes, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing consisting of a large number of hosts or network servers.

[0051] The server can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0052] Among them, Artificial Intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0053] Fundamental AI technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interaction systems, and mechatronics. AI software technologies primarily encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0054] The network where the computer device is located includes but is not limited to the Internet, wide area network, metropolitan area network, local area network, virtual private network (VPN), etc.

[0055] This embodiment is applied to a private network bandwidth bottleneck detection system. The private network bandwidth bottleneck detection system includes probe collectors deployed on the starting server and the end server of the private network path, and a data analyzer deployed on any server in the private network path. The private network bandwidth bottleneck detection method includes:

[0056] S10, in response to a bandwidth bottleneck detection instruction for a target private network, the probe collector performs traceroute on the target private network to obtain traceroute path information, and sends the traceroute path information to the data analyzer.

[0057] In this embodiment, the target private network may include an enterprise intranet, a data center internet network, etc. The transmission path of the target private network is relatively stable and certain.

[0058] In this embodiment, the bandwidth bottleneck detection instruction is used to trigger the detection of the bandwidth bottleneck of the target private network. For example, by executing the bandwidth bottleneck detection instruction, it can be detected that a certain network node or link of the target private network has become a performance bottleneck for data transmission due to limited bandwidth.

[0059] In this embodiment, the bandwidth bottleneck detection instruction can be automatically triggered when the target private network is put into use, so as to achieve comprehensive monitoring of the bandwidth of the target private network.

[0060] In this embodiment, the probe collector performs traceroute on the target private network to obtain traceroute path information including:

[0061] The probe collector tracks the path of the data packet from the source end to the target end and records the delay information of each hop to obtain the traceroute path information.

[0062] The delay information includes a round trip delay, and the round trip delay is used to reflect the time it takes for a data packet to travel from the probe collection end to the router.

[0063] S11, the data analyzer generates a link topology of the target private network according to the traceroute path information.

[0064] In this embodiment, after sending the traceroute path information to the data analyzer, the method further includes:

[0065] The data analyzer detects whether the last hop of the traceroute path information is the IP (Internet Protocol Address) address of the probe collector on the terminal server;

[0066] When detecting that the last hop of the traceroute path information is not the IP address of the probe collector on the destination server, the data analyzer determines that the probe collector on the starting server cannot communicate with the probe collector on the destination server and issues an alarm.

[0067] Through the above embodiment, an alarm can be issued in time when the probe collector on the starting server fails to establish communication with the probe collector on the end server, so as to avoid affecting the effective monitoring of the entire network link.

[0068] In this embodiment, the data analyzer generates the link topology of the target private network according to the traceroute path information, including:

[0069] The data analyzer obtains the sending network card IP address, the receiving network card IP address and the TTL (Time To Live, data packet survival time) value of each route from the traceroute path information;

[0070] The data analyzer uses the probe collector on the starting server as the initial node and the probe collector on the end server as the end node;

[0071] The data analyzer determines a TTL value decreasing rule according to the TTL value of each route, and determines a routing order through which the data packet passes according to the TTL value decreasing rule;

[0072] The data analyzer determines the link connection relationship between each route based on the sending network card IP address and the receiving network card IP address of each route;

[0073] The data analyzer takes each route as a node and starts from the initial node, and sequentially connects each route and the end node according to the route sequence and the link connection relationship to obtain the link topology.

[0074] The TTL value refers to the maximum distance a data packet can travel when passing through a route. Every time a data packet passes through a route, its survival count decreases by 1, that is, the TTL value decreases by 1.

[0075] Through the above embodiment, the traceroute path information collected by the probe collectors deployed at both ends of the network path can be used to generate a link topology. Since the probe collector does not rely on specific network equipment and uses bypass mode to collect data, it does not affect normal business traffic and is compatible with network equipment from different manufacturers.

[0076] S12, the probe collector performs traffic injection along the link topology, and in the process of performing traffic injection, performs a ping test on each routing node in the link topology to obtain the real-time round-trip delay and packet loss rate of each routing node, and sends the real-time round-trip delay and packet loss rate of each routing node to the data analyzer.

[0077] In this embodiment, the probe collector performs traffic injection along the link topology, including:

[0078] The probe collector constructs a SOCKET network data packet to generate TCP (Transmission Control Protocol) test traffic;

[0079] The probe collector transmits high-flow data from the initial node to the end node, and from the end node to the initial node based on the TCP test flow.

[0080] In the above embodiment, the probe collector simulates end-to-end high-volume data traffic by constructing a large number of socket network packets, enabling subsequent analysis of the impact of flow control on the network transport layer. Furthermore, traffic injection can trigger flow control policies such as QoS (Quality of Service), traffic shaping, and bandwidth limiting, allowing subsequent data analysis to capture the impact of these policies on network performance.

[0081] In this embodiment, a ping test is used to calculate parameters such as real-time round-trip delay and packet loss rate in combination with packet capture, thereby providing data for the subsequent data analyzer to analyze and locate bandwidth bottlenecks.

[0082] S13, the data analyzer locates the bandwidth bottleneck of the target private network according to the real-time round-trip delay and packet loss rate of each routing node.

[0083] In this embodiment, the data analyzer locates the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node, including:

[0084] When it is detected that the increase in the real-time round-trip delay of any routing node is greater than a first preset range, and the increase in the packet loss rate is greater than a second preset range, the data analyzer obtains the ping test direction and data transmission direction corresponding to the any routing node;

[0085] When the ping test direction corresponding to the arbitrary routing node is the same as the data transmission direction, the data analyzer determines that the sending network card of the previous routing node of the arbitrary routing node is abnormal, and determines the previous routing node of the arbitrary routing node as the failure point causing the bandwidth bottleneck; or

[0086] When the ping test direction corresponding to the arbitrary routing node is different from the data transmission direction, the data analyzer determines that the sending network card of the arbitrary routing node is abnormal, and determines the arbitrary routing node as a failure point causing a bandwidth bottleneck.

[0087] Specifically, this embodiment performs two traffic injections in different directions (i.e., from the initial node to the end node, and from the end node to the initial node), and determines whether there is a problem with the data packet exit network card of the route (i.e., the sending network card). Based on this premise, when the ping test is in the same direction as the data transmission direction, the ping is on the entry network card of the route, and will not pass through the problematic route, so the round-trip delay, packet loss rate and other data will not change much. Then, after passing through the problematic route, that is, the next route, its round-trip delay and packet loss rate will increase, so it can be determined that the problematic route may be the previous route of the route with increased round-trip delay and packet loss rate. To prove this result, it can be determined that the ping test is in the opposite direction of the data transmission. When the ping test reaches the problematic route, if its round-trip delay and packet loss rate increase, then the problematic route can be determined.

[0088] For example, if the data transmission direction is: Probe A → R1 → R2 → R3 → R4 → Probe B, and assume that R2 is the problem router.

[0089] When the ping test is in the same direction as the transmission, probe A does not need to pass through the egress network card of R2 when pinging R2, but needs to pass through the egress network card of R2 when pinging R3. Therefore, the round-trip delay and packet loss rate of R2 will not increase, but the round-trip delay and packet loss rate of R3 will increase; or

[0090] When the ping test is in the opposite direction of the transmission, probe B does not need to pass through the egress network card of R2 when pinging R3, but needs to pass through the egress network card of R2 when pinging R2. In this case, the round-trip delay and packet loss rate of R2 increase.

[0091] Through the above embodiments, it is possible to comprehensively analyze parameters such as delay changes and packet loss rates under high load conditions to accurately determine the bandwidth bottleneck nodes that are limited.

[0092] In this embodiment, after the data analyzer locates the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node, the method further includes:

[0093] Send troubleshooting tips to the routing operations personnel corresponding to the fault point that causes the bandwidth bottleneck.

[0094] Through the above embodiment, relevant operation and maintenance personnel can be notified in time to check the problematic routing node, thereby determining whether it is a physical problem or a QoS policy problem.

[0095] It can be seen from the above technical solutions that, on the one hand, the probe collector is deployed on the starting server and the end server of the private network path, and does not rely on specific network equipment, so it has stronger compatibility. Combined with the analysis capabilities of the data analyzer, it can further be compatible with complex network configurations in a multi-hop private network environment; on the other hand, the probe collector is used to traceroute the target private network, and the data analyzer is used to generate the link topology based on the traceroute results, and combined with traffic injection and ping tests to analyze the changes in the transport layer parameters of the round-trip delay and packet loss rate caused by traffic control, so that bandwidth-limited nodes can be accurately identified.

[0096] like Figure 2 , which is a functional module diagram of a preferred embodiment of the private network bandwidth bottleneck detection system of the present invention. The private network bandwidth bottleneck detection system 11 includes a probe collector 110 deployed on the starting server and the end server of the private network path, respectively, and a data analyzer 111 deployed on any server in the private network path. The modules / units referred to in the present invention refer to a series of computer program segments that can be executed by a processor and can perform fixed functions, which are stored in a memory. In this embodiment, the functions of each module / unit will be described in detail in subsequent embodiments.

[0097] The probe collector 110 is configured to, in response to a bandwidth bottleneck detection instruction for a target private network, perform traceroute on the target private network to obtain traceroute path information, and send the traceroute path information to the data analyzer 111;

[0098] The data analyzer 111 is configured to generate a link topology of the target private network based on the traceroute path information;

[0099] The probe collector 110 is further configured to perform traffic injection along the link topology, perform a ping test on each routing node in the link topology during the traffic injection process to obtain the real-time round-trip delay and packet loss rate of each routing node, and send the real-time round-trip delay and packet loss rate of each routing node to the data analyzer 111;

[0100] The data analyzer 111 is further configured to locate the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node.

[0101] It can be seen from the above technical solutions that, on the one hand, the probe collector is deployed on the starting server and the end server of the private network path, and does not rely on specific network equipment, so it has stronger compatibility. Combined with the analysis capabilities of the data analyzer, it can further be compatible with complex network configurations in a multi-hop private network environment; on the other hand, the probe collector is used to traceroute the target private network, and the data analyzer is used to generate the link topology based on the traceroute results, and combined with traffic injection and ping tests to analyze the changes in the transport layer parameters of the round-trip delay and packet loss rate caused by traffic control, so that bandwidth-limited nodes can be accurately identified.

[0102] like Figure 3 FIG. 1 is a schematic diagram of the structure of a computer device according to a preferred embodiment of the present invention for implementing a method for detecting a bandwidth bottleneck in a private network.

[0103] The computer device 1 may include a memory 12 , a processor 13 , and a bus (the arrow in the figure represents the bus), and may also include a computer program stored in the memory 12 and executable on the processor 13 , such as a private network bandwidth bottleneck detection program.

[0104] Those skilled in the art will understand that the schematic diagram is merely an example of the computer device 1 and does not constitute a limitation on the computer device 1. The computer device 1 may have either a bus structure or a star structure. The computer device 1 may also include more or less other hardware or software than shown in the figure, or a different arrangement of components. For example, the computer device 1 may also include input and output devices, network access devices, etc.

[0105] It should be noted that the computer device 1 is only an example. Other existing or future electronic products that are suitable for the present invention should also be included in the scope of protection of the present invention and included here by reference.

[0106] The memory 12 includes at least one type of readable storage medium, including flash memory, a removable hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 12 may be an internal storage unit of the computer device 1, such as a removable hard disk of the computer device 1. In other embodiments, the memory 12 may also be an external storage device of the computer device 1, such as a plug-in removable hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a flash memory card, etc. equipped on the computer device 1. Furthermore, the memory 12 may include both an internal storage unit of the computer device 1 and an external storage device. The memory 12 can be used not only to store application software installed in the computer device 1 and various types of data, such as the code of a private network bandwidth bottleneck detection program, but also to temporarily store data that has been output or is about to be output.

[0107] In some embodiments, processor 13 may be comprised of an integrated circuit, such as a single packaged integrated circuit or multiple packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and a combination of various control chips. Processor 13 is the control core (control unit) of computer device 1, connecting the various components of computer device 1 using various interfaces and circuits. It executes programs or modules stored in memory 12 (such as a dedicated network bandwidth bottleneck detection program) and accesses data stored in memory 12 to perform various functions and process data.

[0108] The processor 13 executes the operating system of the computer device 1 and various installed applications. The processor 13 executes the applications to implement the steps in the above-mentioned embodiments of the method for detecting a bandwidth bottleneck in a private network, for example Figure 1 Steps shown.

[0109] Exemplarily, the computer program may be divided into one or more modules / units, which are stored in the memory 12 and executed by the processor 13 to implement the present invention. The one or more modules / units may be a series of computer-readable instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program in the computer device 1. For example, the computer program may be divided into a probe collector 110 and a data analyzer 111.

[0110] The integrated unit implemented as a software functional module can be stored in a computer-readable storage medium. The software functional module stored in the storage medium includes instructions for causing a computer device (which can be a personal computer, computing device, or network device, etc.) or a processor to execute portions of the private network bandwidth bottleneck detection method described in various embodiments of the present invention.

[0111] If the modules / units integrated in the computer device 1 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the present invention can also implement all or part of the processes in the above-mentioned method embodiments by instructing relevant hardware devices through a computer program. The computer program can be stored in a computer-readable storage medium. When executed by a processor, the computer program can implement the steps of each of the above-mentioned method embodiments.

[0112] The computer program includes computer program code, which may be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium may include any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory, etc.

[0113] Furthermore, the computer-readable storage medium may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function, etc.; the data storage area may store data created according to the use of the blockchain node, etc.

[0114] Blockchain, as used in this article, refers to a novel application model for computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Blockchain is essentially a decentralized database, a series of data blocks linked together using cryptographic methods. Each block contains information about a batch of online transactions, used to verify the validity of this information (to prevent counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, the platform product and service layer, and the application service layer.

[0115] The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 3 The figure shows that only one straight line is used, but it does not mean that there is only one bus or one type of bus. The bus is configured to realize the connection and communication between the memory 12 and at least one processor 13.

[0116] Although not shown, the computer device 1 may also include a power supply (such as a battery) to power various components. Preferably, the power supply can be logically connected to the at least one processor 13 via a power management device, thereby enabling functions such as charge management, discharge management, and power consumption management through the power management device. The power supply may also include one or more DC or AC power supplies, a recharging device, a power failure detection circuit, a power converter or inverter, a power status indicator, and other arbitrary components. The computer device 1 may also include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be further described here.

[0117] Furthermore, the computer device 1 may also include a network interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is generally used to establish a communication connection between the computer device 1 and other computer devices.

[0118] Optionally, the computer device 1 may further include a user interface, which may be a display or an input unit (such as a keyboard). Optionally, the user interface may also be a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen. The display may also be appropriately referred to as a display screen or display unit, and is used to display information processed by the computer device 1 and to display a visual user interface.

[0119] It should be understood that the embodiment is for illustration only and the scope of the patent application is not limited to this structure.

[0120] It will be understood by those skilled in the art that Figure 3The structure shown does not constitute a limitation on the computer device 1 , and may include fewer or more components than shown in the figure, or combine certain components, or arrange the components differently.

[0121] Combine Figure 1 The memory 12 in the computer device 1 stores a plurality of instructions to implement a method for detecting a bandwidth bottleneck in a private network. The processor 13 can execute the plurality of instructions to implement:

[0122] In response to a bandwidth bottleneck detection instruction for a target private network, the probe collector performs traceroute on the target private network to obtain traceroute path information, and sends the traceroute path information to the data analyzer;

[0123] The data analyzer generates a link topology of the target private network according to the traceroute path information;

[0124] The probe collector performs traffic injection along the link topology, and in the process of performing traffic injection, performs a ping test on each routing node in the link topology to obtain the real-time round-trip delay and packet loss rate of each routing node, and sends the real-time round-trip delay and packet loss rate of each routing node to the data analyzer;

[0125] The data analyzer locates the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node.

[0126] Specifically, the specific implementation method of the processor 13 for the above instructions can refer to Figure 1 The description of the relevant steps in the corresponding embodiments will not be repeated here.

[0127] It should be noted that the data involved in this case were all obtained legally. The software tools or components not produced by our company that appear in the embodiments of this application are merely examples and do not represent actual use.

[0128] In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the module division is merely a logical functional division, and actual implementation may employ other division methods.

[0129] The present invention can be used in a wide variety of general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and the like. The present invention can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present invention can also be practiced in distributed computing environments in which tasks are performed by remote processing devices connected via a communications network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

[0130] The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed across multiple network elements. Some or all of the modules may be selected to achieve the purpose of the solution of this embodiment according to actual needs.

[0131] In addition, the functional modules in various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or hardware plus software functional modules.

[0132] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0133] Therefore, the embodiments should be considered in all respects as illustrative and non-restrictive, and the scope of the invention is defined by the appended claims rather than the foregoing description, and all changes that come within the meaning and range of equivalents of the claims are intended to be embraced therein. Any reference to a figure in a claim should not be construed as limiting the claim to which it relates.

[0134] Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices described in the present invention may also be implemented by a single unit or device through software or hardware. Terms such as first and second are used to indicate names and do not imply any particular order.

[0135] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not limiting. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A method for detecting a bandwidth bottleneck in a private network, characterized in that: Applied to a private network bandwidth bottleneck detection system, the private network bandwidth bottleneck detection system includes probe collectors deployed on the starting server and the end server of the private network path respectively, and a data analyzer deployed on any server in the private network path; The private network bandwidth bottleneck detection method includes: In response to a bandwidth bottleneck detection instruction for a target private network, the probe collector performs traceroute on the target private network to obtain traceroute path information, and sends the traceroute path information to the data analyzer; The data analyzer generates a link topology of the target private network according to the traceroute path information; The probe collector performs traffic injection along the link topology, and in the process of performing traffic injection, performs a ping test on each routing node in the link topology to obtain the real-time round-trip delay and packet loss rate of each routing node, and sends the real-time round-trip delay and packet loss rate of each routing node to the data analyzer; The data analyzer locates the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node, including: when it is detected that the increase in the real-time round-trip delay of any routing node is greater than a first preset range, and the increase in the packet loss rate is greater than a second preset range, the data analyzer obtains the ping test direction and data transmission direction corresponding to the arbitrary routing node; when the ping test direction corresponding to the arbitrary routing node is the same as the data transmission direction, the data analyzer determines that the sending network card of the previous routing node of the arbitrary routing node is abnormal, and determines the previous routing node of the arbitrary routing node as the fault point causing the bandwidth bottleneck; or when the ping test direction corresponding to the arbitrary routing node is different from the data transmission direction, the data analyzer determines that the sending network card of the arbitrary routing node is abnormal, and determines the arbitrary routing node as the fault point causing the bandwidth bottleneck.

2. The method for detecting a private network bandwidth bottleneck according to claim 1, wherein: The probe collector performs traceroute on the target private network to obtain traceroute path information including: The probe collector tracks the path of the data packet from the source end to the target end and records the delay information of each hop to obtain the traceroute path information.

3. The method for detecting a private network bandwidth bottleneck according to claim 1, wherein: After sending the traceroute path information to the data analyzer, the method further includes: The data analyzer detects whether the last hop of the traceroute path information is the IP address of the probe collector on the terminal server; When detecting that the last hop of the traceroute path information is not the IP address of the probe collector on the destination server, the data analyzer determines that the probe collector on the starting server cannot communicate with the probe collector on the destination server and issues an alarm.

4. The method for detecting a private network bandwidth bottleneck according to claim 1, wherein: The data analyzer generates the link topology of the target private network according to the traceroute path information, including: The data analyzer obtains the sending network card IP address, the receiving network card IP address and the TTL value of each route from the traceroute path information; The data analyzer uses the probe collector on the starting server as the initial node and the probe collector on the end server as the end node; The data analyzer determines a TTL value decreasing rule according to the TTL value of each route, and determines a routing order through which the data packet passes according to the TTL value decreasing rule; The data analyzer determines the link connection relationship between each route based on the sending network card IP address and the receiving network card IP address of each route; The data analyzer takes each route as a node and starts from the initial node, and sequentially connects each route and the end node according to the route sequence and the link connection relationship to obtain the link topology.

5. The method for detecting a private network bandwidth bottleneck according to claim 4, wherein: The probe collector performs traffic injection along the link topology, including: The probe collector constructs a SOCKET network data packet to generate TCP test traffic; The probe collector transmits high-flow data from the initial node to the end node, and from the end node to the initial node based on the TCP test flow.

6. The method for detecting a private network bandwidth bottleneck according to claim 1, wherein: After the data analyzer locates the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node, the method further includes: Send troubleshooting tips to the routing operations personnel corresponding to the fault point that causes the bandwidth bottleneck.

7. A private network bandwidth bottleneck detection system, characterized in that: The private network bandwidth bottleneck detection system includes probe collectors deployed on the starting server and the end server of the private network path respectively, and a data analyzer deployed on any server of the private network path; The private network bandwidth bottleneck detection system includes: The probe collector is configured to, in response to a bandwidth bottleneck detection instruction for a target private network, perform traceroute on the target private network to obtain traceroute path information, and send the traceroute path information to the data analyzer; The data analyzer is configured to generate a link topology of the target private network based on the traceroute path information; The probe collector is further used to perform traffic injection along the link topology, and in the process of performing traffic injection, perform a ping test on each routing node in the link topology to obtain the real-time round-trip delay and packet loss rate of each routing node, and send the real-time round-trip delay and packet loss rate of each routing node to the data analyzer; The data analyzer is also used to locate the bandwidth bottleneck of the target private network based on the real-time round-trip delay and packet loss rate of each routing node, including: when it is detected that the increase in the real-time round-trip delay of any routing node is greater than a first preset range, and the increase in the packet loss rate is greater than a second preset range, the data analyzer obtains the ping test direction and data transmission direction corresponding to the arbitrary routing node; when the ping test direction corresponding to the arbitrary routing node is the same as the data transmission direction, the data analyzer determines that the sending network card of the previous routing node of the arbitrary routing node is abnormal, and determines the previous routing node of the arbitrary routing node as the fault point causing the bandwidth bottleneck; or when the ping test direction corresponding to the arbitrary routing node is different from the data transmission direction, the data analyzer determines that the sending network card of the arbitrary routing node is abnormal, and determines the arbitrary routing node as the fault point causing the bandwidth bottleneck.

8. A computer device, characterized in that: The computer device comprises: a memory storing at least one instruction; and The processor executes the instructions stored in the memory to implement the private network bandwidth bottleneck detection method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one instruction, and the at least one instruction is executed by a processor in a computer device to implement the private network bandwidth bottleneck detection method according to any one of claims 1 to 6.

Images