A user service request and processing method, device and medium

Abstract

The present invention discloses a user service request and processing method, device and medium, including: a client sends a user service domain name resolution request carrying information related to the client's physical location to a domain name server; receives a user server list returned by the domain name server; sends a detection message to the user server according to the user server list according to business needs; after determining network information and / or user service information according to the message fed back by the user server, determines the server that provides the user service. By adopting the present invention, more real-time service information can be obtained, and in some scenarios where service load changes rapidly, better load sharing capabilities can be provided.

Description

Technical Field

[0001] The present invention relates to the field of wireless communication technology, and in particular to a user service request and processing method, device and medium. Background Art

[0002] CAN (Computing-aware Networking) is a new network architecture proposed to cope with the development trend of computing-network integration. It interconnects dynamically distributed computing resources based on ubiquitous network connections. Through the unified and coordinated scheduling of multi-dimensional resources such as network, storage, and computing power, massive applications can call computing resources in different locations on demand and in real time, achieve global optimization of connections and computing power in the network, and provide a consistent user experience.

[0003] At present, there have been some explorations of the implementation mechanisms of CAN networks, such as the computing power routing mechanism of CFN (Computing First Networking), which allows routers to perceive computing power information and perform routing forwarding. However, its shortcomings are: the implementation is relatively complicated, and the basic operations of the IP forwarding plane need to be changed, and the cost of upgrading all routing equipment is high. Summary of the invention

[0004] The present invention provides a user service request and processing method, device and medium to support the implementation of a computing power-aware network, for example.

[0005] The present invention provides the following technical solutions:

[0006] A user service request method, characterized by comprising:

[0007] The client sends a user service domain name resolution request carrying information related to the client's physical location to the DNS server;

[0008] The client receives the user server list returned by the DNS server;

[0009] The client sends a detection message to the user server according to the user server list according to the service requirements;

[0010] After determining the network information and / or user service information according to the message fed back by the user server, the client determines the server that provides the user service.

[0011] In implementation, the user service is a computing power service. After determining the network information and computing power service information based on the message fed back by the user server, the client decides on the server that provides the computing power service.

[0012] In implementation, the client sends a detection message to the server in an agreed manner.

[0013] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0014] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0015] ECS;

[0016] The user's latitude and longitude information;

[0017] The cell information accessed by the user.

[0018] During implementation, the client receives a message fed back by the user server, which is a feedback message from the server to the user's detection message, and the feedback message carries the computing power service information.

[0019] In implementation, the network information is determined based on the difference between the sending time of the probe message and the receiving time of the feedback message.

[0020] A method for processing a user detection message, comprising:

[0021] The user server receives a message sent by the client carrying a client detection request;

[0022] The user server constructs a feedback message based on its own load conditions;

[0023] The user server sends the feedback message to the detected client.

[0024] In implementation, the user server provides computing power services.

[0025] In implementation, the user server listens to the detection message at the agreed port.

[0026] In implementation, the feedback message includes the current load status of the user server.

[0027] In implementation, when the user server provides computing power services, the computing power load situation is stored in a special TLV in the feedback message.

[0028] A method for processing a user service request, comprising:

[0029] The DNS server receives a user service domain name resolution request sent by a client and carrying information related to the client's physical location;

[0030] The DNS server determines the associated user server based on the client's physical location related information;

[0031] The DNS server returns a user server list to the client according to the load conditions of each user server. The user servers on the user server list are user servers that can provide user services to the client.

[0032] In implementation, the user service is a computing power service.

[0033] In implementation, the associated user server is determined from the user servers registered on the DNS server.

[0034] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0035] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0036] ECS;

[0037] The user's latitude and longitude information;

[0038] The cell information accessed by the user.

[0039] During implementation, it further includes:

[0040] Update the user service information of each user server according to the user information reported by each user server.

[0041] A client includes:

[0042] The processor reads the program in the memory and performs the following processes:

[0043] Send a user service domain name resolution request carrying information about the client's physical location to the DNS server;

[0044] Receive the user server list returned by the DNS server;

[0045] According to the service requirements, a detection message is sent to the user server according to the user server list;

[0046] After determining the network information and / or user service information according to the message fed back by the user server, determine the server that provides the user service;

[0047] A transceiver is used to receive and send data under the control of the processor.

[0048] In implementation, the user service is a computing power service. After determining the network information and computing power service information based on the message fed back by the user server, the client decides on the server that provides the computing power service.

[0049] In implementation, the client sends a detection message to the server in an agreed manner.

[0050] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0051] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0052] User subnet information (edns-client-subnet);

