A detection method, apparatus, system and communication equipment

Abstract

This invention provides a detection method, apparatus, system, and communication device, relating to the field of communication technology. The method includes: a DNS sending a list of servers corresponding to a service request to a user equipment (UE), the server list including different servers providing the same service; the UE sending a probe packet carrying the server list to an ingress gateway; and the ingress gateway sending the probe packet to different servers in the server list. This invention's solution uses multicast to send node status probe packets, eliminating the need to send probe packets to each user, thus effectively reducing the number of probe packets sent and solving the problem of high network overhead in current route detection methods.

Description

Technical Field

[0001] This invention relates to the field of data communication networks, and in particular to a detection method, apparatus and system. Background Technology

[0002] Currently, a unified resource and service view has been established for the entire network's computing power resources. This view enables mutual awareness of network status and data center service and resource status, allowing user requests to be scheduled to the best data center for computation, thus ensuring a good user experience.

[0003] Taking a computing power-aware network as an example, there are two ways to obtain network information and computing power information:

[0004] Active probing: This requires sending multiple probe packets, such as probe packets sent to different servers, and multiple probe packets sent to each server, resulting in a large amount of information; in addition, it also sends announcements even when there are no user requests, which are invalid information.

[0005] Passive Probe: The user sends multiple probe packets to multiple service ID nodes along multiple network paths; probes network information and node information.

[0006] Since existing probes are all based on unicast mechanisms, although they are sent based on service IDs, after being mapped at the ingress gateway, they become multiple probe packets sent to different IP addresses, which brings certain network overhead. When a large number of probe packets are sent in the network, it will bring significant network overhead. Summary of the Invention

[0007] The purpose of this invention is to provide a detection method, apparatus, and system that can solve the problem of high network overhead in existing route detection methods.

[0008] To achieve the above objectives, embodiments of the present invention provide a detection method, comprising:

[0009] Receive a list of servers corresponding to the service requests from the DNS side. The server list includes different servers for the same service.

[0010] Send a probe packet carrying a list of servers.

[0011] Optionally, the probe packet includes: the forwarding path corresponding to different servers.

[0012] Optionally, the probe packet may also include: a multicast packet header and service requirement information;

[0013] The server list and forwarding path are encapsulated in the multicast packet header.

[0014] To achieve the above objectives, embodiments of the present invention provide a communication device, including: a transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; when the communication device is a user equipment, the processor executes the program or instructions to implement the steps in the detection method described above.

[0015] To achieve the above objectives, embodiments of the present invention provide a detection method, comprising:

[0016] Receive probe packets carrying a list of servers, which includes different servers serving the same service;

[0017] The probe packets are sent to different servers in the server list.

[0018] Optionally, after sending the probe packets to different servers in the server list, the method further includes:

[0019] Receive load information from different servers.

[0020] Optionally, the probe packet includes: forwarding paths corresponding to different servers;

[0021] The probe packets are sent to different servers in the server list, including:

[0022] According to the respective forwarding paths of different servers, the probe packets are sent to different servers in the server list.

[0023] To achieve the above objectives, embodiments of the present invention provide a communication device, including: a transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; when the communication device is an ingress gateway, the processor executes the program or instructions to implement the steps in the detection method described above.

[0024] To achieve the above objectives, embodiments of the present invention provide a detection method, comprising:

[0025] Receive service requests;

[0026] The system provides a list of servers corresponding to the business requests, including different servers serving the same service.

[0027] To achieve the above objectives, embodiments of the present invention provide a communication device, including: a transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; when the communication device is a domain name server (DNS), the processor executes the program or instructions to implement the steps in the detection method described above.

[0028] To achieve the above objectives, embodiments of the present invention provide a detection method, comprising:

[0029] Receive probe packets carrying a list of servers, which includes different servers serving the same service;

[0030] Calculate the forwarding path for each server in the server list;

[0031] Return the forwarding path.

[0032] Optionally, the probe packet includes: a multicast packet header and service requirement information;

