Information processing method, related device and storage medium

Abstract

The application discloses an information processing method, a first domain name system (DNS), a second DNS and a storage medium. The method comprises the following steps: the first DNS receives first information, wherein the first information is used for domain name query of a first service, and the first information comprises demand information and a first service identifier; a target first server corresponding to the first service is determined by using the demand information; and second information is sent, wherein the second information comprises address information of the target first server.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of network scheduling, and in particular to an information processing method, related equipment and a storage medium. BACKGROUND

[0002] Domain Name System (DNS) recursive query refers to the deployment position of the query service, which needs to be queried level by level; in the case that there is no cache service of the deployment position of the local, the upper layer server is queried, which increases the time delay of the query.

[0003] In the related art, in the scenario of DNS recursive query, two kinds of DNS, authoritative DNS and local DNS (expressed in English as local DNS), are deployed in the operator network; among them, the local DNS is the first hop for user access to the network, and is used to query the deployment position of the service, while the authoritative DNS is used to parse the query result. By setting local cache, the local DNS can reduce the number of queries to the upper DNS.

[0004] However, in the scenario of computing power network, there is currently no DNS query scheme. SUMMARY

[0005] To solve the problems in the related art, the embodiments of the present application provide an information processing method, related equipment and a storage medium.

[0006] The technical scheme of the embodiments of the present application is implemented as follows:

[0007] The embodiments of the present application provide an information processing method applied to a first DNS, comprising:

[0008] Receiving first information, the first information being used for requesting domain name query of a first service, the first information containing demand information and a first service identifier;

[0009] Determining a target first server corresponding to the first service by using the demand information;

[0010] Sending second information, the second information containing address information of the target first server.

[0011] In the above scheme, the target first server corresponding to the first service is determined by using the demand information, comprising:

[0012] Determining the target first server by using third information and the demand information, the third information containing service state information of at least one first service.

[0013] In the above scheme, the target first server is determined by using the third information and the demand information, comprising:

[0014] The target first server is determined by using the third information, the requirement information and fourth information, and the fourth information comprises service location information of at least one first service.

[0015] In the above scheme, the method further comprises:

[0016] In a case where the target first server cannot be determined by using the third information and the requirement information, fifth information is sent to a second DNS, the fifth information being used for requesting to determine the target first server, and the fifth information at least comprising the requirement information and the first service identifier;

[0017] Second information sent by the second DNS is received.

[0018] In the above scheme, the method further comprises:

[0019] The third information is reported to a second DNS.

[0020] In the above scheme, a reporting period of the third information is associated with a service state information change frequency and / or a service request number.

[0021] In the above scheme, the method further comprises:

[0022] Service state information sent by the at least one first service is received to obtain the third information.

[0023] In the above scheme, a sending period of the service state information is associated with a service state information change frequency and / or a service request number.

[0024] In the above scheme, after the first information is received, the method further comprises:

[0025] Sixth information is sent to at least one first service associated with the first DNS, and the sixth information is used for requesting service state information.

[0026] Service state information sent by at least one first service associated with the first DNS is received to obtain the third information.

[0027] In the above scheme, the method further comprises:

[0028] In a case where at least one first service associated with the first DNS is not found, seventh information is sent to a second DNS, and the seventh information is used for requesting service state information of the at least one first service.

[0029] Service state information of at least one first service sent by the second DNS is received to obtain the third information.

[0030] In the scheme, the target first server corresponding to the first service is determined by using the demand information.

[0031] The eighth information is sent to at least one first service, and the eighth information is used to request at least one first service meeting the demand information;

[0032] The service state information sent by at least one first service meeting the demand information is received to obtain the ninth information, and the ninth information includes at least one first service meeting the demand information and corresponding service state information;

[0033] The target first server is determined by using the ninth information.

[0034] In the scheme, the method further includes:

[0035] The demand information and the address information of the target first server are cached.

[0036] In the scheme, the target first server corresponding to the first service is determined by using the demand information.

[0037] The address information of the target first server is determined from the cached tenth information by using the demand information, and the tenth information includes the mapping relationship between the demand information of at least one service and the address information of the server.

[0038] In the scheme, the method further includes:

[0039] The effective duration of the tenth information is set based on the service state information change frequency and / or the service request number.

[0040] In the scheme, the method further includes:

[0041] The eleventh information is determined, and the eleventh information represents the probability of determining the address information of the target first server based on the tenth information;

[0042] The effective duration of the tenth information is adjusted by using the eleventh information.

[0043] In the scheme, the demand information includes at least one of the following:

[0044] Resource demand information;

[0045] Performance demand information.

[0046] In the scheme, the resource demand information includes at least one of the following:

[0047] Computing power demand information;

[0048] Network demand information.

[0049] The embodiment of the present application further provides an information processing method, which is applied to a second DNS and comprises the following steps:

[0050] receiving fifth information sent by the first DNS, and sending the fifth information to a DNS other than the first DNS, the fifth information being used for requesting to determine a target first server corresponding to the first service, and the fifth information comprising at least demand information and a first service identifier; receiving second information sent by the DNS other than the first DNS, and sending the second information to the first DNS, the second information comprising address information of the target first server;

[0051] or,

[0052] receiving third information reported by the first DNS, the third information comprising service state information of at least one first service;

[0053] or,

[0054] in a case where at least one first service associated with the first DNS is not found, receiving seventh information sent by the first DNS, the seventh information being used for requesting service state information of the at least one first service; and sending the service state information of the at least one first service to the first DNS.

[0055] In the above scheme, the reporting period of the third information is associated with a service state information change frequency and / or a service request number.

[0056] The embodiment of the present application further provides a first DNS, comprising a first processor and a first communication interface; wherein,

[0057] the first communication interface is used for receiving first information, the first information being used for requesting a domain name query of a first service, and the first information comprising demand information and a first service identifier;

[0058] the first processor is used for determining a target first server corresponding to the first service by using the demand information, and sending second information comprising address information of the target first server through the first communication interface.

[0059] The embodiment of the present application further provides a second DNS, comprising a second processor and a second communication interface; wherein,

[0060] the second communication interface is used for:

[0061] The system receives a fifth message from a first DNS and sends the fifth message to other DNS servers besides the first DNS. The fifth message is used to request the determination of the target first server corresponding to the first service. The fifth message includes at least request information and a first service identifier. The system also receives a second message from other DNS servers besides the first DNS and sends the second message to the first DNS. The second message includes the address information of the target first server.

[0062] or,

[0063] Receive third information reported by the first DNS, the third information containing service status information of at least one first service;

[0064] or,

[0065] If no first service associated with the first DNS is found, the system receives a seventh message from the first DNS, the seventh message being used to request service status information of at least one first service; and sends the service status information of the at least one first service to the first DNS.

[0066] This application also provides a first DNS, including: a first processor and a first memory for storing a computer program capable of running on the processor.