[0053] The user's latitude and longitude information;

[0054] The cell information accessed by the user.

[0055] During implementation, the client receives a message fed back by the user server, which is a feedback message from the server to the user's detection message, and the feedback message carries the computing power service information.

[0056] In implementation, the network information is determined based on the difference between the sending time of the probe message and the receiving time of the feedback message.

[0057] A client includes:

[0058] The client sending module is used to send a user service domain name resolution request carrying information related to the client's physical location to the DNS server;

[0059] The client receiving module is used to receive the user server list returned by the DNS server;

[0060] A client detection module, used to send a detection message to the user server according to the user server list according to business needs;

[0061] The client decision module is used to determine the server that provides user services after determining the network information and / or user service information according to the message fed back by the user server.

[0062] During implementation, the client decision module is further used to determine the server that provides the computing power service after determining the network information and computing power service information based on the message fed back by the user server when the user service is a computing power service.

[0063] During implementation, the client detection module is further used to send a detection message to the server in an agreed manner.

[0064] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0065] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0066] ECS;

[0067] The user's latitude and longitude information;

[0068] The cell information accessed by the user.

[0069] During implementation, the client receiving module is further used to receive a feedback message from the server to the user's detection message, and the feedback message carries the computing power service information.

[0070] In implementation, the network information is determined based on the difference between the sending time of the probe message and the receiving time of the feedback message.

[0071] A user server, comprising:

[0072] The processor reads the program in the memory and performs the following processes:

[0073] Receive a message sent by a client carrying a client detection request;

[0074] Construct feedback messages based on their own load conditions;

[0075] Sending the feedback message to the detected client;

[0076] A transceiver is used to receive and send data under the control of the processor.

[0077] In implementation, the user server provides computing power services.

[0078] In implementation, the user server listens to the detection message at the agreed port.

[0079] In implementation, the feedback message includes the current load status of the user server.

[0080] In implementation, when the user server provides computing power services, the computing power load situation is stored in a special TLV in the feedback message.

[0081] A user server, comprising:

[0082] A user server receiving module, used for receiving a message sent by a client and carrying a client detection request;

[0083] The user server message module is used to construct feedback messages according to its own load conditions;

[0084] The user server sending module is used to send the feedback message to the detected client.

[0085] In implementation, the user server provides computing power services.

[0086] In implementation, the user server receiving module is further used to monitor the detection message at the agreed port.

[0087] In implementation, the feedback message includes the current load status of the user server.

[0088] In implementation, when the user server provides computing power services, the computing power load situation is stored in a special TLV in the feedback message.

[0089] A DNS server, comprising:

[0090] The processor reads the program in the memory and performs the following processes:

[0091] Receive a user service domain name resolution request sent by a client and carrying information related to the client's physical location;

[0092] Determine an associated user server according to the client physical location related information;

[0093] Returning a user server list to the client according to the load of each user server, wherein the user servers on the user server list are user servers that can provide user services to the client;

[0094] A transceiver is used to receive and send data under the control of the processor.

[0095] In implementation, the user service is a computing power service.

[0096] In implementation, the associated user server is determined from the user servers registered on the DNS server.

[0097] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0098] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0099] ECS;

[0100] The user's latitude and longitude information;

[0101] The cell information accessed by the user. In this case, the user is a mobile user.

[0102] During implementation, it further includes:

[0103] Update the user service information of each user server according to the user information reported by each user server.

[0104] A DNS server, comprising:

[0105] The DNS server receiving module is used to receive a user service domain name resolution request sent by a client and carrying information related to the client's physical location;

[0106] A DNS server determination module, used to determine an associated user server based on the client physical location related information;

[0107] The DNS server feedback module is used to return a user server list to the client according to the load conditions of each user server. The user servers on the user server list are user servers that can provide user services to the client.

[0108] In implementation, the user service is a computing power service.

[0109] In implementation, the DNS server determination module is further used to determine, when determining the associated user server, the user server registered on the DNS server.

[0110] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0111] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0112] ECS;

[0113] The user's latitude and longitude information;

[0114] The cell information accessed by the user. In this case, the user is a mobile user.

[0115] During implementation, it further includes:

[0116] The DNS server update module is used to update the user service information of each user server according to the user information reported by each user server.

[0117] A computer-readable storage medium stores a computer program of the user service request method and / or the user service request processing method.

[0118] The beneficial effects of the present invention are as follows:

[0119] In the technical solution provided by the embodiment of the present invention, when the client needs user services, such as computing power services, it initiates a request to the DNS server, and the DNS server returns a list of user servers that can provide user servers. Then, the client sends a detection message to the server according to the user server list based on business needs; after determining the network information and / or user service information based on the message fed back by the server, the server that provides the user service is determined. In the mechanism of this solution, DNS+terminal detection is used to implement LB (Load Balance), which is a solution of central intelligence+distributed intelligence. Therefore, the DNS load-awareness+client active detection mechanism of this solution can obtain more real-time server information, and in some scenarios where the server load changes rapidly, it can provide better load sharing capabilities.

[0120] Furthermore, in the user-aware network scheduling mechanism provided by the solution, there is no need to change the current network configuration or forwarding mechanism. The Client can select a suitable user service node and access the service with the help of a DNS server. BRIEF DESCRIPTION OF THE DRAWINGS

[0121] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0122] Figure 1 A schematic diagram of the implementation flow of the user service request method on the client in an embodiment of the present invention;

[0123] Figure 2 A schematic diagram of an implementation flow of a method for processing a computing power service request on a DNS server in an embodiment of the present invention;

[0124] Figure 3 A schematic diagram of an implementation flow of a method for processing a user detection message on a user server side in an embodiment of the present invention;

[0125] Figure 4 A schematic diagram of the implementation process of a computing power service request in an embodiment of the present invention;

[0126] Figure 5 A schematic diagram of the implementation process of computing power service is provided in an embodiment of the present invention;

[0127] Figure 6 A schematic diagram of the DNS server structure in an embodiment of the present invention;

[0128] Figure 7 This is a schematic diagram of the client structure in an embodiment of the present invention;

[0129] Figure 8 Schematic diagram of the structure of a user server in an embodiment of the present invention. DETAILED DESCRIPTION

[0130] The inventors noticed during the invention process that:

[0131] The purpose of the CAN network is to allow the user terminal to connect to a node with low network latency and strong computing power, that is, to select a computing service node by comprehensively considering the network and computing power conditions.

[0132] The following uses computing power services as an example for explanation. Other similar services also have the common characteristics of computing power services.

[0133] The reason why we need to consider the computing power is that in CAN, the nearest node is not necessarily the most suitable node. Traditional networks only consider accessibility and do not consider the computing power of the service node.

[0134] At present, there are already some implementation mechanisms for CAN networks, such as CFN's computing power routing mechanism, which allows routers to sense computing power information and perform routing forwarding. However, this is relatively complicated to implement and requires changes to the basic operations of the IP forwarding plane, which is relatively costly.

[0135] In the technical solution provided by the embodiment of the present invention, by extending the DNS, the location information of the terminal is identified, and a Server list (candidate server) is fed back to the client, and then the client is allowed to perform detection to obtain the computing power situation, and finally the node is selected based on the computing power situation and the network situation.

[0136] The embodiment of the present invention provides a method of solving the problem of providing computing power services and network integration services by extending DNS (Domain Name Server) without modifying the forwarding plane at the bottom layer of the network.

[0137] The specific implementation of the present invention will be described below in conjunction with the accompanying drawings.

[0138] For ease of understanding, the description will mainly use computing power services as an example to illustrate the way of providing services. Computing power is used as an example because this service is relatively typical and can well adapt to the technical solutions provided in the embodiments of the present invention. Therefore, computing power services are used as an example here; however, this solution can also be used for other services, as long as it is a business that requires service integration. The computing power service is only used to teach technical personnel in this field how to implement the present invention specifically, but it does not mean that it can only be used for computing power services. During the implementation process, the environment in which it can be used can be determined in combination with practical needs.

[0139] In the process of specific description using computing power service as an example, the implementation of the client, DNS server and computing power server will be described respectively, and then an example of their coordinated implementation will be given to better understand the implementation of the solution given in the embodiment of the present invention. This description does not mean that they must be implemented in coordination or must be implemented separately. In fact, when the client, DNS server and computing power server are implemented separately, they also solve their own problems, and when the two are used in combination, better technical effects will be obtained.

[0140] Figure 1 A flowchart for implementing a user service request method on a client, as shown in the figure, may include:

[0141] Step 101: The client sends a user service domain name resolution request carrying information related to the client's physical location to the DNS server;

[0142] Step 102: The client receives the user server list returned by the DNS server;

[0143] Step 103: The client sends a detection message to the user server according to the user server list based on the service requirements;

[0144] Step 104: After determining the network information and / or user service information according to the message fed back by the user server, the client determines the server that provides the user service.

[0145] Specifically, the information related to the client's physical location is carried according to the DNS extension mechanism, that is, the EDNS0 mechanism is carried in the DNS message. The information related to the client's physical location in the ENDS0 mechanism can be any one of the following or a combination thereof:

[0146] ECS (user subnet information, edns-client-subnet);

[0147] The user's latitude and longitude information;

[0148] The cell information (cell ID) of the user's access. At this time, the user is a mobile user.

[0149] Specifically, the information related to the physical location of the client is described here as "related information" because, for example, ECS and cell ID are actually network information, which can be associated with location information through a mapping table.

[0150] In implementation, the user service is a computing power service. After determining the network information and computing power service information based on the message fed back by the user server, the client decides on the server that provides the computing power service.

[0151] In implementation, the client physical location related information may be inserted by LocalDNS, such as ECS, or may be inserted by the client, such as the user's latitude and longitude information, or cell ID information.

[0152] In practice, the client sends a detection message to the server in an agreed manner, for example, a UDP (User Datagram Protocol) message is sent to a specific port 100 of the server, and the message content can be empty or contain some information of the client, for example, it can appear in the form of TLV (type, length, value, tag, length, value), carrying user ID, geographic location and other information.

[0153] In implementation, the user access request is a domain name resolution request DNS message sent by the client to the DNS server. The object of resolution is a domain name related to a service identifier (service ID). Information related to the client's physical location can be carried in the above-mentioned DNS message in the format of edns-client-subnet (extended DNS-client-subnet).

[0154] In the implementation, the client receives a message fed back by the user server, which is a feedback message from the server to the user's detection message, and the feedback message carries the computing power service information. For example, the message is also a UDP (User Datagram Protocol) message, the destination port number is the source port number used by the client to send the detection message, and the content is the information of the server, which can appear in the form of TLV, carrying the computing power of the server, including the total computing power, the available computing power, etc.

[0155] The network information is determined based on the difference between the detection message sending time and the feedback message receiving time, that is, it can be determined based on the difference between the detection message sending time and the feedback message receiving time, that is, the sum of the two-way delays between the client and the user server.

[0156] Figure 2 A flowchart of a method for processing a computing power service request on a DNS server is provided, as shown in the figure, which may include:

[0157] Step 201: The DNS server receives a user service domain name resolution request sent by a client and carrying information related to the client's physical location;

[0158] Step 202: The DNS server determines the associated user server according to the client's physical location related information;

[0159] Step 203: The DNS server returns a user server list to the client according to the load conditions of each computing power server. The user servers on the user server list are user servers that can provide user services to the client.

[0160] The user server on this side (such as the computing power server) mainly goes to the DNS server to register its own computing power service, update the computing power status, and after receiving the client's detection (for example, listening on port 100), feedback a message about its own service status.

[0161] In implementation, the user service is a computing power service.

[0162] Specifically, for the DNS server, the DNS server is configured with a service ID table entry. Each computing server that can execute this service registers the service ID, its own service IP, and its own location information with the DNS server.

[0163] Each server can also update its own computing power information to the DNS server in real time. The update method can refer to the load scheduling technology in the current CDN.

[0164] The DNS server supports resolving the location-related information carried by the user according to edns-client-subnet (extended DNS-client-subnet), that is, it supports DNS requests to provide edns-client-subnet information, and also supports matching the client's network information with the server's physical location information.

[0165] In implementation, the associated user server is determined from the user servers registered on the DNS server.

[0166] During implementation, it further includes:

[0167] Update the user service information of each user server according to the user information reported by each user server.

[0168] During implementation, the client physical location related information in the computing power service domain name resolution request is carried in the above-mentioned DNS message in the format of edns-client-subnet.

[0169] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0170] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0171] ECS;

[0172] The user's latitude and longitude information;

[0173] The cell information accessed by the user. In this case, the user is a mobile user.

[0174] Figure 3 A schematic diagram of a process flow for implementing a method for processing a user detection message on a user server side, as shown in the figure, may include:

[0175] Step 301: The user server receives a message carrying a client detection request sent by a client;

[0176] Step 302: The user server constructs a feedback message according to its own load condition;

[0177] Step 303: The user server sends the feedback message to the detected client.

[0178] Specifically, the user server receives a message carrying a client detection request sent by the client, and the server constructs a feedback message according to its own load situation and sends it to the detecting client.

[0179] In implementation, the user server provides computing power services.

[0180] In implementation, the user server listens to the detection message at the agreed port.

[0181] In implementation, the feedback message includes the current load status of the user server.

[0182] In implementation, when the user server provides computing power services, the computing power load situation is stored in a special TLV in the feedback message.

[0183] Specifically, the feedback message includes the current load status of the user server. The computing power load status can be stored in a special TLV in the feedback message. At the same time, there can also be a special TLV to carry the total computing power status.

