Network detection method and device, electronic equipment, storage medium and program product

Abstract

This disclosure provides a network probing method, apparatus, electronic device, computer-readable storage medium, and computer program product, relating to artificial intelligence technologies such as cloud computing and cloud networking, and applicable to intelligent cloud scenarios. The method includes: determining a target cloud network as the object of probing based on a network probing request; determining a probing start point and a probing end point within the target cloud network; determining a target probing method based on the cloud network types to which the start and end points belong; and using probing data packets constructed according to the target probing method and satisfying the network probing request to perform network probing on the cloud networks to which the start and end points belong and the communication link between them. This method can comprehensively probe various parameters, including link connectivity, network latency, packet loss rate, and cloud network operating status, improving the comprehensiveness of monitoring and probing of various networks in a hybrid cloud network architecture.

Description

Technical Field

[0001] This disclosure relates to the field of data processing technology, specifically to artificial intelligence technology fields such as cloud computing and cloud network technology, and can be applied in intelligent cloud scenarios. In particular, it relates to a network detection method, device, electronic device, computer-readable storage medium, and computer program product. Background Technology

[0002] As cloud networks become more complex and cloud network products proliferate, the gateways of virtual networks and physical network resources remain a black box for users, who lack comprehensive monitoring and diagnostic capabilities for these complex cloud products.

[0003] Especially in a hybrid cloud network architecture, if users do not have their own network detection service, they cannot have real-time and comprehensive control over the network quality of the hybrid cloud. Summary of the Invention

[0004] This disclosure provides a network detection method, apparatus, electronic device, computer-readable storage medium, and computer program product.

[0005] In a first aspect, embodiments of this disclosure propose a network detection method, comprising: determining a target cloud network as the detection object according to a network detection request; determining a detection start point and a detection end point under the target cloud network; determining a target detection method according to the cloud network types to which the detection start point and the detection end point belong; and using a detection data packet constructed according to the target detection method and satisfying the network detection request to perform network detection on the cloud networks to which the detection start point and the detection end point belong and the communication link between them.

[0006] Secondly, embodiments of this disclosure propose a network detection device, comprising: a detection target determination unit configured to determine a target cloud network as the detection target according to a network detection request; a detection start point and end point determination unit configured to determine a detection start point and a detection end point under the target cloud network; a target detection method determination unit configured to determine a target detection method according to the cloud network types to which the detection start point and the detection end point belong; and a network detection unit configured to perform network detection on the cloud networks to which the detection start point and the detection end point belong and the communication link between them using a detection data packet constructed according to the target detection method and satisfying the network detection request.

[0007] Thirdly, embodiments of this disclosure provide an electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to implement the network probing method as described in the first aspect.

[0008] Fourthly, embodiments of this disclosure provide a non-transitory computer-readable storage medium storing computer instructions that enable a computer to implement the network probing method as described in the first aspect when executed.

[0009] Fifthly, embodiments of this disclosure provide a computer program product including a computer program that, when executed by a processor, can implement the steps of the network probing method as described in the first aspect.

[0010] The network detection scheme provided in this disclosure, after determining the target cloud network as the detection object based on the network detection request, directly selects the detection start point under the target cloud network. This allows the network detection between the detection start point and the detection end point to better represent the network status of the target cloud network. At the same time, it provides multiple detection methods to better meet the actual needs of network detection between different types of cloud networks under the hybrid cloud network framework. Furthermore, by matching the detection method and constructing the detection data packet according to the detection request, it can comprehensively detect multiple parameters including link connectivity, network latency, packet loss rate, and cloud network working status, thereby improving the comprehensiveness of monitoring and detection of various networks under the hybrid cloud network architecture.

[0011] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0012] Other features, objects, and advantages of this disclosure will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0013] Figure 1 This is an exemplary system architecture to which this disclosure can be applied;

[0014] Figure 2 A flowchart of a network detection method provided in this disclosure embodiment;

[0015] Figure 3 A branch diagram illustrating two different implementation branches for determining the detection starting point, provided in embodiments of this disclosure;

[0016] Figure 4 A branch diagram illustrating two different implementations of constructing probe data packets provided in this embodiment of the disclosure;

[0017] Figure 5 A flowchart illustrating a method for network probing using probe data packets, provided in this embodiment of the disclosure;

[0018] Figure 6 A schematic diagram of an overall architecture provided for an embodiment of this disclosure;

[0019] Figure 7 A schematic diagram of a control plane flow provided in an embodiment of this disclosure;

[0020] Figure 8 This is a schematic diagram of the internal process of the agent provided in the embodiments of this disclosure;

[0021] Figure 9 This is a schematic diagram illustrating the agent issuing Vping commands according to an embodiment of this disclosure;

[0022] Figure 10 This is a schematic diagram of the Vping naming process provided in an embodiment of the present disclosure;

[0023] Figure 11 This is a schematic diagram of an internal alarm mechanism provided in an embodiment of the present disclosure;

[0024] Figure 12a and Figure 12b These are schematic diagrams illustrating alarm information provided by the alarm robot according to embodiments of this disclosure;

[0025] Figure 13 A structural block diagram of a network detection device provided in this disclosure embodiment;

[0026] Figure 14 This is a schematic diagram of the structure of an electronic device suitable for performing a network detection method, provided as an embodiment of the present disclosure. Detailed Implementation

[0027] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding; these should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description. It should be noted that, unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0028] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0029] Figure 1 An exemplary system architecture 100 is shown, in which embodiments of the network probing methods, apparatuses, electronic devices, and computer-readable storage media of this disclosure can be applied.

[0030] like Figure 1 As shown, the system architecture 100 may include terminal devices 101, 102, and 103, a network 104, and a cloud network 105. The network 104 serves as the medium for providing communication links between the terminal devices 101, 102, and 103 and the cloud network 105. The network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables. The cloud network 105 may be constructed from multiple physical servers.

