Edge node scheduling method and cloud scheduling platform

Abstract

A method for scheduling edge nodes and a cloud scheduling platform are disclosed, relating to the field of computer technology. This method is applied to a cloud scheduling platform. After receiving a DNS request from a target user, the cloud scheduling platform determines the IP address of the first edge node corresponding to the target access information indicated in the DNS request, based on edge node scheduling information, and returns the IP address of the first edge node to the target user. Since the first edge node scheduled by the cloud scheduling platform has fewer ASs on its network link to the target AS indicated by the target access information than other edge nodes, when the target user accesses the first edge node corresponding to the target domain name through the target AS, the number of AS hops on the network link is reduced compared to accessing other edge nodes corresponding to the target domain name. This reduces access latency and improves network communication quality.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an edge node scheduling method and a cloud scheduling platform. Background Technology

[0002] Currently, when users access edge nodes for various services via domain names, the Domain Name System (DNS) schedules the nearest edge node to the user based on their geographical location. However, this scheduling scheme results in network communication quality that fails to meet user needs when accessing edge nodes.

[0003] Therefore, improving the quality of network communication when accessing edge nodes has become an urgent technical problem to be solved. Summary of the Invention

[0004] This application provides an edge node scheduling method and a cloud scheduling platform, which can improve the network communication quality when accessing edge nodes.

[0005] Firstly, an edge node scheduling method is provided, applied to a cloud scheduling platform. The cloud scheduling platform is deployed on infrastructure, which stores edge node scheduling information. The edge node scheduling information is used to indicate the correspondence between at least one access message and at least one Internet Protocol (IP) address of an edge node. The access message is used to indicate the domain name corresponding to the IP address of the edge node and the Autonomous System Number (ASN) of the Autonomous System (AS) directly connected to the user's electronic device. The method includes: receiving a Domain Name System (DNS) request from a target user, the DNS request indicating target access information, the target access information indicating the target domain name and the ASN of the target AS directly connected to the target user's electronic device; determining, based on the edge node scheduling information, the IP address of a first edge node corresponding to the target access information, the number of ASs on the network link between the first edge node and the target AS being less than the number of ASs on the network link between a second edge node and the target AS, the second edge node indicating edge nodes other than the first edge node; and returning the IP address of the first edge node based on the DNS request.

[0006] In the above scheduling scheme, the infrastructure where the cloud scheduling platform resides stores edge node scheduling information. This information indicates the correspondence between at least one access request and at least one edge node's Internet Protocol (IP) address. Based on this, after receiving a DNS request from a target user, the cloud scheduling platform determines the IP address of the first edge node corresponding to the target access request based on the edge node scheduling information and returns the IP address of the first edge node to the target user. Since the number of ASs on the network link between the first edge node scheduled by the cloud scheduling platform and the target AS is less than the number of ASs on the network link between the second edge node and the target AS, when the target user's electronic device accesses the first edge node corresponding to the target domain name through the target AS, compared to accessing other edge nodes corresponding to the target domain name (e.g., the second edge node), the number of AS hops on the network link can be reduced, thereby reducing access latency and improving network communication quality.

[0007] In one possible implementation, determining the IP address of the first edge node corresponding to the target access information based on the edge node scheduling information includes: determining the IP address of each edge node corresponding to the target access information from the edge node scheduling information, wherein the IP address of each edge node is the IP address of the first edge node.

[0008] In this implementation, the edge node scheduling information directly indicates the network links with the fewest ASs. In this way, the cloud scheduling platform can directly allocate the edge nodes indicated by the edge node scheduling information to the target users, thereby helping to improve the efficiency of allocating edge nodes to target users and thus improving the user experience of the target users.

[0009] In another possible implementation, the edge node scheduling information is also used to indicate the number of edge nodes corresponding to the access information and the number of ASs on the network link between the access information and the AS indicated by the access information. Based on the edge node scheduling information, the IP address of the first edge node corresponding to the target access information is determined, including: determining the IP address of each edge node corresponding to the target access information from the edge node scheduling information; determining the IP address of the first edge node from the IP addresses of each edge node corresponding to the target access information based on the number of ASs on the network link between each edge node and the target AS; the number of ASs on the network link between the first edge node and the target AS is less than or equal to a number threshold.

[0010] In this implementation, the edge node scheduling information indicates the number of ASs on different network links. In this way, the cloud scheduling platform can allocate edge nodes to target users based on the relationship between the number of ASs on each network link and the number threshold. This not only improves the flexibility of edge node allocation by setting an appropriate number threshold, but also helps to increase the diversity of edge node allocation methods.

[0011] In another possible implementation, the DNS request includes a target source IP address, and the infrastructure also stores source IP address information. The source IP address information is used to indicate the correspondence between at least one source IP address and at least one ASN. The ASN corresponding to the source IP address is the ASN of the AS directly connected to the electronic device to which the source IP address belongs. The method further includes: determining the target ASN corresponding to the target source IP address based on the source IP address information. The target ASN is the ASN of the target AS indicated by the DNS request.

[0012] In this implementation, by pre-storing source IP address information, the ASN of the target AS can be determined based on the target source IP address indicated by the DNS request. This not only helps to simplify the amount of DNS data, but also helps to reduce the workload of the DNS server that forwards the DNS request.

[0013] In another possible implementation, the DNS request includes the ASN of the target AS. The method also includes retrieving the ASN of the target AS from the DNS request. This improves the ease and versatility of retrieving the ASN of the target AS.

[0014] In another possible implementation, the access information is also used to indicate the geographic location of the user's electronic device; the target access information is also used to indicate the target geographic location of the target user's electronic device, and the distance between the first edge node and the target geographic location is less than the distance between the second edge node and the target geographic location.

[0015] In this implementation, the distance between the selected first edge node and the target geographical location is less than the distance between the second edge node and the target geographical location, thereby selecting the edge node with the closest geographical location to the target user. This shortens the geographical distance between the target user and the edge node to be accessed, and further improves the quality of network communication.

[0016] In another possible implementation, the source IP address information is also used to indicate the correspondence between at least one source IP address and at least one location address, and the location address corresponding to the source IP address is used to indicate the location address of the electronic device to which the source IP address belongs. The method further includes: determining the target location address corresponding to the target source IP address based on the source IP address information, where the target location address is the address of the target geographical location.

[0017] In this implementation, by pre-storing source IP address information, the ASN of the target AS can be determined based on the target source IP address indicated by the DNS request. This not only helps to simplify the amount of DNS data, but also helps to reduce the workload of the DNS server that forwards the DNS request.

[0018] In another possible implementation, the DNS request includes the target location address. The method also includes retrieving the target location address from the DNS request. This improves the ease and versatility of retrieving the target location address.

[0019] In another possible implementation, the access information includes an ASN line, wherein the ASN line is used to indicate the Autonomous System Number (AS) of the Autonomous System (AS) directly connected to by the user's electronic device and the geographical location of the user's electronic device; the target access information includes a target ASN line, wherein the target ASN line is used to indicate the ASN of the target AS directly connected to by the target user's electronic device and the target geographical location of the target user's electronic device.

[0020] In this implementation, the location address and ASN indicated by the access information in the edge node scheduling information are represented by the ASN line. This reduces the number of parameters in the access information, thereby improving the retrieval efficiency of the cloud scheduling platform.

[0021] In another possible implementation, the access information includes the location address and the Autonomous System number of the AS to which the user's electronic device is directly connected, and the target access information includes the target location address and the Autonomous System number of the target AS to which the target user's electronic device is directly connected.

[0022] In another possible implementation, the target geographic location is used to indicate multiple address elements. The method further includes: combining the target ASN and a first address element among the multiple address elements to obtain the target ASN line; wherein the first address element includes any one of the name of the region indicated by the target geographic location, the name of the area indicated by the target geographic location, or the name of the province indicated by the target geographic location, with the region level being higher than the area level, and the area level being higher than the province level.

[0023] In this implementation, the cloud scheduling platform determines the ASN line corresponding to the target user based on the first address element and the target ASN. Compared with using all address elements of the target address location to determine the ASN line corresponding to the target user, this not only helps to reduce the complexity of the ASN line corresponding to the target user, but also helps to improve the diversity of the ASN line corresponding to the target user.

[0024] In another possible implementation, the infrastructure stores the priorities of at least one ASN line, wherein the address element indicated by a higher priority ASN line has a lower priority than the address element indicated by a lower priority ASN line. The target ASN line is obtained by combining a target ASN and a first address element from a plurality of address elements, including: determining a first address element from a plurality of address elements based on the priority of the at least one ASN line, wherein the priority of the ASN line corresponding to the first address element is higher than the priority of the ASN line corresponding to a second address element, and the second address element is used to indicate address elements among the plurality of address elements not used to determine an ASN line; and combining the target ASN and the first address element to obtain a first ASN line, wherein the first ASN line is the target ASN line.

[0025] In this implementation, by prioritizing the determination of high-priority ASN lines for target users, that is, prioritizing the use of low-level address elements to determine ASN lines for target users, the smaller geographical area is prioritized as the geographical location of the target user. This helps to ensure that the selection of edge nodes based on geographical location can accurately select edge nodes that are geographically close to the target user.

[0026] In another possible implementation, the method further includes: if the edge node scheduling information does not include the first ASN line, determining a third address element from multiple address elements, wherein the priority of the ASN line corresponding to the third address element is higher than the priority of the ASN line corresponding to the second address element; combining the target ASN and the third address element to obtain the second ASN line, wherein the second ASN line is the target ASN line.

[0027] In this implementation, by setting a low-level target ASN for the target user when no edge node is found on a high-priority target ASN line, the success rate of selecting an edge node for the target user can be improved.

[0028] Secondly, a cloud scheduling platform is provided. This device includes functional units for executing any of the methods provided in the first aspect, wherein the actions performed by each functional unit are implemented in hardware or by executing corresponding software via hardware. For example, the cloud scheduling platform includes a receiving module, a determining module, and a sending module. The receiving module is used to receive a Domain Name System (DNS) request from a target user. The DNS request indicates target access information, which indicates the target domain name and the ASN of the target AS directly connected to the target user's electronic device. The determining module is used to determine, based on edge node scheduling information, the IP address of a first edge node corresponding to the target access information, and that the number of ASs on the network link between the first edge node and the target AS is less than the number of ASs on the network link between a second edge node and the target AS. The second edge node indicates edge nodes other than the first edge node. The sending module is used to return the IP address of the first edge node based on the DNS request.

[0029] Thirdly, a processor is provided that can be used to execute any of the methods provided in the first aspect above.

[0030] Fourthly, a chip is provided, comprising: a processor and a power supply circuit; the power supply circuit can be used to supply power to the chip; the processor can be used to execute any of the methods provided in the first aspect above.

[0031] Fifthly, a computing device is provided, comprising: a processor, a memory, and computer programs / instructions stored in the memory; the processor executes the computer programs / instructions to cause the computing device to perform any of the methods provided in the first aspect above.

[0032] A sixth aspect provides a computing device cluster, comprising: at least one computing device, each computing device including a processor, a memory, and computer programs / instructions stored in the memory; the processor of each computing device executes the computer programs / instructions to enable the computing device cluster to implement any of the methods provided in the first aspect above.

[0033] In a seventh aspect, a computer program product is provided, comprising a computer program / instructions that, when executed by a computing device, implement any of the methods provided in the first aspect above.

[0034] Eighthly, a computer-readable storage medium is provided, on which a computer program / instructions are stored, which, when executed by a computing device, implement any of the methods provided in the first aspect above.

[0035] The technical effects of any of the implementation methods in aspects two through eight can be seen in the technical effects of different implementation methods in aspect one above, and will not be repeated here. Attached Figure Description