[0067] Wherein, when the first processor is used to run the computer program, it executes the steps of any of the above-described first DNS-side methods.

[0068] This application also provides a second DNS, including: a second processor and a second memory for storing a computer program capable of running on the processor.

[0069] Wherein, when the second processor is used to run the computer program, it executes the steps of any of the methods described above for the second DNS side.

[0070] This application embodiment also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of any of the first DNS-side methods described above, or implements the steps of any of the second DNS-side methods described above.

[0071] The information processing method, related equipment, and storage medium provided in this application embodiment include: a first DNS receiving first information, which is used to request a domain name query for a first service, and the first information includes demand information and a first service identifier; using the demand information, determining a target first server corresponding to the first service; and sending second information, which includes the address information of the target first server. The technical solution provided in this application embodiment allows the first DNS to select the optimal server based on the demand information of a service (such as a computing power service) during the DNS query process, thereby ensuring that the selected server meets the business requirements of the service; that is, in a computing power network scenario, the first DNS can combine the demand factors of the computing power service to select a server that meets the business requirements, thus achieving effective DNS querying. Attached Figure Description

[0072] Figure 1 This is a schematic flowchart of the first information processing method according to an embodiment of this application;

[0073] Figure 2 This is a schematic diagram of the structure of an information format in an application example of this application;

[0074] Figure 3 This is a schematic flowchart of the second information processing method according to an embodiment of this application;

[0075] Figure 4 This is a flowchart illustrating the method for proactively sensing information using DNS, as an application example in this application.

[0076] Figure 5 This is a schematic diagram of the method for passively sensing information using DNS, as an application example in this application.

[0077] Figure 6 This is a flowchart illustrating the method for performing DNS queries via caching in the application example of this application;

[0078] Figure 7 This is a schematic diagram of the structure of the first information processing device according to an embodiment of this application;

[0079] Figure 8 This is a schematic diagram of the structure of a second type of information processing device according to an embodiment of this application;

[0080] Figure 9 This is a schematic diagram of the first DNS structure according to an embodiment of this application;

[0081] Figure 10 This is a schematic diagram of the second DNS structure according to an embodiment of this application;

[0082] Figure 11 This is a schematic diagram of the information processing system structure according to an embodiment of this application. Detailed Implementation

[0083] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0084] In related technologies, DNS local caching stores the mapping relationship between domain name information and Internet Protocol (IP) addresses. Therefore, during the DNS query process, the query result is usually returned based on the geographical location of the user (also known as the requester or service requester) and is the nearest business server to the user.

[0085] When dealing with computing power networks, services have high demands for both computing power and network resources, thus requiring joint optimization and scheduling of these resources. However, existing query schemes cannot meet the business needs of computing power services.

[0086] Based on this, in various embodiments of this application, when a user initiates a DNS query request, the user carries the service (such as computing power service) demand information, so that the first DNS can select the optimal server based on the demand information, thereby ensuring that the selected server can meet the service's business requirements.

[0087] This application provides an information processing method applied to a first DNS, such as... Figure 1 As shown, the method includes:

[0088] Step 101: Receive first information, which is used to request a domain name query for the first service. The first information includes demand information and the identifier of the first service.

[0089] Step 102: Using the demand information, determine the target first server corresponding to the first service;

[0090] Step 103: Send the second information, which contains the address information of the target first server.

[0091] In practical applications, the first DNS can be called a local DNS, and it should at least be able to perform service domain name queries. This application does not limit the name of the first DNS, as long as its function is implemented. In addition, the first service can be understood as a service or node in a network (such as a computing network), so it can be called a service node or node, etc. This application does not limit the name of the first service.

[0092] In practical applications, users can send first information to the first DNS to request a domain name query for the first service; wherein, the first information includes demand information and a first service identifier, and the first service identifier can indicate the first service.

[0093] In one embodiment, the demand information includes at least one of the following:

[0094] Resource demand information;

[0095] Performance requirements information.

[0096] The resource requirement information may include computing power requirement information and / or network requirement information. The network requirement information may include network latency. The computing power requirement information may include information such as service type, service response latency, and service quality. This application embodiment does not limit the specific content of the computing power requirement information and network requirement information.

[0097] Here, after receiving the first information, the first DNS can select the target first server for the first service based on the service status information and demand information of the first service.

[0098] Specifically, in one embodiment, determining the target first server corresponding to the first service using the demand information includes:

[0099] Using the third information and the demand information, the target first server is determined, wherein the third information includes service status information of at least one first service.

[0100] The service status information may include information such as deployment location, status information, load information, or business requirements. This application embodiment does not limit the specific content of the service status information.

[0101] Here, before determining the target first server, the first DNS can obtain the third information in different ways; among them, the third information can be obtained by the first service actively reporting.

[0102] Based on this, in one embodiment, the method may further include:

[0103] Receive service status information sent by at least one first service to obtain the third information.

[0104] Different primary services can be deployed in different regions, and each primary service can be aware of the service status information of the region it is located in.

[0105] In practical applications, after each of the at least one first services obtains the service status information of its region, it can send the service status information to the first DNS according to the sending period (also known as the reporting period). After receiving the service status information sent by the at least one first service, the first DNS can update the mapping relationship between the service identifier and the IP address, that is, add the service status information to the mapping relationship table between the service identifier and the IP address to obtain the third information.

[0106] Specifically, in one embodiment, the service status information sending period is associated with the service status information change frequency and / or the number of service requests.

[0107] In practical applications, different service status information sending cycles can be set according to preset service types. Specifically, for the first service, the sending cycle can be set according to the frequency of service status information changes and / or the number of service requests.

[0108] For example, a shorter sending period can be set for the first service whose service status information changes rapidly; or, a shorter sending period can be set for the first service whose service request count meets a threshold (which can be understood as a popular service); or, a sending period can be set for the first service based on the average value of service status information within a preset time period (e.g., 5 seconds); or, a sending period can be set for the first service based on the perception time of service status information, for example, service status information with a closer perception time has a larger weight, and service status information with a farther perception time has a smaller weight.

[0109] In practical applications, the first DNS can also obtain the third information through passive sensing.

[0110] Specifically, in one embodiment, after receiving the first information, the method further includes:

[0111] Send a sixth message to at least one first service associated with the first DNS, the sixth message being used to request service status information;

[0112] The third information is obtained by receiving service status information sent by at least one first service associated with the first DNS.

[0113] In practical applications, multiple DNS can be deployed in the network, and these multiple DNS include the first DNS. Different DNS can correspond to different state awareness zones. Accordingly, at least one first service is deployed in each state awareness zone. In this case, at least one first service associated with the first DNS can be understood as at least one first service in the state awareness zone where the first DNS is located.

[0114] In practical applications, after the user sends the first information to the first DNS, the first DNS can generate a first list (also known as a service candidate list) based on cached records or distance information. The first list contains at least one first service and the IP address corresponding to each first service; and sends the sixth information to at least one first service in the first list.

