Connection detection method, apparatus, device, and readable storage medium

Abstract

This application provides a connection detection method, apparatus, device, and readable storage medium. The method includes: acquiring connection detection task information, which includes M first identifiers, N second identifiers, and target parameter information. The first identifiers are identifiers of source-side devices in a source-side device set, and the second identifiers are identifiers of target-side devices in a target-side device set; constructing a connection detection command for a source-side device set based on the connection detection task information; simulating login to the source-side device set based on the device information of the source-side device set to send the connection detection command to the source-side device set; receiving the echo result sent by the source-side device set based on the connection detection command; and analyzing the echo result based on the device information of the source-side device set to obtain a connection detection analysis result.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a connection detection method, apparatus, device, and readable storage medium. Background Technology

[0002] Starting with the fourth-generation (4G) mobile communication era, the core network links evolved from No.7 signaling to a full Internet Protocol (IP) architecture. The network element nodes gradually shifted from a traditional tree-like network to a full-mesh network, significantly increasing the complexity of the links between network nodes. Taking the 4G Evolved Packet Core (EPC) as an example, any two Serving Gateways (SGWs) and the PDN... gateway Signaling interactions between PDN Gateways (PGWs) can occur via the S5 interface (based on the IP protocol stack). In the 5G core network architecture, all control plane network elements interoperate using a Service-Based Interface (SBI). Signaling interactions can occur between any two network elements within the Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Unified Data Management (UDM), and Network Repository Function (NRF). An anomaly in any of these link relationships can potentially impact the overall network availability. Therefore, network connectivity detection for these network elements is crucial.

[0003] Currently, network connectivity testing methods can be broadly divided into two types: manual testing and automatic testing by network element devices. However, manual testing is time-consuming and cannot adapt to the testing of a large number of links, while automatic testing by network element devices is performed automatically by machines, and humans can only passively view the results, which is less flexible. Summary of the Invention

[0004] This application provides a connection detection method, apparatus, device, and readable storage medium, which can solve the technical problems of long manual detection time and poor flexibility of automatic detection in related technologies, enabling users to flexibly, on demand, and quickly perform large-scale network connection detection.

[0005] In a first aspect, embodiments of this application provide a connection detection method, the method comprising:

[0006] Obtain connection detection task information, which includes M first identifier information, N second identifier information, and target parameter information. The first identifier information is the identifier information of the source-side devices in the source-side device set, the second identifier information is the identifier information of the target-side devices in the target-side device set, and the target parameter information is used to implement the connection detection task. M and N are both positive integers.

[0007] Based on the connection detection task information, a connection detection instruction for the source-side device set is constructed. The connection detection instruction is used by the source-side device set to detect the network connectivity between the source-side device set and the target-side device set.

[0008] Based on the device information of the source-side device set, a simulated login to the source-side device set is performed to send the connection detection command to the source-side device set. The device information of the source-side device set is obtained based on the M first identifier information.

[0009] Receive the echo result sent by the source-side device set based on the connection detection command;

[0010] Based on the device information of the source-side device set, the echo results are analyzed to obtain connection detection analysis results.

[0011] Secondly, embodiments of this application provide a connection detection device, the device comprising:

[0012] The acquisition module is used to acquire connection detection task information, which includes M first identifier information, N second identifier information and target parameter information. The first identifier information is the identifier information of the source-side devices in the source-side device set, the second identifier information is the identifier information of the target-side devices in the target-side device set, and the target parameter information is used to implement the connection detection task. M and N are both positive integers.

[0013] The instruction generation module is used to construct a connection detection instruction for the source-side device set based on the connection detection task information. The connection detection instruction is used by the source-side device set to detect the network connectivity between the source-side device set and the target-side device set.

[0014] The instruction channel module is used to simulate logging into the source-side device set based on the device information of the source-side device set, so as to send the connection detection instruction to the source-side device set. The device information of the source-side device set is obtained based on the M first identification information; and to receive the echo result sent by the source-side device set based on the connection detection instruction.

[0015] The result analysis module is used to analyze the displayed results based on the device information of the source-side device set to obtain the connection detection analysis results.

[0016] Thirdly, embodiments of this application provide an electronic device, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, it implements the steps of the connection detection method as described in the first aspect.

[0017] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the connection detection method as described in the first aspect.

[0018] Fifthly, embodiments of this application provide a computer program product including computer instructions that, when executed by a processor, implement the steps of the connection detection method as described in the first aspect.

[0019] In this embodiment, by acquiring connection detection task information, which includes M first identifiers, N second identifiers, and target parameter information, the first identifiers are identifiers of source-side devices in the source-side device set, the second identifiers are identifiers of target-side devices in the target-side device set, and the target parameter information is used to implement the connection detection task, where M and N are both positive integers; based on the connection detection task information, a connection detection instruction for the source-side device set is constructed, which is used by the source-side device set to detect network connectivity with the target-side device set; based on the device information of the source-side device set, a simulated login to the source-side device set is performed to send the connection detection instruction to the source-side device set, where the device information is obtained based on the M first identifiers; the echo result sent by the source-side device set based on the connection detection instruction is received; and based on the device information of the source-side device set, the echo result is analyzed to obtain a connection detection analysis result. This allows for the automatic execution of network connectivity testing tasks, addressing the technical problem of low efficiency in manual network connectivity testing. Furthermore, by setting connectivity testing task information, users can independently specify one or more source-side and target-side devices to be tested, and independently select the target parameter information for implementing the connectivity testing task. This addresses the technical problem of inflexible use of automatic testing in related technologies, enabling users to flexibly, on demand, and quickly conduct large-scale network connectivity testing. Attached Figure Description

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

[0021] Figure 1 This is a flowchart of a connection detection method provided in an embodiment of this application;

[0022] Figure 2 This is a flowchart of the instruction channel module;

[0023] Figure 3 This is a user interface diagram of the connection detection method provided in the embodiments of this application;

[0024] Figure 4 This is a system architecture diagram of a connection detection device provided in an embodiment of this application;

[0025] Figure 5 This is a structural diagram of a connection detection device provided in an embodiment of this application;

[0026] Figure 6 This is a structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

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

[0028] In network element link relationships, any anomaly in any link pair can potentially impact the overall network availability. Unlike connection-oriented No.7 signaling, the IP protocol itself does not maintain link state. Therefore, it's impossible to monitor and manage link operation status in the network based solely on the IP protocol. End-to-end connection state awareness requires higher-layer protocols built on top of IP. Typical connection probe protocols suitable for manual link detection include Internet Control Controllers. messageThe Internet Control Message Protocol (ICMP) is used as a protocol, such as the ping command used daily. At the same time, connection detection of different protocol layers can also be performed by manually simulating the Transmission Control Protocol (TCP) three-way handshake and the IP-based Group of Protocols (GTP) echo request.