[0031] Users can use terminal devices 101, 102, and 103 to interact with cloud network 105 via network 104 to receive or send messages, etc. Various applications for enabling information communication between the terminal devices 101, 102, and 103 and cloud network 105 can be installed. These applications include network detection applications, task assignment applications, and instant messaging applications.

[0032] Terminal devices 101, 102, and 103 can be either hardware or software. When terminal devices 101, 102, and 103 are hardware, they can be various electronic devices with displays, including but not limited to smartphones, tablets, laptops, and desktop computers. When terminal devices 101, 102, and 103 are software, they can be installed in the electronic devices listed above. They can be implemented as multiple software programs or software modules, or as a single software program or software module, without specific limitations.

[0033] A cloud network 105 typically manifests as a virtual product built from hardware devices. This cloud network 105 can be a single cloud network or it can be constructed from multiple cloud networks of different types (e.g., a hybrid cloud network).

[0034] The cloud network 105 can provide various services through its built-in applications. Taking a network detection application that provides network detection services as an example, when the cloud network 105 runs this application, it can achieve the following: First, it receives network detection requests from terminal devices 101, 102, and 103 through network 104, and determines the target cloud network as the detection object based on the network detection request; then, it determines the detection start point and the detection end point under the target cloud network; next, it determines the target detection method based on the cloud network types to which the detection start point and the detection end point belong; finally, it uses the detection data packets constructed according to the target detection method and satisfying the network detection request to perform network detection on the cloud networks to which the detection start point and the detection end point belong and the communication link between them.

[0035] It should be noted that, in addition to being temporarily obtained from terminal devices 101, 102, and 103 via network 104, network probe requests can also be pre-stored locally on cloud network 105 through various means. Therefore, when cloud network 105 detects that this data is already stored locally (e.g., when it begins processing previously reserved pending network probe tasks), it can choose to directly obtain this data from locally. In this case, the exemplary system architecture 100 may also exclude terminal devices 101, 102, and 103 and network 104.

[0036] The network detection methods provided in the subsequent embodiments of this disclosure are generally executed by the cloud network 105. Specifically, they are typically executed by a network device that is directly connected to the cloud network or acts as a control node under the cloud network. Correspondingly, the network detection device is also generally located in the cloud network 105.

[0037] It should be understood that Figure 1 The number of terminal devices, networks, and cloud networks shown is merely illustrative. Any number of terminal devices, networks, and cloud networks can be included depending on implementation needs.

[0038] Please refer to Figure 2 , Figure 2 A flowchart of a network detection method provided in this disclosure embodiment, wherein process 200 includes the following steps:

[0039] Step 201: Based on the network probe request, determine the target cloud network to be probed;

[0040] This step is intended for the entity performing the network probing method (e.g., Figure 1 The cloud network 105 shown determines the target cloud network as the object of detection based on the received network detection request.

[0041] That is, the network probe request contains at least some information for identifying the probe target, so as to identify the target cloud network from multiple candidate cloud networks based on the relevant information. Specifically, the relevant information can be recorded in a preset field of the network probe request. At the same time, in order to increase security, the content of the field can also be encrypted using a preset encryption method so that only the execution entity with the corresponding decryption means can correctly identify the probe target.

[0042] This information can be the network address, network number, network name, etc. of a cloud network under a hybrid cloud network architecture (such as a public cloud network, private cloud network, local data center, virtual private cloud network, or hybrid cloud network, which can be obtained by mixing at least two of the public cloud network, private cloud network, local data center, and virtual private cloud network). The specific choice can be made flexibly according to the actual situation, and no specific limitation is made here.

[0043] The target cloud network being probed can be either the primary network or a secondary network (also called a subnet) under the primary network. Usually, the cloud network type of the secondary network is the same as that of the primary network. However, in special cases, there may be situations where the cloud network type of the secondary network is different from that of the primary network.

[0044] Step 202: Determine the detection start point and the detection end point within the target cloud network;

[0045] Building upon step 201, this step aims to have the aforementioned executing entity determine a probe starting point that can represent the target cloud network under the target cloud network being probed, and to determine the probe endpoint based on the network probe request. The network address of the probe starting point can be an available network address within the address range corresponding to the target cloud network. For example, in the case of specifically using the Internet Protocol (IP), the probe starting point can correspond to a free IP address within the IP network range corresponding to the target cloud network, that is, using the free IP address as the IP address of the probe starting point. Of course, other methods can also be used.

[0046] Step 203: Determine the target detection method based on the cloud network type to which the detection start point and detection end point belong;

[0047] Based on step 202, this step aims to have the aforementioned executing entity determine the target detection method that can be used to conduct network detection between the two corresponding types of cloud networks, according to the cloud network types to which the detection start point and detection end point belong.

[0048] Considering the various types of cloud networks included in a hybrid cloud network architecture, this disclosure provides multiple network probing methods, including Internet Control Message Protocol (ICMP, used to transmit control messages between IP hosts and routers), Domain Name System (DNS), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP), in order to enable network probing between these different types of cloud networks. The specific method selected can be determined based on the starting and ending points of the actual network probing request, as well as whether the cloud network types to which they belong are the same or whether there are cross-network issues.

[0049] In addition, when the target cloud network being probed is a target secondary network, the target primary network to which the target secondary network belongs can be further determined, so as to determine the target detection method based on the cloud network type of the target primary network and the cloud network type of the cloud network to which the probe endpoint belongs.

[0050] Step 204: Using the probe data packets constructed according to the target probe method and satisfying the network probe request, perform network probe on the cloud networks to which the probe start point and probe end point belong respectively and the communication link between them.