[0115] If at least one of the first services in the first list is within the state awareness area corresponding to the first DNS, then the first DNS can directly send the sixth information to the at least one first service. The sixth information may include the demand information, the first service identifier, the type information, etc. The specific content of the sixth information is not limited in this application embodiment.

[0116] If at least one of the first services in the first list is not within the state awareness area corresponding to the first DNS, the first DNS can send a seventh message to the second DNS to query the service status information; wherein, the second DNS can be called the authoritative DNS or the upper-level DNS. In this application embodiment, the name of the second DNS is not limited, as long as its function is implemented.

[0117] Based on this, in one embodiment, the method may further include:

[0118] If no first service associated with the first DNS is found, a seventh message is sent to the second DNS, the seventh message being used to request service status information of at least one first service;

[0119] The third information is obtained by receiving service status information of at least one first service sent by the second DNS.

[0120] The second DNS can manage multiple DNS in the network, and the multiple DNS include the first DNS.

[0121] Here, when at least one first service in the first list is not in the state awareness area corresponding to the first DNS, the first DNS can determine that at least one first service associated with the first DNS has not been found. At this time, the first DNS can send the seventh information to the second DNS, and the second DNS can query the service status information through other DNS besides the first DNS. In this way, the hierarchical awareness computing power service of DNS is realized.

[0122] In practical applications, during the service status information query process, in order for other DNS servers to know the type of the seventh information, the first DNS server can also add a type identifier to the seventh information to indicate that the seventh information is used to request service status information. For example, as shown...Figure 2 As shown, the first DNS can carry a type identifier through the Opcode field or Z field in the message header.

[0123] In practical applications, after the first DNS obtains the third information, it can report the third information to the second DNS so that the second DNS can manage the service status information of all first services in the network.

[0124] Based on this, in one embodiment, the method may further include:

[0125] The third information is reported to the second DNS.

[0126] Here, the first DNS can report the third information to the second DNS according to a preset reporting period; wherein, in one embodiment, the reporting period of the third information is related to the frequency of service status information changes and / or the number of service requests.

[0127] In practical applications, the reporting period can be set according to the frequency of changes in service status information and / or the number of service requests. For example, a shorter reporting period can be set for the first service whose service status information changes rapidly.

[0128] In practical applications, after obtaining the third information, the first DNS can determine the target first server based on the third information and the demand information. Specifically, the first DNS can determine whether at least one first service can meet the demand through service status information and demand information; and select one first service from at least one first service that meets the demand, thereby determining the corresponding target first server.

[0129] Alternatively, the first service can locally determine whether the required information is met, obtain a judgment result, and then the first DNS selects the target first server based on the judgment result.

[0130] Based on this, in one embodiment, determining the target first server corresponding to the first service using the demand information includes:

[0131] Send an eighth message to at least one first service, the eighth message being used to request at least one first service to satisfy the required information;

[0132] Receive service status information sent by at least one first service that satisfies the requirement information to obtain ninth information, the ninth information including at least one first service that satisfies the requirement information and the corresponding service status information;

[0133] Using the ninth piece of information, the target first server is identified.

[0134] In practical applications, the first DNS can send eighth information to the at least one first service, and the eighth information may include the requirement information; for each first service, the first service can use its own service status information to determine whether it can meet the requirement information; if the requirement information is met, the first service can return a judgment result and service status information to the first DNS, and the judgment result indicates that the first service meets the requirement information.

[0135] Here, after receiving service status information from at least one first service that meets the requirements, the first DNS can select one first service from the at least one first service that meets the requirements based on the service status information, thereby determining the target first server. For example, if there are five first services that meet the requirements, the first DNS can select the optimal first service from the five first services based on the service status information and service location information of the first services, thereby obtaining the corresponding target first server.

[0136] Furthermore, if the required information is not met, the first service may send a judgment result to the first DNS to inform the first service that the required information has not been met.

[0137] In practical applications, the first DNS can also combine the service location information of the first service to select the optimal target first server.

[0138] Specifically, in one embodiment, determining the target first server using the third information and the demand information includes:

[0139] Using the third information, the demand information, and the fourth information, the target first server is determined, wherein the fourth information includes service location information of at least one first service.

[0140] The fourth information may be actively sent by at least one first service, or it may be reported by at least one first service that meets the requirement information after the first DNS sends the eighth information. This application embodiment does not limit the specific method of obtaining the fourth information.

[0141] In practical applications, during the process of determining the target first server, the first DNS can query from the cache; if the target first server is not found in the cache, the target first server can be determined by local lookup or second DNS lookup. This can improve the efficiency of service domain name query and reduce the resolution load of the DNS system.

[0142] Based on this, in one embodiment, determining the target first server corresponding to the first service using the demand information includes:

[0143] Using the demand information, the address information of the target first server is determined from the cached tenth information, wherein the tenth information contains a mapping relationship between the demand information of at least one service and the address information of the server.

[0144] The tenth piece of information can be understood as service-related information cached in the computing power cache, specifically including the identifier of at least one service (or the domain name information of at least one service), the corresponding demand information, and the mapping relationship between the server address information.

[0145] It should be noted that, in this embodiment, the cache is divided into a regular cache and a computing power cache (which can be understood as cached information being associated with service demand information); wherein, the regular cache contains a mapping relationship between the identifier of at least one service and its corresponding IP address information. Thus, for different types of services, the first DNS can query the service domain name from the corresponding cache.

[0146] For example, suppose the cache contains service-related information for three computing services (computing service A, computing service B, and computing service C). The computing service cache includes at least the domain name information (www.abc.com) of computing service A, the address information of the server of computing service A (IP1 and IP2), and a first indication, which indicates that the address information of the server of computing service A is obtained based on the demand information. The general cache includes at least the domain name information (www.a.com) of computing service B, the address information of the server of computing service B (IP2, IP4, and IP5), and a second indication, which indicates that the address information of the server of computing service B is not obtained based on the demand information, i.e., computing demand factors are not considered. Furthermore, the general cache also includes at least the domain name information (www.ab.com) of computing service C, the address information of the server of computing service C (IP3 and IP4), and a third indication, which indicates that the address information of the server of computing service C is not obtained based on the demand information, i.e., computing demand factors are not considered.

[0147] In practical applications, after receiving the first information, the first DNS can determine whether the first service is a computing power service or a normal service. If the first service is a computing power service, it can use the demand information and the first service identifier to query the service domain name from the computing power cache. If the first service is a normal service, it can query the service domain name from the normal cache.

[0148] For example, suppose a user sends a query request to a first DNS to request a domain name lookup for service A; after receiving the query request, if the query request carries the computing power requirement for service A, then the first DNS can determine that service A is a computing power service; if the query request does not carry the computing power requirement for service A, then the first DNS can determine that service A is a normal service. This application embodiment does not limit the specific method for determining the service type.