[0029] Taking a connection detection scenario based on the ICMP protocol as an example, the sending end initiates an ICMP request message (Echo Request). After receiving the request message, the receiving end replies with an ICMP response message (Echo Reply). After receiving the ICMP response, the sending end confirms the uplink and downlink status and records the latency information.

[0030] Currently, network connectivity testing methods can be broadly categorized into two types: manual testing and automatic testing by network element devices.

[0031] To obtain the desired link status data on demand, maintenance personnel typically need to manually perform some operations, namely, manually checking the network connectivity status. The overall operation process can be summarized into the following five steps:

[0032] 1) Determine the login IP address of the source server to be tested for link detection, as well as the login username and password;

[0033] 2) Determine the source / destination interfaces to be tested for link detection, and the corresponding IP addresses of the interfaces;

[0034] 3) Determine the network protocol (such as ICMP, GTP, TCP, etc.) used for link detection, and determine the detection command to be used in conjunction with the product model of the source-side device;

[0035] 4) Log in to the source server and issue a detection command;

[0036] 5) Based on the information returned by the instruction, determine the link detection result and record the detection data (such as latency, packet loss rate, latency jitter, etc.).

[0037] However, this solution has the following technical problems:

[0038] 1) A single link detection takes a long time. A complete link detection operation involves five steps. Even if each step takes an average of 0.5 minutes, the total time is 2.5 minutes.

[0039] 2) For batch link testing of a large number of links, the manual operation steps of logging into each device, confirming each instruction, issuing each command, and confirming each result are not applicable to the testing of a large number of links.

[0040] Taking a 5G core network in a major city of a certain operator as an example, the network contains approximately 10 AMFs, 20 SMFs, 10 CHFs, 10 UDMs, 10 PCFs, and 40 UPFs. Among them, the network element combinations with signaling interaction relationships are: AMF-AMF, SMF-SMF, AMF-SMF, AMF-UDM, SMF-UDM, AMF-PCF, SMF-PCF, SMF-CHF, and SMF-UPF. The A-end and B-end network elements within the combination are fully interconnected. Even without considering cross-provincial links, there are a total of 2035 links between network elements within the province, as shown in Table 1 below.

[0041] Table 1. Link Relationships Between Network Elements

[0042]

[0043] If the detection method of issuing instructions one by one is adopted, taking the estimated time of 2.5 minutes for a single link detection as an example, multiplying it by the total number of links 2035, the total time will exceed 5000 minutes (more than 8 hours).

[0044] Currently, operators can reduce operation time by writing batch scripts. For the same source device and the same source address (e.g., 1.1.1.1), detection commands initiated for different destination addresses (e.g., 1.1.1.2, 1.1.1.3) can have their operation time reduced by writing batch commands. The ping test command is used as an example:

[0045] ping -S 1.1.1.1 1.1.1.2;

[0046] ping -S 1.1.1.1 1.1.1.3;

[0047] ...

[0048] While this method can reduce the time spent on issuing instructions in step 4) of manual testing, it cannot reduce the time spent on other steps. That is, it still requires manual login to network element devices, manual confirmation of interface connection protocols, manual organization of source / target side address information, and manual collection of echo results. The overall time spent on connection testing is still very large.

[0049] Regarding automated connection detection methods for network devices, some network devices support deploying connection detection for specific protocols on the device itself. The main working mechanism is as follows:

[0050] 1) Based on business logic needs, network devices first establish network connections with specific target localities using specific protocols (e.g., TCP, GTP, or Hypertext Transfer Protocol (HTTP) connections).

[0051] 2) For connections where a link relationship has been established, the target link connection status is periodically checked by sending connection probe messages (i.e., heartbeat messages);

[0052] 3) When a failure is detected in the connection detection of a specific target link, the network device will display an alarm message indicating that the link is faulty on its local end, prompting network maintenance personnel to check and confirm the status of the link connection.

[0053] Currently, some equipment manufacturers' network equipment products support the aforementioned connection detection mechanism. Taking one particular device as an example, this device supports periodic detection of HTTP protocol connections. When a connection interruption to a peer local exchange is detected, it outputs an HTTP link failure alarm, such as... Figure 1 As shown.

[0054] While this solution can solve the tedious operations of frequent manual device logins, script writing and issuing commands, it also has the following technical problems:

[0055] 1) The relevant connection detection operations are executed automatically by the machine, and the human can only passively view the results. It is difficult to manually arrange and actively initiate relevant detection work. The detection operations cannot be manually arranged based on actual detection needs, resulting in poor flexibility.

[0056] 2) The relevant connection detection method is limited to a single source-side network element. The detection results can only reflect the results of a single device and cannot reflect the overall network situation.

[0057] 3) The relevant connection detection methods can only return information about link connection failures in the form of alarms. They only record event information of complete connection failure and interruption, and usually do not return data such as link latency and packet loss. There is a lack of information and they cannot reflect network link quality information.

[0058] Based on the limitations of network connectivity detection schemes in related technologies, this application proposes a new connectivity detection method to solve the problems of low efficiency in manual network connectivity detection and inflexibility in the use of inherent automated connectivity detection in devices, enabling users to flexibly, on demand and quickly perform large-scale network connectivity detection.

[0059] See Figure 1 , Figure 1 This is a flowchart of a connection detection method provided in an embodiment of this application, such as... Figure 1 As shown, the method includes the following steps:

[0060] Step 101: Obtain connection detection task information. The connection detection task information includes M first identifier information, N second identifier information, and target parameter information. The first identifier information is the identifier information of the source-side devices in the source-side device set, and the second identifier information is the identifier information of the target-side devices in the target-side device set. The target parameter information is used to implement the connection detection task. M and N are both positive integers.

[0061] Step 102: Based on the connection detection task information, construct a connection detection instruction for the source-side device set. The connection detection instruction is used by the source-side device set to detect the network connectivity with the target-side device set.

[0062] Step 103: Based on the device information of the source-side device set, simulate logging into the source-side device set to send the connection detection command to the source-side device set. The device information of the source-side device set is obtained based on the M first identifier information.

[0063] Step 104: Receive the echo result sent by the source-side device set based on the connection detection command;

[0064] Step 105: Based on the device information of the source-side device set, analyze the echo results to obtain the connection detection analysis results.