[0036] Figure 1 This application provides a schematic diagram of the architecture of a cloud service system.

[0037] Figure 2 A flowchart illustrating an edge node scheduling method provided in this application embodiment;

[0038] Figure 3 A schematic diagram of an ASN management interface provided in an embodiment of this application;

[0039] Figure 4 A schematic diagram of an ASN line management interface provided in an embodiment of this application;

[0040] Figure 5 A schematic diagram of a scheduling information management interface provided in an embodiment of this application;

[0041] Figure 6 A schematic diagram illustrating the scheduling of edge nodes provided in an embodiment of this application;

[0042] Figure 7 A schematic diagram of a cloud scheduling platform provided in an embodiment of this application;

[0043] Figure 8 A schematic diagram of a computing device provided in an embodiment of this application;

[0044] Figure 9 A schematic diagram of a computing device cluster provided in an embodiment of this application;

[0045] Figure 10 This is a schematic diagram of the connection of a computing device cluster provided in an embodiment of this application. Detailed Implementation

[0046] To facilitate understanding, a brief introduction to the relevant terms used in this application will be provided first.

[0047] An Autonomous System (AS), also known as an Autonomous Domain, is a collection of Internet Protocol (IP) networks and routers provided by an Internet Service Provider (ISP). IP networks and routers within an AS execute the same routing policies. Each AS has a unique Autonomous System Number (ASN). Routers within an AS communicate with each other using the Interior Gateway Protocol (IGP), while different ASes communicate with each other using the Border Gateway Protocol (BGP).

[0048] Domain name (DS): Also known as a network domain, it is the name of a computer or group of computers on the Internet, consisting of a string of names separated by dots, used to identify the electronic location of the computer during data transmission.

[0049] IP address: Used to uniquely identify a device on the Internet; that is, different devices have different IP addresses.

[0050] Domain Name System (DNS): Used to provide mapping services between domain names and IP addresses, so that users can access resources on the Internet through domain names.

[0051] A Content Delivery Network (CDN) is a network architecture that enables users to quickly access and download content by deploying server nodes across multiple geographical locations. A CDN caches content on servers in multiple geographical locations and routes user requests to the nearest server node based on the user's location, thus achieving fast access and download. The service nodes deployed across multiple geographical locations can also be called CDN nodes.

[0052] Edge nodes are nodes that allow users to access them via domain names. They can also be referred to as points of presence (POPs) provided to users.

[0053] The technical solution provided in this application will be described in detail below with reference to the accompanying drawings.

[0054] Currently, when users access edge nodes of various services through domain names, the Domain Name System (DNS) will schedule the edge node closest to the user's geographical location based on the user's geographical location.

[0055] For example, user A is located in location A. When user A accesses domain A through an electronic device, for example, domain A is www.exampleA.com, electronic device A requests DNS to assign an IP address corresponding to domain A. After receiving user A's request, DNS assigns user A the IP address of the edge node closest to location A. For example, domain A corresponds to multiple edge node IPs, where edge node A is closer to location A than other edge nodes. Based on this, DNS assigns the IP address of edge node A to user A so that user A can access edge node A through domain A.

[0056] However, although this scheduling access assigns the user the edge node closest to the user, the network communication quality when the user accesses that edge node still cannot meet the user's needs.

[0057] Therefore, improving the quality of network communication when accessing edge nodes has become an urgent technical problem to be solved.

[0058] In view of this, this application provides an edge node scheduling method applied to a cloud scheduling platform. After receiving a DNS request from a target user, the cloud scheduling platform instructs the target user's electronic device to directly connect to the target AS according to the DNS request. It determines the IP address of the first edge node corresponding to the target domain name carried in the DNS request. The number of ASs on the network link between the first edge node and the target AS is less than the number of ASs on the network links between other edge nodes and the target AS. Therefore, after the cloud scheduling platform returns the IP address of the first edge node to the target user, the target user's electronic device accesses the first edge node corresponding to the target domain name through the target AS. Compared with accessing other edge nodes corresponding to the target domain name, this reduces the number of AS hops on the network link, thereby reducing access latency and packet loss rate, and thus improving network communication quality.

[0059] For example, this edge node scheduling method is applicable to scenarios of distributed systems, which include multiple edge nodes deployed in a distributed manner, and the distributed system has a large number of clients distributed across a wide geographical area, through which users can access the server on the edge nodes.

[0060] It should be noted that the application scenarios of the edge node scheduling method in this application embodiment are not limited; the above are merely illustrative examples.

[0061] It should be noted that the various implementation methods of the above-mentioned edge node scheduling method will be discussed in [the following section]. Figure 2 The embodiments shown are described in detail, and will not be elaborated here.

[0062] Next, the system architecture involved in the technical solution provided in this application will be further described with reference to the accompanying drawings.

[0063] Figure 1 This is an architecture diagram of a cloud service system provided in an embodiment of this application. Figure 1 As shown, the cloud service system includes infrastructure and a cloud scheduling platform deployed on the infrastructure.

[0064] For example, when a user accesses an edge node via a domain name, the cloud service system receives a DNS request from the user. Then, the cloud service system schedules the IP address of the edge node for the user by executing the scheduling method described above. When the user accesses the edge node corresponding to the target domain name via the IP address of the edge node scheduled by the cloud service system, the access latency can be reduced and the quality of network communication can be improved.

[0065] For example, the edge nodes in the embodiments of this application can be edge nodes of content delivery networks, edge nodes of edge computing, edge nodes of edge clouds, etc.

[0066] It should be noted that the embodiments of this application do not limit the service type to which the edge node belongs; the above is merely an illustrative example.

[0067] In this embodiment, the cloud scheduling platform includes a parsing system. The parsing system is used to execute the aforementioned scheduling method.

[0068] Optionally, the cloud service system may include at least one resolution node, and each of the at least one resolution node has a resolution system deployed on it. Each of the at least one resolution node executes the edge node scheduling method described above through the resolution system.

[0069] In this embodiment, when the cloud service system includes multiple DNS resolution nodes, these nodes can process DNS requests from different users in parallel, which helps improve the response efficiency of DNS requests from each user. Conversely, including only one DNS resolution system in the cloud service system can reduce the cost of the cloud service system.

[0070] It should be noted that in the embodiments of this application, at least one may include one or more, and multiple refers to two or more.

[0071] For example, when a cloud service system includes multiple resolution nodes, the multiple resolution nodes can be distributed and deployed on infrastructure in different regions, or the multiple resolution nodes can be deployed on infrastructure in the same region, or some of the multiple resolution nodes can be deployed on infrastructure in the same region, while other resolution nodes can be deployed on infrastructure in different regions.

[0072] For example, M resolution nodes of a cloud service system are deployed in the same region, where M is a positive integer greater than 1. The M resolution nodes can be deployed on infrastructure in the same availability zone (AZ), or they can be deployed on infrastructure in different availability zones.

[0073] Optionally, the cloud scheduling platform may also include an address management system. This address management system manages the user's source IP address information, which includes information such as the user's location address, ASN, and ISP.

[0074] For example, the address management system can be deployed on infrastructure in the same geographic region as the resolution system, or it can be deployed on infrastructure in a different geographic region. When the address management system and the resolution system are deployed in the same geographic region, the address management system can be deployed on infrastructure in the same availability zone as the resolution system, or it can be deployed on infrastructure in a different availability zone.

[0075] Optionally, the cloud service system may include an address management node on which an address management system is deployed. This helps reduce the management cost of source IP address information.

[0076] It should be noted that the embodiments of this application do not limit the number of address management nodes configured in the cloud service system; the above is merely an illustrative example.

[0077] In this example, by using an address management system to manage the user's source IP address information, compared to having the resolution system manage the user's source IP address information, the workload of the resolution system is reduced, thereby improving the performance of the resolution system when executing edge node scheduling methods, and thus improving the user experience.

[0078] Optionally, the cloud scheduling platform may also include a scheduling system. This scheduling system is used to manage edge node scheduling information, etc.

[0079] For example, the scheduling system can be deployed on the same infrastructure as the resolution system, or it can be deployed on infrastructure in a different region. When the scheduling system and the resolution system are deployed in the same region, they can be deployed on the same infrastructure in the same availability zone, or they can be deployed on infrastructure in a different availability zone.

[0080] Optionally, the cloud service system may include a scheduling node on which a scheduling system is deployed. This helps reduce the management cost of scheduling information at edge nodes.

[0081] It should be noted that the embodiments of this application do not limit the number of scheduling nodes configured in the cloud service system; the above is merely an illustrative example.

[0082] In this example, by using a scheduling system to manage edge node scheduling information, compared to having the parsing system manage edge node scheduling information, the workload of the parsing system is reduced, thereby improving the performance of the parsing system when executing edge node scheduling methods, and ultimately improving the user experience.

[0083] For example, such as Figure 1 As shown, the cloud scheduling platform can communicate with the DNS server, and the DNS can communicate with the edge node client (hereinafter referred to as the client) running on the user's electronic device. After the user enters the target domain name on the client, the client sends a DNS request carrying the target domain name to the DNS server. After receiving the DNS request, the DNS server forwards the DNS request to the cloud scheduling platform. The cloud scheduling platform determines the IP address of the edge node corresponding to the target domain name by executing the edge node scheduling method provided in this application embodiment, and returns the IP address of the edge node corresponding to the target domain name to the client through the DNS server, so that the client can access the edge node corresponding to the target domain name through the IP address of the edge node corresponding to the target domain name.

[0084] For example, electronic devices can be tablet computers, handheld computers, personal computers (PCs), personal digital assistants (PDAs), ultra-mobile personal computers (UMPCs), laptops, netbooks, desktop computers, or all-in-one computers, etc.

[0085] It should be noted that the embodiments of this application do not limit the type of electronic device; the above is merely an illustrative example.

[0086] For example, a DNS server can be a DNS server provided by an ISP, a DNS server provided by a public DNS service provider, or a DNS server provided by an enterprise-level DNS service provider.

[0087] It should be noted that the embodiments of this application do not limit the object to which the DNS server belongs; the above is merely an illustrative example.

[0088] It should be noted that the system architecture and application scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of this application, and do not constitute a limitation on the technical solutions provided in this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new application scenarios, the technical solutions provided in this application are also applicable to similar technical problems.

[0089] For ease of understanding, the edge node scheduling method provided in this application embodiment will be described exemplarily below with reference to the above system architecture and accompanying drawings.

[0090] Figure 2 This is a flowchart illustrating an edge node scheduling method provided in an embodiment of this application. Exemplarily, the edge node scheduling method may include the following steps 201-203. The steps in this embodiment can be abbreviated as "S" and will not be described further thereafter.

[0091] The following is based on Figure 1 Taking the system architecture shown as an example, for Figure 2 The edge node scheduling method shown is illustrated by example.

[0092] Optionally, before executing S201, the cloud scheduling platform obtains the user's source IP address information and stores the obtained source IP address information.

[0093] Among them, the source IP address information is used to indicate the correspondence between at least one source IP address and at least one network access information. The source IP address is the IP address used by the user's electronic device, and the network access information includes the Autonomous System's ASN that the user's electronic device is directly connected to.

[0094] It should be noted that since the edge node clients run on the user's electronic device, the source IP address can also be called the client IP address, or the IP address corresponding to the client, which will not be elaborated further.

[0095] For ease of description, the "IP address used by the user's electronic device" will be referred to as the user's IP address, the "autonomous system directly connected to the user's electronic device" will be referred to as the user's AS, and the "ASN of the autonomous system directly connected to the user's electronic device" will be referred to as the user's ASN.

[0096] For example, the source IP address can be Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), etc.