[0051] Building upon step 203, this step aims to have the aforementioned executing entity first construct a probe data packet that meets the requirements of the network probe request according to the target probe method. Then, this probe data packet is used to perform network probes on the cloud networks to which the probe origin and destination belong, as well as the communication link between them. That is, the probe data packet's probe targets not only include the connectivity of the communication link, but also, based on verified connectivity, the specific connectivity status and the operational status of the cloud networks to which the probe origin and destination belong, thereby improving the comprehensiveness of the probe and avoiding abnormal judgments where two cloud networks are malfunctioning but maintain connectivity.

[0052] The network detection method provided in this disclosure, after determining the target cloud network as the detection object based on the network detection request, directly selects a detection starting point under the target cloud network. This allows the network detection between the detection starting point and the detection endpoint to better represent the network status of the target cloud network. At the same time, it provides multiple detection methods to better meet the actual needs of network detection between different types of cloud networks under the hybrid cloud network framework. Furthermore, by matching the detection method and constructing the detection data packet according to the detection request, it can comprehensively detect multiple parameters including link connectivity, network latency, packet loss rate, and cloud network operating status, thereby improving the comprehensiveness of monitoring and detection of various networks under the hybrid cloud network architecture.

[0053] Regarding how to determine the detection starting point under the target cloud network, this embodiment further divides the implementation into two different methods based on whether there are historical detection points under the target cloud network, in order to provide the optimal implementation method as much as possible under various circumstances, such as... Figure 2 The branch diagram shown includes the following branches:

[0054] Branch 1: If no historical probe points exist within the target cloud network, the aforementioned execution entity can determine the target IP network segment corresponding to the target cloud network. Then, based on the idle IPs within the target IP network segment, the starting IP for the probe can be used. Specifically, any idle IP can be used as the starting IP for this probe, or a target idle IP determined according to a certain round-robin or selection algorithm can be used as the starting IP. Here, an idle IP refers to an IP that is not currently in use.

[0055] Branch Two: If a historical probe point exists within the target network cloud, the aforementioned execution entity can determine the operational status of that historical probe point. Then, if it's confirmed that the operational status does not conflict with the probe method required by the network probe request, the historical probe point can be directly used as the probe starting point. Conversely, if its operational status conflicts with the probe method required by the network probe request, the network probe can be initiated without immediately starting, waiting for the historical probe point's operational status to change to a state that does not conflict with the probe method required by the network probe request. Alternatively, an idle IP address can be selected as the probe starting point, following the method in Branch One.

[0056] The historical probe point can include a historical probe start point and a historical probe end point. When the network probe task being performed by the historical probe point does not conflict with the newly received network probe, it is considered that its working status does not conflict with the probe method required by the network probe request. For example, the target probe method corresponding to the network probe task being performed does not conflict with the probe method used by the newly received network probe task.

[0057] This means reusing the same probe point as much as possible to perform multiple network probe tasks, in order to minimize the occupation of IP resources under the target cloud network.

[0058] Regarding how to construct probe data packets that meet the requirements, this embodiment further divides two different implementation methods based on the network characteristics and probe needs of the target cloud network, to provide a matching implementation method in corresponding situations, such as... Figure 3 The branch diagram shown includes the following branches:

[0059] Method 1: When the network probe request requests network quality probe on the target cloud network (i.e., the network that has been previously generated to implement existing services), the aforementioned execution entity will also control that the generated probe data packets do not contain any additional routing information, in order to check whether the routing information of the target cloud network has been correctly configured in the previous configuration information, so as to require that the existing routing parameters be fully used in the data transmission process of the probe data packets, thereby achieving the purpose of network quality probe on the network services provided by the existing network.

[0060] Method 2: When the network probe request requires network availability probe of the target cloud network as an incremental network (i.e., a newly generated or newly created network for implementing incremental services), the aforementioned execution entity will also control the generated probe data packet to additionally add the target routing information required for the network probe item corresponding to the incremental network, so as to verify the availability of the incremental network by adding the target routing information itself without fully configuring the routing information.

[0061] Of course, in addition to differentiating between incremental and existing services based on their usage scenarios, other methods can also be used for differentiation. Based on these differences, the information to be included in the probe data packets described above can be adjusted to match the corresponding scenario requirements. These will not be elaborated on here.

[0062] Based on any of the above embodiments, this embodiment further describes how to specifically utilize the constructed probe data packets for network probing. Figure 4 A flowchart of a method for network probing using probe packets is shown, wherein the process 400 includes the following steps:

[0063] Step 401: Construct a probe data packet that satisfies the network probe request according to the target probe method;

[0064] This section can be found at [link / reference]. Figure 3 The various implementation schemes provided by the embodiments shown will not be repeated here.

[0065] Step 402: Control the detection starting point to send out a detection data packet pointing to the detection endpoint;

[0066] Based on step 401, this step aims to have the aforementioned executing entity control the detection starting point to send a detection data packet to the detection endpoint, that is, the detection data packet is sent from the detection starting point and the destination is the detection endpoint.

[0067] Step 403: In response to the detection starting point receiving response data returned by the detection endpoint, determine that the communication link between the detection starting point and the detection endpoint is connected;

[0068] Based on step 402, this step aims to determine whether the communication link between the probe start point and the probe end point is not connected (i.e., not connected) if the probe start point receives response data returned by the probe end point after sending the probe data packet, and when the response data is not received, the communication link between the probe start point and the probe end point is connected (i.e., connected).

[0069] In other words, connectivity verification only requires checking whether a response data is received, which is the most basic purpose of detection.

[0070] Step 404: Determine the communication packet loss rate and network latency based on the number of lost packets and the reception time corresponding to the response data;