[0065] In step 101, the connection detection task information refers to the information required to perform the connection detection task. This connection detection task information may include M first identifiers, N second identifiers, and target parameter information. The first identifiers can be either the device name of the source device or its IP address (i.e., the source IP address). The second identifiers can be either the device name of the target device or its IP address (i.e., the target IP address).

[0066] In some embodiments, both M and N can be greater than 1, meaning that network connection detection between multiple source-side devices and multiple target-side devices can be supported simultaneously, which is suitable for connection detection of a large number of links.

[0067] In some embodiments, the target parameter information may include relevant parameters for implementing the connection detection task, such as interface type, interface protocol type, and detection message parameters. The detection message parameters may include the number of detection packets, the size of the detection packets, the detection packet sending interval, and the detection response waiting time.

[0068] In some embodiments, the connection detection task information may include, but is not limited to: the name information of the source-side device (which can support one or more devices via parameter M), the name information of the target-side device or the target IP address (which can support one or more devices via parameter N), the interface type and interface protocol type used for detection, and detection packet parameters (such as the number of packets sent and the packet interval).

[0069] In some embodiments, the connection detection task information may include, but is not limited to: the name information of the source device, the name information of the target device (or the target IP address), the interface type and protocol used to implement the connection detection task (i.e., the interface protocol type), the IP address type (such as IPv4 or IPv6) to implement the connection detection task, the source interface plane (i.e., the source interface identifier, for the case where the same interface type of the same device contains multiple addresses), the target interface plane (i.e., the target interface identifier), and detection packet parameters (such as the number of detection packets, the size of the detection packets, the detection packet sending interval, the detection waiting response time, etc.).

[0070] In some embodiments, the device can receive connection detection task information sent by other devices. In some embodiments, the connection detection device can provide a user interface for inputting connection detection task information, thereby allowing the user to actively arrange the connection detection task information and improving the flexibility of connection detection.

[0071] Unlike manual connection testing, which requires a series of processes such as collecting source and destination IP addresses, retrieving test command formats, and constructing instructions in advance, this embodiment can receive connection testing task information input by maintenance personnel. Compared with the complex parameters of manual implementation, it can simplify information input.

[0072] In step 102, the connection detection device may include an instruction generation module. This module can automatically and in batches construct connection detection instructions for the source-side device set based on the connection detection task information, thus eliminating the need for manual construction of connection detection instructions one by one.

[0073] The instruction generation module supports JSON data submitted via HTTP POST. Below is a sample JSON file containing the connection detection task information:

[0074] {

[0075] srcNeNameList:[AMF001, SMF001, AMF002],

[0076] dstNeNameList:[AMF002, AMF003, SMF001],

[0077] ifType: "sbiIcmp",

[0078] ipType: "IPv4",

[0079] srcIfPlane: 1,

[0080] dstIfPlane: 2,

[0081] pktNum: 5,

[0082] pktSize: 80,

[0083] timeOutMs: 600,

[0084] intevalMs: 500,

[0085] }

[0086] In some embodiments, the data fields in the connection detection instructions can be filled based on relevant parameters in the connection detection task information to construct connection detection instructions for the source-side device set. The connection detection instructions for the source-side device set can include connection detection instructions for each individual source-side device, and each source-side device can have multiple connection detection instructions. The number of connection detection instructions for each source-side device can be determined based on the number of detection packets, thus enabling batch construction of connection detection instructions for the source-side device set.

[0087] In some embodiments, the connectivity detection device may further include a device information management module, and the instruction generation module may construct a connectivity detection instruction for the source-side device set based on the given connectivity detection task information and the data from the device information management module.

[0088] The device information management module is used to store static data information of network devices in the network device cluster. The static data information may include: device login IP, device login port number, device model, device username and password, and a set of elements containing three data attributes: {interface type, interface IP, interface protocol type}.

[0089] The device information management module can store device information based on a data table format. In some embodiments, the device information may include the following fields:

[0090] Device name, device login IP address, device login port number, device model, login username, login password, <interface type 1> IPv4 address set, <interface type 1> IPv6 address set, <interface type 2> IPv4 address set, <interface type 2> IPv6 address set, <interface type 3> IPv4 address set, <interface type 3> IPv6 address set, etc.

[0091] The table structure and stored data of a typical equipment information management module are shown in Table 2 below.

[0092] Table 2 Equipment Information Storage Table

[0093]

[0094] The input of the equipment information management module can be manually entered. It can receive equipment information data call requests from other modules in the linked detection device, such as the instruction generation module, and correspondingly, it can output the equipment information data called by other modules.

[0095] In some embodiments, the target parameter information includes: the interface type, interface protocol type, and detection message parameters for implementing the connection detection task; step 102 specifically includes:

[0096] Based on the M first identifiers, the interface type, and the interface protocol type, the source IP address of the connection detection task is obtained; and based on the N second identifiers, the target IP address of the connection detection task is obtained.

[0097] Based on the device model information, interface type, and interface protocol type in the device information of the source-side device set, the instruction command format of the connection detection task is determined;

[0098] Based on the detection message parameters, determine the instruction message input parameters for connecting the detection task;

[0099] Based on the source IP address, destination IP address, command format, and command message input parameters, a connection detection command for the source-side device set is constructed.

[0100] In some embodiments, if the first identification information in the connection detection task information is the name information of the source-side device, then the device information management module needs to be invoked to obtain the device information of the source-side device set. The device information of the source-side device set may include the device information of each source-side device. Then, based on the device information of the source-side devices, the source IP address is determined. Obtaining the source IP address of the connection detection task based on the M first identification information, the interface type, and the interface protocol type includes:

[0101] Based on the name information of the source-side device, obtain the device information of the source-side device set, wherein the first identification information is the name information of the source-side device;

[0102] Based on the interface type and interface protocol type, obtain the list of source IP addresses of the corresponding interfaces in the source-side device set;

[0103] Based on the source interface identifier, the source IP address of the connection detection task is determined from the list of source IP addresses.

[0104] After obtaining the connection detection task information, the instruction generation module can query the device information management module based on the source-side device name information carried in the connection detection task information to obtain the device information of each source-side device.

[0105] In some embodiments, if the second identification information in the connection detection task information is the name information of the target-side device, then the device information management module needs to be invoked to obtain the device information of the target-side device set. The device information of the target-side device set may include the device information of each target-side device. Then, based on the device information of the target-side devices, the target IP address is determined. Obtaining the target IP address of the connection detection task based on the N pieces of second identification information includes:

[0106] Based on the name information of the target side device, obtain the device information of the target side device set, wherein the second identification information is the name information of the target side device;

[0107] Based on the interface type and interface protocol type, obtain the target IP address list of the corresponding interface in the target-side device set;

[0108] Based on the target interface identifier, the target IP address of the connection detection task is determined from the list of target IP addresses.

[0109] That is, after the instruction generation module obtains the connection detection task information, it can also query the device information management module based on the name information of the target side device carried in the connection detection task information to obtain the device information of each target side device.

[0110] In this embodiment, based on the information pre-entered by the device information management module, the source-side device name set / target-side device name set can be directly entered during the task information input stage. Detection can be triggered without searching or entering detailed IP address information, simplifying the information query work during the initiation stage of related detection tasks.

[0111] In some embodiments, the instruction generation module can query the source IP address list and target IP address list of the corresponding interface in the device information returned by the device information management module based on the interface type and interface protocol type of the connection detection task carried in the target parameter information. Furthermore, based on the source interface plane and target interface plane carried in the input target parameter information, the module selects the source IP address / target IP address with the corresponding serial number as the data field of the source IP address and target IP address in the connection detection instruction to be constructed.

[0112] Furthermore, based on the device model information, interface type, and interface protocol type in the device information of the source-side device set, the instruction command format of the connection detection task is determined; and based on the detection message parameters, the instruction message input parameters of the connection detection task are determined.

[0113] Accordingly, based on the source IP address, destination IP address, command format, and command message input parameters, a connection detection command for the source-side device set can be constructed, thereby enabling the construction of a connection detection command for a specific source-side device to a specific destination-side device (or destination IP address) combination.

[0114] To construct a connection detection command for a service interface ICMP protocol connection detection task between an AMF device with a source IP address of 10.124.0.3 and an SMF device with a destination IP address of 10.124.0.8, an example of its construction is as follows:

[0115] NGPING: VPNNAME="ChinaMobile_SG", IPTYPE=IPv4, SRCIPV4ADDR="10.124.0.3", PACKETNUM=3, PACKETSIZE=80, INTERVAL=500, TIMEOUT=600, TTL=255,DSTIPV4ADDR="10.124.0.8".

[0116] The input parameters for the instruction message can be: number of packets 3, packet size 80, packet interval 500ms, and waiting timeout interval 600ms.

[0117] After the instruction generation module completes the construction of connection detection instructions for all source-side devices and target-side devices, it can output the source-side device set and the connection detection instructions to be sent to each source-side device.

[0118] This embodiment proposes an automated command construction and generation method. The command generation module can automatically generate connection detection commands on behalf of manual labor based on the input connection detection task information and index pre-entered device information. Specifically, the command generation module receives the connection detection task information input by the maintenance personnel, and automatically constructs connection detection commands in batches based on the input task information set. It can query the device information management module for detailed information of the corresponding source / target device based on the source / target device name information, and complete the connection detection command from a specific source device to a specific target device (or IP address) based on the source / target IP address, command format, and other input parameters. This achieves automatic construction of connection detection commands, eliminating the need for manual command construction one by one.

[0119] In step 103, the connection detection device may further include an instruction channel module. The instruction generation module may output the source-side device set and the connection detection instructions to be sent to each source-side device to the instruction channel module.

[0120] The command channel module can obtain device information for each source-side device in the corresponding source-side device set from the device information management module based on the source-side device set information provided by the command generation module. This information includes login address, port number, username, and password. Based on this device information, the module can simulate logging into each source-side device in the set. In other words, the input information to the command channel module mainly consists of the source-side device set information and connection detection commands output by the command generation module, as well as the device information obtained from the device information management module, such as login address, port number, username, and password.

[0121] In some embodiments, login can be performed serially on each source-side device in the source-side device group. In some embodiments, login can be performed in parallel on each source-side device in the source-side device group. This embodiment eliminates the cumbersome step of manually retrieving device login information required under the manual connection detection scheme.

[0122] In some embodiments, step 103 specifically includes:

[0123] Based on the device information of the source-side device set, different software processes are used to simulate logging into the source-side devices in the source-side device set in parallel, and the software processes correspond one-to-one with the source-side devices.

[0124] When each software process successfully logs into the source device, for each software process, the connection detection command of the source device corresponding to the software process is sequentially sent to the source device.

[0125] The command channel module supports simultaneous login to multiple source-side devices using an asynchronous multi-threaded approach. It issues connection detection commands based on the command generation module's output and receives and records the echo results from the source-side devices. This embodiment eliminates the need for manual login to each network element for command issuance. Compared to the inflexibility of automatic connection detection schemes, the command channel module allows for flexible arrangement of source and target-side devices.

[0126] The command channel module can support the allocation of different source-side devices to different virtual software processes. Each software process corresponds one-to-one with a source-side device and can execute the login, command issuance, and logout operations of their respective source-side devices in parallel. This can avoid the accumulation of waiting time after the previous connection detection command is issued and before the response message is returned, which would cause the program command issuance time to be too long.

[0127] The operation mechanism of the instruction channel module follows the following procedural rules, and its detailed process is as follows: Figure 2 As shown.

[0128] 1) The command channel module divides the connection detection command issuance process into the following sub-processes:

[0129] Source-side device login;

[0130] Connection detection command issued (batch 1);

[0131] Connection detection command issued (batch 2);

[0132] ...

[0133] Connection detection command issued (batch N);

[0134] Log out of source-side device.

[0135] 2) In each sub-process, the execution of different software processes is carried out in parallel and independently.

[0136] 3) Different sub-processes are executed sequentially; the next sub-process will only start after the previous sub-process is completed.

[0137] Correspondingly, the output of the command channel module is the name of the source-side device in the source-side device set involved in the connection detection command issuance, and the echo result of each connection detection command. That is, in step 104, the command channel module receives the echo results sent by the source-side device set based on the connection detection command. The echo results may include network connection parameter information between the source-side device and the target-side device, such as minimum round-trip time (RTT) (ms); average RTT (ms); maximum RTT (ms); number of packets sent; number of packets received; packet loss rate (%), etc.

[0138] This embodiment proposes a method for parallel issuance of connection detection commands across multiple commands and devices. Specifically, the command channel module, based on a multi-threaded concurrency mechanism, allows manual login to multiple source-side devices awaiting connection detection commands in parallel. Based on this parallel command issuance process, command issuance and echo collection are achieved. In detail, different software processes execute their respective login, N batch command issuance, and logout operations in parallel, avoiding the accumulation of waiting time between the issuance of a previous connection detection command and the return of a response message, which would otherwise lead to excessively long command issuance times.