[0097] It should be noted that the embodiments of this application do not limit the version of the source IP address; the above is merely an illustrative example.

[0098] For example, at least one source IP address includes a target source IP address, and the target source IP address can be any one of the at least one source IP address. The following uses the target source IP address as an example to illustrate the embodiments of this application.

[0099] For example, if the target source IP address is the target user's IP address, the target user's electronic device is directly connected to the target AS, and the target AS's Autonomous System Number is the target ASN, then the target network access information corresponding to the target source IP address includes the target ASN.

[0100] In this embodiment, by obtaining the user's source IP address information, the cloud scheduling platform can determine the user's ASN based on the source IP address carried in the DNS request, thereby helping to improve the diversity of ways for the cloud scheduling platform to obtain the user's ASN.

[0101] Optionally, the network access information may also include the location address of the physical location of the user's electronic device.

[0102] For example, if the target user's electronic device is located at a target physical location and the address of the target physical location is the target location address, then the target network access information includes the target location address.

[0103] It should be noted that, for ease of description, the "location address of the physical location of the user's electronic device" will be referred to as the user's location address, and will not be elaborated further.

[0104] In this embodiment, by setting the network access information to include the user's location address, the cloud scheduling platform can determine the user's location address based on the source IP address used by the user's electronic device. This allows the platform to schedule edge nodes for the user based on the user's location address, which helps to select edge nodes that are physically close to the user and thus improves the network communication quality when the user's electronic device accesses the edge nodes.

[0105] Optionally, the network access information may also include the ISP identifier of the ISP to which the user's electronic device is directly connected.

[0106] It should be noted that, for ease of description, the "ISP identifier of the ISP to which the user's electronic device is directly connected" will be referred to as the user's ISP identifier, and will not be repeated hereafter.

[0107] In this embodiment, by setting the network access information to include the user's ISP identifier, it not only helps to improve the richness of the network access information, but also allows the cloud scheduling platform to determine the user's ISP identifier based on the user's source IP address. This enables the platform to schedule edge nodes for the user based on the user's ISP identifier, thus contributing to the diversity of ways to select edge nodes for the user.

[0108] The following example, using network access information including the user's location address and ASN, illustrates the first implementation method of the cloud scheduling platform obtaining the user's source IP address information through S1-S2.

[0109] S1: The address management system obtains the user's source IP address information and sends the source IP address information to the resolution system.

[0110] One source IP address corresponds to one network entry information entry, meaning there is a one-to-one correspondence between source IP addresses and network entry information entries. One network entry information entry includes at least one ASN (Application Not Responding), meaning one source IP address corresponds to at least one ASN. One network entry information entry includes one location address, meaning one source IP address corresponds to one location address.

[0111] It should be noted that this application does not limit the number of ASNs corresponding to a single source IP address. The following example, where one source IP address corresponds to one ASN, will be used to illustrate this application.

[0112] For example, after obtaining a user's source IP address information, the address management system stores the source IP address information and sends it to the resolution system so that the resolution system can determine the user's location address and ASN based on the user's source IP address. For instance, the address management system can store the source IP address information on a physical disk provided by the infrastructure.

[0113] It should be noted that this application does not limit the method by which the address management system obtains source IP address information. For example, the address management system can obtain source IP address information provided by a third party, or it can obtain source IP address information entered manually.

[0114] For example, source IP address information is used to indicate at least one geographic location, at least one location address including a target geographic location, the target geographic location can be any one of the at least one geographic location, and the address of the target geographic location is the target location address.

[0115] The following describes an exemplary embodiment of this application, using the target geographical location as an example.

[0116] Optionally, the target location address includes multiple address elements, with different address elements having different levels. For example, the multiple address elements may include region, province, city, district, etc. Among them, the region has a higher level than the province, the province has a higher level than the city, and the city has a higher level than the district.

[0117] In one example, multiple address elements can be ordered from high to low level; for example, a location address might be in the form of Region A, Province B, City C, etc. In another example, multiple address elements can be ordered from low to high level; for example, a location address might be in the form of City C, Province B, Region A, etc.

[0118] It should be noted that the embodiments of this application do not limit the representation of the location address; the above is merely an illustrative example.

[0119] For example, the source IP address information may include the content shown in Table 1.

[0120] Table 1

[0121] Source IP address Location address Autonomous System Number 192.196.112.123 A region B province C city ASN1 192.178.113.123 A region B province C city ASN2 192.156.114.123 A region B province C city ASN3 …… …… ……

[0122] It should be noted that the representation of source IP address information in this application embodiment is not limited, and the table representation above is only for illustrative purposes.

[0123] S2: The parsing system receives source IP address information sent by the address management system and stores the source IP address information.

[0124] For example, after receiving the source IP address information from the address management system, the resolution system stores the source IP address information. For instance, the resolution system can store the source IP address information on a physical disk provided by the infrastructure.

[0125] In the above embodiments, the cloud scheduling platform obtains source IP address information through the address management system and provides it to the resolution system so that the resolution system can use the source IP address information when executing the edge node scheduling method. In this way, compared with the resolution system directly obtaining and managing the source IP address information, it helps to reduce the workload of the resolution system, thereby helping to improve the performance of the resolution system when executing the scheduling method, and thus helping to improve the user experience.

[0126] The following example illustrates the second method for cloud scheduling platforms to obtain user source IP address information, using network access information including the user's location address and ASN as examples.

[0127] Optionally, the source IP address information may include the user's ASN information. The user's ASN information indicates the correspondence between at least one source IP address and at least one ASN, where one source IP address corresponds to one or more ASNs.

[0128] It should be noted that this application does not limit the number of ASNs corresponding to a single source IP address. The following example, where one source IP address corresponds to one ASN, will be used to illustrate the embodiments of this application.

[0129] For example, when the cloud scheduling platform needs to obtain source IP address information, the address management system obtains the user's ASN information and sends it to the resolution system. After receiving the user's ASN information from the address management system, the resolution system stores the user's ASN information.

[0130] It should be noted that the process by which the cloud scheduling platform obtains the user's ASN information can be referred to in the above S1-S2 descriptions, and will not be repeated here.

[0131] Optionally, the source IP address information may include the user's location address information. The location address information indicates a correspondence between at least one source IP address and at least one location address, with one source IP address corresponding to one location address.

[0132] For example, when the cloud scheduling platform needs to obtain source IP address information, the address management system obtains the location address information and sends the user's location address information to the resolution system. After receiving the location address information sent by the address management system, the resolution system stores the location address information.

[0133] It should be noted that the process of the cloud scheduling platform obtaining location address information can be referred to the above S1-S2 descriptions, and will not be repeated here.

[0134] Optionally, before executing S201, the edge node scheduling method may further include the following S3. By executing S3, the cloud scheduling platform can obtain the ASN information of the edge node, which is used to indicate the ASN of at least one autonomous system to which the edge node is connected.

[0135] It should be noted that in the embodiments of this application, "at least one autonomous system connected to the edge node" can also be referred to as an AS that the edge node can cover, and "at least one autonomous system connected to the edge node can also be referred to as an ASN that the edge node can cover.

[0136] In one example, the autonomous systems connected to the edge nodes include those directly connected to the edge nodes. In another example, the autonomous systems connected to the edge nodes include both those directly connected to the edge nodes and those not directly connected to the edge nodes.

[0137] It should be noted that the embodiments of this application do not limit the connection method between the autonomous system indicated by the ASN information of the edge node and the edge node; the above is merely an illustrative example. The following example, "the autonomous system connected to the edge node includes an autonomous system directly connected to the edge node," will be used to illustrate the embodiments of this application.

[0138] S3: The scheduling system obtains and stores the ASN information of the edge nodes.

[0139] The ASN information of the edge node is used to indicate the correspondence between the IP address of at least one edge node and at least one ASN, and the IP address of one edge node corresponds to one or more ASNs.

[0140] It should be noted that in this embodiment of the application, different edge nodes have different IP addresses.

[0141] For example, the IP address of the edge node can be Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), etc.

[0142] It should be noted that this application embodiment does not limit the version of the IP of the edge node; the above is merely an illustrative example.

[0143] For example, at least one edge node includes a target edge node, which can be any one of the at least one edge nodes. The following description uses a target edge node as an example to illustrate embodiments of this application.

[0144] For example, the IP address of the target edge node connects to N autonomous systems, where N is a positive integer greater than or equal to 1, and the autonomous system numbers of the N autonomous systems include N ASNs. Therefore, the IP address of the target edge node corresponds to N ASNs.

[0145] For example, the administrator of the cloud dispatch platform can log in to the dispatch system via an electronic device. After logging in, the electronic device displays the ASN management interface. For instance, the ASN management interface could be... Figure 3 The interface shown in (a) is as follows. The ASN management interface includes a destination IP address control and an ASN control. The destination IP address control is used to input the IP address of the edge node, and the ASN control is used to input the ASN corresponding to the IP address of the edge node. Figure 3 As shown in (b), the administrator can enter the IP address of the edge node and the corresponding ASN on the ASN management interface. The scheduling system can then retrieve the IP address and ASN entered by the user on the ASN management interface to obtain the ASN information of the edge node. The scheduling system can then store the ASN information of the edge node. For example, the scheduling system can store the ASN information of the edge node on a physical disk provided by the infrastructure.

[0146] For example, the ASN information of an edge node may include the contents shown in Table 2.

[0147] Table 2

[0148]

[0149]

[0150] It should be noted that the representation of ASN information of edge nodes in this application embodiment is not limited, and the table representation above is only for illustrative purposes.

[0151] In the above embodiments, the cloud scheduling platform manages the ASN information of edge nodes through the scheduling system. This allows it to determine edge node scheduling information by combining the ASes that the edge node can cover. This helps ensure that the AS of the user indicated by the edge node scheduling information belongs to an AS that the edge node can cover, thereby helping to control the number of ASes in the network link between the edge node indicated by the edge node scheduling information and the user's AS. Furthermore, compared to obtaining and managing the ASN information of edge nodes through a resolution system, this reduces the workload of the resolution system, thereby improving the performance of the resolution system when executing the scheduling method, and ultimately improving the user experience.

[0152] Optionally, before executing S201, the cloud scheduling platform may also obtain line information, which is used to indicate at least one line.

[0153] In this embodiment of the application, at least one line includes at least one ASN line. The ASN line is used to indicate the user's ASN and the user's location address. At least one ASN line may include at least one of ASN_province, ASN_area, or ASN_country.

[0154] The following is an exemplary description of the process by which the cloud scheduling platform obtains at least one ASN line through S4.

[0155] S4: The scheduling system obtains the user's ASN line information.

[0156] The ASN line information is used to indicate at least one ASN line corresponding to at least one ASN, wherein one ASN corresponds to one or more ASN lines.

[0157] In one example, the administrator of the cloud dispatch platform can log in to the dispatch system via an electronic device. After logging in, the electronic device displays the ASN line management interface. For example, the ASN line management interface could be... Figure 4The interface shown in (a) is as follows. The ASN line management interface includes an ASN control and an ASN line control. The ASN control is used to indicate the input ASN, and the ASN line control is used to indicate the input ASN line. Figure 4 As shown in (b), the administrator can enter the ASN and its corresponding ASN line on the ASN line management interface. The scheduling system can then obtain the ASN and its corresponding ASN line entered by the user on the ASN line management interface, thus obtaining the user's ASN line information. After obtaining the user's ASN line information, the scheduling system can store it. For example, the scheduling system can store the user's ASN line information on a physical disk provided by the infrastructure.

[0158] For example, ASN line information includes the contents shown in Table 3.

[0159] Table 3

[0160] Autonomous System Number ASN Line ASN1 ASN1_A region, ASN1_B province ASN2 ASN2_A region, ASN2_B province ASN3 ASN2_A region, ASN2_B province