[0033] The server list and forwarding path are encapsulated in the multicast packet header.

[0034] To achieve the above objectives, embodiments of the present invention provide a communication device, including: a transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; when the communication device is a controller, the processor executes the program or instructions to implement the steps in the detection method described above.

[0035] To achieve the above objectives, embodiments of the present invention provide a detection device, comprising:

[0036] The first receiving module is used to receive a list of servers corresponding to the service request from the DNS side. The server list includes different servers for the same service.

[0037] The first sending module is used to send probe packets carrying a list of servers.

[0038] Optionally, the probe packet includes: the forwarding path corresponding to different servers.

[0039] Optionally, the probe packet may also include: a multicast packet header and service requirement information;

[0040] The server list and forwarding path are encapsulated in the multicast packet header.

[0041] To achieve the above objectives, embodiments of the present invention provide a detection device, comprising:

[0042] The second receiving module is used to receive probe packets carrying a list of servers, which includes different servers providing the same service.

[0043] The second sending module is used to send probe packets to different servers in the server list.

[0044] Optionally, the detection device also includes:

[0045] The third receiving module is used to receive load information from different servers.

[0046] Optionally, the probe packet includes: forwarding paths corresponding to different servers;

[0047] The second sending module includes:

[0048] The sending submodule is used to send probe packets to different servers in the server list according to their respective forwarding paths.

[0049] To achieve the above objectives, embodiments of the present invention provide a detection device applied to a Domain Name Server (DNS), comprising:

[0050] The fourth receiving module is used to receive service requests from the user equipment side;

[0051] The third sending module is used to send a list of servers corresponding to the service request to the user equipment. The server list includes different servers for the same service.

[0052] To achieve the above objectives, embodiments of the present invention provide a detection device, comprising:

[0053] The fifth receiving module is used to receive probe packets carrying a list of servers, which includes different servers providing the same service.

[0054] The calculation module is used to calculate the forwarding path for each server in the server list.

[0055] The fourth sending module is used to return the forwarding path.

[0056] Optionally, the probe packet includes: a multicast packet header and service requirement information;

[0057] The server list and forwarding path are encapsulated in the multicast packet header.

[0058] To achieve the above objectives, embodiments of the present invention provide a detection system, including: a user equipment, a domain name server (DNS), and an ingress gateway; wherein,

[0059] DNS returns a list of servers corresponding to the service request to the user equipment. The server list includes different servers for the same service.

[0060] The user equipment sends a probe packet carrying a list of servers to the ingress gateway;

[0061] The ingress gateway sends probe packets to different servers in the server list.

[0062] Optionally, the detection system further includes: a controller, wherein the controller receives a probe packet carrying a server list from the user equipment side, the server list including different servers of the same service; calculates a forwarding path for each of the different servers in the server list; and sends the forwarding path in the probe packet to the ingress gateway.

[0063] Optionally, the probe packet includes: a multicast packet header and service requirement information;

[0064] The server list and forwarding path are encapsulated in the multicast packet header.

[0065] To achieve the above objectives, embodiments of the present invention provide a readable storage medium having a program or instructions stored thereon, which, when executed by a processor, implement the steps in the detection method described above.

[0066] The beneficial effects of the above-described technical solution of the present invention are as follows:

[0067] The present invention provides a detection method, apparatus, system, and communication device in which a user equipment (UE) sends a service request to a Domain Name Server (DNS); the DNS returns a list of servers corresponding to the service request to the UE, including different servers providing the same service; the UE sends a probe packet carrying the server list to the ingress gateway; and the ingress gateway sends the probe packet to different servers in the server list. This multicast-based node status probe packet transmission, instead of sending a probe packet to each user, effectively reduces the number of probe packets sent and reduces network redundancy. Furthermore, the probe packet can also carry the forwarding path of different servers, thus supporting probe packets sent along specified paths. Compared to traditional multicast, which cannot specify paths, this effectively supports path-specific probes, providing support for subsequent path and node policy generation. Attached Figure Description