[0071] Having verified connectivity in step 403, this step aims for the aforementioned executing entity to further determine the communication packet loss rate and network latency based on the number of lost packets and reception time corresponding to the response data. The communication packet loss rate corresponds to the ratio of effective information transmission to reception; a lower rate indicates better network quality and less redundant data transmission to ensure the communication target receives complete and effective information. Network latency corresponds to transmission time; a lower rate indicates better network quality and timely message reception by the communication target.

[0072] In other words, the packet loss rate and network latency are obtained by statistical analysis of the number of received response data and the time of receipt.

[0073] Step 405: Based on the data content of the response data and the packet content of the probe data packet, determine the network operating status of the networks to which the probe start point and probe end point belong respectively.

[0074] Based on step 403, this step aims to have the aforementioned executing entity determine the network operating status of the networks to which the probe start point and probe end point belong, respectively, according to the data content of the response data and the packet content of the probe data packet.

[0075] Unlike step 404, which only statistically analyzes the received response data in terms of the number of received packets and the reception time to obtain the communication packet loss rate and network latency, this step performs in-depth content verification on the packet content of the probe data packet and the data content of the response data. This is used to determine whether the probe start point has correctly sent the probe data packet as required and whether the probe end point has responded correctly in the response data based on the packet content sent by the probe data packet. Based on the judgment results, the network working status of the networks to which the probe start point and probe end point belong is determined, so as to avoid the abnormal judgment that the two cloud networks are working abnormally but can still maintain connectivity.

[0076] To enhance understanding, this disclosure also provides a specific implementation scheme based on a particular application scenario. Please refer to:

[0077] For ease of understanding, the full names and Chinese meanings of some specialized English abbreviations used in the description of this embodiment will be explained below:

[0078] VSA (Vnet Smart Analyzer): Abbreviation for network detection service, which has functions such as network detection, data aggregation and analysis, and alarms;

[0079] VSA-Master: Network Probe Master (Master Node, or Control Node), mainly acts as an HTTP server (Web server), manages probe agents (nodes, or proxies), and schedules pinglists (the concrete manifestation of probe flows);

[0080] VSA-Agent: Network Probe Agent, responsible for sending and receiving probe packets, counting packet loss data, and pushing NSQ (Real-time Distributed Message Passing Platform);

[0081] Alarmd: The network detection and alarm module is responsible for synchronizing alarm policies, pulling InfluxDB (time series database) data for calculation, and issuing alarms through the robot;

[0082] VPing: Virtual machine network connectivity detection. The probe packet is sent directly from the agent to the CN (top-level domain). The returned result determines whether the network is accessible and the network quality.

[0083] Pinglist: The specific manifestation of the probe flow. Each pinglist contains various parameters of the probe data packet, and the agent sends packets based on the pinglist.

[0084] ETCD: Global ETCD for network probing, storing probing agents and ping lists;

[0085] NSQ (Real-time Distributed Messaging Platform): VNTP component, message queue, probe agent pushes probe results to NSQ;

[0086] InfluxDB (Time Series Database): A VNTP (Virtual Network Transmission Protocol) component. The VNTP time series database stores the results pushed by the agent into InfluxDB.

[0087] The overall network architecture of the solution provided in this embodiment is as follows: Figure 6 As shown, the VSA, as the control core of network probing, mainly has three functions:

[0088] 1. HTTP server

[0089] It provides an API (Application Programming Interface) to the console (configuration interface, typically used to configure routing information) and is responsible for controlling the probe instances.

[0090] 2. Scheduler, watch ETCD, listen for online / offline events of the probe agent.

[0091] When an agent comes online, it processes probe flows (data flows) in the same region (physical area) as the agent that are in an unbound state (literally translated as: not unbound, usually understood as incomplete or not offline). The probe flow is then bound to the agent, and the online agent executes the probe task.

[0092] When an agent goes offline, the probe flow bound to that agent is processed, and the probe flow is reassigned to other probe agents in that region. If the offline agent has other probe agents in the same az (areas that can provide services in a specific region), the probe agents in the same az are selected first.

[0093] 3. PinglistManager (ping command list controller) is responsible for managing the pinglist.

[0094] When a probe flow is created, updated, or deleted, the pinglist is assembled, put into ETCD, and handed over to the corresponding agent for processing.

[0095] The main functions of the Agent are:

[0096] 1. Upon going online, the agent registers with the VSA via ETCD, indicating that the agent is available and can accept probe tasks. The status of the agent information with the VSA is maintained by renewing the lease. If the agent goes offline and the lease is not renewed, the ETCD key will be deleted, the VSA will delete the agent, migrate the probe tasks on the agent, and will not assign new probe tasks to the agent.

[0097] 2. Watch ETCD, listen to the pinglist, and when there is a pinglist that belongs to you, process and generate a probe task and execute it to start sending probe packets;

[0098] 3. Generate SendMetric and RecvMetric information based on the sent and received packets, and generate a pb message for pushing VNTP based on SendMetric and RecvMetric, and push it to NSQ;

[0099] 4. Added HTTP server capability, providing VPing functionality and supporting virtual machine network detection.

[0100] The aforementioned functional components will execute according to the control plane flow described below, and a general flowchart is shown in the figure. Figure 7 As shown:

[0101] 1. After the probe agent starts, it puts its own information to ETCD to register. ETCD key: / v1 / VSA / probe / probe_agent / {agent_IP};

[0102] 2. VSA watches the agent's registration information from ETCD and processes probe flows where the agent's region status is unbound;

[0103] 3. VSA inserts the information of the newly launched agent into the database;

[0104] 4. Users create probe instances via the console;

[0105] 5. The console calls the VSA API to create a probe instance;