[0161] It should be noted that the representation of the user's ASN line information in this application embodiment, as shown in the table above, is for illustrative purposes only.

[0162] In another example, the cloud scheduling platform's scheduling system can obtain source IP address information and automatically determine the user's ASN information based on the source IP address information. For example, referring to Table 1, based on the correspondence between region A, province B, city C, and ASN1, the ASN line corresponding to ASN1 can include ASN1_region A, ASN1_area E, ASN1_province B, etc.

[0163] For example, the infrastructure where the scheduling system is located stores a mapping between regions and provinces. The scheduling system can determine the region corresponding to ASN1 based on the province corresponding to ASN1, and thus determine the ASN line.

[0164] In the above embodiments, the cloud scheduling platform manages the user's ASN line information through the scheduling system. This allows it to combine the user's ASN and location address to determine edge node scheduling information, thus helping to select the network link with the closest geographical location and the fewest AS hops for the user. Furthermore, compared to managing the user's ASN line information through a resolution system, this reduces the workload of the resolution system, thereby improving its performance when executing scheduling methods and ultimately enhancing the user experience.

[0165] Optionally, at least one line may further include at least one of the following: a custom line (custom_view), an ISP line, a province-name line (province), an area-name line (area), a country-name line (country), a continent-name line (continent_legacy), an abroad default line (abroad), or a default line (default_view). The ISP line includes ISP_province (isp_province), ISP_area (isp_area), and ISP_country (isp_country).

[0166] For example, the province name line can include the province A line, the region name line can include the region E line, the area name line can include the area A line, the ISP_province name can include ISP1_B province, the ISP_region name can include ISP1_E region, and the ISP_area name can include ISP1_A area.

[0167] It should be noted that for information regarding ISP lines, please refer to the above explanation of ASN lines; it will not be repeated here.

[0168] Optionally, the cloud scheduling platform can also obtain custom line information, which is used to indicate the source IP address corresponding to the custom line.

[0169] For example, the scheduling system acquires and stores custom line information. Then, the scheduling system sends the custom line information to the resolution system. Upon receiving the custom line information, the resolution system stores it. For instance, the resolution system can store the custom line information on a physical disk provided by the infrastructure. Later, when the resolution system executes the edge node scheduling method, it can determine whether the user can use the custom line based on the source IP address carried in the user's DNS request, thereby determining whether the edge node used by the user can be determined based on the custom line. For example, if the source IP address carried in the DNS request belongs to the source IP address corresponding to the custom line, then the address of the edge node can be determined for the user based on the custom line. Conversely, if the source IP address carried in the DNS request does not belong to the source IP address corresponding to the custom line, then the IP address of the edge node cannot be determined for the user based on the custom line.

[0170] In this embodiment, by obtaining custom line information, it is possible to determine whether the user's source IP address belongs to the custom line, thereby determining whether the edge node used by the user can be determined based on the custom line, which helps to improve the diversity of ways to schedule edge nodes for users.

[0171] Optionally, the cloud scheduling platform can also obtain information about default lines outside the domain, which is used to indicate the source IP address corresponding to the default line outside the domain.

[0172] It should be noted that for information regarding default external line information, please refer to the above explanation of custom line information; it will not be repeated here.

[0173] Optionally, the cloud scheduling platform can also obtain default line information, which is used to indicate the source IP address corresponding to the default line.

[0174] It should be noted that for information regarding default line information, please refer to the above explanation regarding custom line information; it will not be repeated here.

[0175] Optionally, the edge node scheduling method may further include: the scheduling system acquiring line priority information and storing the line priority information.

[0176] The line priority information is used to indicate the priority of each line in at least one line. In other words, the line priority information can be used to indicate the priority of each ASN line in at least one ASN line.

[0177] For example, the priority of each line in at least one line, from high to low, is as follows: custom line, ASN line, ISP line, province name, region name, area name, continent name, external default, and default line.

[0178] For example, the priorities of at least one ASN line, from highest to lowest, are: ASN_province name, ASN_area name, and ASN_region name. The address element indicated by a higher-priority ASN line has a lower level than the address element indicated by a lower-priority ASN line. For instance, the ASN_province name has a higher priority than the ASN_area name; the address element indicated by the ASN_province name is "province," while the address element indicated by the ASN_area name is "area," with "province" having a lower level than "area."

[0179] For example, the priority of ISP lines from high to low is as follows: ISP_province name, ISP_region name, ISP_location name.

[0180] In the above embodiments, by managing line priority information, when the cloud scheduling platform determines multiple ASN lines based on the user's DNS request, the IP address of the edge node can be determined through the ASN line with the highest priority, which helps to reduce the number of times the edge node is determined. This can improve the efficiency of determining the edge node and improve the user experience.

[0181] Optionally, before executing S201, the edge node scheduling method may also include the following S5-S6. By executing S5-S6, the cloud scheduling platform can obtain the edge node scheduling information.

[0182] S5: The scheduling system obtains the edge node scheduling information and sends the edge node scheduling information to the parsing system.

[0183] Among them, the edge node scheduling information is used to indicate the correspondence between at least one access information and at least one edge node IP address, and the access information is used to indicate the target domain name of the edge node and the ASN of the autonomous system directly connected to the user's electronic device.

[0184] It should be noted that, for ease of description, the IP address of the edge node will be referred to as the destination IP address below, and will not be repeated hereafter.

[0185] In this application embodiment, access information includes various situations, which are illustrated below by examples from situations a to c.

[0186] In case a, the access information is only used to indicate the target domain name of the edge node and the ASN of the AS directly connected to the user's electronic device.

[0187] In this scenario, by setting access information to indicate the user's ASN, the IP address of the edge node that the user can use can be determined based on the ASN indicated by the DNS request and the edge node scheduling information, which helps to select the edge node with the fewest AS hops for the user.

[0188] In case b, the access information is used to indicate the target domain name of the edge node, the ASN of the AS directly connected to the user's electronic device, and the location address of the geographical location of the user's electronic device.

[0189] In this scenario, by setting access information to indicate the user's location address, the IP address of the edge node that the user can use can be determined based on the location address indicated by the DNS request and the edge node scheduling information, which helps to select the edge node with the closest physical location for the user.

[0190] In case c, the access information is used to indicate the target domain name of the edge node and the user's ASN line, wherein the user's ASN line is used to indicate the ASN of the AS directly connected to the user's electronic device and the location address of the geographical location of the user's electronic device.

[0191] In this scenario, the user's ASN and location address are indicated via the ASN line. This reduces the number of parameters included in the access information, which not only helps to improve the difficulty of managing edge node scheduling information but also helps to improve the speed of traversing edge node scheduling information. This, in turn, helps to improve the speed of executing edge node scheduling methods and improves the user experience.

[0192] In this embodiment of the application, the edge node scheduling information includes multiple cases, which are illustrated below by case 1 and case 2.

[0193] Case 1: The number of ASs on the network link between an edge node corresponding to an access message and an AS indicated by the access message is less than the number of ASs on the network link between an edge node not corresponding to an access message and an AS indicated by the access message.

[0194] For example, at least one access information includes access information 1, which can be any one of the at least one access information, wherein the access information includes domain name 1 and ASN 1, and ASN 1 is the ASN of AS1.

[0195] Example 1a: Edge node scheduling information is used to indicate the IP address of edge node 1 corresponding to access information 1. The number of ASs on the network link between edge node 1 and AS1 is less than the number of ASs on the network links between other edge nodes 1 and AS1. "Other edge nodes 1" indicates at least one edge node other than edge node 1.

[0196] It should be noted that if the number of ASs on the network link between edge node 1 and AS1 is 0, it can be considered that edge node 1 and AS1 are directly connected.

[0197] Example 1b: Edge node scheduling information is used to indicate the IP address of edge node 1 and the IP address of edge node 2 corresponding to access information 1. The number of ASs on the network link between edge node 1 and AS1, and the number of ASs on the network link between edge node 2 and AS1 are both less than the number of ASs on the network link between other edge nodes 2 and AS1. Other edge nodes 2 are used to indicate at least one edge node other than edge node 1 and edge node 2.

[0198] In one example, combining the above case a, the edge node scheduling information may include the contents shown in Table 4.

[0199] Table 4

[0200] domain name Autonomous System Number IP address of edge node www.example.com ASN1 100.200.123.112 www.example.com ASN2, ASN3 100.210.123.112 www.example.com ASN2, ASN3 100.220.123.112 www.example.com ASN4 100.230.123.112

[0201] It should be noted that the representation of edge node scheduling information in this application embodiment is not limited, and the table representation above is only for illustrative purposes.

[0202] In another example, combined with case b above, the edge node scheduling information may include the content shown in Table 5.

[0203] Table 5

[0204] domain name Autonomous System Number Location address IP address of edge node www.example.com ASN1 A region B province C city 100.200.123.112 www.example.com ASN2, ASN3 A region B province C city 100.210.123.112 www.example.com ASN2, ASN3 A region B province C city 100.220.123.112 www.example.com ASN4 A region B province C city 100.230.123.112

[0205] It should be noted that the representation of edge node scheduling information in this application embodiment is not limited, and the table representation above is only for illustrative purposes.

[0206] In yet another example, combined with case c above, the edge node scheduling information may include the contents shown in Table 6.

[0207] Table 6

[0208] domain name ASN Line IP address of edge node www.example.com ASN1_B Province 100.200.123.112 www.example.com ASN2_B Province, ASN3_B Province 100.210.123.112 www.example.com ASN2_B Province, ASN3_B Province 100.220.123.112 www.example.com ASN4_B Province 100.230.123.112

[0209] It should be noted that the representation of edge node scheduling information in this application embodiment is not limited, and the table representation above is only for illustrative purposes.

[0210] In this scenario, by setting edge node scheduling information to directly indicate edge nodes with fewer ASs on the network link, the edge nodes indicated by the edge node scheduling information can be selected when scheduling edge nodes for users, thereby improving the efficiency of scheduling edge nodes for users and thus improving the user experience.

[0211] In scenario 2, edge node scheduling information is also used to indicate the number of edge nodes corresponding to the access information and the number of ASs on the network link of the AS indicated by the access information.

[0212] Example 2a: The scheduling information is used to indicate the IP address of the edge node 1 corresponding to access information 1, and the number of ASs on the network link between edge node 1 and AS1.

[0213] In one example, combining the above case a, the edge node scheduling information may include the contents shown in Table 7.

[0214] Table 7

[0215] domain name Autonomous System Number Number of ASs on a network link IP address of edge node www.example.com ASN1 0 100.200.123.112 www.example.com ASN1 3 100.210.123.112 www.example.com ASN2 0 100.210.123.112 www.example.com ASN2 0 100.220.123.112 www.example.com ASN2 4 100.200.123.112 www.example.com ASN3 0 100.210.123.112 www.example.com ASN3 1 100.220.123.112 www.example.com ASN4 3 100.230.123.112

[0216] In another example, combining the above scenario b, the edge node scheduling information may include the contents shown in Table 8.

[0217] Table 8

[0218]

[0219] In yet another example, combined with case c above, the edge node scheduling information may include the contents shown in Table 9.

[0220] Table 9

[0221] domain name ASN Line Number of ASs on a network link IP address of edge node www.example.com ASN1_B Province 0 100.200.123.112 www.example.com ASN1_B Province 3 100.210.123.112 www.example.com ASN2_B Province 0 100.210.123.112 www.example.com ASN2_B Province 0 100.220.123.112 www.example.com ASN2_B Province 4 100.200.123.112 www.example.com ASN3_B Province 0 100.220.123.112 www.example.com ASN3_B Province 1 100.220.123.112 www.example.com ASN3_B Province 3 100.230.123.112