[0068] Figure 1 This is a flowchart illustrating the computing power route detection method in the detection system according to an embodiment of the present invention. Figure 1 ;

[0069] Figure 2 This is a flowchart illustrating the computing power route detection method in the detection system according to an embodiment of the present invention. Figure 2 ;

[0070] Figure 3 This is a schematic diagram of the packaging structure of the probe packet according to an embodiment of the present invention;

[0071] Figure 4 This is a schematic diagram of the information structure of the forwarding path in an embodiment of the present invention;

[0072] Figure 5 This is a schematic diagram of the forwarding path according to an embodiment of the present invention;

[0073] Figure 6 This is a schematic diagram of the detection device on the user equipment side according to an embodiment of the present invention;

[0074] Figure 7 This is a schematic diagram of the detection device on the inlet gateway side according to an embodiment of the present invention;

[0075] Figure 8 This is a schematic diagram of the DNS-side detection device according to an embodiment of the present invention;

[0076] Figure 9 This is a schematic diagram of the detection device on the controller side according to an embodiment of the present invention.

[0077] Figure 10 This is one of the structural block diagrams of a communication device according to an embodiment of the present invention;

[0078] Figure 11 This is a second structural block diagram of a communication device according to an embodiment of the present invention. Detailed Implementation

[0079] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0080] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the invention. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0081] In various embodiments of the present invention, it should be understood that the sequence number of each process described below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0082] In addition, the terms "system" and "network" are often used interchangeably in this article.

[0083] In the embodiments provided in this application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0084] In the computing power routing detection method, since the detection is based on the unicast mechanism, although it can be sent based on the server ID, after being mapped at the ingress gateway, it becomes multiple probe packets sent to different IP addresses, which brings additional network overhead.

[0085] like Figure 1 As shown, an embodiment of the present invention provides a detection system comprising: a user equipment, a domain name server (DNS), and an ingress gateway; wherein the detection method includes, but is not limited to, the following steps:

[0086] The user equipment sends a service request to the Domain Name Resolution (DNS) server; that is, the user equipment sends a service request to the DNS to obtain a list of servers corresponding to the requested service. The service request may also include service requirements, such as latency.

[0087] DNS returns a list of servers (or destination server list, destination node list, etc.) corresponding to the service request to the user equipment. The server list includes different servers for the same service.

[0088] For example, the server list includes different servers such as server1 and server2 for the same service.

[0089] The user equipment (UE) sends a multicast probe packet carrying a list of servers to the ingress gateway. The destination server list information for the multicast probe is obtained based on DNS, and the multicast probe packet is generated based on this list. In other words, at the ingress gateway, the received server list is added to the same multicast group, and a multicast probe packet is generated. Optionally, the multicast packet carries the source IP address (ingress gateway address).

[0090] The ingress gateway sends multicast probe packets to different servers in the server list to perform server load probing.

[0091] For example, the ingress gateway replicates multiple probe packets as server1 and server2, and sends them to server1 and server2 respectively. Server1 and server2 receive the probe packets, fill in their load information, and send it back to the ingress gateway. The ingress gateway receives load probe information from different servers providing the same service, completing the load probing. In this method, only server load information is obtained; the destination servers are placed in a multicast group, and network forwarding path status is not considered. Thus, multicast-based unicast transmission of multiple probe packets saves network bandwidth by adding multiple destination servers to a single multicast group.

[0092] like Figure 2 As shown, an embodiment of the present invention provides a detection system comprising: a user equipment, a domain name server (DNS), and an ingress gateway; wherein the detection method includes, but is not limited to, the following steps:

[0093] The user equipment sends a service request to the Domain Name Server (DNS). This service request may also include service requirements, such as latency.

[0094] DNS returns a list of servers (or destination server list, destination node list, etc.) corresponding to the service request to the user equipment. The server list includes different servers for the same service.

[0095] For example, the server list includes different servers such as server1 and server2 for the same service.