[0139] The connection detection device may also include a result analysis module. In step 105, the result analysis module can analyze the echo results based on the device information of the source-side device set to obtain connection detection analysis results.

[0140] The connection detection and analysis results can indicate whether there is a fault in the connection between the source-side device and the target-side device. The connection detection and analysis results can also include network connectivity analysis parameters between the source-side device and the target-side device, such as connection availability, connection quality factor, and connection quality.

[0141] In some embodiments, network connection parameters such as packet loss rate in the output results can be analyzed based on the device information of the source-side device set to determine whether there is a fault in the connection between the source-side device and the target-side device.

[0142] In some embodiments, step 105 specifically includes:

[0143] Based on the device model information and interface protocol type in the device information of the source-side device set, information extraction rules and result analysis rules are determined.

[0144] Based on the information extraction rules, network connection parameter information is extracted from the echo results;

[0145] Based on the network connection parameter information, the network connection analysis between the source-side device group and the target-side device group is performed using the result analysis rules to obtain the connection detection analysis results.

[0146] The results analysis module can combine the device model information and interface protocol type in the device information of the source-side device set obtained by calling the device information management module with the echo results returned by the instruction channel module, and associate the corresponding data analysis logic of a specific device model. This can greatly simplify the tedious work of manually checking each piece of information in the manual inspection scheme.

[0147] Data analysis logic can be further divided into information extraction rules and result analysis rules.

[0148] Taking the example of the echo result of the ICMP protocol connection test of the service interface on the AMF network element of a certain device model, the echo result can be:

[0149] ---10.87.20.5 ping statistics---

[0150] 3 packet(s) transmitted

[0151] 3 packets(s) received

[0152] 0.00% packet loss

[0153] round-trip min / avg / max=9.324 / 10.320 / 11.520ms

[0154] There are a total of 4 reports

[0155] --- END.

[0156] The results analysis module determines the information extraction rules based on the device model information and interface protocol type. These rules indicate the information fields to be extracted:

[0157] {

[0158] Minimum RTT (ms);

[0159] Average RTT (ms);

[0160] Maximum RTT (ms);

[0161] Number of messages sent;

[0162] Number of messages received;

[0163] Packet loss rate (%)

[0164] }

[0165] Taking the extraction process of the minimum RTT (ms) field in this connection detection scenario as an example, the result analysis module extracts the field value based on the device model information and interface protocol type, matching specific information extraction rules, and following these steps:

[0166] 1) Index and record the original record <last> <5> Line text string;

[0167] 2) Use the <, =, and > characters to split the string obtained in step 1). Assuming the first group is the first element, take the first element from the resulting string array. <2> Group elements;

[0168] 3) Based on the string obtained in step 2), further segment the text string using the < / > characters, and take the first character from the resulting string array. <1> Group elements, used as the field value for the minimum RTT (ms).

[0169] Accordingly, when extracting network connection parameter information from the output results, the network connection analysis between the source-side device in the source-side device group and the target-side device in the target-side device group can be performed based on the network connection parameter information and the result analysis rules to obtain the connection detection analysis results.

[0170] In some embodiments, the network connection parameter information includes the packet loss rate and average round-trip time between the source-side device group and the target-side device group. Based on the network connection parameter information, the network connection analysis between the source-side device group and the target-side device group is performed using the result analysis rules to obtain connection detection analysis results, including at least one of the following:

[0171] The packet loss rate is compared with a first threshold used to evaluate connection availability in the result analysis rules to obtain a first comparison result; based on the first comparison result, the connection availability between the source-side device in the source-side device group and the target-side device in the target-side device group is determined, and the connection detection analysis result includes the connection availability;

[0172] Based on the packet loss rate and average round-trip time, the connection quality factor between the source-side device group and the target-side device group is determined using the calculation method in the result analysis rules. The connection detection analysis results include the connection quality factor.

[0173] The connection quality factor is compared with the second threshold used to evaluate connection quality in the result analysis rules to obtain a second comparison result; based on the second comparison result, the connection quality between the source-side device in the source-side device group and the target-side device in the target-side device group is determined, and the connection detection analysis result includes the connection quality.

[0174] The example shows the output results and extracted network connection parameter information from the ICMP protocol connection test performed on the AMF network element of a certain device model.

[0175] The extracted network connection parameters include packet loss rate and average round-trip time. Based on device model information and interface protocol type, the result analysis module matches specific result analysis rules and provides the connection detection analysis results in the following steps:

[0176] 1) Analyze connection availability based on packet loss rate (%).

[0177] Based on the result analysis rules, a first threshold for judging connection availability can be determined, namely TH1, TH2, and TH3. When the packet loss rate (%) is less than TH1, the output result is that the connection is available; when the packet loss rate (%) is greater than TH1 and less than TH2, the output result is that the connection has slight packet loss; when the packet loss rate (%) is greater than TH2 and less than TH3, the output result is that the connection has moderate packet loss; when the packet loss rate (%) is greater than TH3, the output result is that the connection is unavailable.

[0178] Among them, the thresholds TH1, TH2, and TH3 can be different depending on the device model information and the interface protocol type.

[0179] 2) Analyze connection quality based on packet loss rate (%) and average RTT (ms).

[0180] The results analysis module can determine the calculation method in the results analysis rules based on device model information and interface protocol type, that is, match a specific function formula. This function formula is the connection quality factor Q=f(Loss, RTT). Accordingly, the packet loss rate and average RTT parameters can be input to calculate the connection quality factor. A larger value for Q indicates better connection quality, and vice versa.

[0181] In some embodiments, the functional formula connecting the quality factor Q can be in the following form:

[0182]

[0183] Among them, parameters α and m are two fixed parameters, which are set as needed based on the different actual benchmarks in the connection quality assessment.

[0184] Furthermore, based on the result analysis rules, a second threshold, TH4 and TH5, can be determined to evaluate connection quality. Based on the calculated connection quality factor Q, the result analysis module can provide different connection quality analysis results. For example, when Q is greater than TH4, the output is "excellent connection quality"; when Q is less than TH4 but greater than TH5, the output is "medium connection quality"; and when Q is less than TH5, the output is "poor connection quality".

[0185] The thresholds TH4 and TH5 can be different depending on the device model information and the interface protocol type.

[0186] Correspondingly, the results analysis module can output the extracted network connectivity parameter information and connectivity detection analysis results. The network connectivity parameter information includes, but is not limited to, the following data structures:

[0187] {

[0188] Minimum RTT (ms);

[0189] Average RTT (ms);

[0190] Maximum RTT (ms);

[0191] Number of messages sent;

[0192] Number of messages received;

[0193] Packet loss rate (%)

[0194] }

[0195] The connection detection analysis results include, but are not limited to, the following data structures:

[0196] {

[0197] Connection availability (enumerated values);

[0198] Connect the quality factor Q;

[0199] Connection quality (enumerated values);

[0200] }

[0201] It can output structured data, providing a prerequisite for the result generation module in the subsequent connection detection device to generate visualized results, and can solve the problem of poor readability of the automatic connection detection result output of the device.

[0202] This embodiment proposes an information extraction and analysis method. The result analysis module determines the information extraction rules based on the original data of the displayed results, device model information, and interface protocol type, and extracts information from the displayed results based on the information extraction rules. Based on the extracted network connection parameter information, combined with the device model information and interface protocol type obtained by the device information management module, the pre-entered result analysis rules are matched to automatically perform data analysis and automatically output the connection detection analysis results.

[0203] In some embodiments, the result analysis module can determine the information fields to be extracted, such as minimum RTT (ms), average RTT (ms), maximum RTT (ms), number of sent packets, number of received packets, and packet loss rate (%), based on the acquired device model information and interface protocol type. Based on the acquired device model information and interface protocol type, it matches specific built-in data analysis logic, analyzes connection availability based on the packet loss rate (%), and uses thresholds TH1, TH2, and TH3 to determine the baseline point set in the connection availability assessment. Based on the acquired device model information, interface protocol type, and the input packet loss rate and average RTT parameters, it matches specific function formulas to calculate connection quality. This allows for automatic data reading and analysis, automatically outputting connection detection and analysis results, simplifying the tedious work of manual result checking.

[0204] The result generation module can format and organize the data based on the connection detection and analysis results and the network connection parameter information provided by the result analysis module, and can also support visualization output based on HTTP JSON or Excel spreadsheet files.

[0205] Figure 3 This is a user interface diagram of the connection detection method provided in the embodiments of this application, such as... Figure 3As shown, a user request can initiate a connection detection task from several AMF devices to several SMF devices. After receiving the HTTP JSON data, the user page displays the connection detection and analysis results of the SBI service interface from multiple AMF devices to multiple SMF devices in a table format.

[0206] This application also provides a connection detection device, which may include several component modules, namely an instruction generation module, a device information management module, an instruction channel module, a result analysis module, and a result generation module, as shown in the system architecture diagram below. Figure 4 As shown.

[0207] The system comprises the following modules: Device Information Management Module: This module contains static data information about the devices to be logged in, including: device login IP, device login port number, device model, device username and password, and a set of elements containing three data attributes: {interface type, interface IP, protocol type}. Command Channel Module: This module can simultaneously establish login connections with different peer network devices and issue commands. The login module supports the following communication protocols: TELNET, SSH, HTTP, and SSL. Command Generation Module: Based on given task information and device information, this module automatically generates batch connection detection commands to be issued. Result Analysis Module: Based on the raw data returned by the command channel module, combined with the corresponding device model information obtained from the device information management module, and associated with the corresponding data analysis logic for a specific device model, this module generates raw analysis results for the connectivity and quality of the detected link. Result Generation Module: Based on the analysis results and network connection parameter information provided by the result analysis module, this module formats and organizes the data, and supports output via HTTP JSON or Excel spreadsheets.

[0208] This system allows users to independently specify multiple source and target devices for testing, select the network protocol types to be tested, and set testing parameters such as testing intervals and timeout durations, offering significant flexibility in connection testing. Furthermore, compared to manual device login for connection testing, this embodiment employs automated parallel login to multiple network elements, automatically generates and issues connection testing commands, and automatically collects and analyzes the returned results. This significantly reduces testing time overhead, improves work efficiency, and minimizes occasional errors and oversights in manual analysis. Compared to solutions relying on built-in alarm detection on the device itself, this embodiment utilizes external middleware for batch testing of multiple devices. Testing operations can be initiated manually, offering greater flexibility. Testing devices can cover the entire network, and the generated results are more detailed and comprehensive than alarm-based information.

[0209] The embodiments of this application have significant commercial value. Under an all-IP architecture, the connectionless nature of network protocols and the need to ensure the availability of link connections have long been contradictory. The embodiments of this application can effectively meet the requirement of rapid connection detection under large-scale network architectures, thereby ensuring and improving network quality.

[0210] See Figure 5 , Figure 5 This is a structural diagram of a connection detection device provided in an embodiment of this application, as shown below. Figure 5 As shown, the connection detection device 500 includes:

[0211] The acquisition module 501 is used to acquire connection detection task information, which includes M first identification information, N second identification information and target parameter information. The first identification information is the identification information of the source-side devices in the source-side device group, the second identification information is the identification information of the target-side devices in the target-side device group, and the target parameter information is used to implement the connection detection task. M and N are both positive integers.

[0212] The instruction generation module 502 is used to construct a connection detection instruction for the source-side device set based on the connection detection task information. The connection detection instruction is used by the source-side device set to detect the network connectivity between the source-side device set and the target-side device set.

[0213] The instruction channel module 503 is used to simulate logging into the source-side device set based on the device information of the source-side device set, so as to send the connection detection instruction to the source-side device set, wherein the device information of the source-side device set is obtained based on the M first identification information; and to receive the echo result sent by the source-side device set based on the connection detection instruction.

[0214] The result analysis module 504 is used to analyze the displayed results based on the device information of the source-side device set to obtain the connection detection analysis results.

[0215] Optionally, the target parameter information includes: the interface type, interface protocol type, and detection message parameters for implementing the connection detection task; the instruction generation module 502 is specifically used for:

[0216] Based on the M first identifiers, the interface type, and the interface protocol type, the source IP address of the connection detection task is obtained; and based on the N second identifiers, the target IP address of the connection detection task is obtained.

[0217] Based on the device model information, interface type, and interface protocol type in the device information of the source-side device set, the instruction command format of the connection detection task is determined;

[0218] Based on the detection message parameters, determine the instruction message input parameters for connecting the detection task;

[0219] Based on the source IP address, destination IP address, command format, and command message input parameters, a connection detection command for the source-side device set is constructed.

[0220] Optionally, the instruction generation module 502 is further configured to:

[0221] Based on the name information of the source-side device, obtain the device information of the source-side device set, wherein the first identification information is the name information of the source-side device;

[0222] Based on the interface type and interface protocol type, obtain the list of source IP addresses of the corresponding interfaces in the source-side device set;