[0222] In this scenario, by setting the edge node scheduling information to indicate the number of ASs on the network link, it helps to increase the diversity of ways and choices for scheduling edge nodes for users, thereby improving the user experience.

[0223] The following section combines scenarios c and 1 to introduce various ways for the cloud scheduling platform to obtain edge node scheduling information.

[0224] In one example, the scheduling system can automatically determine edge node scheduling information based on the user's source IP address, the edge node's ASN information, ASN line information, and domain name information. The domain name information indicates the domain name corresponding to the edge node's IP address.

[0225] In this embodiment, the cloud scheduling platform automatically generates edge node scheduling information through the scheduling system, which helps to improve the convenience and diversity of methods for obtaining edge node scheduling information.

[0226] In another example, the administrator of the cloud scheduling platform can log in to the scheduling system via an electronic device. After logging in, the electronic device displays a scheduling information management interface. For example, the scheduling information management interface could be... Figure 5 The interface shown in (a) is as follows. The scheduling information principle interface includes a domain name control, an access information control, and a destination IP address control. The domain name control indicates the domain name of the edge node, the access information control indicates the user's access information, and the destination IP address control indicates the IP address of the edge node. For example, as shown... Figure 5 As shown in (b), the administrator can enter the domain name, access information, and the corresponding edge node's IP address on the scheduling information management interface. The scheduling system then obtains the domain name, access information, and the IP address of the edge node corresponding to the accessed node from the user's input on the scheduling information management interface, thus acquiring the edge node scheduling information. After obtaining the edge node scheduling information, the scheduling system can store it. For example, the scheduling system can store the edge node scheduling information on a physical disk provided by the infrastructure.

[0227] For example, the edge node scheduling information includes multiple entries, and each entry includes access information and a correspondence between an edge node. The multiple entries include a target entry, which can be any one of the multiple entries. The following description uses a target entry as an example to illustrate the embodiments of this application.

[0228] Optionally, the edge node scheduling method further includes: the scheduling system acquiring the target entry; and if the ASN indicated by the ASN line in the target entry does not belong to the ASN corresponding to the destination IP address in the target entry, the scheduling system outputting a prompt message.

[0229] The prompt information indicates that the ASN indicated by the ASN line in the target entry does not belong to the ASN corresponding to the destination IP address (i.e., the IP address of the edge node) in the target entry.

[0230] For example, when the scheduling system retrieves entry 1, if the ASN indicated by the ASN line in entry 1 does not belong to the ASN corresponding to the destination IP address in entry 1, the scheduling system outputs a prompt message. When the scheduling system retrieves entry 2, if the ASN indicated by the ASN line in entry 2 belongs to the ASN corresponding to the destination IP address in entry 2, the scheduling system does not output a prompt message.

[0231] For example, entry 1 includes ASN2_B and 100.200.123.112. ASN2_B indicates ASN2. Referring to Table 2, since ASN2 is not the ASN corresponding to 100.200.123.112, the scheduling system outputs a prompt message. As another example, referring to Table 6, entry 2 includes ASN1_B as shown in the second row of Table 6 and 100.200.123.112. ASN1_B indicates ASN1. Referring to Table 2, the ASN corresponding to 100.200.123.112 is ASN1; therefore, the scheduling system does not output a prompt message.

[0232] In the above embodiments, if the ASN indicated by the ASN line in the target entry does not belong to the ASN corresponding to the destination IP address in the target entry, the scheduling system outputs a prompt message. This can remind the administrator that the ASN indicated by the ASN line in the target entry is not an ASN that the edge node can cover, so that the administrator can adjust the ASN line in the target entry in a timely manner so that the ASN indicated by the ASN line in the target entry is an ASN that the edge node can cover.

[0233] S6: The parsing system receives edge node scheduling information sent by the scheduling system and stores the edge node scheduling information.

[0234] For example, after receiving edge node scheduling information from the address management system, the resolution system stores the edge node scheduling information. For instance, the resolution system can store the edge node scheduling information on a physical disk provided by the infrastructure.

[0235] In the above embodiments, the cloud scheduling platform obtains edge node scheduling information through the address management system and provides it to the resolution system. This allows the resolution system to schedule the IP address of the edge node for the user based on the edge node scheduling information when executing the edge node scheduling method. Compared to the resolution system obtaining and managing the edge node scheduling information, this helps reduce the workload of the resolution system, thereby improving the performance of the resolution system when executing the scheduling method and ultimately improving the user experience.

[0236] The above embodiments detail the scheme for managing edge node scheduling information by the cloud scheduling platform. Below, in conjunction with S201-S203, we describe the scheme for the cloud scheduling platform to schedule edge nodes for users based on edge node scheduling information.

[0237] S201: The cloud scheduling platform requests to receive a DNS request from the target user. The DNS request is used to indicate the target access information, which is used to indicate the target domain name and the target user's ASN.

[0238] In this embodiment, the DNS request may include a target domain name. The target domain name is the domain name of the edge node that the target user wants to access.

[0239] Optionally, the DNS request may also include the target source IP address. The target source IP address is the IP address of the target user's electronic device.

[0240] In this embodiment, by setting the DNS request to include the target source IP address, the cloud scheduling platform can determine the target geographical location address of the target user's electronic device, the autonomous system number of the target AS directly connected to the target user's electronic device, etc., based on the IP address of the target user's electronic device. This helps to improve the diversity of ways to determine the target geographical location address and the autonomous system number of the target AS.

[0241] In one example, a client running on an edge node is connected to the target user's electronic device. The user enters a target domain name, such as www.example.com, on the client's interface. The electronic device then sends a DNS request to the DNS server via the client. Upon receiving the DNS request, the DNS server forwards it to a cloud scheduling platform deployed on the infrastructure. The cloud scheduling platform then receives the DNS request from the target user. For example, the DNS server forwards the DNS request to the cloud scheduling platform's resolution system, and the cloud scheduling platform receives the DNS request from the target user through its resolution system.

[0242] In another example, electronic devices can also send DNS requests to the cloud scheduling platform via a client.

[0243] Example a1, the target user includes user a, the DNS request includes DNS request a, the cloud scheduling platform receives DNS request a from user a, the DNS request includes www.example.com and 192.196.112.123.

[0244] Example b1, the target user includes user b, the DNS request includes DNS request b, the cloud scheduling platform receives DNS request b from user b, DNS request b includes www.example.com and 192.178.113.123.

[0245] Example c1, the target user includes user c, the DNS request includes DNS request c, the cloud scheduling platform receives DNS request c from user c, the DNS request includes www.example.com and 192.156.114.123.

[0246] It should be noted that the embodiments of this application do not limit the way the cloud scheduling platform obtains DNS requests; the above is merely an illustrative example.

[0247] S202: The cloud scheduling platform determines the IP address of the first edge node corresponding to the target access information indicated by the DNS request based on the edge node scheduling information. The target access information indicates the ASN of the target AS directly connected to the target domain name and the target user's electronic device.

[0248] The number of ASs on the network link between the first edge node and the target AS is less than the number of ASs on the network link between the second edge node and the target AS. The second edge node is used to indicate edge nodes other than the first edge node.

[0249] For example, after receiving a DNS request from a target user, the cloud scheduling platform determines the IP address of the first edge node corresponding to the target access information indicated in the DNS request, based on the edge node scheduling information. The number of ASs on the network link between the first edge node and the target AS is less than the number of ASs on the network links between other edge nodes and the target AS.

[0250] It should be noted that the first edge node in the embodiments of this application refers to a type of edge node, and the number of ASs on the network link between this type of edge node and the target AS is less than the number of ASs on the network link between other edge nodes and the target AS.

[0251] In this embodiment of the application, the edge node scheduling method further includes: the cloud scheduling platform obtaining the target network access information indicated by the DNS request.

[0252] In one implementation, the cloud scheduling platform determines the target network access information corresponding to the target source IP address based on the source IP address information, thereby obtaining the target network access information indicated by the DNS request, and then obtaining the target access information indicated by the DNS request. The target access information includes the target domain name and the target network access information.

[0253] Example 1: The target network access information includes the target ASN of the target AS directly connected to the target user's electronic device.

[0254] Example a2, combined with example a1 above, after the resolution system obtains the DNS request a, it determines that 192.196.112.123 corresponds to the target network access information a1, and the target network access information a1 includes ASN1.

[0255] Example b2, combined with example b1 above, after the resolution system obtains the DNS request b, it determines that 192.196.112.123 corresponds to the target network access information b1, and the target network access information b1 includes ASN2.

[0256] Example c2, combined with example c1 above, after the resolution system obtains the DNS request c, it determines that 192.196.112.123 corresponds to the target network access information c1, and the target network access information c1 includes ASN3.

[0257] In this example, by setting the target network access information to include the target user's target ASN, edge nodes can be scheduled for the target user based on the target user's target ASN. This helps to select edge nodes with fewer ASs on the network link for the target user, thereby reducing the number of ASs on the network link for the target user's electronic devices to access the edge node, reducing the latency of the target user's electronic devices to access the edge node, and improving the network communication quality when the target user's electronic devices access the edge node.

[0258] Example 2: The target network access information includes the target location address of the target user's electronic device and the target ASN of the target AS directly connected to the target user's electronic device.

[0259] Example a3, combined with example a1 above, after the resolution system obtains the DNS request a, it determines that 192.196.112.123 corresponds to the target network access information a2, which includes region A, province B, city C, and ASN1.

[0260] Example b3, combined with example b1 above, after the resolution system obtains the DNS request b, it determines that 192.196.112.123 corresponds to the target network access information b2, which includes region A, province B, city C, and ASN2.

[0261] Example c3, combined with example c1 above, after the resolution system obtains the DNS request c, it determines that 192.196.112.123 corresponds to the target network access information c2, which includes region A, province B, city C, and ASN3.

[0262] In this embodiment, by setting the target network access information to include the target user's target location address, edge nodes can be scheduled for the target user based on the target user's target location address. This helps to select edge nodes that are geographically close to the target user, thereby further improving the network communication quality when the target user's electronic device accesses the edge node.

[0263] In the above implementation, the cloud scheduling platform obtains the target network access information indicated by the DNS request based on the source IP address information. This not only helps to simplify the complexity of DNS requests, but also helps to improve the diversity of ways to obtain the target network access information indicated by the DNS request.

[0264] In another implementation, the DNS request includes target network access information. The cloud scheduling platform resolves the DNS request to obtain the target network access information indicated by the DNS request, and then obtains the target access information indicated by the DNS request. For example, after receiving the initial DNS request from the target user, the DNS server obtains the target network access information based on the target source IP address carried in the DNS request. Then, based on the target network access information and the initial DNS request, the DNS server obtains the target user's DNS request and forwards it to the cloud scheduling platform. This helps improve the convenience and versatility of the cloud scheduling platform in obtaining target network access information.

[0265] In this application embodiment, the first edge node includes multiple cases, which are illustrated below by case A and case B.

[0266] Case A: The number of ASs on the network link between the first edge node and the target AS is less than the number of ASs on the network link between the second edge node and the target AS. The second edge node is used to indicate edge nodes other than the first edge node.

[0267] The following describes the process of determining the IP address of the first edge node, using methods 1 to 2, in conjunction with scenario A.

[0268] Method 1, in conjunction with Example 1 above, the cloud scheduling platform determines that the IP address of the edge node corresponding to the target domain name and the target ASN in the edge node scheduling information is the IP address of the first edge node.

[0269] Example a4, combined with Example a2 and Table 4 above, the parsing system determines that the IP address of the edge node corresponding to www.example.com and ASN1 is 100.200.123.112. For example, 100.200.123.112 is the IP address of edge node a.