[0184] Figure 4 This is a flowchart for implementing a computing power service request. As shown in the figure, when the client requests the DNS server to resolve the service ID, the following process occurs:

[0185] 1: The client accesses the network and sends a computing power access request for service ID 1 to the DNS server. At the same time, the DNS request will carry its own ECS (extended DNS-client-subnet, edns-client-subnet) information, which can be inserted into the client's ECS information by LocalDNS.

[0186] 2: After receiving the DNS, it queries several associated servers based on the ECS information of the Client, and based on the computing load of the server, it feeds back a server list (computing power server list) to the Client. Optionally, it can also carry the computing power information.

[0187] The server can also be sorted according to load conditions, etc.

[0188] 3: The client receives the above server list and sends a detection message to the server to detect the network status according to business needs.

[0189] For example, send one or several probe messages to each server.

[0190] 4: The client receives the message from the server, from which it can obtain relevant network information, such as latency, and the server's computing power information;

[0191] Afterwards, the client can decide which server to use to obtain the required service based on the network and computing power conditions.

[0192] The following is an example to illustrate.

[0193] Those skilled in the art will readily appreciate that the specific server names, addresses, and URLs in the examples may change in the future, but these changes do not affect the understanding and disclosure of the implementation of the solution.

[0194] Figure 5 The following is a flow chart of the implementation process for providing computing power services. As shown in the figure, when the client requests the service ID from the DNS server, the following process occurs:

[0195] For the DNS server, you can register a service on the authoritative DNS server of a certain operator XXXX, such as serivce1.XXXX.com. This service1 can be supported by multiple MEC (Mobile Edge Computing) nodes as computing servers, that is, any MEC connected can complete the service1.

[0196] This authoritative DNS server collects information about each MEC site by running a communication program with the software or equipment of each MEC site, such as the site's health status, number of session connections, response time, geographic location information, computing power, etc.

[0197] 1: The client requests service 1 in the DNS request and provides information related to the physical location.

[0198] Specifically, the physical location is, for example, ECS in EDNS0.

[0199] 2: With the help of the authoritative DNS server of the aforementioned operator XXXX, the DNS sends the server list to the client according to the situation of each MEC node (server), the service ID registered by each server, the physical location information of the client and server, and the computing power of each server node.

[0200] 3: Client detects these servers.

[0201] 4: The server responds with server-related information such as computing power status.

[0202] 5: The client considers the computing power and network performance (such as latency) to decide which server to access for service.

[0203] Specifically, the client detects each server, obtains the network information to reach each server, and then selects a server based on the network information and computing power.

[0204] The specific detection method is, for example, detection is performed after the client and service communicate in a certain way according to a private app related to service1, or the client sends a UDP message to the specific port 100 of the server according to the agreement. The message content can be empty or some information of the client, such as TLV, carrying user ID information, physical location related information, etc.

[0205] The specific decision-making method, for example, is to score the latency, score the computing power, add weights, calculate a comprehensive score, and then compare and select a service node, or consider the latency to be less than a certain threshold, and then select a service node with the best computing power.

[0206] Based on the same inventive concept, a client, a DNS server, and a computer-readable storage medium are also provided in the embodiments of the present invention. Since the principles of solving problems by these devices are similar to user service requests and processing methods, the implementation of these devices can refer to the implementation of the methods, and the repeated parts will not be repeated.

[0207] When implementing the technical solution provided by the embodiment of the present invention, it can be implemented as follows.

[0208] Figure 6 The following is a schematic diagram of the DNS server structure, as shown in the figure, including:

[0209] The processor 600 is used to read the program in the memory 620 and execute the following process:

[0210] Receive a user service domain name resolution request sent by a client and carrying information related to the client's physical location;

[0211] Determine an associated user server according to the client physical location related information;

[0212] Returning a user server list to the client according to the load of each user server, wherein the user servers on the user server list are user servers that can provide user services to the client;

[0213] The transceiver 610 is configured to receive and send data under the control of the processor 600 .

[0214] In implementation, the user service is a computing power service.

[0215] In implementation, the associated user server is determined from the user servers registered on the DNS server.

[0216] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0217] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0218] ECS;

[0219] The user's latitude and longitude information;

[0220] The cell information accessed by the user. In this case, the user is a mobile user.

[0221] During implementation, it further includes:

[0222] Update the user service information of each user server according to the user information reported by each user server.

[0223] Among them, Figure 6 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 600 and memory represented by memory 620. The bus architecture may also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 610 may be a plurality of components, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 when performing operations.