[0106] 6. VSA automatically assigns probe IPs or calls Neutron (Virtual Network Service) to create probe ports based on user-specified IPs. If an available probe port exists, it will be used first. If there are not enough probe ports, a new one will be created. Then, a DNS resolution request is constructed using the probe domain name, and a probe flow is generated and stored in the database. A probe flow is uniquely identified using a 5-tuple. The same probe flow is not allowed to exist in the same VPC (Virtual Private Cloud).

[0107] 7. VSA assembles a pinglist based on the probe flow and puts it into ETCD. ETCD key: / v1 / VSA / probe / agent_IP / {agent_IP} / instance / {instance_id} / pinglist / {flow_id};

[0108] 8. The agent watches the pinglist assigned to it from ETCD and generates probe tasks based on the pinglist;

[0109] 9. The agent worker executes the probe task, periodically encapsulates and sends probe packets to the specified probe target IP, and assembles and pushes VNTP pb messages based on the response packets;

[0110] 10. The agent pushes the probe results (pb message) to VNTP;

[0111] 11. After processing the messages, VNTP stores them in InfluxDB. Simultaneously, it obtains packet loss rate, latency, and DNS resolution success rate information through processing and pushes this information to the BCM (Bureau Management Module).

[0112] 12. By configuring alarm policies in the BCM, users can receive alarms in a timely manner and achieve timely perception of the detected service quality.

[0113] The internal execution flow of the probe agent can be found in [link to relevant documentation]. Figure 8 The diagram shown is as follows:

[0114] Among them, flows: map (graph), which stores the probe tasks generated based on pinglist;

[0115] SendChan: channel, used for worker and stats communication, transmitted by SendMetric;

[0116] RecvChan: channel used for communication between receiver and stats, transmitted by RecvMetric;

[0117] recvCache: a map that stores FlowMetric information obtained from RecvMetric, with the key being SessionId, consisting of a six-tuple;

[0118] NSQ: Message Queue, used to communicate with VNTP and push pb messages to VNTP.

[0119] 1. The agent iterates through the flows once per second, hashes the probe tasks that need to be executed in that second to different workers, and then assigns them to the workers for execution;

[0120] 2. The worker assembles and sends probe packets according to the probe task, and generates SendMetric to send to SendChan;

[0121] 3. After receiving the probe response packet, the receiver organizes the packet information to generate a RecvMetric, sends it to the RecvChan, and parses the response packet;

[0122] 4. After receiving RecvMetric from RecvChan, stats concatenates the SessionId with RecvMetric and updates FlowMetric. If it is the first time RecvMetric is received, it is created.

[0123] 5. After receiving SendMetric from SendChan, stats checks whether the current time has exceeded the timeout period. If it has, it uses SessionId to look up the FlowMetric corresponding to the probe task, assembles StatMessage and delivers it to batcher; otherwise, it waits for the timeout to expire.

[0124] 6. The batcher delivers StatMessages to NSQ_pusher in batches;

[0125] 7. NSQ_pusher assembles the PB Message based on StatMessage, publishes it to NSQ, and is consumed and processed by VNTP.

[0126] When users create virtual machines (VMs), especially when creating hundreds or thousands of VMs in batches, they often end up delivering VMs that are not connected to the network. Because there are so many VMs, it's impossible to identify which VM is not working immediately. VPing can check VM connectivity after NOVA (the tool used to create virtual machines) has finished creating the VMs, thus avoiding the delivery of VMs that are not connected to the network.

[0127] After the virtual machine is largely created, at a certain point in time (often an empirical value), the VPing interface is called to check if the virtual machine is connected to the network. If the check result is not available, the process is retried until the maximum number of retries is reached. If so, the virtual machine is determined to be unavailable, the creation fails, and the virtual machine is rolled back.

[0128] The currently agreed VPing results and NOVA-compute responses are as follows:

[0129] Service error, network error, incorrect request parameters, etc.: code! = 200. To avoid this, if this error occurs even once out of all retries, the virtual machine is considered created successfully. This also prevents virtual machine creation failures caused by VPing service errors.

[0130] Service is normal, but the probe fails: code==200, ReceivePkts==0. In this case, continue to retry Vping until the probe result is successful. If the probe fails after the maximum number of retries, the virtual machine is considered to have failed and is rolled back.

[0131] Service is normal, detection successful: code == 200, ReceivePkts > 0. If this occurs even once, the virtual machine is considered to be connected to the network and can be delivered to the user.

[0132] Because network probing uses an asynchronous architecture, the pinglist is distributed using ETCD. After the master distributes the pinglist, the agent processes it asynchronously. However, VPing requires a synchronous interface; after calling it, the system waits for the probe results to return. Therefore, the original asynchronous probing architecture is not suitable for implementing VPing functionality. Considering all factors, VPing is implemented on the probe agent. The probe agent also provides HTTP server functionality, allowing direct calls to the interfaces on the probe agent using VPing (see [link to relevant documentation]). Figure 9 (See the schematic diagram shown).

[0133] Each region selects several probe agents to handle VPping tasks. These probe agents are connected to a VPN, and NOVA-compute calls the VPping interface through the VPN to distribute the Vping tasks across multiple probe agents, reducing agent load and ensuring that Vping tasks do not interfere with normal network probe tasks, while also guaranteeing the success rate of Vping. (Although load testing results show that a single probe agent can handle the Vping tasks of creating 1,000 virtual machines online without pressure, a multi-node approach is still chosen for high availability.)

[0134] Each probe agent is assigned a probe source IP address. The assigned IP address is a public-private segment allocated by SYS. When sending VPing probe packets, the probe agents uniformly use this source IP address.

[0135] In order for CN to send probe packets back to the probe agent, a public route needs to be configured in Neutron. The destination IP is the probe agent's source IP, and the next-hop VTEP is the probe agent's host IP (see [link to Neutron configuration]). Figure 10 (See the schematic diagram shown).