[0270] Example b4, combined with Example b2 above and Table 4 above, the parsing system determines that the IP addresses of the edge nodes corresponding to www.example.com and ASN2 are 100.210.123.112 and 100.220.123.112, respectively. For example, 100.210.123.112 is the IP address of edge node b, and 100.220.123.112 is the IP address of edge node c.

[0271] In example c4, combined with example c2 and Table 4 above, the parsing system determines that the IP addresses of the edge nodes corresponding to www.example.com and ASN3 are 100.210.123.112 and 100.220.123.112, respectively.

[0272] Method 2, combined with Example 1 above, involves the cloud scheduling platform determining the target domain name and the IP address of the first edge node corresponding to the target ASN from the edge node scheduling information. Specifically, the number of ASs on the network link between the first edge node and the target AS is less than or equal to a certain threshold.

[0273] Optionally, the quantity threshold can be any value between 0 and 2.

[0274] It should be noted that the embodiments in this application do not impose any limitation on the quantity threshold; the above is merely an illustrative example. The quantity threshold can be dynamically determined based on the actual network link between the user's AS and the edge node.

[0275] In one example, the quantity threshold is 0. This allows for the selection of directly connected edge nodes for users, thereby minimizing the impact of accessing edge nodes and ultimately improving the quality of network communication when accessing them.

[0276] Example a5, combined with Example a2 and Table 7 above, shows that ASN1 is the Autonomous System Number of AS1. There are 0 ASs on the network link between 100.200.123.112 (i.e., edge node a) and AS1, meaning edge node a is directly connected to AS1. There are 3 ASs on the network link between 100.210.123.112 (i.e., edge node b) and AS1. Based on this, the resolution system can determine that the IP address of the first edge node corresponding to www.example.com and ASN1 is 100.200.123.112.

[0277] Example b5, combined with Example b2 above and Table 7 above, ASN2 is the Autonomous System Number of AS2. 100.210.123.112 (i.e., edge node b) has 0 ASs on its network link with AS2, meaning edge node b is directly connected to AS2. 100.220.123.112 (i.e., edge node c) has 0 ASs on its network link with AS2, meaning edge node c is directly connected to AS2. 100.200.123.112 (i.e., edge node d) has 4 ASs on its network link with AS2. Based on this, the resolution system can determine that the IP address of the first edge node corresponding to www.example.com and ASN2 is at least one of 100.210.123.112 or 100.220.123.112.

[0278] In another example, the quantity threshold is 2. This allows the user to select more edge nodes, thus increasing the diversity of choices and improving the user experience.

[0279] In another example, the quantity threshold is 1. This not only helps to select fewer edge nodes with fewer ASs on the user's network link, but also helps to balance the number of edge nodes selected for the user.

[0280] In example c5, combining with example c2 above and Table 7 above, ASN3 is the Autonomous System Number of AS3. There are 0 ASs on the network link between 100.210.123.112 (i.e., edge node b) and AS3, meaning edge node b is directly connected to AS3. There is 1 AS on the network link between 100.220.123.112 (i.e., edge node c) and AS3. Based on this, the resolution system can determine that the IP address of the first edge node corresponding to www.example.com and ASN2 is at least one of 100.210.123.112 or 100.220.123.112.

[0281] In this scenario, by selecting network links with fewer ASs between the edge node and the target AS, the number of AS hops on the network links connecting the target user's electronic devices to the edge node can be reduced, thereby reducing the latency of the target user's electronic devices accessing the edge node and improving the network communication quality when the target user's electronic devices access the edge node.

[0282] In case B, the number of ASs on the network link between the first edge node and the target AS is less than the number of ASs on the network link between the second edge node and the target AS. The second edge node is used to indicate edge nodes other than the first edge node, and the distance between the first edge node and the target geographical location is less than the distance between at least some of the second edge nodes and the target geographical location.

[0283] In this scenario, by selecting network links that are closer to the target location address than the edge node, the physical distance when the target user's electronic device accesses the edge node can be reduced, thereby helping to further improve the network communication quality when the target user's electronic device accesses the edge node.

[0284] The following describes the process of determining the IP address of the first edge node, using methods 3 and 4, in conjunction with scenario B.

[0285] Method 3: The cloud scheduling platform determines the target domain name, target location address, and IP address of the first edge node corresponding to the target ASN based on the edge node scheduling information.

[0286] Example 3: The cloud scheduling platform determines that the IP address of the edge node corresponding to the target domain name, target location address, and target ASN in the edge node scheduling information is the IP address of the first edge node.

[0287] It should be noted that the relevant explanations for Example 3 can be found in the explanations for Method 1 above, and will not be repeated here.

[0288] Example 4: The cloud scheduling platform determines the target domain name, target location address, and the IP address of the first edge node corresponding to the target ASN from the edge node scheduling information. The number of ASs on the network link between the first edge node and the target AS is less than or equal to a certain threshold.

[0289] It should be noted that the relevant explanations for Example 4 can be found in the explanations for Method 2 above, and will not be repeated here.

[0290] In this approach, the edge node corresponding to the target domain name is determined by the target location and the target ASN, which helps to simplify the steps of determining the edge node and thus improves the efficiency of edge node determination.

[0291] Method 4: The cloud scheduling platform determines the IP address of the first edge node corresponding to the target domain name and the target ASN line based on the edge node scheduling information. In other words, the target access information includes the target ASN line, which indicates the ASN of the target AS directly connected to by the target user's electronic device and the target geographical location of the target user's electronic device.

[0292] Optionally, the edge scheduling method may further include: the cloud scheduling platform determining the target ASN line indicated by the DNS request based on the target location address and target ASN indicated by the DNS request.

[0293] For example, the target geographic location is used to indicate multiple address elements. The cloud scheduling platform's parsing system combines the target ASN with the first address element among the multiple address elements to obtain the target ASN line. The first address element includes any one of the following: the name of the region indicated by the target geographic location, the name of the area indicated by the target geographic location, or the name of the province indicated by the target geographic location. The region level is higher than the area level, and the area level is higher than the province level. For example, referring to Table 1, the multiple address elements include Region A, Province B, and City C, where Province B belongs to Area E. Based on this, the first address element can include any one of Province B, Area E, or Region A.

[0294] Optionally, the cloud scheduling platform may determine the target ASN line indicated by the DNS request based on the target location address and target ASN. This may include the cloud scheduling platform determining the target ASN line indicated by the DNS request based on the priority of each ASN line among at least one ASN line. The following sections (S7-S8) describe the process of determining the target ASN line indicated by the DNS request based on the priority of each ASN line among at least one ASN line.

[0295] S7: The cloud scheduling platform determines the first address element from multiple address elements based on the priority of at least one ASN line.

[0296] The ASN line corresponding to the first address element has a higher priority than the ASN line corresponding to the second address element. The second address element is used to indicate the address element among multiple address elements that was not used to determine the ASN line.

[0297] For example, the priorities of ASN lines from high to low are: ASN_province name, ASN_region name, or ASN_location name. According to Table 1, after the cloud scheduling platform's resolution system receives the DNS request, it determines province B as the first address element based on the fact that the priority of the ASN line corresponding to province B is higher than the priority of the ASN line corresponding to region E and the priority of the ASN line corresponding to region A.

[0298] S8: The cloud scheduling platform combines the target ASN and the first address element to obtain the first ASN line, wherein the first ASN line is the target ASN line.

[0299] For example, after obtaining the first address element, the cloud scheduling platform's parsing system combines the target ASN with the first address element. Referring to Table 1, the parsing system combines ASN1 with province B to obtain ASN1_province B, which is the target ASN line. Then, based on the target domain name and ASN1_province B, the parsing system traverses the edge node scheduling information to find the IP address of the edge node corresponding to the target domain name and ASN1_province B.

[0300] In the above embodiments, when multiple address elements indicated by the target geographic location correspond to multiple ASN lines, the ASN line with higher priority is determined first. This helps to determine the edge node closest to the physical location of the target user based on the target ASN line, thereby helping to improve the user's network communication quality.

[0301] Optionally, the edge node scheduling method may also include the following S9-S10.

[0302] S9: If the edge node scheduling information does not include the first ASN line, determine the third address element from multiple address elements. The ASN line corresponding to the third address element has a higher priority than the ASN line corresponding to the second address element.

[0303] For example, when the parsing system searches for edge node scheduling information, it terminates the process if it finds the IP address of the edge node corresponding to the target domain name and province ASN1_B. If the parsing system does not find the IP address of the edge node corresponding to the target domain name and province ASN1_B, that is, if the edge node scheduling information does not include the first ASN line, the parsing system determines the next target ASN line. Based on this, the parsing system determines the third address element from multiple address elements. Referring to Table 1, the third address element is region E.

[0304] S10: Combine the target ASN and the third address element to obtain the second ASN line, which is the target ASN line.

[0305] For example, after obtaining the third address element, the resolution system combines the target ASN with the third address element. Referring to Table 1, the resolution system combines ASN1 with the E region, resulting in ASN1_E region, which represents the target ASN line. Then, based on the target domain name and the ASN1_E region, the resolution system traverses the edge node scheduling information to find the IP address of the edge node corresponding to the target domain name and the ASN1_E region.

[0306] For example, the resolution system can repeat steps S8-S9 until it finds the target domain name indicated by the DNS request and the IP address of the edge node corresponding to the target ASN line.

[0307] In the above embodiments, when no corresponding edge node IP address is found for a determined target ASN line, the cloud scheduling platform continues to determine the next level of ASN line to query the edge node IP address. This helps to improve the success rate of scheduling edge nodes for target users.

[0308] The implementation process of method 4 will be illustrated below through examples 5 and 6.

[0309] Example 5: The cloud scheduling platform determines that the IP address of the edge node corresponding to the target domain name and the target ASN line in the edge node scheduling information is the IP address of the first edge node.

[0310] It should be noted that the relevant explanations for Example 5 can be found in the explanations for Method 1 above, and will not be repeated here.

[0311] Example 6: The cloud scheduling platform determines the target domain name and the IP address of the first edge node corresponding to the target ASN line from the edge node scheduling information. The number of ASs on the network link between the first edge node and the target AS is less than or equal to a certain threshold.

[0312] It should be noted that the relevant explanations for Example 6 can be found in the explanations for Method 2 above, and will not be repeated here.

[0313] In this approach, by indicating the target ASN line of the target location and the target ASN, the edge node corresponding to the target domain name is determined, which helps to improve the efficiency of traversing the edge node scheduling information, and thus helps to improve the efficiency of determining the edge node.

[0314] Optionally, the edge scheduling method may further include: if the edge node scheduling information does not include the target ASN line, the cloud scheduling platform determines the target line indicated by the DNS request; the cloud scheduling platform determines the IP address of the edge node corresponding to the target domain name and the target line based on the edge node scheduling information. The target line may include at least one of the following: a custom line, an ISP line, a province-name line, a region-name line, a geographical area-name line, a continent-name line, an external default line, or a default line.

[0315] It should be noted that the process of determining the IP address of the edge node corresponding to the target line can be referred to the above explanation of determining the IP address of the edge node corresponding to the target ASN line, and will not be repeated here.

[0316] In the above embodiments, by determining the target line indicated by the DNS request and the IP address of the edge node corresponding to the target line, it not only helps to improve the diversity of ways to schedule edge nodes for users, but also helps to improve the success rate of scheduling edge nodes for users.

[0317] S203: The cloud scheduling platform returns the IP address of the first edge node based on a DNS request.

[0318] For example, after the cloud scheduling platform's DNS resolution system obtains the IP address of the first edge node, it returns the IP address of the first edge node to the client on the target user's electronic device via DNS. Upon receiving the IP address of the first edge node, the client on the target user's electronic device accesses the first edge node using that IP address.