[0096] The user equipment sends a list of destination nodes to the controller.

[0097] The controller receives probe packets from the user equipment side carrying a list of servers, which includes different servers providing the same service.

[0098] The controller calculates the forwarding path for each server in the server list; the controller then sends the forwarding path in the probe packet to the ingress gateway. In other words, the controller generates the point-to-multipoint forwarding path for the destination node and sends it to the ingress gateway.

[0099] This allows for the generation of multicast probe packets based on the list of destination servers, and further generation and encapsulation of the respective forwarding paths (or probe paths) for different servers. Thus, the path-specified multicast mechanism can be used to specify uplink probe paths, enabling multicast probe packets to be sent to the same server along different uplink paths.

[0100] The ingress gateway sends probe packets to different servers in the server list according to the forwarding path to perform server load probing and path-along probing. Specifically, the ingress gateway sends multicast probe packets along the execution path, carrying service requirements. Routers along the path write the necessary information, such as timestamps and bandwidth, to achieve server load probing and path-along probing. To support the different needs of different services, different network and computing power information needs to be probed. Service requirements, such as low latency or high bandwidth, are carried in the multicast probe packet payload to instruct routers along the path to fill in the relevant information.

[0101] Optionally, Bit Index Explicit Replication (BIER) is a novel multicast forwarding technology. BIER encapsulates each multicast packet with a BIER header, containing multicast receiver information. BIER routers forward BIER multicast packets based on the information in the BIER header, without maintaining individual multicast forwarding state information. At the network layer, multicast replication can significantly save network bandwidth and reduce network load. In this embodiment, BIER packet encapsulation can be used. To further indicate probe packets for different paths, the uplink path of the probe packet can be specified. For example, the probe packet (or multicast packet) includes a multicast header and service requirement information, where the server list and forwarding path are encapsulated in the multicast header. That is, to obtain load information and uplink / downlink path information, the controller needs to send multicast probe packets along the specified path, carrying the service requirement within the multicast probe packet. This allows for the probing of information for multiple specified uplink paths by specifying the forwarding path of the multicast packet.

[0102] like Figure 3 As shown, a multicast message includes a multicast header and a payload. The multicast header includes an outer header, a multicast encapsulation, and an inner header. The multicast encapsulation specifies the multicast path and destination node, such as the route A→B→E→F→server2. The payload carries service requirement information.

[0103] Optionally, the forwarding path can be indicated using a bitmap. For example, assuming there are six routes A, B, C, D, E, and F, ... Figure 4 As shown, the bitmap for route A is "01", where 0 indicates the next hop is the user device and 1 indicates the next hop is route B. The bitmap for route B is "011", where 0 indicates the next hop is route A, 1 indicates the next hop is route C, and 2 indicates the next hop is route E. The bitmap for route C is "011", where 0 indicates the next hop is route B, 1 indicates the next hop is route D, and 2 indicates the next hop is route F. The bitmap for route D is "01", where 0 indicates the next hop is route C and 1 indicates the next hop is server1. The bitmap for route E is "01", where 0 indicates the next hop is route B and 1 indicates the next hop is route F. The bitmap for route F is "001", where 0 indicates the next hop is route C, 1 indicates the next hop is route E, and 2 indicates the next hop is server2.

[0104] like Figure 5As shown, after obtaining the list of destination nodes returned by DNS, the controller plans point-to-multipoint paths between the ingress gateway and multiple destination nodes, calculates the corresponding multicast paths, and sends them to the ingress gateway. For routes along the path, each routing node generates and maintains its own Bitmap table to indicate the forwarding path of the next hop. The forwarding path for server1 is: User Equipment → Route A → Route B → Route C → Route D → server1. The forwarding paths for server2 include: User Equipment → Route A → Route B → Route C → Route F → server2, and User Equipment → Route A → Route B → Route E → Route F → server2.