[0136] The agent_server calls the Vping module to issue a Vping task. This task will carry Vping parameters (destination IP, MAC address, VTEP, etc.) and a notifier.

[0137] The deadline in the notifier is the task issuance time plus the specified timeout (usually 1 second). NotifyChan is used to notify the agent_server whether the Vping task has been completed.

[0138] The Vping module uses the Vping parameter six-tuple to generate a session ID, stores the Notifier in recvCache, and sends a Vping packet to the virtual machine of the specified CN.

[0139] After the virtual machine returns a packet, the receiver module generates a RecvMetric, which contains parameters such as the source and destination IP addresses of the received data packet. This RecvMetric is then put into the VPingRecvChan, which is not the same RecvChan used for network probing.

[0140] The Vping module generates a session ID based on the RecvMetric parameter, retrieves the corresponding Notifier from recvCache, performs packet reception statistics, and if the number of received packets equals the number of sent packets, deletes the Notifier from recvCache, closes the NotifyChan in the Notifier, and notifies the agent_server to return immediately; otherwise, the agent_server will return automatically after the timeout period.

[0141] Since the Notifier in recvCache is not deleted after packet loss or timeout, the cleaner will periodically clean up timed-out Notifiers.

[0142] The Vping module includes built-in ICMP and TCP packet templates during initialization. When a Vping task is received, the templates can be modified directly, eliminating the need to repeatedly format data packets and greatly improving efficiency.

[0143] The internal alarm mechanism within the aforementioned overall architecture is detailed in [reference needed]. Figure 11 The diagram shown is as follows:

[0144] 1. The probe agent formats the probe results into a VNTP message and pushes it to NSQ;

[0145] 2. VNTP saverd consumes messages from NSQ for processing;

[0146] 3. Saverd will write the probe data to InfluxDB after processing is complete;

[0147] 4. Create alarm policies using the VSA command line or by calling the interface;

[0148] 5. The VSA master writes the alarm policy into the database;

[0149] 6. The VSA alarm module Alarmd periodically synchronizes the alarm policies in the DB and pulls the probe data from InfluxDB at a 1-minute interval for calculation and statistics. Based on the configured alarm policies, it determines whether the alarm conditions are met. If they are met, an alarm is triggered and the alarm record is written to the DB. If the alarm recovery conditions are met, the alarm recovery action is executed.

[0150] 7. Call the RuLiu interface to push alarm or alarm recovery information to the designated alarm robot.

[0151] The alarm content and format presented by the alarm robot can be found in [reference needed]. Figure 12a and Figure 12b .

[0152] By applying the corresponding program products to network probing products and services monitoring VPC network connection quality, it is possible to support Ping probing of cloud servers, NAT (Network Address Translation) gateways, VPN (Virtual Private Network) gateways, peering connections, leased line gateways, and cloud intelligent networks. This allows for monitoring key indicators such as network connection latency and packet loss rate, providing real-time connection quality awareness and real-time alerts for connection failures. It significantly enhances cloud network monitoring and diagnostic capabilities, enabling targeted probing services while meeting the needs of intelligent cloud users in hybrid cloud network measurement and analysis.

[0153] Further reference Figure 13 As an implementation of the methods shown in the above figures, this disclosure provides an embodiment of a network detection device, which is similar to... Figure 2 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0154] like Figure 13 As shown, the network detection device 1300 of this embodiment may include: a detection target determination unit 1301, a detection start point and end point determination unit 1302, a target detection method determination unit 1303, and a network detection unit 1304. The detection target determination unit 1301 is configured to determine a target cloud network as the detection target based on a network detection request; the detection start point and end point determination unit 1302 is configured to determine a detection start point and a detection end point within the target cloud network; the target detection method determination unit 1303 is configured to determine a target detection method based on the cloud network types to which the detection start point and the detection end point belong; and the network detection unit 1304 is configured to use detection data packets constructed according to the target detection method and satisfying the network detection request to perform network detection on the cloud networks to which the detection start point and the detection end point belong, and the communication link between them.

[0155] In this embodiment, the specific processing and technical effects of the following components in the network detection device 1300—namely, the detection target determination unit 1301, the detection start and end point determination unit 1302, the target detection method determination unit 1303, and the network detection unit 1304—can be found by referring to [reference needed]. Figure 2The relevant descriptions of steps 201-203 in the corresponding embodiments will not be repeated here.

[0156] In some optional implementations of this embodiment, the detection start point and end point determination unit 1302 includes a detection start point determination subunit configured to determine the detection start point under the target cloud network. The detection start point determination subunit can be further configured to:

[0157] In response to the absence of historical probe points under the target cloud network, the target Internet Protocol (IP) network segment corresponding to the target cloud network is determined; where historical probe points include the historical probe start point and the historical probe end point;

[0158] The starting IP address is selected from the available IP addresses within the target IP network segment.

[0159] In some optional implementations of this embodiment, the detection start point and end point determination unit 1302 includes a detection start point determination subunit configured to determine the detection start point under the target cloud network. The detection start point determination subunit can be further configured to:

[0160] In response to the existence of historical detection points under the target network cloud network, determine the working status of the historical detection points;

[0161] The detection method does not conflict with the working status and network detection request requirements, and historical detection points are used as the starting point for detection.

[0162] In some optional implementations of this embodiment, in response to the target cloud network being probed being a target secondary network, the network probe device 1300 may further include:

[0163] The target primary network determination unit is configured to determine the target primary network to which the target secondary network belongs;

[0164] Correspondingly, the target detection method determination unit 1303 can be further configured as follows:

[0165] The target detection method is determined based on the cloud network type of the target primary network and the cloud network type of the detection endpoint.

[0166] In some optional implementations of this embodiment, the target detection method includes any one of the following:

[0167] Control Message Protocol, Domain Name System, Transmission Control Protocol, User Data Packet Protocol.