[0223] Based on the source interface identifier, the source IP address of the connection detection task is determined from the list of source IP addresses.

[0224] Optionally, the instruction generation module 502 is further configured to:

[0225] Based on the name information of the target side device, obtain the device information of the target side device set, wherein the second identification information is the name information of the target side device;

[0226] Based on the interface type and interface protocol type, obtain the target IP address list of the corresponding interface in the target-side device set;

[0227] Based on the target interface identifier, the target IP address of the connection detection task is determined from the list of target IP addresses.

[0228] Optionally, the instruction channel module 503 is specifically used for:

[0229] Based on the device information of the source-side device set, different software processes are used to simulate logging into the source-side devices in the source-side device set in parallel, and the software processes correspond one-to-one with the source-side devices.

[0230] When each software process successfully logs into the source device, for each software process, the connection detection command of the source device corresponding to the software process is sequentially sent to the source device.

[0231] Optionally, the result analysis module 504 is specifically used for:

[0232] Based on the device model information and interface protocol type in the device information of the source-side device set, information extraction rules and result analysis rules are determined.

[0233] Based on the information extraction rules, network connection parameter information is extracted from the echo results;

[0234] Based on the network connection parameter information, the network connection analysis between the source-side device group and the target-side device group is performed using the result analysis rules to obtain the connection detection analysis results.

[0235] Optionally, the network connection parameter information includes the packet loss rate and average round-trip time between the source-side device and the target-side device, and the result analysis module 504 is further used for at least one of the following:

[0236] The packet loss rate is compared with a first threshold used to evaluate connection availability in the result analysis rules to obtain a first comparison result; based on the first comparison result, the connection availability between the source-side device in the source-side device group and the target-side device in the target-side device group is determined, and the connection detection analysis result includes the connection availability;

[0237] Based on the packet loss rate and average round-trip time, the connection quality factor between the source-side device group and the target-side device group is determined using the calculation method in the result analysis rules. The connection detection analysis results include the connection quality factor.

[0238] The connection quality factor is compared with the second threshold used to evaluate connection quality in the result analysis rules to obtain a second comparison result; based on the second comparison result, the connection quality between the source-side device in the source-side device group and the target-side device in the target-side device group is determined, and the connection detection analysis result includes the connection quality.

[0239] The connection detection device 500 can implement all the processes implemented in the above-described connection detection method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0240] See Figure 6 The figure shows a structural diagram of an electronic device provided in an embodiment of the present invention. Figure 6 As shown, the electronic device 600 includes: a processor 601, a memory 602, a user interface 603, and a bus interface 604.

[0241] Processor 601 is used to read the program from memory 602 and execute the following procedures:

[0242] Obtain connection detection task information, which includes M first identifier information, N second identifier information, and target parameter information. The first identifier information is the identifier information of the source-side devices in the source-side device set, the second identifier information is the identifier information of the target-side devices in the target-side device set, and the target parameter information is used to implement the connection detection task. M and N are both positive integers.

[0243] Based on the connection detection task information, a connection detection instruction for the source-side device set is constructed. The connection detection instruction is used by the source-side device set to detect the network connectivity between the source-side device set and the target-side device set.

[0244] Based on the device information of the source-side device set, a simulated login to the source-side device set is performed to send the connection detection command to the source-side device set. The device information of the source-side device set is obtained based on the M first identifier information.

[0245] Receive the echo result sent by the source-side device set based on the connection detection command;

[0246] Based on the device information of the source-side device set, the echo results are analyzed to obtain connection detection analysis results.

[0247] exist Figure 6 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 601 and memory represented by memory 602 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 604 provides an interface. For different user devices, user interface 603 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0248] The processor 601 is responsible for managing the bus architecture and general processing, while the memory 602 can store the data used by the processor 601 when performing operations.

[0249] In some embodiments, the target parameter information includes: the interface type, interface protocol type, and detection message parameters for implementing the connection detection task; the processor 601 is further configured to:

[0250] Based on the M first identifiers, the interface type, and the interface protocol type, the source IP address of the connection detection task is obtained; and based on the N second identifiers, the target IP address of the connection detection task is obtained.

[0251] Based on the device model information, interface type, and interface protocol type in the device information of the source-side device set, the instruction command format of the connection detection task is determined;

[0252] Based on the detection message parameters, determine the instruction message input parameters for connecting the detection task;

[0253] Based on the source IP address, destination IP address, command format, and command message input parameters, a connection detection command for the source-side device set is constructed.

[0254] In some embodiments, the processor 601 is further configured to:

[0255] Based on the name information of the source-side device, obtain the device information of the source-side device set, wherein the first identification information is the name information of the source-side device;

[0256] Based on the interface type and interface protocol type, obtain the list of source IP addresses of the corresponding interfaces in the source-side device set;

[0257] Based on the source interface identifier, the source IP address of the connection detection task is determined from the list of source IP addresses.

[0258] In some embodiments, the processor 601 is further configured to:

[0259] Based on the name information of the target side device, obtain the device information of the target side device set, wherein the second identification information is the name information of the target side device;

[0260] Based on the interface type and interface protocol type, obtain the target IP address list of the corresponding interface in the target-side device set;

[0261] Based on the target interface identifier, the target IP address of the connection detection task is determined from the list of target IP addresses.

[0262] In some embodiments, the processor 601 is further configured to:

[0263] Based on the device information of the source-side device set, different software processes are used to simulate logging into the source-side devices in the source-side device set in parallel, and the software processes correspond one-to-one with the source-side devices.

[0264] When each software process successfully logs into the source device, for each software process, the connection detection command of the source device corresponding to the software process is sequentially sent to the source device.

[0265] In some embodiments, the processor 601 is further configured to:

[0266] Based on the device model information and interface protocol type in the device information of the source-side device set, information extraction rules and result analysis rules are determined.

[0267] Based on the information extraction rules, network connection parameter information is extracted from the echo results;

[0268] Based on the network connection parameter information, the network connection analysis between the source-side device group and the target-side device group is performed using the result analysis rules to obtain the connection detection analysis results.

[0269] In some embodiments, the network connection parameter information includes the packet loss rate and average round-trip time between the source-side device and the target-side device. The processor 601 is further configured to:

[0270] The packet loss rate is compared with a first threshold used to evaluate connection availability in the result analysis rules to obtain a first comparison result; based on the first comparison result, the connection availability between the source-side device in the source-side device group and the target-side device in the target-side device group is determined, and the connection detection analysis result includes the connection availability;