[0105] In this embodiment of the invention, the user equipment (UE) sends a service request to the DNS; the DNS returns a list of servers corresponding to the service request to the UE, the server list including different servers providing the same service; the UE sends a probe packet carrying the server list to the ingress gateway; the ingress gateway then sends the probe packet to different servers in the server list. This method of sending node status probe packets based on multicast packets effectively reduces the number of probe packets sent and reduces redundant packets in the network. Furthermore, the multicast probe packet can also carry the forwarding paths of different servers, thus supporting multicast probe packets sent along specified paths. Compared to traditional multicast, which cannot specify paths, this effectively supports path-specific probes, providing support for subsequent path and node policy generation.

[0106] The detection method of this invention has been described above from a system perspective. The following section will provide a detailed explanation of the method from different nodes.

[0107] Optionally, the detection method of this embodiment of the invention is applied to a user equipment and includes:

[0108] Receive a list of servers corresponding to the service requests from the DNS side. The server list includes different servers for the same service.

[0109] Send a probe packet carrying a list of servers.

[0110] Optionally, the probe packet may also include forwarding paths corresponding to different servers.

[0111] Optionally, the probe packet includes a multicast header and service requirement information, wherein the server list and forwarding path are encapsulated in the multicast header.

[0112] Optionally, the detection method of this embodiment of the invention includes:

[0113] Receive probe packets carrying a list of servers, which includes different servers serving the same service;

[0114] The probe packets are sent to different servers in the server list.

[0115] Optionally, after sending the probe packets to different servers in the server list, the method further includes:

[0116] Receive load information from different servers.

[0117] Optionally, the probe packet may also include forwarding paths corresponding to different servers, and the steps of sending the probe packet to different servers in the server list include:

[0118] According to the respective forwarding paths of different servers, the probe packets are sent to different servers in the server list.

[0119] Optionally, the detection method of this embodiment of the invention, applied to DNS, includes:

[0120] Receive service requests;

[0121] The system provides a list of servers corresponding to the business requests, including different servers serving the same service.

[0122] Optionally, the detection method of this embodiment of the invention is applied to a controller and includes:

[0123] Receive probe packets carrying a list of servers, which includes different servers serving the same service;

[0124] Calculate the forwarding path for each server in the server list;

[0125] Return the forwarding path.

[0126] Optionally, the probe packet includes a multicast header and service requirement information, wherein the server list and forwarding path are encapsulated in the multicast header.

[0127] The detection system and method embodiments of each node side of the present invention have been described above. The corresponding device embodiments will be further described below with reference to the accompanying drawings.

[0128] like Figure 6 As shown, an embodiment of the present invention provides a detection device applied to user equipment, comprising:

[0129] The first receiving module 610 is used to receive a list of servers corresponding to the service request from the DNS side. The server list includes different servers for the same service.

[0130] The first sending module 620 is used to send a probe packet carrying a list of servers to the ingress gateway.

[0131] Optionally, the probe packet may also include forwarding paths corresponding to different servers.

[0132] Optionally, the probe packet includes a multicast header and service requirement information, wherein the server list and forwarding path are encapsulated in the multicast header.

[0133] like Figure 7 As shown, this embodiment of the invention provides a detection device applied to an ingress gateway, comprising:

[0134] The second receiving module 710 is used to receive probe packets carrying a server list, the server list including different servers of the same service;

[0135] The second sending module 720 is used to send probe packets to different servers in the server list.

[0136] Optionally, the detection device also includes:

[0137] The third receiving module is used to receive load information from different servers.

[0138] Optionally, the probe packet also includes forwarding paths corresponding to different servers, and the second sending module 720 includes:

[0139] The sending submodule is used to send probe packets to different servers in the server list according to their respective forwarding paths.

[0140] like Figure 8 As shown, this embodiment of the invention provides a detection device applied to DNS, comprising:

[0141] The fourth receiving module 810 is used to receive service requests from the user equipment side;

[0142] The third sending module 820 is used to send a list of servers corresponding to the service request to the user equipment. The server list includes different servers for the same service.