[0149] Here, for different types of services, the first DNS can set different validity periods for the computing power cache to avoid the computing power cache being in a valid state when the service status changes (such as changes in service status information or location information), thereby causing the first DNS to be unable to select the optimal target first server.

[0150] Based on this, in one embodiment, the method may further include:

[0151] The validity period of the tenth information is set based on the frequency of service status information changes and / or the number of service requests.

[0152] The frequency of service status information changes can be understood as the update cycle of service status information. For example, if the frequency of service status information changes for the first service is high, a shorter effective duration, such as 5 seconds, can be set; or, if the number of service requests for the first service is higher than a first threshold (e.g., 5 times), indicating that the first service is a popular service, a longer effective duration, such as 10 seconds, can be set.

[0153] In practical applications, the first DNS can also combine the hit probability of the computing power cache to adjust the validity period of the tenth information, so as to increase the probability of the first DNS selecting the optimal target first server.

[0154] Based on this, in one embodiment, the method may further include:

[0155] The eleventh piece of information is determined, wherein the eleventh piece of information represents the probability of determining the address information of the target first server based on the tenth piece of information;

[0156] The effective duration of the tenth information is adjusted using the eleventh information.

[0157] In practical applications, within a preset time period, the first DNS can calculate the probability of determining the address information of the target first server based on the tenth information. If the calculated probability is higher than or equal to the second threshold (e.g., 0.7), the validity period of the tenth information can be maintained, i.e., no adjustment is needed. If the calculated probability is lower than the second threshold, the validity period of the tenth information can be reduced based on the frequency of service status information changes of the first service, for example, from 10s to 8s.

[0158] In practical applications, during a service domain name query, if the first DNS cannot find a first service that meets the required information and therefore cannot determine the target first server, a query request can be sent to the second DNS to determine the target first server. This enables cross-DNS collaborative service domain name queries.

[0159] Based on this, in one embodiment, the method may further include:

[0160] If the target first server cannot be determined using the third information and the demand information, a fifth information is sent to the second DNS. The fifth information is used to request the determination of the target first server, and the fifth information includes at least the demand information and the first service identifier.

[0161] Receive the second information sent by the second DNS.

[0162] In practical applications, the second device can also perform service domain name queries.

[0163] Here, the first DNS can send the fifth information to the second DNS, so that the second DNS can combine the service status information of all first services in the network and forward the fifth information to other DNS besides the first DNS, thereby performing service domain name queries.

[0164] In practical applications, after obtaining the address information of the target first server, the first DNS can feed back the address information of the target first server to the user. Additionally, the first DNS can also update the tenth information based on the address information of the target first server.

[0165] Based on this, in one embodiment, the method may further include:

[0166] The requirement information and the address information of the target first server are cached.

[0167] In practical applications, the first DNS can cache the demand information and the address information of the target first server; in addition, the first DNS can also cache the first service identifier. That is to say, for the first service, the first DNS can store the first service identifier, demand information, and address information of the target first server in the computing power cache to realize the updating of the tenth information.

[0168] Accordingly, embodiments of this application provide an information processing method applied to a second DNS, such as... Figure 3 As shown, the method includes:

[0169] Step 301: Receive the fifth information sent by the first DNS and send the fifth information to other DNS other than the first DNS. The fifth information is used to request the determination of the target first server corresponding to the first service. The fifth information includes at least the request information and the first service identifier. Receive the second information sent by other DNS other than the first DNS and send the second information to the first DNS. The second information includes the address information of the target first server.

[0170] Step 302: Receive the third information reported by the first DNS, the third information containing service status information of at least one first service;

[0171] Step 303: If no first service associated with the first DNS is found, receive a seventh message sent by the first DNS, the seventh message being used to request service status information of at least one first service; send the service status information of the at least one first service to the first DNS.

[0172] In practical applications, in step 301, the second DNS can send the fifth information to other DNS servers (referred to as the third DNS) besides the first DNS, based on the service status information of all first services in the network. The third DNS then determines the target first server based on the first service identifier and the demand information, and subsequently determines the address information of the target first server. Then, the second DNS can receive the address information of the target first server reported by the third DNS.

[0173] In practical applications, in step 303, if the first DNS does not find at least one first service associated with the first DNS, the second DNS can receive the seventh information sent by the first DNS. Since the second DNS maintains the service status information of all first services in the network in different state-aware areas, the second DNS can determine the fourth DNS associated with the at least one first service and forward the seventh information to the fourth DNS to query the service status information through the fourth DNS. The at least one first service can be understood as being within the state-aware area where the fourth DNS is located.

[0174] It should be noted that, in the scenario where the first DNS cannot determine the target first server, the second DNS performs step 301; or, in the scenario where the first DNS obtains the third information, the second DNS performs step 302; or, in the scenario where the first DNS does not find at least one first service associated with the first DNS, the second DNS performs step 303.

[0175] The information processing method provided in this application embodiment includes a first DNS receiving first information, which is used to request a domain name query for a first service. The first information includes demand information and a first service identifier. Using the demand information, a target first server corresponding to the first service is determined. Second information is sent, which includes the address information of the target first server. The technical solution provided in this application embodiment allows the first DNS to select the optimal server based on the demand information of a service (such as a computing power service) during the DNS query process, thereby ensuring that the selected server meets the service's business requirements. In other words, in a computing power network scenario, the first DNS can combine the demand factors of the computing power service to select a server that meets the business requirements, thus achieving efficient DNS querying.

[0176] The following section provides a more detailed description of this application with reference to application examples.

[0177] This application example proposes a scheme for DNS awareness and scheduling in computing power networks. By combining DNS iterative query and resolution caching mechanisms, and through extensions and enhancements, it is possible to achieve collaborative DNS scheduling between computing power and the network (which can be referred to as computing network).

[0178] This application example defines a mechanism for a computing power network DNS to proactively perceive information. For service A in the computing power network, different first DNSs correspond to different deployment locations for service A; among them, the first DNS is responsible for perceiving service status information.

[0179] Specifically, the process of the first DNS actively sensing information, such as Figure 4 As shown, it includes the following steps:

[0180] Step 401: Set different information reporting periods t1 for different types of computing power services;

[0181] Here, a period t1 can be set for the computing power service based on the changes in its state or the number of service requests. For example, a shorter period t1 is set for computing power services with rapid state changes; a longer period t1 is set for computing power services with rapid state changes; and a shorter period t1 is set for computing power services with a high number of service requests.

[0182] Step 402: Set different information reporting periods t2 for the first DNS according to different types of computing power services;