[0271] Based on the packet loss rate and average round-trip time, the connection quality factor between the source-side device group and the target-side device group is determined using the calculation method in the result analysis rules. The connection detection analysis results include the connection quality factor.

[0272] The connection quality factor is compared with the second threshold used to evaluate connection quality in the result analysis rules to obtain a second comparison result; based on the second comparison result, the connection quality between the source-side device in the source-side device group and the target-side device in the target-side device group is determined, and the connection detection analysis result includes the connection quality.

[0273] Preferably, the present invention also provides an electronic device 600, including a processor 601, a memory 602, and a computer program stored in the memory 602 and executable on the processor 601. When the computer program is executed by the processor 601, it implements the various processes of the above-described connection detection method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0274] This invention also provides a readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes of the above-described connection detection method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0275] This application also provides a computer program product, including computer instructions. When executed by a processor, the computer instructions implement the various processes of the above-described connection detection method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0276] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0277] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0278] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0279] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of the present invention, depending on actual needs.

[0280] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0281] If the aforementioned functions 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 technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0282] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A connection detection method, characterized in that, The method includes: Obtain connection detection task information, which includes M first identifier information, N second identifier information, and target parameter information. The first identifier information is the identifier information of the source-side devices in the source-side device set, the second identifier information is the identifier information of the target-side devices in the target-side device set, and the target parameter information is used to implement the connection detection task. M and N are both positive integers. Based on the connection detection task information, a connection detection instruction for the source-side device set is constructed. The connection detection instruction is used by the source-side device set to detect the network connectivity between the source-side device set and the target-side device set. Based on the device information of the source-side device set, a simulated login to the source-side device set is performed to send the connection detection command to the source-side device set. The device information of the source-side device set is obtained based on the M first identifier information. Receive the echo result sent by the source-side device set based on the connection detection command; Based on the device information of the source-side device set, the echo results are analyzed to obtain connection detection analysis results.

2. The method according to claim 1, characterized in that, The target parameter information includes: the interface type, interface protocol type, and detection message parameters for implementing the connection detection task; the construction of the connection detection instructions for the source-side device set based on the connection detection task information includes: Based on the M first identifiers, the interface type, and the interface protocol type, the source IP address of the connection detection task is obtained; and based on the N second identifiers, the target IP address of the connection detection task is obtained. Based on the device model information, interface type, and interface protocol type in the device information of the source-side device set, the instruction command format of the connection detection task is determined; Based on the detection message parameters, determine the instruction message input parameters for connecting the detection task; Based on the source IP address, destination IP address, command format, and command message input parameters, a connection detection command for the source-side device set is constructed.

3. The method according to claim 2, characterized in that, The step of obtaining the source IP address of the connection detection task based on the M first identifiers, the interface type, and the interface protocol type includes: Based on the name information of the source-side device, obtain the device information of the source-side device set, wherein the first identification information is the name information of the source-side device; Based on the interface type and interface protocol type, obtain the list of source IP addresses of the corresponding interfaces in the source-side device set; Based on the source interface identifier, the source IP address of the connection detection task is determined from the list of source IP addresses.

4. The method according to claim 2, characterized in that, The step of obtaining the target IP address of the connection detection task based on the N second identifier information includes: Based on the name information of the target side device, obtain the device information of the target side device set, wherein the second identification information is the name information of the target side device; Based on the interface type and interface protocol type, obtain the target IP address list of the corresponding interface in the target-side device set; Based on the target interface identifier, the target IP address of the connection detection task is determined from the list of target IP addresses.

5. The method according to claim 1, characterized in that, The step of simulating login to the source-side device set based on the device information of the source-side device set, and then sending the connection detection command to the source-side device set, includes: Based on the device information of the source-side device set, different software processes are used to simulate logging into the source-side devices in the source-side device set in parallel, and the software processes correspond one-to-one with the source-side devices. When each software process successfully logs into the source device, for each software process, the connection detection command of the source device corresponding to the software process is sequentially sent to the source device.

6. The method according to claim 1, characterized in that, The connection detection analysis results are obtained by analyzing the device information based on the source-side device set, including: Based on the device model information and interface protocol type in the device information of the source-side device set, information extraction rules and result analysis rules are determined. Based on the information extraction rules, network connection parameter information is extracted from the echo results; Based on the network connection parameter information, the network connection analysis between the source-side device group and the target-side device group is performed using the result analysis rules to obtain the connection detection analysis results.

7. The method according to claim 6, characterized in that, The network connection parameter information includes the packet loss rate and average round-trip time between the source-side devices in the source-side device group and the target-side devices in the target-side device group. Based on the network connection parameter information, the network connection analysis between the source-side devices in the source-side device group and the target-side devices in the target-side device group is performed using the result analysis rules to obtain connection detection analysis results, including at least one of the following: The packet loss rate is compared with a first threshold used to evaluate connection availability in the result analysis rules to obtain a first comparison result; Based on the first comparison result, the connectivity availability between the source-side device cluster and the target-side device cluster is determined, and the connectivity detection and analysis result includes the connectivity availability; Based on the packet loss rate and average round-trip time, the connection quality factor between the source-side device group and the target-side device group is determined using the calculation method in the result analysis rules. The connection detection analysis results include the connection quality factor. The connection quality factor is compared with the second threshold used to evaluate connection quality in the result analysis rules to obtain a second comparison result; Based on the second comparison result, the connection quality between the source-side device cluster and the target-side device cluster is determined, and the connection detection and analysis result includes the connection quality.

8. A connection detection device, characterized in that, The device includes: The acquisition module is used to acquire connection detection task information, which includes M first identifier information, N second identifier information and target parameter information. The first identifier information is the identifier information of the source-side devices in the source-side device set, the second identifier information is the identifier information of the target-side devices in the target-side device set, and the target parameter information is used to implement the connection detection task. M and N are both positive integers. The instruction generation module is used to construct a connection detection instruction for the source-side device set based on the connection detection task information. The connection detection instruction is used by the source-side device set to detect the network connectivity between the source-side device set and the target-side device set. The instruction channel module is used to simulate logging into the source-side device set based on the device information of the source-side device set, so as to send the connection detection instruction to the source-side device set. The device information of the source-side device set is obtained based on the M first identification information; and to receive the echo result sent by the source-side device set based on the connection detection instruction. The result analysis module is used to analyze the displayed results based on the device information of the source-side device set to obtain the connection detection analysis results.

9. An electronic device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the connection detection method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the connection detection method as described in any one of claims 1 to 7.

11. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the steps of the connection detection method as described in any one of claims 1 to 7.

Images