[0143] like Figure 9 As shown, an embodiment of the present invention provides a detection device applied to a controller, comprising:

[0144] The fifth receiving module 910 is used to receive a probe packet carrying a server list, the server list including different servers of the same service;

[0145] Calculation module 920 is used to calculate the forwarding path for each of the different servers in the server list;

[0146] The fourth sending module 930 is used to return the forwarding path.

[0147] Optionally, the probe packet includes a multicast header and service requirement information, wherein the server list and forwarding path are encapsulated in the multicast header.

[0148] It is worth noting that this device embodiment corresponds to the above method embodiment. All implementations of the above method embodiment are applicable to this device embodiment and can achieve the same technical effect, so they will not be described again.

[0149] like Figure 10 As shown, this embodiment of the invention provides a communication device, which is a user equipment, including a transceiver 1010, a processor 1000, a memory 1020, and a program or instructions stored in the memory 1020 and executable on the processor 1000; when the processor 1000 executes the program or instructions, it implements the steps in the detection method applied to the user equipment side described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0150] The transceiver 1010 is used to receive and send data under the control of the processor 1000.

[0151] Among them, Figure 10 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 1000 and memory represented by memory 1020 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. The bus interface provides an interface. Transceiver 1010 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. For different user equipment, user interface 1030 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

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

[0153] like Figure 11 As shown, this embodiment of the invention provides a communication device, which is an ingress gateway, DNS, or controller, such as... Figure 11 As shown, it includes a transceiver 1110, a processor 1100, a memory 1120, and a program or instructions stored in the memory 1120 and executable on the processor 1100; when the processor 1100 executes the program or instructions, it implements the steps in the above-mentioned detection method applied to the above-mentioned ingress gateway, DNS, or controller side, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0154] The transceiver 1110 is used to receive and send data under the control of the processor 1100.

[0155] Among them, Figure 11 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1100) and memory (memory 1120). The bus architecture may also link together 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. The bus interface provides an interface. The transceiver 1110 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 may store data used by the processor 1100 during operation.

[0156] An embodiment of the present invention provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the steps in the detection method described above and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0157] The processor mentioned above is the processor in the communication device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0158] In this embodiment of the invention, the module can be implemented in software so that it can be executed by various types of processors. For example, an identified executable code module may include one or more physical or logical blocks of computer instructions, which may be constructed as objects, procedures, or functions. Nevertheless, the executable code of the identified module does not need to be physically located together, but may include different instructions stored in different bits, which, when logically combined, constitute the module and achieve the module's intended purpose.

[0159] In practice, an executable code module can be a single instruction or many instructions, and can even be distributed across multiple different code segments, different programs, and across multiple memory devices. Similarly, operational data can be identified within the module and can be implemented in any suitable form and organized within any suitable type of data structure. This operational data can be collected as a single dataset or distributed across different locations (including different storage devices), and can exist, at least in part, solely as electronic signals within the system or network.

[0160] When a module can be implemented using software, considering the current level of hardware technology, modules that can be implemented in software can be implemented using hardware circuits by those skilled in the art to achieve the corresponding functions, without considering cost. These hardware circuits include conventional very-large-scale integrated circuits (VLSI) or gate arrays, as well as existing semiconductors such as logic chips and transistors, or other discrete components. Modules can also be implemented using programmable hardware devices, such as field-programmable gate arrays, programmable array logic, and programmable logic devices.

[0161] The exemplary embodiments described above are with reference to the accompanying drawings. Many different forms and embodiments are feasible without departing from the spirit and teachings of the invention. Therefore, the invention should not be construed as limiting the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided to make the invention complete and convey the scope of the invention to those skilled in the art. In these drawings, component dimensions and relative dimensions may be exaggerated for clarity. The terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. As used herein, unless clearly indicated otherwise, the singular forms “a,” “an,” and “the” are intended to include all such forms. It will be further understood that the terms “comprising” and / or “including”, when used in this specification, indicate the presence of the stated features, integers, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, integers, steps, operations, components, and / or groups thereof. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of the range and any subranges in between.