[0183] In practical applications, for computing power services with stored service status information (i.e., existing service status information), a period t2 can be set based on the changes in the service status, the number of service requests, or the existing service status information. For example, a shorter period t2 can be set for computing power services with rapidly changing status; or, a shorter period t2 can be set for popular computing power services; or, the average service status over a preset time period can be determined using the stored service status information, and this average value can be used as the period t2; or, the period t2 can be determined based on the time the service status information was stored, for example, service status information stored more recently has a higher weight, while service status information stored more recently has a lower weight.

[0184] Step 403: Computing service A located in region 1 reports service status information to the first DNS according to the reporting period t1;

[0185] Step 404: The first DNS obtains the service status information of computing power service A and stores the corresponding mapping relationship;

[0186] In practical applications, the first DNS adds service status information to the original service identifier and IP address mapping relationship; that is, the first DNS stores the mapping relationship between service identifier, IP address and service status information.

[0187] Step 405: The first DNS reports service status information and service location information to the second DNS according to the reporting period t2;

[0188] The second DNS is capable of maintaining the service location and status information of all services in the computing power network across all regions.

[0189] Here, if the first DNS receives service status information of a newly added computing power service, such as the service status information of computing power service B, it will trigger a report to the second DNS.

[0190] Step 406: After receiving the service status information, the second DNS stores the identification information, location information and service status information of computing power service A.

[0191] In addition, this application example also defines a mechanism for DNS to trigger passive awareness of service status information.

[0192] In practical applications, the first DNS triggers the process of passively sensing service status information, such as... Figure 5 As shown, it includes the following steps:

[0193] Step 501: The service requester initiates a DNS resolution request;

[0194] The DNS resolution request carries the domain name information and demand information of computing power service A.

[0195] Step 502: After receiving the DNS resolution request, if the demand information includes computing power demand information, the first DNS1 generates a candidate node list.

[0196] In practical applications, the first DNS1 reads the domain name information and demand information of computing power service A, such as computing power demand and computing power service quality. If the demand information includes computing power demand information, the first DNS1 can generate a node candidate list based on cache records or distance information. The node candidate list contains multiple IP addresses of computing power service A.

[0197] Step 503: For the computing power service in the current area, the first DNS1 sends a status query packet;

[0198] The status query packet carries the service identifier, demand information, and packet type information of computing power service A.

[0199] Here, the first DNS1 can determine whether computing service A in the node candidate list is within the region corresponding to the first DNS1 based on the preset correspondence; for computing service A within the region corresponding to the first DNS1, the first DNS1 can directly send a status query packet.

[0200] Step 504: Each computing power service A locally determines whether the demand information can be met and sends a response information to the first DNS;

[0201] The response information includes the service status information of computing power service A.

[0202] In practical applications, after receiving a status query packet, computing service A can use the demand information in the status query packet and its own service status information to determine whether computing service A can meet the demand. If the demand can be met, computing service A sends a response message to the first DNS, so that the first DNS can select a suitable computing service based on the response message, and the first DNS will send the selected computing service to the service requester.

[0203] In addition, after receiving the status query packet, computing service A can also send the service identifier and service status information of computing service A to the first DNS. In this way, the first DNS can combine the demand information to determine whether the computing service can meet the demand, and thus select a suitable computing service; then, it will inform the service requester of the selected computing service.

[0204] Step 505: For computing power services in other regions, send a status query packet to the second DNS;

[0205] In this application example, a new DNS message sending mechanism is defined, namely, a state query packet that uses a trigger mechanism.

[0206] Specifically, if computing service A in the node candidate list is not in the region corresponding to the first DNS1, the first DNS1 can send a status query packet to the second DNS.

[0207] Step 506: After receiving the status query packet, the second DNS sends a status query packet to the first DNS2 corresponding to computing power service A in the node candidate list.

[0208] After receiving the status query packet, the second DNS can forward it to the first DNS2 corresponding to computing service A. Upon receiving the status query packet, the first DNS2 then initiates a status query to computing service A. During this process, the second DNS needs to indicate the type of the status query packet to inform the first DNS2 that the packet contains status query information.

[0209] For example, such as Figure 5 As shown, a type identifier can be carried in the Opcode or Z field of the DNS header to indicate the type of the state query packet.

[0210] In addition, in order to query multiple computing services A at the same time, when the second DNS sends a status query packet to the first DNS2, it can also send one or more computing service-related information, such as the number of questions (QCOUNT) and the number of answers (ACOUNT). The number of answers can be an integer greater than or equal to 1.

[0211] After the first DNS2 initiates a status query packet to the computing power service A, the computing power service A can return status response information to the first DNS2. The status response information carries service status information and the type identifier of the status query packet. The first DNS2 can send the status response information to the first DNS1 through the second DNS. After receiving the status response information and identifying the type identifier of the status query packet, the first DNS1 reads the service status information of the computing power service and thus selects the computing power service.

[0212] In related technologies, when a service requester requests domain name resolution for a service, if the first DNS cannot find the domain name resolution result, the domain name resolution request is iterated to the second DNS. The second DNS then recursively returns the domain name resolution request to the first DNS that can find the domain name resolution result, and finally returns the domain name resolution result to the service requester. The above process considers whether the corresponding domain name request record exists in the DNS.

[0213] In this application example, the cache is divided into a regular cache and a computing power cache. When a service requester (e.g., service requester 1) initiates a domain name resolution request, if the domain name resolution request carries requirement information (specifically including network requirements and computing power requirements, such as network latency, service type, service response latency, service quality, etc.), then the service type can be determined to be a computing power service; in this case, it is necessary to query the computing power cache to obtain the domain name resolution result.

[0214] Specifically, the process of obtaining domain name resolution results through caching, such as Figure 6 As shown, it includes the following steps:

[0215] Step 601: The service requester (e.g., service requester 2) initiates a domain name resolution request to the first DNS to request the domain name resolution result of the service;

[0216] The domain name resolution request carries domain name information and requirement information.

[0217] Step 602: After the first DNS obtains the domain name resolution request, it reads the demand information to determine whether it is necessary to query the computing power cache; and then searches for the domain name resolution result corresponding to the service through the cache.

[0218] Here, when the domain name resolution request does not carry the requirement information, the first DNS determines that the service is a normal service and retrieves the domain name resolution result by querying the normal cache; when the domain name resolution request carries the requirement information, the first DNS determines that the service is a computing power service and retrieves the domain name resolution result by querying the computing power cache.

[0219] In practical applications, when searching for the domain name resolution results of computing power services, if multiple computing power services meet the computing power requirements, the first DNS can select the optimal computing power service from the multiple computing power services that meet the computing power requirements and send the domain name resolution results corresponding to the computing power service selected by the service requester.

[0220] In addition, if the first DNS cannot find a computing power service that meets the computing power requirements, it can send a domain name resolution request to the second DNS. The second DNS, in conjunction with the global service status information, forwards the domain name resolution request to other DNS (i.e., the third DNS) other than the first DNS. The third DNS further resolves the domain name and sends the domain name resolution result to the first DNS through the second DNS. The first DNS returns the domain name resolution result to the service requester and caches the domain name resolution result in the computing power cache.