[0168] In some optional implementations of this embodiment, the target cloud network includes at least one of the following:

[0169] Public cloud network, private cloud network, local data center, virtual private cloud network, hybrid cloud network; wherein, the hybrid cloud network is obtained by mixing at least two of the public cloud network, private cloud network, local data center and virtual private cloud network.

[0170] In some optional implementations of this embodiment, the network detection unit 1304 includes a detection data packet construction subunit configured to construct detection data packets that satisfy the network detection request according to the target detection method. The detection data packet construction subunit can be further configured to:

[0171] In response to a network probing request, network quality probing is performed on the target cloud network, which is an existing network, and the probing data packets are controlled to not contain routing information.

[0172] In response to a network probe request, the system requests network availability probes on the target cloud network, which is an incremental network, and controls the probe data packets to include the target routing information required for the network probe items corresponding to the incremental network.

[0173] In some optional implementations of this embodiment, the network detection unit 1304 is further configured to:

[0174] Construct probe data packets that satisfy network probe requests according to target probe methods;

[0175] Control the starting point of the probe to send out probe data packets pointing to the end point of the probe;

[0176] In response to the detection starting point receiving response data returned by the detection endpoint, it is determined that the communication link between the detection starting point and the detection endpoint is connected;

[0177] The communication packet loss rate and network latency are determined based on the number of lost packets and the reception time corresponding to the response data.

[0178] Based on the data content of the response data and the packet content of the probe data packet, determine the network operating status of the networks to which the probe start point and probe end point belong respectively.

[0179] This embodiment exists as a device embodiment corresponding to the above method embodiment. The network detection device provided in this embodiment, after determining the target cloud network as the detection object according to the network detection request, directly selects the detection starting point under the target cloud network, so that the network detection between the detection starting point and the detection ending point can better represent the network status of the target cloud network. At the same time, it also provides multiple detection methods to better meet the actual needs of network detection between different types of cloud networks under the hybrid cloud network framework. Furthermore, by matching the detection method and constructing the detection data packet according to the detection request, it can comprehensively detect multiple parameters including link connectivity, network latency, packet loss rate, and cloud network working status, thereby improving the comprehensiveness of monitoring and detection of various networks under the hybrid cloud network architecture.

[0180] According to embodiments of this disclosure, this disclosure also provides an electronic device, the electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to implement the network detection method described in any of the above embodiments when executed.

[0181] According to embodiments of this disclosure, this disclosure also provides a readable storage medium storing computer instructions that enable a computer to implement the network detection method described in any of the above embodiments when executed.

[0182] According to embodiments of this disclosure, this disclosure also provides a computer program product that, when executed by a processor, can implement the network detection method described in any of the above embodiments.

[0183] Figure 14 A schematic block diagram of an example electronic device 1400 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0184] like Figure 14As shown, device 1400 includes a computing unit 1401, which can perform various appropriate actions and processes according to a computer program stored in read-only memory (ROM) 1402 or a computer program loaded from storage unit 1408 into random access memory (RAM) 1403. The RAM 1403 may also store various programs and data required for the operation of device 1400. The computing unit 1401, ROM 1402, and RAM 1403 are interconnected via bus 1404. Input / output (I / O) interface 1405 is also connected to bus 1404.

[0185] Multiple components in device 1400 are connected to I / O interface 1405, including: input unit 1406, such as a keyboard, mouse, etc.; output unit 1407, such as various types of displays, speakers, etc.; storage unit 1408, such as a disk, optical disk, etc.; and communication unit 1409, such as a network card, modem, wireless transceiver, etc. Communication unit 1409 allows device 1400 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0186] The computing unit 1401 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 1401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 1401 performs the various methods and processes described above, such as network probing methods. For example, in some embodiments, the network probing method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 1408. In some embodiments, part or all of the computer program may be loaded and / or installed on device 1400 via ROM 1402 and / or communication unit 1409. When the computer program is loaded into RAM 1403 and executed by the computing unit 1401, one or more steps of the network probing method described above may be performed. Alternatively, in other embodiments, the computing unit 1401 may be configured to perform network probing methods by any other suitable means (e.g., by means of firmware).

[0187] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0188] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0189] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0190] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0191] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0192] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and Virtual Private Server (VPS) services, such as high management difficulty and weak business scalability.

[0193] According to the technical solution of this disclosure, after determining the target cloud network as the object of detection based on the network detection request, the detection starting point is directly selected under the target cloud network. This allows the network detection between the detection starting point and the detection endpoint to better represent the network status of the target cloud network. At the same time, multiple detection methods are provided to better meet the actual needs of network detection between different types of cloud networks under the hybrid cloud network framework. Furthermore, the detection data packets constructed according to the matching detection method and the detection request can comprehensively detect multiple parameters, including link connectivity, network latency, packet loss rate, and cloud network working status, thereby improving the comprehensiveness of monitoring and detection of various networks under the hybrid cloud network architecture.

[0194] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0195] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A network detection method, comprising: determining a target cloud network as a detection object according to a network detection request, the target cloud network comprising a hybrid cloud network, the hybrid cloud network being obtained by mixing at least two of a public cloud network, a private cloud network, a local data center and a virtual private cloud network; determining a detection starting point under the target cloud network, and determining a detection ending point, the determining the detection starting point under the target cloud network comprising: in response to a historical detection point existing under the target cloud network, determining a working state of the historical detection point; in response to the working state not conflicting with a detection mode required by the network detection request, taking the historical detection point as the detection starting point; determining a target detection mode according to cloud network types to which the detection starting point and the detection ending point respectively belong, wherein the target detection mode can be used for network detection between the cloud network types to which the detection starting point and the detection ending point respectively belong; performing network detection on cloud networks to which the detection starting point and the detection ending point respectively belong and a communication link between the two cloud networks by using detection data packets satisfying the network detection request and constructed according to the target detection mode, the detection data packets comprising a connectivity of the communication link and working states of the cloud networks to which the detection starting point and the detection ending point respectively belong.