[0162] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A detection method, characterized in that, include: Receive a list of servers corresponding to the service request from the DNS server side, the server list including different servers for the same service; Send a probe packet carrying the list of servers; The probe packet includes forwarding paths corresponding to different servers.

2. The detection method according to claim 1, characterized in that, The detection packet also includes: a multicast packet header and service requirement information; The server list and the forwarding path are encapsulated in the multicast packet header.

3. A detection method, characterized in that, include: Receive a probe packet carrying a server list, wherein the server list includes different servers for the same service; wherein the probe packet includes: forwarding paths corresponding to different servers; The probe packets are sent to different servers in the server list.

4. The detection method according to claim 3, characterized in that, After sending the probe packets to different servers in the server list, the method further includes: Receive the load information of each of the different servers.

5. The detection method according to claim 3 or 4, characterized in that, Sending the probe packets to different servers in the server list, respectively, including: The probe packet is sent to different servers in the server list according to their respective forwarding paths.

6. A detection method, characterized in that, include: Receive service requests; The system provides a list of servers corresponding to the service request, which includes different servers serving the same service. This enables the user equipment to send probe packets carrying the list of servers; wherein the probe packets include: forwarding paths corresponding to different servers.

7. A detection method, characterized in that, include: Receive probe packets carrying a list of servers, the list of servers including different servers for the same service; Calculate the forwarding path for each server in the server list; Return to the forwarding path.

8. The detection method according to claim 7, characterized in that, The probe packet includes: a multicast packet header and service requirement information; The server list and the forwarding path are encapsulated in the multicast packet header.

9. A detection device, characterized in that, include: The first receiving module is used to receive a list of servers corresponding to the service request from the DNS server side, wherein the server list includes different servers for the same service; The first sending module is used to send a probe packet carrying the list of servers; The probe packet includes forwarding paths corresponding to different servers.

10. A detection device, characterized in that, include: The second receiving module is used to receive a probe packet carrying a server list, wherein the server list includes different servers of the same service; wherein the probe packet includes: forwarding paths corresponding to different servers; The second sending module is used to send the probe packets to different servers in the server list.

11. A detection device, characterized in that, include: The fourth receiving module is used to receive service requests; The third sending module is used to send a list of servers corresponding to the service request to the user equipment. The server list includes different servers for the same service. This enables the user equipment to send probe packets carrying the server list; wherein the probe packets include: forwarding paths corresponding to different servers.

12. A detection device, characterized in that, include: The fifth receiving module is used to receive a probe packet carrying a server list, wherein the server list includes different servers for the same service; The calculation module is used to calculate the forwarding path for each of the different servers in the server list; The fourth sending module is used to return the forwarding path.

13. A detection system, characterized in that, include: User equipment, DNS server, and ingress gateway; among which... The Domain Name Server (DNS) sends a list of servers corresponding to the service request to the user equipment, and the server list includes different servers for the same service. The user equipment sends a probe packet carrying the server list to the ingress gateway; wherein, the probe packet includes: forwarding paths corresponding to different servers; The ingress gateway sends the probe packets to different servers in the server list.

14. A communication device, characterized in that, include: A transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; characterized in that, when the communication device is a user equipment, the processor executes the program or instructions to implement the steps of the detection method as described in any one of claims 1 to 2; When the communication device is an ingress gateway, the processor executes the program or instructions to implement the steps in the detection method as described in any one of claims 3 to 5; When the communication device is a Domain Name Server (DNS), the processor executes the program or instructions to implement the steps in the detection method as described in claim 6. When the communication device is a controller, the processor executes the program or instructions to implement the steps in the detection method as described in any one of claims 7 to 8.

15. A readable storage medium having a program or instructions stored thereon, characterized in that, When the program or instructions are executed by the processor, they implement the steps of the detection method as described in any one of claims 1 to 8.

Images