[0221] Step 603: The first DNS determines whether there is a cached record with similar computing power requirements for the request information; if there is a cached record with similar computing power requirements, the computing power cache is read and the result is returned directly.

[0222] Under the mechanism of generating DNS cache records based on geographical location, the first DNS can directly return the domain name resolution result to the service requester by querying the cache record; however, the cache record is often updated infrequently. However, considering service status information and demand information, the requirements for DNS domain name resolution increase. Therefore, for domain name resolution requests with similar locations or demands, results can be returned directly based on the first DNS cache record. In other words, if the demand information of the computing power service is close to the demand information in the computing power cache, the corresponding domain name resolution result can be directly obtained from the computing power cache, thereby reducing the amount of DNS domain name resolution and improving domain name resolution efficiency.

[0223] Here, in the computing power cache, different cache time-to-live (TTL) values ​​can be set for different computing power services. For example, a longer cache TTL can be set for popular computing power services to improve query efficiency. Additionally, the TTL can be adjusted based on the update cycle of the service status information corresponding to the computing power service and the cache hit rate. This prevents situations where the service status information of the computing power service changes but the computing power cache is not updated, leading to the first DNS failing to select the optimal computing power service. For example, if the computing power cache hit rate is high, the current TTL can be maintained; if the computing power cache hit rate is low, the TTL can be reduced.

[0224] In this application example, both the first and second DNS servers are capable of sensing DNS computing power service status information. This is achieved by supporting two methods: the computing power service proactively reporting its status to the DNS, or the service status information being queried by a resolution request. The type of the computing power status information query packet is also identified, thus enabling hierarchical DNS awareness of the computing power service status.

[0225] Secondly, during the DNS resolution process, the system supports including demand information when initiating DNS resolution requests. This allows the DNS to perceive both demand and status information, and then collaboratively select the optimal computing power service at each level, achieving joint optimization and scheduling of computing power and network resources. Furthermore, it supports different mechanisms, such as the computing power service determining locally whether to meet business needs or the DNS determining whether to meet business needs.

[0226] Furthermore, this application example also supports computing power caching that considers computing power status information. This allows DNS to directly query the new computing power cache for computing power service requests. Additionally, a differentiated cache TTL setting mechanism is introduced; different TTLs are set for different types of computing power services, and the TTL is dynamically adjusted based on the cache hit rate to periodically or triggerfully update the resolution results.

[0227] To implement the method of the embodiments of this application, the embodiments of this application also provide an information processing device, which is set on the first DNS, such as... Figure 7As shown, the device includes:

[0228] The first receiving unit 701 is configured to receive first information, the first information being used to request a domain name query for a first service, the first information including request information and a first service identifier;

[0229] The determining unit 702 is used to determine the target first server corresponding to the first service using the demand information;

[0230] The sending unit 703 is used to send second information, which includes the address information of the target first server.

[0231] In one embodiment, the determining unit 702 is used to determine the target first server using third information and the demand information, wherein the third information includes service status information of at least one first service.

[0232] In one embodiment, the determining unit 702 is used to determine the target first server using the third information, the demand information, and the fourth information, wherein the fourth information includes service location information of at least one first service.

[0233] In one embodiment, the sending unit 703 is further configured to send fifth information to the second DNS when the target first server cannot be determined using the third information and the demand information. The fifth information is used to request the determination of the target first server, and the fifth information includes at least the demand information and the first service identifier.

[0234] Accordingly, the first receiving unit 701 is also configured to receive the second information sent by the second DNS.

[0235] In one embodiment, the sending unit 703 is further configured to report the third information to the second DNS.

[0236] In one embodiment, the first receiving unit 701 is further configured to receive service status information sent by the at least one first service to obtain the third information.

[0237] In one embodiment, the sending unit 703 is further configured to send sixth information to at least one first service associated with the first DNS, the sixth information being used to request service status information;

[0238] Accordingly, the first receiving unit 701 is further configured to receive service status information sent by at least one first service associated with the first DNS, and obtain the third information.

[0239] In one embodiment, the sending unit 703 is further configured to send a seventh message to the second DNS if at least one first service associated with the first DNS is not found, the seventh message being used to request service status information of at least one first service;

[0240] Accordingly, the first receiving unit 701 is further configured to receive service status information of at least one first service sent by the second DNS, and obtain the third information.

[0241] In one embodiment, the determining unit 702 is configured to:

[0242] Send an eighth message to at least one first service, the eighth message being used to request at least one first service to satisfy the required information;

[0243] Receive service status information sent by at least one first service that satisfies the requirement information to obtain ninth information, the ninth information including at least one first service that satisfies the requirement information and the corresponding service status information;

[0244] Using the ninth piece of information, the target first server is identified.

[0245] In one embodiment, the determining unit 702 is further configured to cache the demand information and the address information of the target first server.

[0246] In one embodiment, the determining unit 702 is used to determine the address information of the target first server from the cached tenth information using the demand information, the tenth information containing a mapping relationship between demand information of at least one service and address information of the server.

[0247] In one embodiment, the determining unit 702 is further configured to set the effective duration of the tenth information based on the frequency of service status information changes and / or the number of service requests.

[0248] In one embodiment, the determining unit 702 is further configured to:

[0249] The eleventh piece of information is determined, wherein the eleventh piece of information represents the probability of determining the address information of the target first server based on the tenth piece of information;

[0250] The effective duration of the tenth information is adjusted using the eleventh information.

[0251] In practical applications, the first receiving unit 701 and the sending unit 703 can be implemented by the communication interface in the information processing device; the determining unit 702 can be implemented by the processor in the information transmission device in combination with the communication interface.

[0252] To implement the method of this application embodiment, this application embodiment also provides an information processing apparatus, configured on a second DNS, such as... Figure 8 As shown, the device includes:

[0253] The first forwarding unit 801 is configured to receive fifth information sent by the first DNS and send the fifth information to other DNS other than the first DNS. The fifth information is used to request the determination of the target first server corresponding to the first service. The fifth information includes at least demand information and a first service identifier. The unit also receives second information sent by other DNS other than the first DNS and sends the second information to the first DNS. The second information includes the address information of the target first server.

[0254] The second receiving unit 802 is used to receive third information reported by the first DNS, the third information including service status information of at least one first service;

[0255] The second forwarding unit 803 is configured to receive a seventh message sent by the first DNS when no first service associated with the first DNS is found, the seventh message being used to request service status information of at least one first service; and to send the service status information of the at least one first service to the first DNS.

[0256] In practical applications, the first forwarding unit 801, the second receiving unit 802, and the second forwarding unit 803 can be implemented by the communication interface in the information processing device.