[0319] Example a, such as Figure 6 As shown, client a on user a's electronic device receives DNS response information a returned by the cloud scheduling platform. DNS response information a includes the IP address of edge node a. Subsequently, client a accesses edge node a using the IP address of edge node a.

[0320] Example b, such as Figure 6 As shown, client b on user b's electronic device receives DNS response information b returned by the cloud scheduling platform. DNS response information b includes the IP address of edge node b. Then, client b selects the IP address of edge node b and accesses edge node b through that IP address.

[0321] Example c, such as Figure 6As shown, client c on user c's electronic device receives DNS response information c returned by the cloud scheduling platform. The DNS response information c includes the IP address of edge node b and the IP address of edge node c. Then, client c selects the IP address of edge node c and accesses edge node c through that IP address.

[0322] In the above scheduling scheme, after receiving a DNS request from the target user, the cloud scheduling platform determines the IP address of the first edge node corresponding to the target access information indicated by the DNS request based on the edge node scheduling information, and returns the IP address of the first edge node to the target user. Since the number of ASs on the network link between the first edge node scheduled by the cloud scheduling platform and the target AS is less than the number of ASs on the network link between the second edge node and the target AS, when the target user's electronic device accesses the first edge node corresponding to the target domain name through the target AS, compared to accessing other edge nodes corresponding to the target domain name, the number of AS hops on the network link can be reduced. This not only reduces access latency but also reduces packet loss rate, thereby improving network communication quality.

[0323] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, the cloud scheduling platform includes the corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0324] This application embodiment can, based on the above method, exemplarily divide the cloud scheduling platform into functional modules. For example, the cloud scheduling platform may include functional modules corresponding to each functional division, or two or more functions may be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods.

[0325] For example, Figure 7A possible schematic diagram of the cloud scheduling platform (i.e., cloud scheduling platform 700) involved in the above embodiments is shown. The actions performed by the cloud scheduling platform 700 can be executed by a computing device or by executing corresponding software on a computing device. The cloud scheduling platform 700 may include: a receiving module 701, a determining module 702, and a sending module 703; the receiving module 701 is used to receive a Domain Name System (DNS) request from a target user, the DNS request being used to indicate target access information, and the target access information being used to indicate the target domain name and the ASN of the target AS directly connected to the target user's electronic device. For example... Figure 2 S201 is shown. The determining module 702 is used to determine, based on edge node scheduling information, the IP address of the first edge node corresponding to the target access information, and the number of ASs on the network link between the first edge node and the target AS, which is less than the number of ASs on the network link between the second edge node and the target AS. The second edge node is used to indicate edge nodes other than the first edge node. For example, Figure 2 S202 is shown. The sending module 703 is used to return the IP address of the first edge node based on a DNS request. For example, Figure 2 S203 is shown.

[0326] Optionally, the determining module 702 is specifically used to: determine the IP address of each edge node corresponding to the target access information from the edge node scheduling information, wherein the IP address of each edge node is the IP address of the first edge node.

[0327] Optionally, the edge node scheduling information is also used to indicate the number of edge nodes corresponding to the access information and the number of ASs on the network link between the access information and the AS indicated by the access information. The determining module 702 is specifically used to: determine the IP address of each edge node corresponding to the target access information from the edge node scheduling information; determine the IP address of the first edge node from the IP addresses of each edge node corresponding to the target access information according to the number of ASs on the network link between each edge node and the target AS; the number of ASs on the network link between the first edge node and the target AS is less than or equal to a number threshold.

[0328] Optionally, the DNS request includes a target source IP address, and the infrastructure also stores source IP address information. The source IP address information is used to indicate the correspondence between at least one source IP address and at least one ASN. The ASN corresponding to the source IP address is the ASN of the AS directly connected to the electronic device to which the source IP address belongs. The determining module 702 is further used to: determine the target ASN corresponding to the target source IP address based on the source IP address information. The target ASN is the ASN of the target AS indicated by the DNS request.

[0329] Optionally, the DNS request includes the ASN of the target AS. The determination module 702 is further configured to: obtain the ASN of the target AS from the DNS request.

[0330] Optionally, the access information is also used to indicate the geographical location of the user's electronic device; the target access information is also used to indicate the target geographical location of the target user's electronic device, and the distance between the first edge node and the target geographical location is less than the distance between the second edge node and the target geographical location.

[0331] Optionally, the source IP address information is also used to indicate the correspondence between at least one source IP address and at least one location address, and the location address corresponding to the source IP address is used to indicate the location address of the electronic device to which the source IP address belongs. The determining module 702 is also used to: determine the target location address corresponding to the target source IP address based on the source IP address information, and the target location address is the address of the target geographical location.

[0332] Optionally, the DNS request includes the target location address. The determination module 702 is further configured to: obtain the target location address in the DNS request.

[0333] Optionally, the access information includes an ASN line, wherein the ASN line is used to indicate the Autonomous System Number (AS) of the Autonomous System (AS) directly connected to by the user's electronic device and the geographical location of the user's electronic device; the target access information includes a target ASN line, wherein the target ASN line is used to indicate the ASN of the target AS directly connected to by the target user's electronic device and the target geographical location of the target user's electronic device.

[0334] Optionally, the access information includes the location address and the Autonomous System number of the AS directly connected to the user's electronic device, and the target access information includes the target location address and the Autonomous System number of the target AS directly connected to the target user's electronic device.

[0335] Optionally, the target geographic location is used to indicate multiple address elements, and the determining module 702 is further used to: combine the target ASN and a first address element among the multiple address elements to obtain the target ASN line; wherein, the first address element includes any one of the name of the region indicated by the target geographic location, the name of the area indicated by the target geographic location, or the name of the province indicated by the target geographic location, with the region level being higher than the area level, and the area level being higher than the province level.

[0336] Optionally, the infrastructure stores the priorities of at least one ASN line, wherein the address element indicated by a higher priority ASN line has a lower level than the address element indicated by a lower priority ASN line. The determining module 702 is further configured to: determine a first address element from multiple address elements based on the priority of the at least one ASN line, wherein the priority of the ASN line corresponding to the first address element is higher than the priority of the ASN line corresponding to a second address element, and the second address element is used to indicate address elements among the multiple address elements that are not used to determine an ASN line; combine the target ASN and the first address element to obtain a first ASN line, wherein the first ASN line is the target ASN line.

[0337] Optionally, the determining module 702 is further configured to: determine a third address element from multiple address elements when the edge node scheduling information does not include the first ASN line, wherein the priority of the ASN line corresponding to the third address element is higher than the priority of the ASN line corresponding to the second address element; combine the target ASN and the third address element to obtain the second ASN line, wherein the second ASN line is the target ASN line.

[0338] For a detailed description of the above-mentioned optional methods, please refer to the aforementioned method embodiments, which will not be repeated here. Furthermore, the explanation of any of the cloud scheduling platforms 700 provided above, as well as the description of their beneficial effects, can be found in the corresponding method embodiments described above, and will not be repeated here.

[0339] In this application, the receiving module 701, the determining module 702, and the transmitting module 703 can all be implemented in software or in hardware. For example, the implementation of the receiving module 701 will be described below. Similarly, the implementation of the determining module 702 and the transmitting module 703 can be referenced from the implementation of the receiving module 701.

[0340] As an example of a software functional unit, the receiving module 701 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, or a container. Further, the aforementioned computing instance may be one or more. For example, the receiving module 701 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed within the same region or in different regions. Further, the multiple hosts / virtual machines / containers used to run the code may be distributed within the same availability zone (AZ) or in different AZs, each AZ including one or more geographically proximate data centers. Typically, a region may include multiple AZs.

[0341] Similarly, multiple hosts / virtual machines / containers used to run this code can be distributed within the same Virtual Private Cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Communication between two VPCs within the same region, as well as between VPCs in different regions, requires a communication gateway to be set up within each VPC to enable interconnection between VPCs.

[0342] As an example of a hardware functional unit, the receiving module 701 may include at least one computing device, such as a server. Alternatively, the receiving module 701 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be implemented using a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), generic array logic (GAL), or any combination thereof.

[0343] The multiple computing devices included in the receiving module 701 can be distributed in the same region or in different regions. Similarly, the multiple computing devices included in the receiving module 701 can be distributed in the same Availability Zone (AZ) or in different AZs. Likewise, the multiple computing devices included in the receiving module 701 can be distributed in the same Virtual Private Cloud (VPC) or in multiple VPCs. These multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0344] It should be noted that, in other embodiments, the receiving module 701 can be used to execute any step in the edge node scheduling method, the determining module 702 can be used to execute any step in the edge node scheduling method, and the sending module 703 can be used to execute any step in the edge node scheduling method. The steps implemented by the receiving module 701, the determining module 702, and the sending module 703 can be specified as needed. By implementing different steps in the edge node scheduling method through the receiving module 701, the determining module 702, and the sending module 703, all functions of the data storage device can be realized.

[0345] This application also provides a computing device 800. For example... Figure 8 As shown, the computing device 800 includes a bus 802, a processor 804, a memory 806, and a communication interface 808. The processor 804, the memory 806, and the communication interface 808 communicate with each other via the bus 802. The computing device 800 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in the computing device 800.

[0346] The 802 bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 7 The bus 802 may be represented by a single line, but this does not mean that there is only one bus or one type of bus. The bus 802 may include a path for transmitting information between various components of the computing device 800 (e.g., memory 806, processor 804, communication interface 808).

[0347] Processor 804 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0348] The memory 806 may include volatile memory, such as random access memory (RAM). The processor 804 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0349] The memory 806 stores executable program code, which the processor 804 executes to implement the functions of the aforementioned receiving module 701, determining module 702, and transmitting module 703, thereby realizing the edge node scheduling method. In other words, the memory 806 stores instructions for executing the edge node scheduling method.

[0350] The communication interface 808 uses transceiver modules such as, but not limited to, network interface cards and transceivers to enable communication between the computing device 800 and other devices or communication networks.

[0351] For example, the computing device 800 described above may be Figure 1 The equipment in the infrastructure shown.

[0352] This application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

[0353] like Figure 9 As shown, the computing device cluster 900 includes at least one computing device 800. The memory 806 of one or more computing devices 800 in the computing device cluster 900 may store the same instructions for executing edge node scheduling methods.

[0354] In some possible implementations, the memory 806 of one or more computing devices 800 in the computing device cluster may also store partial instructions for executing the edge node scheduling method. In other words, a combination of one or more computing devices 800 can jointly execute the instructions for executing the edge node scheduling method.

[0355] It should be noted that the memory 806 in different computing devices 800 within the computing device cluster can store different instructions, each used to execute a portion of the functions of the cloud scheduling platform. That is, the instructions stored in the memory 806 of different computing devices 800 can implement the functions of one or more modules among the receiving module 701, the determining module 702, and the sending module 703.

[0356] In some possible implementations, one or more computing devices in a computing device cluster can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN), etc. Figure 10 One possible implementation is shown. For example... Figure 10 As shown, the two computing devices 800A and 800B are connected via a network. Specifically, they are connected to the network through the communication interfaces in each computing device.

[0357] In this type of possible implementation, the memory 806 in computing device 800A stores instructions for executing the functions of receiving module 701 and transmitting module 703. Meanwhile, the memory 806 in computing device 800B stores instructions for executing the functions of determining module 702.

[0358] Figure 10 The connection method between the computing device clusters shown can be that, considering that the edge node scheduling method provided in this application requires a large amount of computation, the function of the determination module 702 is delegated to the computing device 800B.