[0224] The embodiment of the present invention further provides a DNS server, including:

[0225] The DNS server receiving module is used to receive a user service domain name resolution request sent by a client and carrying information related to the client's physical location;

[0226] A DNS server determination module, used to determine an associated user server based on the client physical location related information;

[0227] The DNS server feedback module is used to return a user server list to the client according to the load conditions of each user server. The user servers on the user server list are user servers that can provide user services to the client.

[0228] In implementation, the user service is a computing power service.

[0229] In implementation, the DNS server determination module is further used to determine, when determining the associated user server, the user server registered on the DNS server.

[0230] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0231] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0232] ECS;

[0233] The user's latitude and longitude information;

[0234] The cell information accessed by the user. In this case, the user is a mobile user.

[0235] During implementation, it further includes:

[0236] The DNS server update module is used to update the user service information of each user server according to the user information reported by each user server.

[0237] For the convenience of description, the various parts of the above-mentioned device are divided into various modules or units according to their functions and described separately. Of course, when implementing the present invention, the functions of each module or unit can be implemented in the same or multiple software or hardware.

[0238] Figure 7 The following is a schematic diagram of the client structure. As shown in the figure, the client includes:

[0239] The processor 700 is used to read the program in the memory 720 and execute the following process:

[0240] Send a user service domain name resolution request carrying information about the client's physical location to the DNS server;

[0241] Receive the user server list returned by the DNS server;

[0242] According to the service requirements, a detection message is sent to the user server according to the user server list;

[0243] After determining the network information and / or user service information according to the message fed back by the user server, determine the server that provides the user service;

[0244] The transceiver 710 is configured to receive and send data under the control of the processor 700 .

[0245] In implementation, the user service is a computing power service. After determining the network information and computing power service information based on the message fed back by the user server, the client decides on the server that provides the computing power service.

[0246] In implementation, the client sends a detection message to the server in an agreed manner.

[0247] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0248] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0249] ECS;

[0250] The user's latitude and longitude information;

[0251] The cell information accessed by the user.

[0252] During implementation, the client receives a message fed back by the user server, which is a feedback message from the server to the user's detection message, and the feedback message carries the computing power service information.

[0253] In implementation, the network information is determined based on the difference between the sending time of the probe message and the receiving time of the feedback message.

[0254] Among them, Figure 7 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 700 and various circuits of memory represented by memory 720 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 710 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. For different user devices, the user interface 730 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0255] The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 can store data used by the processor 700 when performing operations.

[0256] An embodiment of the present invention further provides a client, including:

[0257] The client sending module is used to send a user service domain name resolution request carrying information related to the client's physical location to the DNS server;

[0258] The client receiving module is used to receive the user server list returned by the DNS server;

[0259] A client detection module, used to send a detection message to the user server according to the user server list according to business needs;

[0260] The client decision module is used to determine the server that provides user services after determining the network information and / or user service information according to the message fed back by the user server.

[0261] During implementation, the client decision module is further used to determine the server that provides the computing power service after determining the network information and computing power service information based on the message fed back by the user server when the user service is a computing power service.

[0262] During implementation, the client detection module is further used to send a detection message to the server in an agreed manner.

[0263] In implementation, the client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

[0264] In implementation, the information related to the client's physical location includes one or a combination of the following information:

[0265] ECS;

[0266] The user's latitude and longitude information;

[0267] The cell information accessed by the user.

[0268] During implementation, the client receiving module is further used to receive a feedback message from the server to the user's detection message, and the feedback message carries the computing power service information.

[0269] In implementation, the network information is determined based on the difference between the sending time of the probe message and the receiving time of the feedback message.

[0270] For the convenience of description, the various parts of the above-mentioned device are divided into various modules or units according to their functions and described separately. Of course, when implementing the present invention, the functions of each module or unit can be implemented in the same or multiple software or hardware.

[0271] Figure 8 The schematic diagram of the user server structure is shown in the figure, including:

[0272] The processor 800 is used to read the program in the memory 820 and execute the following process:

[0273] Receive a message sent by a client carrying a client detection request;

[0274] Construct feedback messages based on their own load conditions;

[0275] Sending the feedback message to the detected client;

[0276] The transceiver 810 is configured to receive and send data under the control of the processor 800 .

[0277] In implementation, the user server provides computing power services.

[0278] In implementation, the user server listens to the detection message at the agreed port.

[0279] In implementation, the feedback message includes the current load status of the user server.

[0280] In implementation, when the user server provides computing power services, the computing power load situation is stored in a special TLV in the feedback message.