[0257] It should be noted that the information processing device provided in the above embodiments is only illustrated by the division of the above program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the information processing device and the information processing method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0258] Based on the hardware implementation of the above program modules, and in order to implement the method on the first DNS side of the embodiments of this application, the embodiments of this application also provide a first DNS, such as... Figure 9 As shown, the first DNS900 includes:

[0259] The first communication interface 901 is capable of exchanging information with the second DNS;

[0260] The first processor 902 is connected to the first communication interface 901 to enable information interaction with the second DNS, and is used to execute the methods provided by one or more technical solutions on the first DNS side when running a computer program;

[0261] The computer program is stored in the first memory 903.

[0262] Specifically, the first communication interface 901 is used to receive first information, which is used to request a domain name query for the first service, and the first information includes demand information and a first service identifier;

[0263] The first processor 902 is configured to use the demand information to determine the target first server corresponding to the first service; and to send second information through the first communication interface 901, the second information including the address information of the target first server.

[0264] In one embodiment, the first processor 902 is used to determine the target first server using third information and the demand information, wherein the third information includes service status information of at least one first service.

[0265] In one embodiment, the first processor 902 is configured to determine the target first server using the third information, the demand information, and the fourth information, wherein the fourth information includes service location information of at least one first service.

[0266] In one embodiment, the first communication interface 901 is further configured to:

[0267] If the target first server cannot be determined using the third information and the demand information, a fifth information is sent to the second DNS. The fifth information is used to request the determination of the target first server, and the fifth information includes at least the demand information and the first service identifier.

[0268] Receive the second information sent by the second DNS.

[0269] In one embodiment, the first communication interface 901 is further configured to report the third information to the second DNS.

[0270] In one embodiment, the first communication interface 901 is further configured to receive service status information sent by the at least one first service to obtain the third information.

[0271] In one embodiment, the first communication interface 901 is further configured to:

[0272] Send a sixth message to at least one first service associated with the first DNS, the sixth message being used to request service status information;

[0273] The third information is obtained by receiving service status information sent by at least one first service associated with the first DNS.

[0274] In one embodiment, the first communication interface 901 is further configured to:

[0275] If no first service associated with the first DNS is found, a seventh message is sent to the second DNS, the seventh message being used to request service status information of at least one first service;

[0276] The third information is obtained by receiving service status information of at least one first service sent by the second DNS.

[0277] In one embodiment, the first communication interface 901 is used for:

[0278] Send an eighth message to at least one first service, the eighth message being used to request at least one first service to satisfy the required information;

[0279] Receive service status information sent by at least one first service that satisfies the requirement information to obtain ninth information, the ninth information including at least one first service that satisfies the requirement information and the corresponding service status information;

[0280] Accordingly, the first processor 902 is used to determine the target first server using the ninth information.

[0281] In one embodiment, the first processor 902 is further configured to cache the demand information and the address information of the target first server.

[0282] In one embodiment, the first processor 902 is configured to use the demand information to determine the address information of the target first server from cached tenth information, the tenth information containing a mapping relationship between demand information of at least one service and address information of the server.

[0283] In one embodiment, the first processor 902 is further configured to set the validity period of the tenth information based on the frequency of service status information changes and / or the number of service requests.

[0284] In one embodiment, the first processor 902 is further configured to determine eleventh information, the eleventh information representing the probability of determining the address information of the target first server based on the tenth information;

[0285] The effective duration of the tenth information is adjusted using the eleventh information.

[0286] It should be noted that the specific processing procedures of the first processor 902 and the first communication interface 901 can be understood by referring to the above method.

[0287] Of course, in practical applications, the various components in the first DNS900 are coupled together via a bus system 904. It can be understood that the bus system 904 is used to implement communication between these components. In addition to a data bus, the bus system 904 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 9 The general designated all buses as Bus System 904.

[0288] The first memory 903 in this embodiment is used to store various types of data to support the operation of the first DNS 900. Examples of such data include any computer program used to operate on the first DNS 900.

[0289] The methods disclosed in the embodiments of this application can be applied to the first processor 902, or implemented by the first processor 902. The first processor 902 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 902. The first processor 902 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 902 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 903. The first processor 902 reads the information in the first memory 903 and completes the steps of the aforementioned method in combination with its hardware.

[0290] In an exemplary embodiment, the first DNS900 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0291] Based on the hardware implementation of the above program modules, and in order to implement the method on the second DNS side of the embodiments of this application, the embodiments of this application also provide a second DNS, such as... Figure 10As shown, the second DNS1000 includes:

[0292] The second communication interface 1001 is capable of exchanging information with the first DNS;

[0293] The second processor 1002 is connected to the second communication interface 1001 to enable information interaction with the first DNS and to execute the methods provided by one or more technical solutions on the second DNS side when running a computer program.

[0294] The computer program is stored in the second memory 1003.

[0295] Specifically, the second communication interface 1002 is used for:

[0296] The system receives a fifth message from a first DNS and sends the fifth message to other DNS servers besides the first DNS. The fifth message is used to request the determination of the target first server corresponding to the first service. The fifth message includes at least request information and a first service identifier. The system also receives a second message from other DNS servers besides the first DNS and sends the second message to the first DNS. The second message includes the address information of the target first server.

[0297] or,

[0298] Receive third information reported by the first DNS, the third information containing service status information of at least one first service;

[0299] or,

[0300] If no first service associated with the first DNS is found, the system receives a seventh message from the first DNS, the seventh message being used to request service status information of at least one first service; and sends the service status information of the at least one first service to the first DNS.

[0301] It should be noted that the specific processing procedures of the second communication interface 1001 and the second processor 1002 can be understood by referring to the above method.

[0302] Of course, in practical applications, the various components in the second DNS1000 are coupled together via bus system 1004. It can be understood that bus system 1004 is used to implement communication between these components. In addition to a data bus, bus system 1004 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 10 The general labeled all buses as Bus System 1004.

[0303] The second memory 1003 in this embodiment is used to store various types of data to support the operation of the second DNS 1000. Examples of such data include any computer program used to operate on the second DNS 1000.

[0304] The methods disclosed in the above embodiments of this application can be applied to the second processor 1002, or implemented by the second processor 1002. The second processor 1002 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the second processor 1002. The second processor 1002 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 1002 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the second memory 1003. The second processor 1002 reads the information in the second memory 1003 and completes the steps of the aforementioned method in conjunction with its hardware.

[0305] In an exemplary embodiment, the second DNS1000 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0306] It is understood that the memories (first memory 903 and second memory 1003) in the embodiments of this application can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0307] To implement the methods provided in the embodiments of this application, the embodiments of this application also provide an information processing system, such as... Figure 11 As shown, the system includes: a first DNS1101 and a second DNS1102.

[0308] It should be noted that the specific processing procedures of the first DNS1101 and the second DNS1102 have been detailed above and will not be repeated here.