2. The method of claim 1, wherein, the determining the detection starting point under the target cloud network comprises: in response to no historical detection point existing under the target cloud network, determining a target Internet Protocol (IP) network segment corresponding to the target cloud network, wherein the historical detection point comprises a historical detection starting point and a historical detection ending point; based on a free IP in the target IP network segment, taking an IP at the detection starting point as a starting IP.

3. The method of claim 1, wherein, in response to the target cloud network as a target secondary network, further comprising: determining a target primary network to which the target secondary network belongs; correspondingly, the determining the target detection mode according to cloud network types to which the detection starting point and the detection ending point respectively belong comprises: determining the target detection mode according to a cloud network type of the target primary network and a cloud network type of a cloud network to which the detection ending point belongs.

4. The method of claim 1, wherein, the target detection mode comprises any one of the following: a control message protocol, a domain name system, a transmission control protocol, and a user data packet protocol.

5. The method of claim 1, wherein, the constructing the detection data packets satisfying the network detection request according to the target detection mode comprises: in response to the network detection request requiring network quality detection on the target cloud network as a stock network, controlling the detection data packets to not contain routing information; in response to the network detection request requiring network availability detection on the target cloud network as an incremental network, controlling the detection data packets to contain target routing information required by a network detection item corresponding to the incremental network.

6. The method according to any one of claims 1 to 5, wherein, the performing the network detection on the cloud networks to which the detection starting point and the detection ending point respectively belong and the communication link between the two cloud networks by using the detection data packets satisfying the network detection request and constructed according to the target detection mode comprises: Construct a probe data packet that satisfies the network probe request according to the target probe method described above; Control the detection starting point to send a detection data packet pointing to the detection endpoint; In response to the detection starting point receiving response data returned by the detection endpoint, it is determined that the communication link between the detection starting point and the detection endpoint is connected; Based on the number of lost packets and the reception time corresponding to the response data, the communication packet loss rate and network latency are determined; Based on the data content of the response data and the packet content of the probe data packet, the network operating status of the networks to which the probe start point and the probe end point belong are determined.

7. A network detection device, comprising: The detection target determination unit is configured to determine the target cloud network as the detection target based on the network detection request. The target cloud network includes a hybrid cloud network, which is obtained by mixing at least two of the following: public cloud network, private cloud network, local data center and virtual private cloud network. The detection start point and end point determination unit is configured to determine the detection start point and the detection end point under the target cloud network. The detection start point and end point determination unit includes a detection start point determination subunit configured to determine the detection start point under the target cloud network. The detection start point determination subunit is further configured to: determine the working status of the historical detection point in response to the existence of historical detection points under the target cloud network. In response to the fact that the working state does not conflict with the detection method required by the network detection request, the historical detection point is used as the detection starting point; The target detection method determination unit is configured to determine the target detection method based on the cloud network types to which the detection start point and the detection end point belong, wherein the target detection method can be used to perform network detection between the cloud network types to which the detection start point and the detection end point belong; The network detection unit is configured to use a detection data packet constructed according to the target detection method and satisfying the network detection request to perform network detection on the cloud networks to which the detection start point and the detection end point belong, and the communication link between them. The detection objects of the detection data packet include the connectivity of the communication link and the working status of the cloud networks to which the detection start point and the detection end point belong.

8. The apparatus of claim 7, wherein, The detection start point and end point determination unit includes a detection start point determination subunit configured to determine the detection start point under the target cloud network, and the detection start point determination subunit is further configured to: In response to the absence of historical probe points under the target cloud network, a target Internet Protocol (IP) network segment corresponding to the target cloud network is determined; wherein, the historical probe points include a historical probe start point and a historical probe end point; The idle IP address in the target Internet Protocol (IP) segment is used as the starting IP address for the probe.

9. The apparatus of claim 7, wherein, In response to the target cloud network being the object of the probe being a target secondary network, the method further includes: The target primary network determination unit is configured to determine the target primary network to which the target secondary network belongs; Correspondingly, the target detection method determination unit is further configured to: The target detection method is determined based on the cloud network type of the target primary network and the cloud network type of the detection endpoint.

10. The apparatus of claim 7, wherein, The target detection method includes any one of the following: Control Message Protocol, Domain Name System, Transmission Control Protocol, User Data Packet Protocol.

11. The apparatus of claim 7, wherein, The network detection unit includes a probe data packet construction subunit configured to construct probe data packets that satisfy the network detection request according to the target detection method, and the probe data packet construction subunit is further configured to: In response to the network probing request to perform network quality probing on the target cloud network, which is an existing network, the probe data packet is controlled to not contain routing information. In response to the network probe request requiring network availability probe of the target cloud network as an incremental network, the probe data packet is controlled to include the target routing information required for the network probe item corresponding to the incremental network.

12. The apparatus of any one of claims 7-11, wherein, The network detection unit is further configured to: Construct a probe data packet that satisfies the network probe request according to the target probe method described above; Control the detection starting point to send a detection data packet pointing to the detection endpoint; In response to the detection starting point receiving response data returned by the detection endpoint, it is determined that the communication link between the detection starting point and the detection endpoint is connected; Based on the number of lost packets and the reception time corresponding to the response data, the communication packet loss rate and network latency are determined; Based on the data content of the response data and the packet content of the probe data packet, the network operating status of the networks to which the probe start point and the probe end point belong are determined.

13. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the network probing method according to any one of claims 1-6.

14. A non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the network detection method according to any one of claims 1-6.

15. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the network detection method according to any one of claims 1-6.

Images