[0281] Among them, Figure 8 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 800 and memory represented by memory 820. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 810 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 800 is responsible for managing the bus architecture and general processing, and the memory 820 may store data used by the processor 800 when performing operations.

[0282] The embodiment of the present invention further provides a user server, including:

[0283] A user server receiving module, used for receiving a message sent by a client and carrying a client detection request;

[0284] The user server message module is used to construct feedback messages according to its own load conditions;

[0285] The user server sending module is used to send the feedback message to the detected client.

[0286] In implementation, the user server provides computing power services.

[0287] In implementation, the user server receiving module is further used to monitor the detection message at the agreed port.

[0288] In implementation, the feedback message includes the current load status of the user server.

[0289] In implementation, when the user server provides computing power services, the computing power load situation is stored in a special TLV in the feedback message.

[0290] For the convenience of description, the various parts of the above-mentioned device are divided into various modules or units according to their functions and described separately. Of course, when implementing the present invention, the functions of each module or unit can be implemented in the same or multiple software or hardware.

[0291] A computer-readable storage medium stores a computer program of the user service request method and / or the user service request processing method.

[0292] For specific implementation, please refer to the implementation of the user service request method on the client side and / or the user service request processing method on the DNS server side.

[0293] In summary, in the technical solution provided by the embodiment of the present invention, the Client carries the service ID related to computing power and information related to the physical location in the DNS request. The service ID can be a string. The service ID is registered as a domain name, and the physical location is, for example, ECS in ENDS0.

[0294] The DNS server sends a server list to the client based on the service ID registered by each server, the physical location information of the client and server, and the computing power of each server node;

[0295] The client actively detects each server, obtains the network information to reach each server, and then selects a server based on the network information and computing power.

[0296] In the current mechanism, DNS is generally used to implement the so-called LB, while in the mechanism of this solution, DNS+terminal detection is used to implement LB, which is central intelligence+distributed intelligence. In the computing power-aware network scheduling mechanism provided by the solution, there is no need to change the current network configuration or forwarding mechanism. The client can select the appropriate computing power node with the help of the DNS server and access the service.

[0297] Traditional DNS scheduling is based on the decisions of the upper-layer network. The DNS load-aware + client active detection mechanism of this solution can obtain more real-time server information and provide better load sharing capabilities in some scenarios where the server load changes rapidly.

[0298] In computing scenarios, some businesses are highly real-time and change quickly, and are more suitable for the DNS macro-scheduling + client micro-scheduling solution.

[0299] ServiceID is registered and scheduled in the operator's service DNS, which helps operators get rid of dumb pipes in the network and have greater voice.

[0300] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

[0301] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0302] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0303] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0304] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A user service request method, characterized in that: include: The client sends a user service domain name resolution request carrying information about the client's physical location to the domain name server DNS server; The client receives the user server list returned by the DNS server; The client sends a detection message to the user server according to the user server list according to the service requirements; After the client determines the network information and user service information based on the message fed back by the user server, it decides the server that provides the user service; The network information is determined according to the difference between the sending time of the detection message and the receiving time of the feedback message.

2. The method according to claim 1, characterized in that The user service is a computing power service. After determining the network information and computing power service information according to the message fed back by the user server, the client decides on the server that provides the computing power service.

3. The method according to claim 1, characterized in that The client sends a detection message to the server in an agreed manner.

4. The method according to claim 1, characterized in that The client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

5. The method according to claim 4, characterized in that Information related to the client's physical location includes one or a combination of the following information: User subnet information ECS, user's latitude and longitude information, user's access cell information.

6. The method according to claim 1 or 3, characterized in that: The client receives a message fed back by the user server, which is a feedback message from the server to the user's detection message, and the feedback message carries computing power service information.

7. A method for processing user detection messages, characterized in that: include: The user server receives a message sent by the client carrying a client detection request; The user server constructs a feedback message based on its own load conditions; The user server sends the feedback message to the detected client; The client sends a user service domain name resolution request carrying information related to the client's physical location to the DNS server, and the client sends a detection message to the user server according to the user server list returned by the DNS server; The feedback message is used to determine the network information and the user service information. After determining the network information and the user service information, the client determines the server that provides the user service; The network information is determined according to the difference between the sending time of the detection message and the receiving time of the feedback message.

8. The method according to claim 7, characterized in that The user server provides computing power services.

9. The method according to claim 7, characterized in that The user server listens to the detection message at the agreed port.

10. The method according to claim 7 or 8, characterized in that The feedback message includes the current load status of the user server.

11. The method according to claim 10, characterized in that When the user server provides computing power services, the computing power load situation is stored in a special TLV in the feedback message.