[0309] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium. For example, it may include a first memory 903 storing a computer program, which can be executed by a first processor 902 of a first DNS 900 to complete the steps described in the aforementioned first DNS-side method. Another example is a second memory 1003 storing a computer program, which can be executed by a second processor 1002 of a second DNS 1000 to complete the steps described in the aforementioned second DNS-side method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0310] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0311] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0312] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. An information processing method, characterized in that, Applied to the first domain name system, DNS, including: Receive first information, the first information being used to request a domain name query for a first service, the first information including demand information and a first service identifier, the demand information including at least one of the following: resource demand information; performance demand information; Using the aforementioned demand information, determine the target first server corresponding to the first service; Send a second message, the second message containing the address information of the target first server; wherein, The step of using the demand information to determine the target first server corresponding to the first service includes: Using the third information and the aforementioned demand information, the target first server is determined, wherein the third information includes service status information of at least one first service; wherein, The step of determining the target first server using the third information and the demand information includes: Using the third information, the demand information, and the fourth information, the target first server is determined, wherein the fourth information includes service location information of at least one first service; The method further includes: If no first service associated with the first DNS is found, a seventh message is sent to the second DNS, the seventh message being used to request service status information of at least one first service; Receive service status information of at least one first service sent by the second DNS to obtain the third information; The method further includes: If the target first server cannot be determined using the third information and the demand information, a fifth information is sent to the second DNS. The fifth information is used to request the determination of the target first server, and the fifth information includes at least the demand information and the first service identifier. Receive the second information sent by the second DNS; The step of using the demand information to determine the target first server corresponding to the first service includes: Send an eighth message to at least one first service, the eighth message being used to request at least one first service to satisfy the required information; Receive service status information sent by at least one first service that satisfies the requirement information to obtain ninth information, the ninth information including at least one first service that satisfies the requirement information and the corresponding service status information; Using the ninth piece of information, the target first server is identified; The method further includes: The requirement information and the address information of the target first server are cached.

2. The method according to claim 1, characterized in that, The method further includes: The third information is reported to the second DNS.

3. The method according to claim 2, characterized in that, The reporting cycle of the third information is related to the frequency of changes in service status information and / or the number of service requests.

4. The method according to claim 1, characterized in that, The method further includes: Receive service status information sent by at least one first service to obtain the third information.

5. The method according to claim 4, characterized in that, The frequency of sending service status information is related to the frequency of changes in service status information and / or the number of service requests.

6. The method according to claim 1, characterized in that, After receiving the first information, the method further includes: Send a sixth message to at least one first service associated with the first DNS, the sixth message being used to request service status information; The third information is obtained by receiving service status information sent by at least one first service associated with the first DNS.

7. The method according to claim 1, characterized in that, The step of using the demand information to determine the target first server corresponding to the first service includes: Using the demand information, the address information of the target first server is determined from the cached tenth information, wherein the tenth information contains a mapping relationship between the demand information of at least one service and the address information of the server.

8. The method according to claim 7, characterized in that, The method further includes: The validity period of the tenth information is set based on the frequency of service status information changes and / or the number of service requests.

9. The method according to claim 7, characterized in that, The method further includes: The eleventh piece of information is determined, wherein the eleventh piece of information represents the probability of determining the address information of the target first server based on the tenth piece of information; The effective duration of the tenth information is adjusted using the eleventh information.

10. The method according to claim 7, characterized in that, The resource requirement information includes at least one of the following: Information on computing power requirements; Network demand information.

11. An information processing method, characterized in that, Applied to the second DNS, including: The system receives a fifth message from a first DNS and sends the fifth message to other DNS servers besides the first DNS. The fifth message is used to request the determination of a target first server corresponding to a first service. The fifth message includes at least requirement information and a first service identifier. The requirement information includes at least one of the following: resource requirement information; performance requirement information; and receives a second message from other DNS servers besides the first DNS and sends the second message to the first DNS. The second message includes the address information of the target first server. Receive third information reported by the first DNS, the third information containing service status information of at least one first service; If no first service associated with the first DNS is found, the system receives a seventh message from the first DNS, the seventh message being used to request service status information of at least one first service; and sends the service status information of the at least one first service to the first DNS.

12. The method according to claim 11, characterized in that, The reporting cycle of the third information is related to the frequency of changes in service status information and / or the number of service requests.

13. A first DNS, characterized in that, include: A first processor and a first communication interface; wherein... The first communication interface is used to receive first information, which is used to request a domain name query for a first service. The first information includes demand information and a first service identifier. The demand information includes at least one of the following: resource demand information; performance demand information. The first processor is configured to use the demand information to determine the target first server corresponding to the first service; and to send second information through the first communication interface, the second information including the address information of the target first server; wherein, The first processor is configured to determine the target first server using third information and the demand information, wherein the third information includes service status information of at least one first service; wherein, The first processor is configured to determine the target first server using third information and the demand information, wherein the third information includes service status information of at least one first service; The first communication interface is further configured to send a seventh message to the second DNS if no first service associated with the first DNS is found, the seventh message being used to request service status information of at least one first service; and to receive the service status information of at least one first service sent by the second DNS to obtain the third message; The first communication interface is further configured to send fifth information to the second DNS when the target first server cannot be determined using the third information and the demand information, the fifth information being used to request the determination of the target first server, and the fifth information including at least the demand information and the first service identifier; and to receive second information sent by the second DNS; The first communication interface is used to send an eighth message to at least one first service, the eighth message being used to request at least one first service to satisfy the requirement information; and to receive service status information sent by at least one first service that satisfies the requirement information to obtain a ninth message, the ninth message including at least one first service that satisfies the requirement information and the corresponding service status information. The first processor is configured to use the ninth information to determine the target first server; The first processor is also used to cache the demand information and the address information of the target first server.

14. A second DNS, characterized in that, include: A second processor and a second communication interface; wherein... The second communication interface is used for: The system receives a fifth message from a first DNS and sends the fifth message to other DNS servers besides the first DNS. The fifth message is used to request the determination of a target first server corresponding to a first service. The fifth message includes at least requirement information and a first service identifier. The requirement information includes at least one of the following: resource requirement information; performance requirement information; and receives a second message from other DNS servers besides the first DNS and sends the second message to the first DNS. The second message includes the address information of the target first server. Receive third information reported by the first DNS, the third information containing service status information of at least one first service; If no first service associated with the first DNS is found, the system receives a seventh message from the first DNS, the seventh message being used to request service status information of at least one first service; and sends the service status information of the at least one first service to the first DNS.

15. A first DNS, characterized in that, include: A first processor and a first memory for storing computer programs capable of running on the processor. Wherein, when the first processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 10.

16. A second DNS, characterized in that, include: A second processor and a second memory for storing computer programs that can run on the processor. Wherein, when the second processor is used to run the computer program, it performs the steps of the method described in claim 11 or 12.

17. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 10, or the steps of the method according to claim 11 or 12.

Images