[0359] It should be understood that Figure 10 The functions of the computing device 800A shown can also be performed by multiple computing devices 800. Similarly, the functions of the computing device 800B can also be performed by multiple computing devices 800.

[0360] This application also provides another computing device cluster. The connection relationships between the computing devices in this computing device cluster can be similarly referred to... Figure 9 and Figure 10 The connection method of the computing device cluster is shown. The difference is that the memory 806 of one or more computing devices 800 in this computing device cluster can store the same instructions for executing the edge node scheduling method.

[0361] In some possible implementations, the memory 806 of one or more computing devices 800 in the computing device cluster may also store partial instructions for executing the edge node scheduling method. In other words, a combination of one or more computing devices 800 can jointly execute the instructions for executing the edge node scheduling method.

[0362] This application also provides a processor that can be used to perform the above-described methods.

[0363] This application also provides a chip, including: a processor and a power supply circuit; the power supply circuit can be used to supply power to the processor; the processor can be used to perform the above-described methods.

[0364] This application also provides a computing device, which may include a processor, a memory, and a computer program / instructions stored in the memory; the processor executes the computer program / instructions to enable the computing device to implement the above-described method.

[0365] This application also provides a computing device cluster, which includes at least one computing device; each computing device includes a processor, a memory, and computer programs / instructions stored in the memory, wherein the processor of each computing device executes the computer programs / instructions stored in the memory of each computing device to enable each computing device to implement the above-described method.

[0366] This application also provides a computer program product. The computer program product includes a computer program / instructions, which are software or program products capable of running on a computing device or stored on any usable medium. When the computer program / instructions are executed on at least one computing device, the at least one computing device can perform the methods described above.

[0367] This application also provides a computer-readable storage medium, which can be any available medium capable of being stored by a computing device or a data storage device such as a data center containing one or more available media. The computer-readable storage medium stores a computer program / instructions that, when executed on at least one computing device, enable the at least one computing device to perform the described method.

[0368] For example, the available media may be magnetic media (e.g., floppy disks, magnetic disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid state drives (SSDs)).

[0369] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present invention.

Claims

1. An edge node scheduling method, characterized in that, The method is applied to a cloud scheduling platform deployed on infrastructure that stores edge node scheduling information. This edge node scheduling information indicates a mapping between at least one access message and at least one edge node's Internet Protocol (IP) address. The access message indicates the target domain name corresponding to the edge node's IP address and the Autonomous System Number (ASN) of the Autonomous System (AS) directly connected to the user's electronic device. The method includes: Receive a Domain Name System (DNS) request from a target user, the DNS request being used to indicate target access information, the target access information being used to indicate the ASN of the target AS directly connected to the target domain name and the target user's electronic device; Based on the edge node scheduling information, the IP address of the first edge node corresponding to the target access information is determined. The number of ASs on the network link between the first edge node and the target AS is less than the number of ASs on the network link between the second edge node and the target AS. The second edge node is used to indicate edge nodes other than the first edge node. Based on the DNS request, the IP address of the first edge node is returned.

2. The method according to claim 1, characterized in that, The step of determining the IP address of the first edge node corresponding to the target access information based on the edge node scheduling information includes: From the edge node scheduling information, determine the IP address of each edge node corresponding to the target access information, wherein the IP address of each edge node is the IP address of the first edge node.

3. The method according to claim 1, characterized in that, The edge node scheduling information is further used to indicate the number of edge nodes corresponding to the access information and the number of ASs on the network link indicating the AS by the access information. Determining the IP address of the first edge node corresponding to the target access information based on the edge node scheduling information includes: From the edge node scheduling information, determine the IP address of each edge node corresponding to the target access information; Based on the number of ASs on the network link between each edge node and the target AS, the IP address of the first edge node is determined from the IP addresses of each edge node corresponding to the target access information; the number of ASs on the network link between the first edge node and the target AS is less than or equal to a number threshold.

4. The method according to any one of claims 1-3, characterized in that, The DNS request includes a target source IP address. The infrastructure also stores source IP address information, which indicates a correspondence between at least one source IP address and at least one ASN. The ASN corresponding to the source IP address is the ASN of the AS directly connected to the electronic device to which the source IP address belongs. The method further includes: Based on the source IP address information, the target ASN corresponding to the target source IP address is determined, and the target ASN is the ASN of the target AS indicated by the DNS request.

5. The method according to claim 4, characterized in that, The access information is also used to indicate the geographical location of the user's electronic device; The target access information is also used to indicate the target geographical location of the target user's electronic device, wherein the distance between the first edge node and the target geographical location is less than the distance between the second edge node and the target geographical location.

6. The method according to claim 5, characterized in that, The source IP address information is further used to indicate the correspondence between the at least one source IP address and at least one location address, wherein the location address corresponding to the source IP address is used to indicate the location address of the electronic device to which the source IP address belongs, and the method further includes: Based on the source IP address information, the target location address corresponding to the target source IP address is determined, and the target location address is the address of the target geographical location.

7. The method according to claim 5 or 6, characterized in that, The access information includes an ASN line, wherein the ASN line is used to indicate the Autonomous System Number (ASN) of the Autonomous System (AS) directly connected to by the user's electronic device and the geographical location of the user's electronic device; The target access information includes the target ASN line, wherein the target ASN line is used to indicate the ASN of the target AS directly connected to by the target user's electronic device and the target geographical location of the target user's electronic device.

8. The method according to claim 7, characterized in that, The target geographic location is used to indicate multiple address elements, and the method further includes: The target ASN and the first address element among the plurality of address elements are combined to obtain the target ASN line; The first address element includes any one of the name of the region indicated by the target geographic location, the name of the area indicated by the target geographic location, or the name of the province indicated by the target geographic location, wherein the region has a higher level than the area, and the area has a higher level than the province.

9. The method according to claim 8, characterized in that, The infrastructure stores the priority of at least one ASN line. The step of combining the target ASN and a first address element from the plurality of address elements to obtain the target ASN line includes: Based on the priority of the at least one ASN line, the first address element is determined from the plurality of address elements, wherein the priority of the ASN line corresponding to the first address element is higher than the priority of the ASN line corresponding to the second address element, and the second address element is used to indicate the address elements among the plurality of address elements that were not used to determine the ASN line. The target ASN and the first address element are combined to obtain the first ASN line, which is the target ASN line.

10. The method according to claim 9, characterized in that, The method further includes: If the edge node scheduling information does not include the first ASN line, a third address element is determined from the plurality of address elements, and the ASN line corresponding to the third address element has a higher priority than the ASN line corresponding to the second address element. The target ASN and the third address element are combined to obtain the second ASN line, which is the target ASN line.

11. A cloud scheduling platform, characterized in that, The cloud scheduling platform is deployed on infrastructure, which stores edge node scheduling information. This edge node scheduling information indicates the correspondence between at least one access piece of information and at least one edge node's Internet Protocol (IP) address. The access information indicates the target domain name corresponding to the edge node's IP address and the Autonomous System Number (ASN) of the Autonomous System (AS) directly connected to the user's electronic device. The cloud scheduling platform includes: A receiving module is configured to receive a Domain Name System (DNS) request from a target user, wherein the DNS request is used to indicate target access information, and the target access information is used to indicate the ASN of the target domain name and the target AS directly connected to the target user's electronic device; The determining module is used to determine the IP address of the first edge node corresponding to the target access information based on the edge node scheduling information. The number of ASs on the network link between the first edge node and the target AS is less than the number of ASs on the network link between the second edge node and the target AS. The second edge node is used to indicate edge nodes other than the first edge node. The sending module is used to return the IP address of the first edge node based on the DNS request.

12. The cloud scheduling platform according to claim 11, characterized in that, The determining module is specifically used for: From the edge node scheduling information, determine the IP address of each edge node corresponding to the target access information, wherein the IP address of each edge node is the IP address of the first edge node.

13. The cloud scheduling platform according to claim 11, characterized in that, The edge node scheduling information is also used to indicate the number of edge nodes corresponding to the access information and the number of ASs on the network link indicating the AS by the access information. The determining module is specifically used for: From the edge node scheduling information, determine the IP address of each edge node corresponding to the target access information; Based on the number of ASs on the network link between each edge node and the target AS, the IP address of the first edge node is determined from the IP addresses of each edge node corresponding to the target access information; the number of ASs on the network link between the first edge node and the target AS is less than or equal to a number threshold.

14. The cloud scheduling platform according to any one of claims 11-13, characterized in that, The DNS request includes a target source IP address. The infrastructure also stores source IP address information, which indicates a correspondence between at least one source IP address and at least one ASN. The ASN corresponding to the source IP address is the ASN of the AS directly connected to the electronic device to which the source IP address belongs. The determining module is further configured to: Based on the source IP address information, the target ASN corresponding to the target source IP address is determined, and the target ASN is the ASN of the target AS indicated by the DNS request.

15. The cloud scheduling platform according to claim 14, characterized in that, The access information is also used to indicate the geographical location of the user's electronic device; The target access information is also used to indicate the target geographical location of the target user's electronic device, wherein the distance between the first edge node and the target geographical location is less than the distance between the second edge node and the target geographical location.

16. The cloud scheduling platform according to claim 15, characterized in that, The source IP address information is further used to indicate the correspondence between the at least one source IP address and at least one location address, and the location address corresponding to the source IP address is used to indicate the location address of the electronic device to which the source IP address belongs. The determining module is further used to: Based on the source IP address information, the target location address corresponding to the target source IP address is determined, and the target location address is the address of the target geographical location.

17. The cloud scheduling platform according to claim 15 or 16, characterized in that, The access information includes an ASN line, wherein the ASN line is used to indicate the Autonomous System Number (ASN) of the Autonomous System (AS) directly connected to by the user's electronic device and the geographical location of the user's electronic device; The target access information includes the target ASN line, wherein the target ASN line is used to indicate the ASN of the target AS directly connected to by the target user's electronic device and the target geographical location of the target user's electronic device.

18. The cloud scheduling platform according to claim 17, characterized in that, The target geographic location is used to indicate multiple address elements, and the determining module is further used to: The target ASN and the first address element among the plurality of address elements are combined to obtain the target ASN line; The first address element includes any one of the name of the region indicated by the target geographic location, the name of the area indicated by the target geographic location, or the name of the province indicated by the target geographic location, wherein the region has a higher level than the area, and the area has a higher level than the province.

19. The cloud scheduling platform according to claim 18, characterized in that, The infrastructure stores the priority of at least one ASN line, and the determination module is further configured to: Based on the priority of the at least one ASN line, the first address element is determined from the plurality of address elements, wherein the priority of the ASN line corresponding to the first address element is higher than the priority of the ASN line corresponding to the second address element, and the second address element is used to indicate the address elements among the plurality of address elements that were not used to determine the ASN line. The target ASN and the first address element are combined to obtain the first ASN line, which is the target ASN line.

20. The cloud scheduling platform according to claim 19, characterized in that, If the edge node scheduling information does not include the first ASN line, a third address element is determined from the plurality of address elements, and the ASN line corresponding to the third address element has a higher priority than the ASN line corresponding to the second address element. The target ASN and the third address element are combined to obtain the second ASN line, which is the target ASN line.

21. A computing device cluster, characterized in that, The computing device cluster includes at least one computing device; Each of the at least one computing device includes a processor, a memory, and a computer program / instructions stored in the memory; The processor of each computing device executes computer programs / instructions stored in the memory of each computing device to enable each computing device to implement the method as described in any one of claims 1-10.

22. A computer program product, characterized in that, The computer program product includes a computer program / instruction, which, when executed by a computing device, implements the method as described in any one of claims 1-10.

23. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program / instruction, which, when executed by a computing device, implements the method as described in any one of claims 1-10.

Images