12. A method for processing user service requests, characterized in that: include: The DNS server receives a user service domain name resolution request sent by a client and carrying information related to the client's physical location; The DNS server determines the associated user server according to the client's physical location related information; The DNS server returns a user server list to the client according to the load of each user server, where the user servers on the user server list are user servers that can provide user services to the client; Among them, the user server list is used by the client to send a detection message to the user server according to business needs; after the client determines the network information and user service information based on the message fed back by the user server, it decides the server that provides user services; the network information is determined based on the difference between the sending time of the detection message and the receiving time of the feedback message.

13. The method according to claim 12, characterized in that The user service is a computing power service.

14. The method according to claim 12 or 13, characterized in that The associated user server is determined by determining the user server registered on the DNS server.

15. The method according to claim 12, characterized in that The client physical location related information is carried in the DNS message according to the DNS extension mechanism EDNS0 mechanism.

16. The method according to claim 15, characterized in that Information related to the client's physical location includes one or a combination of the following information: ECS, user's latitude and longitude information, user's access cell information.

17. The method according to claim 12, characterized in that Further including: Update the user service information of each user server according to the user information reported by each user server.

18. A client, characterized in that: include: The processor reads the program in the memory and performs the following processes: Send a user service domain name resolution request carrying information about the client's physical location to the DNS server; Receive the user server list returned by the DNS server; According to the service requirements, a detection message is sent to the user server according to the user server list; After determining the network information and / or user service information according to the message fed back by the user server, determine the server that provides the user service; a transceiver for receiving and transmitting data under the control of the processor; The network information is determined according to the difference between the sending time of the detection message and the receiving time of the feedback message.

19. A client, characterized in that: include: The client sending module is used to send a user service domain name resolution request carrying information related to the client's physical location to the DNS server; The client receiving module is used to receive the user server list returned by the DNS server; A client detection module, used to send a detection message to the user server according to the user server list according to business needs; A client decision module, used to determine the server providing user services after determining network information and / or user service information according to the message fed back by the user server; The network information is determined according to the difference between the sending time of the detection message and the receiving time of the feedback message.

20. A user server, characterized in that: include: The processor reads the program in the memory and performs the following processes: Receive a message sent by a client carrying a client detection request; Construct feedback messages based on their own load conditions; Sending the feedback message to the detected client; a transceiver for receiving and transmitting data under the control of the processor; The client sends a user service domain name resolution request carrying information related to the client's physical location to the DNS server, and the client sends a detection message to the user server according to the user server list returned by the DNS server; The feedback message is used to determine the network information and the user service information. After determining the network information and the user service information, the client determines the server that provides the user service; The network information is determined according to the difference between the sending time of the detection message and the receiving time of the feedback message.

21. A user server, characterized in that: include: A user server receiving module, used for receiving a message sent by a client and carrying a client detection request; The user server message module is used to construct feedback messages according to its own load conditions; A user server sending module, used for sending the feedback message to the detected client; The client sends a user service domain name resolution request carrying information related to the client's physical location to the DNS server, and the client sends a detection message to the user server according to the user server list returned by the DNS server; The feedback message is used to determine the network information and the user service information. After determining the network information and the user service information, the client determines the server that provides the user service; The network information is determined according to the difference between the sending time of the detection message and the receiving time of the feedback message.

22. A DNS server, characterized in that: include: The processor reads the program in the memory and performs the following processes: Receive a user service domain name resolution request sent by a client and carrying information related to the client's physical location; Determine an associated user server according to the client physical location related information; Returning a user server list to the client according to the load of each user server, wherein the user servers on the user server list are user servers that can provide user services to the client; a transceiver for receiving and transmitting data under the control of the processor; The user server list is used by the client to send a detection message to the user server according to business needs; After determining the network information and user service information according to the message fed back by the user server, the client decides on the server that provides the user service; the network information is determined according to the difference between the sending time of the detection message and the receiving time of the feedback message.

23. A DNS server, characterized in that: include: The DNS server receiving module is used to receive a user service domain name resolution request sent by a client and carrying information related to the client's physical location; A DNS server determination module, used to determine an associated user server according to the client physical location related information; A DNS server feedback module, used to return a user server list to the client according to the load of each user server, wherein the user servers on the user server list are user servers that can provide user services to the client; Among them, the user server list is used by the client to send a detection message to the user server according to business needs; after the client determines the network information and user service information based on the message fed back by the user server, it decides the server that provides user services; the network information is determined based on the difference between the sending time of the detection message and the receiving time of the feedback message.

24. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program for executing the method according to any one of claims 1 to 17.

Images