Scheduling method, device and system

By introducing a scheduling method in the CDN system, the user request is scheduled based on the available bandwidth resources of the CDN device, the problem of low bandwidth utilization rate of the CDN device is solved, and efficient bandwidth resource utilization and cost reduction are achieved.

CN119030985APending Publication Date: 2024-11-26HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202310943364.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-24
Filing Date
2023-07-28
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The bandwidth cost in the existing CDN technology is high, and the traditional scheduling methods cannot effectively improve bandwidth utilization, resulting in underutilization of equipment resources.

Method used

By introducing a scheduling method into the CDN system, the scheduling system obtains device information of each CDN device to determine its available bandwidth resources during the scheduling cycle, and schedules user requests based on this information to ensure the quality of service while maximizing bandwidth allocation.

Benefits of technology

While ensuring service quality, it improves the bandwidth utilization rate of CDN equipment, reduces labor costs, and achieves more refined bandwidth planning and scheduling. It is suitable for any bandwidth-capable equipment without manual configuration of business models.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119030985A_ABST
    Figure CN119030985A_ABST
Patent Text Reader

Abstract

A scheduling method, device and system are used for improving the bandwidth utilization rate of CDN devices, and the method comprises the following steps: a scheduling system obtains device information of each CDN device in one or more CDN devices; the equipment information is used for indicating available bandwidth resources of the corresponding CDN equipment in a plurality of unit time periods included in the scheduling period, the scheduling system schedules the first user request to the first CDN equipment in the one or more CDN equipment according to the equipment information of each CDN equipment, the first user request is acquired by the scheduling system at a first moment, and the first user request is acquired by the scheduling system at a second moment. The available bandwidth resources of one or more unit time periods included in the first time period of the scheduling cycle of the first CDN equipment meet the service quality requirement of the first user request for the bandwidth. The scheduling system can distribute the user requests to the CDN equipment in real time and maximumly for granularity in a unit time period, and the bandwidth utilization rate of the CDN equipment is improved on the basis of meeting the service quality.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application claims priority to the Chinese patent application filed with the Intellectual Property Office of the People's Republic of China on May 24, 2023, with application number 202310594139.2 and invention name "A Scheduling Method and Device", all contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the field of computer technology, and in particular to a scheduling method, device and system. Background Art

[0003] The content delivery network (CDN) is a basic network that cloud vendors use to provide content distribution services to content providers. It uses server clusters distributed in different regions to provide users with decentralized storage and high-speed caching of content, and distributes content to fast and stable servers based on network dynamic traffic and load conditions, thereby improving the access response speed of user content. Using CDN will greatly simplify the system maintenance workload of the website. Website maintenance personnel only need to inject the website content into the CDN system, and distribute it across the entire network through servers deployed by CDN in various physical locations, thus achieving full network coverage across operators and regions.

[0004] According to the cost data analysis of CDN operations, bandwidth costs account for more than 80%. Therefore, how to improve bandwidth utilization to reduce bandwidth costs is the main focus of current CDN technology. Summary of the invention

[0005] The present application provides a scheduling method, device and system for improving the bandwidth utilization of CDN equipment while ensuring the quality of service.

[0006] In the first aspect, the present application provides a scheduling method, which can be applied to a CDN system, wherein the CDN system is used to provide CDN services for tenants to transmit content data of an origin station to a client requesting the content data; the CDN system may include a scheduling system and at least one CDN device, wherein the scheduling system is used to schedule a user request from a client to a CDN device; the CDN device is used to respond to a user request and send the content data requested by the user request to the corresponding client; in the method, the scheduling system obtains device information (recorded as first device information) of each CDN device in one or more CDN devices, wherein the first device information is used to indicate the available bandwidth resources of the corresponding CDN device in each unit time period included in the scheduling cycle; it should be noted that the scheduling cycle corresponding to each CDN device may be different, and the difference here may be one or more differences such as the start time, the end time, and the cycle length. Afterwards, the scheduling system schedules the obtained user request to the first CDN device according to the first device information of each CDN device obtained, and the first CDN device may be one or more CDN devices of the one or more CDN devices, and the first CDN device meets the service quality requirements of the first user request for bandwidth. Specifically, for example, the first device information of the first CDN device indicates that the available bandwidth resources of the first device in one or more unit time periods included in the first time period in the scheduling cycle meet the bandwidth service quality requirement of the first user request.

[0007] Through the above method, the scheduling system obtains the first device information of each CDN device in one or more CDN devices, thereby knowing the available bandwidth resources of the CDN device in multiple unit time periods within the scheduling cycle, and scheduling the obtained user request to the first CDN device according to the first device information of the one or more CDN devices, and the first device information of the first CDN device indicates that the first device meets the service quality requirements of the bandwidth of the user request. In the case of meeting the service quality, the scheduling system can maximize the allocation of user requests to CDN devices based on the available bandwidth resources of the CDN device in multiple unit time periods within the scheduling cycle, with the unit time period as the granularity, and provide a bandwidth planning and scheduling solution within the unit time period. Compared with the traditional CDN scheduling technology, it can maximize the bandwidth utilization of small bandwidth devices while ensuring the service quality. And this embodiment is applicable to devices with any bandwidth capacity, and does not limit the type and number of services served on the CDN device, does not require manual configuration of the business model, provides business flexibility, and greatly reduces labor costs.

[0008] In a possible implementation, before the scheduling system obtains the first device information of each CDN device in the one or more CDN devices, it also includes: each CDN device in the multiple CDN devices determines the first device information of the CDN device itself within the scheduling period, and sends the first device information to the scheduling system.

[0009] Through the above method, the CDN device can periodically determine its own device information and report it to the scheduling system to update its own device information in a timely manner, thereby improving the accuracy of the method.

[0010] In a possible implementation, each CDN device determines the first device information of the CDN device itself within the scheduling period, including: the CDN device determines the remaining service duration of each user request being served by the CDN device itself at a first moment, and the bandwidth resources occupied (required) by each user request within a unit time period included in the corresponding remaining service duration; the first moment is the starting moment of the scheduling period or a moment before the scheduling period; the CDN device determines the first device information based on the total bandwidth resources of the CDN device itself within each unit time period and the bandwidth resources occupied within the unit time period included in the remaining service duration of each user request.

[0011] Through the above method, the CDN device can determine the device information of the next scheduling cycle based on the requests being served and its own total bandwidth resources, so as to accurately indicate to the scheduling system the available bandwidth resources of the CDN device in each unit time period in the next scheduling cycle. For example, when the unit time period is 1 second, the scheduling system can implement second-level bandwidth allocation based on the device information reported by the CDN device (similarly, when the unit time period is 1 millisecond, the scheduling system can implement millisecond-level bandwidth allocation based on the device information reported by the CDN device), and maximize the scheduling of user requests for the CDN device, thereby improving the bandwidth utilization of the CDN device.

[0012] In a possible implementation, the service quality requirement of the first user request for bandwidth includes the continuous service duration required by the first user request and the bandwidth resources required in one or more unit time periods included in the continuous service duration; the available bandwidth resources of each unit time period in the one or more unit time periods included in the first time period of the first CDN device in the scheduling period are not less than the bandwidth resources required by the first user request in the corresponding unit time period included in the continuous service duration, specifically, the available bandwidth resources of each unit time period in the one or more unit time periods included in the first time period of the first CDN device in the scheduling period are not less than the bandwidth resources required by the first user request in the corresponding unit time period in the continuous service duration. The duration of the first time period may be equal to the continuous service duration of the first user request. Exemplarily, correspondingly, it may mean that the first unit time period in the continuous service duration corresponds to the first unit time period included in the first time period, the second unit time period in the continuous service duration corresponds to the second unit time period included in the first time period, and so on.

[0013] Through the above method, the scheduling system can strictly ensure that the first CDN device meets the bandwidth quality requirement of the user request.

[0014] In a possible implementation, after the scheduling system schedules the acquired first user request to the first CDN device, the further step includes: the scheduling system determines the second device information of the first CDN device according to the first device information of the first CDN device and the first user request, and uses the second device information as the updated device information of the first CDN device. The second device information is used to indicate the remaining available bandwidth resources in one or more unit time periods included in the scheduling cycle after the first CDN device provides services for the first user request.

[0015] Through the above method, after the scheduling system allocates user requests to the CDN device, the device information (such as the second device information) of the CDN device is updated according to the original device information (such as the first device information) and the user request (such as the first user request), and the second device information can be used to allocate user requests to the CDN device next time. There is no need for the CDN device to report the bandwidth resource status in real time, and more accurate scheduling can be achieved without shortening the scheduling cycle, avoiding the situation where no bandwidth resources are available after the user request is scheduled to the CDN device, thereby achieving more refined scheduling.

[0016] In a possible implementation, the method further includes: the scheduling system obtains second device information of the first CDN device, and schedules the obtained second user request to the first CDN device according to the second device information, the second user request is obtained by the scheduling system at a third moment, and the available bandwidth resources of the first CDN device indicated by the second device information within one or more unit time periods after the third moment of the scheduling period meet the service quality requirements of the second user request for bandwidth.

[0017] Through the above method, the scheduling system schedules user requests according to the updated device information of the CDN device, avoiding the situation where no bandwidth resources are available after the user request is scheduled to the CDN device, and realizing more refined scheduling.

[0018] In a possible implementation, the first user request is used to request content data of a first domain name, and the second user request is used to request content data of a second domain name; or the first user request is used to request content data of the first domain name, and the second user request is used to request content data of the first domain name. That is, the first user request and the second user request can request content data of the same domain name or content data of different domain names, that is, one or more services can be deployed on the same CDN device.

[0019] Through the above method, the content data requested by the user request dispatched to the same CDN device may belong to the same domain name or different domain names. One or more services may be deployed on a CDN device. The present application does not limit the types of services served by the CDN device. That is to say, the services served by the CDN device in this embodiment may be dynamically changing and do not require manual configuration and adjustment by the user, thereby providing business flexibility and greatly saving labor costs.

[0020] In a possible implementation, the CDN system further includes at least one CDN node, and the bandwidth capacity of the CDN device is lower than the bandwidth capacity of the CDN node; the method further includes: the scheduling system obtains a third user request; when the scheduling system determines that one or more CDN devices do not meet the service quality requirements of the third user request for bandwidth, the scheduling system schedules the third user request to the CDN node.

[0021] Through the above method, user requests can be preferentially scheduled to CDN devices to improve the bandwidth utilization of CDN devices and reduce bandwidth costs. At the same time, when there are no available CDN devices, traditional scheduling strategies can be used to schedule user requests to CDN nodes to improve the response efficiency of user requests.

[0022] In the second aspect, the present application also provides a scheduling system, which has the function of implementing the scheduling system behavior in the method example of the first aspect above. The beneficial effects can be found in the description of the first aspect and will not be repeated here. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the structure of the device includes an acquisition module, a scheduling module, and optionally, an update module. These modules can execute the function of scheduling system behavior in the method example of the first aspect above. Please refer to the detailed description in the method example for details, which will not be repeated here.

[0023] In a third aspect, the present application further provides a computing device, which has the function of implementing the CDN device behavior in the method example of the first aspect above. The beneficial effects can be found in the description of the first aspect and will not be repeated here. The functions can be implemented by hardware or by executing corresponding software through hardware. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the structure of the device includes a determination module and a sending module. These modules can execute the functions of the CDN device behavior in the method example of the first aspect above. For details, please refer to the detailed description in the method example and will not be repeated here.

[0024] In a fourth aspect, the present application further provides a CDN system, which includes a scheduling system and at least one CDN device, wherein the scheduling system is used to implement the method performed by the scheduling system in the method instance of the first aspect above, and the CDN device is used to implement the method performed by the CDN device in the method instance of the first aspect above.

[0025] In a fifth aspect, the present application also provides a computing device cluster, which includes at least one computing device, and the at least one computing device has the function of implementing the scheduling system or CDN device behavior in the above-mentioned first aspect. The beneficial effects can be found in the description of the first aspect and will not be repeated here. The structure of each computing device includes a processor and a memory, and the processor is configured to support the computing device to perform part or all of the functions of the scheduling system behavior in the above-mentioned first aspect and any possible implementation of the first aspect, or to perform part or all of the functions of the CDN device behavior in the first aspect and any possible implementation of the first aspect. The memory is coupled to the processor, which stores the necessary program instructions and data for the computing device. The structure of the computing device also includes a communication interface for communicating with other devices.

[0026] In a sixth aspect, the present application also provides a computer-readable storage medium, which stores instructions, and when the computer-readable storage medium is executed on a computer, it enables the computer to execute part or all of the functions of the scheduling system behavior in the above-mentioned first aspect and any possible implementation of the first aspect, or execute part or all of the functions of the CDN device behavior in the above-mentioned first aspect and any possible implementation of the first aspect.

[0027] In the seventh aspect, the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute part or all of the functions of the scheduling system behavior in the above-mentioned first aspect and any possible implementation of the first aspect, or execute part or all of the functions of the CDN device behavior in the above-mentioned first aspect and any possible implementation of the first aspect.

[0028] In an eighth aspect, the present application also provides a computer chip, which is connected to a memory, and the chip is used to read and execute a software program stored in the memory, to execute part or all of the functions of the scheduling system behavior in the above-mentioned first aspect and any possible implementation of the first aspect, or to execute part or all of the functions of the CDN device behavior in the above-mentioned first aspect and any possible implementation of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 A schematic diagram of a system architecture that may be used in an embodiment of the present application;

[0030] Figure 2 A schematic diagram of a scenario of an existing scheduling solution;

[0031] Figure 3 A flowchart corresponding to a scheduling method provided in an embodiment of the present application;

[0032] Figure 4 A schematic diagram of a scheduling cycle provided in an embodiment of the present application;

[0033] Figure 5 A flowchart corresponding to a scheduling method provided in an embodiment of the present application;

[0034] Figure 6 A schematic diagram of a scenario for updating device information provided in an embodiment of the present application.

[0035] Figure 7 A schematic diagram of the structure of a scheduling system provided in an embodiment of the present application;

[0036] Figure 8 A schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0037] Fig. 9A schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0038] Fig.10 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;

[0039] Fig.11 A schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] Figure 1 1 is a schematic diagram of a system architecture that may be applicable to an embodiment of the present application. The system includes an origin node 10, a control platform 20, a CDN 30, a scheduling system 40, and clients 101-104. Among them, the CDN 30 includes CDN devices 80-82. Optionally, the CDN 30 may also include at least one CDN node.

[0041] The tenant (such as a content provider) sets up the source node 10, which can be used to provide services, such as web pages, audio, video playback and other media services. The tenant can purchase CDN services on the control platform 20, set the region where the CDN service needs to be enabled, or set up CDN nodes and / or CDN devices in different regions to transmit the content data of the source node 10 to the client 101-client 105 through the CDN device or CDN node. The client 101-104 is usually a user-side device, such as a smartphone, tablet computer, desktop computer, vehicle-mounted device, wearable device, etc., for users to use to access the content of the source node 10.

[0042] The CDN nodes may include edge cache nodes (such as edge cache nodes 70-71), and the CDN nodes may also include central cache nodes (such as central cache nodes 60-61).

[0043] Among them, the edge cache nodes 70-71, which can also be called proxy caches (surroigate) or service nodes, are only "one hop" away from the terminal device and are used to cache the content data sent by the source station node 10 for the nearby access of the clients 101-104. Specifically, the edge cache nodes 70-71 store the mirror of the source station node 10, and the edge cache nodes 70-71 are usually set at the edge of the network. Therefore, the edge cache nodes 70-71 can replace the source station node 10 to provide content data to the clients 101-104, thereby realizing the edge storage and dissemination of content data, solving the network congestion problem, and improving the response speed of the clients 101-104 accessing the source station node 10.

[0044] In order to ensure that data can be sent from edge cache nodes 70-71 to clients 101-104 as quickly as possible, edge cache nodes 70-71 are usually set in different regions, and services are provided by edge cache nodes in the same region as the clients. For example, edge cache node 70 can be set in South China, edge cache node 71 can be set in Central China, clients 101 and 102 are located in South China, and client 103 is located in Central China. Clients 101 and 102 are in the same region as edge cache node 70, and the distance between them is the shortest. Edge cache node 70 provides services to clients 101 and 102. Similarly, client 103 is in the same region as edge cache node 71, and the distance between them is the shortest. Edge cache node 71 provides services to client 103, and so on.

[0045] For example, in a scheduling strategy, the public DNS server 50 registers the corresponding relationship between the domain name of the source station node 10 and the public IP addresses of the edge cache nodes set in different regions. The client 101 in region 1 sends a domain name access request for the domain name of the source station node 10, and the domain name access request reaches the public DNS server 50. The public DNS server 50 obtains the public IP addresses of the edge cache nodes 70-71 set in multiple regions corresponding to the domain name. The public DNS server 50 compares the public IP address of the client 101 (carried in the source IP address of the domain name access request) with the public IP addresses of the multiple edge cache nodes 70-71, confirms that the public IP address of the edge cache node 70 and the public IP address of the client 101 belong to the same region, and returns the public IP address of the edge cache node 70 to the client 101. The client 101 accesses the edge cache node 70 nearby according to the public IP address of the edge cache node 70 and requests the content to be accessed from it.

[0046] The edge cache node 70 queries whether the content to be accessed is cached locally. If yes, it directly returns to the client 101. If no, it requests the content to be accessed from the upper cache node (central cache node 60) (sends back to the source request). The central cache node 60 queries whether the content to be accessed is cached locally. If yes, it directly returns to the edge cache node 70. If no, it requests the content to be accessed from the upper source node 30. Therefore, when the edge cache node 70 caches the content to be accessed, it can be returned to the client 101 nearby, thereby improving the speed at which the client 101 accesses the content to be accessed.

[0047] For some popular content with frequent client access requests, the edge cache node 70 and the central cache node 60 can send a back-to-source request to the upper-level node in a timely manner and record the content, so that it can be provided to the client in a timely manner after a back-to-source. For some unpopular content with relatively few client access requests, the edge cache node 70 and the central cache node 60 need to send a back-to-source request to the upper-level node step by step, record the content, and then provide it to the client. When no access request for the content is received for a period of time, the content is deleted locally, so as to reasonably use the cache space.

[0048] Each CDN node may include multiple servers, and the bandwidth resources of multiple servers are constructed into the total bandwidth resources of a CDN node. Sufficient bandwidth resources enable the edge cache node to provide high-quality services to many clients in a region at the same time.

[0049] The CDN devices 80-82 may be devices with communication and storage functions. For example, the CDN devices include but are not limited to access network devices close to the user side, such as optical network terminals (ONT), optical line terminals (OLT), routers, etc. Any communication device that can be deployed on the Internet can be used as a CDN device in this embodiment.

[0050] Similar to edge cache nodes, for example, CDN devices can be divided by region and provide services to clients according to the proximity of the region, wherein one region may include one or more CDN devices, and CDN devices can be used to provide services to clients in the same region as the CDN device itself. For another example, CDN devices can be used to cache content data of the source station node 10, and the scheduling system 40 schedules access requests from clients to the CDN devices. When the CDN device caches content to be accessed, the content to be accessed can be directly sent to the client. In one possible scenario, when the CDN device does not cache the content to be accessed, the CDN device can request a return to the source from the edge cache node or the central cache node or directly from the source station node 10 or other CDN devices.

[0051] The characteristic of the CDN device in this embodiment is that the bandwidth specification that can be provided is relatively small. The difference from the CDN node is that the bandwidth specification of the CDN device is smaller than the bandwidth specification of the CDN node. It is worth noting that in some records, the server used to build the CDN node may be referred to as a "CDN device". The CDN device in the embodiment of this application is not a server used to build a CDN node, and the bandwidth specification of the CDN device in this embodiment is usually smaller than the bandwidth specification of these servers. For example, in one application, the bandwidth specification of the CDN node is tens of G to hundreds of G, the bandwidth specification of the server used to build the CDN node is several G to more than ten G, and the bandwidth specification of the CDN device is usually concentrated around 30MB to 200MB. Of course, this is just an example, and this embodiment does not limit the specific bandwidth specifications of each device. In some cases, the bandwidth specification of the CDN device may also be higher than that of the server.

[0052] In addition, CDN equipment features include low bandwidth charges, large numbers, and wide distribution. If these CDN equipment can be used to provide CDN services, it can effectively reduce the burden of CDN service providers in building CDN nodes, reduce tenants' rental costs, and provide tenants with a wider range of CDN services at lower prices. Therefore, how to maximize the bandwidth scheduling and utilization of these CDN equipment without affecting the quality of service is the main research direction of the industry at present, and it is also a key technical point facing the cloud computing field.

[0053] Figure 2 An example of existing scheduling management for CDN devices is shown. In this example, scheduling is mainly performed based on the number of connections of CDN devices. While ensuring the quality of service, CDN devices are grouped according to different business models and device bandwidth specifications.

[0054] Assume that a business model includes domain name A and domain name B, such as Figure 2 As shown, for this business model, the CDN devices in a certain region are divided into four service groups, namely service group 1 to service group 4, and each service group may include one or more CDN devices. Among them, the device bandwidth of each CDN device in service group 1 is 50M, which is configured to be dedicated to the transmission of content data of domain name A. The device bandwidth of each CDN device in service group 2 is 50M, which is configured to be dedicated to the transmission of content data of domain name B. The device bandwidth of each CDN device in service group 3 is 120M, which is configured to be dedicated to the transmission of content data of domain name A. The device bandwidth of each CDN device in service group 4 is 120M, which is configured to be dedicated to the transmission of content data of domain name B.

[0055] Then, the maximum number of connections per CDN device is calculated based on the average download speed of the bearer service on the CDN side and the total device bandwidth of the service group. As shown in Table 1 below, assuming that on the CDN side, the average download speed of domain name A is 10Mbps and the average download speed of domain name B is 5Mbps, then the maximum number of connections per second per CDN device in service group 1 = 50Mb / 10Mbps = 5. Similarly, the maximum number of connections per second per CDN device in service group 2 = 50Mbps / 5Mbps = 10. And so on.

[0056] Table 1

[0057] Bearer Services Average download speed (Mbps) Device Bandwidth (Mbps) Maximum number of connections A domain name 10 50 5 B domain name 5 50 10 A domain name 10 120 12 B domain name 5 120 24

[0058] Continue to see Figure 2 , with a fixed period of time as the scheduling cycle (for example, 5 seconds), each CDN device reports the number of connections that the CDN device is currently serving at the reporting time of each scheduling cycle. When the scheduling system performs service scheduling within the scheduling cycle, it schedules requests for the CDN device based on the number of connections reported by the CDN device and the maximum number of connections of the CDN device to make up the maximum number of connections of the CDN device. For example, if the maximum number of connections of a CDN device is 5 and the number of connections reported by the CDN device is 3, then in the next scheduling cycle, the scheduling system will schedule at most two requests for the CDN device, and each request will occupy 1 connection of the CDN device.

[0059] However, Figure 2The scheduling scheme shown has the following problems: First, the scheme cannot keep the CDN device running with the maximum number of connections throughout the scheduling cycle. On the one hand, it is limited by the number of requests to be scheduled, but the main reason is that due to the large number of CDN devices, in order to reduce the burden of the scheduling system, the length of the scheduling cycle for CDN devices to report service information is usually long. Based on the number of connections reported by the CDN device, the allocation of requests to the CDN device in the entire scheduling cycle is usually inaccurate, which may cause the scheduling system to fail to maximize the scheduling requests for the CDN device according to the actual number of connections during the scheduling cycle, resulting in low bandwidth utilization of the CDN device. However, shortening the length of the scheduling cycle and increasing the reporting frequency will increase the burden on the CDN device and the scheduling system. Second, the scheduling scheme needs to be manually configured according to the business model. The scheduling scheme needs to group the CDN devices according to the business model, and the single CDN device in each group cannot run mixed services. For example, a service group can only be used to serve a domain name. There may be a situation where a service group is overloaded while the other service groups have more idle resources, which is also one of the reasons for the low bandwidth utilization of the device. Moreover, when grouping, the corresponding number of service groups is usually set according to the bandwidth resources required by the traffic peak of the domain name within a period of time, resulting in CDN equipment usually running below the maximum number of connections, which is another reason for the low bandwidth utilization of the equipment. In addition, when the business model changes (such as the domain name of the CDN service changes, or the traffic of the domain name changes), the grouping needs to be adjusted manually in time, which is very inflexible and consumes high labor costs.

[0060] In view of this, the present embodiment provides a scheduling method, which is not limited by the length of the scheduling cycle, allows the length of the scheduling cycle to not be shortened, and does not require manual device grouping and binding relationship establishment according to the business model. In other words, the solution can be dynamically applied to any business model, and does not limit the types and quantity of services served by a single CDN device. It allows mixed running of services on the CDN device, and can achieve more traffic offloading to the CDN device without affecting the service quality, thereby maximizing the bandwidth utilization of the CDN device.

[0061] The following applies to Figure 1 Taking the system shown in FIG. 1 as an example, the scheduling method provided in this embodiment is described in detail. It should be noted that: Figure 1 The system architecture shown is only an example. In actual applications, the system to which this application applies may have relatively Figure 1More or fewer devices / nodes, for example, the system may not include CDN nodes, public DNS servers 50, etc. Any system including the scheduling system 40 and CDN devices is applicable to this embodiment. In some possible cases, the scheduling system 40 and the public DNS server 50 may be deployed in the same device. For another example, the scheduling system may be deployed on a regional basis, such as deploying the same scheduling system 40 in each region, and one scheduling system 40 is used to manage the CDN devices in a region and the distribution of user requests (used to access content data of a specified domain name, such as the aforementioned domain name access request) in the region. In addition, please understand that in order to keep it simple, Figure 1 Only a small number of clients and CDN devices are shown, and the embodiments of the present application do not limit the number of these devices.

[0062] The scheduling method provided in this embodiment may include two aspects. In the first aspect, the CDN device reports the device information within the scheduling period to the scheduling system. Figure 3 In the second aspect, the scheduling system schedules the request to the CDN device, see Figure 5 The method embodiments are described below.

[0063] First aspect:

[0064] Figure 3 A schematic diagram of a flow chart corresponding to the scheduling method provided in this embodiment, in which the scheduling system can be Figure 1 In the scheduling system 40, the CDN device may be Figure 1 Any one of the CDN devices 80-82 in, such as Figure 3 As shown, the method may include the following steps:

[0065] Step 301: The CDN device determines the device information of the CDN device itself in a scheduling period. The device information includes the bandwidth resource status of the CDN device in a plurality of unit time periods included in the scheduling period.

[0066] In this embodiment, the CDN device may periodically execute steps 301-302, each execution of step 301 is used to determine the device information in the next scheduling period, and in step 302, report the latest device information to the scheduling system. In addition, when the system has multiple CDN devices, the method for each CDN device to determine the device information may be the same. As shown below, taking one CDN device as an example, the CDN device (such as Figure 1 The process of the CDN device 80 in FIG. 80 determining its own device information in a scheduling cycle (referred to as the first cycle) is described.

[0067] The process may include: the CDN device 80 determines device information of a scheduling period after the first moment.

[0068] In one example, combining Figure 4 According to (a), the CDN device 80 can determine the device information of the CDN device 80 in the first period at a first moment, and the first moment can be the starting moment of the first period. The device information includes the bandwidth resource status of the CDN device 80 in multiple unit time periods included in the first period, and the unit time period can be a set time period of any length, and the measurement unit can be a time unit such as seconds or millimeters, such as Figure 4 In the example, the length of each unit time period is t, for example, t can be 1 second, 2 seconds, 1 millisecond, 10 milliseconds, etc., and is not specifically limited. In addition, this embodiment does not limit the length of the scheduling period. For ease of explanation, the following example is taken as an example that the length of the scheduling period is 5 seconds and the length of the unit time period is 1 second. 1 second or every second in the following can be replaced by the unit time period.

[0069] In this example, the CDN device 80 determines the device information of the CDN device 80 itself in the first cycle in a manner that may include: the CDN device 80 determines the remaining service duration of each user request among one or more user requests being served at the first moment, taking a user request as an example, the remaining service duration of a user request is determined based on the remaining size of the content data requested by the user request and the download speed of the user request, and then determines the bandwidth resource status of the CDN device 80 per second in the first cycle based on the remaining service duration and download speed of each user request, that is, generates the device information of the CDN device 80 in the first cycle. The bandwidth resource status may be used to indicate the amount of available bandwidth resources (or the amount of remaining bandwidth resources) or the amount of used bandwidth resources, such as the remaining bandwidth water level value or the used bandwidth water level value of the CDN device 80 per second in the first cycle.

[0070] For example, assume that the information of multiple user requests being served by the CDN device 80 at a first moment is as shown in Table 2 below:

[0071] Table 2

[0072]

[0073] Among them, the download speed can be determined according to the average download speed of the domain name on the CDN side. For example, system parameters such as the average download speed of multiple domain names can be pre-set in the CDN device 80. The download speed requested by the user can be determined according to the value of the system parameter. This will be explained in detail below and will not be repeated here.

[0074] The used bandwidth water level value per second in the first cycle is equal to the sum of the bandwidths occupied by the multiple user requests in the second. As shown in Table 2, the used bandwidth water level of CDN device 80 in the first cycle is 40Mb in the first second, 30Mb in the second second, 20Mb in the third second, 10Mb in the fourth second, and 0 in the fifth second.

[0075] Optionally, the CDN device 80 may also convert the used bandwidth water level value per second in the first cycle into the available bandwidth water level value per second in the first cycle according to its own bandwidth specification. For example, if the bandwidth specification of the CDN device is 50Mbps, the available bandwidth resource amount per second in the first cycle is: the available bandwidth water level value in the first second of the first cycle is 10Mb, the available bandwidth water level value in the second second is 20Mb, the available bandwidth water level value in the third second is 30Mb, the available bandwidth water level value in the fourth second is 40Mb, and the available bandwidth water level value in the fifth second is 50Mb.

[0076] In summary, the device information of the CDN device in the first cycle can be used to indicate the bandwidth watermark value or available bandwidth resource amount of the CDN device itself per second in the first cycle. Alternatively, the device information can also indicate the bandwidth resource status per second in other ways, which is not limited in this embodiment.

[0077] The above describes the specific process of a CDN device determining the device information of a scheduling cycle. For the next scheduling cycle, the CDN device repeats the above process to determine the device information of the new scheduling cycle. For example, continue to refer to Figure 4 (a), the CDN device 80 can determine the device information of the first cycle at a first moment, and determine the device information of the second cycle (the next scheduling cycle of the first cycle) at a second moment (which can be the end moment of the first cycle or the start moment of the second cycle), see the above introduction, which will not be repeated here. The first cycle and the second cycle can be adjacent, see Figure 4 Alternatively, there is a time interval between the first cycle and the second cycle, see Figure 4 as shown in (b).

[0078] In another example, see Figure 4As shown in (c), CDN device 80 may determine the device information of CDN device 80 in the first cycle at a first moment, and the first moment may be a moment before the first cycle. For example, CDN device 80 uses the same method as the above example to determine the device of CDN device 80 in a continuous time after the first moment, and the continuous time includes the first cycle. That is, CDN device 80 determines the device information for a longer period of time, but may only report the device information for a part of the time. Similarly, CDN device 80 determines the device information of CDN device 80 in the second cycle at a second moment. The specific determination method can be found in the description of the above example, which will not be repeated here. Among them, the first cycle and the second cycle may be adjacent, see Figure 4 Alternatively, there is a time interval between the first cycle and the second cycle, see Figure 4 As shown in (d), two scheduling cycles arranged in chronological order in the present application may be adjacent or have a gap.

[0079] It is understandable that in order to improve the bandwidth utilization of CDN equipment, it is usually adopted Figure 4 Report in the manner (a).

[0080] It should be noted that if the remaining service time of a user request spans a scheduling cycle, the user request may continue to participate in the device information calculation of the CDN device in the next scheduling cycle. For example, in Table 2, assuming that the remaining size of the resource requested by user request 4 is 80Mb and the average domain name download speed is 10Mbps, the remaining service time of the user request is 8s, which exceeds the length of a scheduling cycle (5s). At the next reporting time, the user requests being served by the CDN device still include the user request 4. At this time, the remaining resource size of the user request 4 will become 30Mbp, and the remaining service time is 3s. The CDN device can determine the device information of the next scheduling cycle (such as the second cycle) based on the user request 4. Alternatively, the CDN device can also determine the device information of multiple scheduling cycles and report the device information of multiple scheduling cycles to the scheduling system.

[0081] Step 302: The CDN device sends the device information to the scheduling system.

[0082] As in the above example, the CDN device 80 sends the device information of the CDN device 80 in the first period to the scheduling system 40. Accordingly, the scheduling system 40 receives the device information sent by the CDN device 80. The scheduling system 40 updates the bandwidth resource status of the CDN device 80 according to the received device information, that is, the scheduling system 40 uses the received device information as the latest device information of the CDN device 80.

[0083] In this embodiment, the scheduling system may receive device information from multiple CDN devices at the same time, and update the bandwidth resource status of the corresponding CDN device according to the received device information. Each CDN in the multiple CDN devices can determine the device information in the same way as the above CDN devices and report its own device information to the scheduling system. Please refer to the above description of the CDN device 80, which will not be repeated here.

[0084] For example, in some possible situations, each CDN device in a plurality of CDN devices has the same reporting time and the same scheduling cycle length, and the plurality of CDN devices report simultaneously. For example, in one example, CDN devices are divided by region, and CDN devices in a region form a set. Each CDN device in one or more CDN devices in the same set is configured with the same reporting time and scheduling cycle length. Figure 1 Taking region 1 in FIG. 3 as an example, in step 301, CDN device 80 in region 1 determines the device information of CDN device 80 in the first cycle at the first moment, and CDN device 81 also determines the device information of CDN device 81 in the first cycle at the first moment. That is, the two CDN devices are configured with the same reporting time and scheduling cycle length.

[0085] It is worth noting that the reporting time and / or different scheduling cycle lengths corresponding to different sets can be the same or different. For example, CDN device 82 in region 3 and CDN devices 90-81 in region 1 are configured with the same reporting time and scheduling cycle length. In step 301, CDN devices 80-82 respectively determine their own device information in the first cycle at the first moment. For another example, the scheduling cycle lengths of CDN devices 82 in region 3 and CDN devices 80-82 in region 1 are different, for example, the scheduling cycle of CDN devices 80-82 is 5 seconds, and the scheduling cycle length of CDN devices 82 is 10 seconds, etc. This embodiment does not limit this.

[0086] In some other possible situations, each CDN device may be configured with different reporting times and / or scheduling cycle lengths. For example, CDN device 80 and CDN device 81 in region 1 report their respective device information at different times.

[0087] Specifically, when reporting device information, multiple CDN devices can report device information to their corresponding scheduling systems. For example, in one example, a scheduling system is used to manage CDN devices in multiple regions, such as: Figure 1In this case, the scheduling system 40 can be used to manage CDN devices 80-82. In this case, CDN devices 80-82 all report device information to the scheduling system 40. In another example, a scheduling system is used to manage CDN devices in a region. For example, a system Figure 1 The basis also includes a scheduling system 41, wherein the scheduling system 40 is used to manage CDN devices 80-81 in region 1, and the scheduling system 41 is used to manage CDN devices 82 in region 3. In this case, the CDN devices 80-81 report device information to the scheduling system 40, and the CDN device 82 reports device information to the scheduling system 41.

[0088] Second aspect:

[0089] Figure 5 A flow chart of a scheduling method provided in an embodiment of the present application, in which the scheduling system may be Figure 1 In the scheduling system 40, the CDN device may be Figure 1 Any one of the CDN devices 80-82 in, such as Figure 5 As shown, the method may include the following steps:

[0090] Step 500: The scheduling system obtains a user request from a client.

[0091] The user request is used to request access to the content of a specified domain name, or to request downloading of specified content data. For example, a user request is used to request downloading of specified content of domain name A or to request downloading of specified content of domain name B, etc.

[0092] There are many ways to obtain the user request. For example, the scheduling system receives the user request from the client, or the scheduling system obtains the user request from the scheduling queue of the scheduling system.

[0093] Step 501: The scheduling system determines the quality of service requirement of the user request for bandwidth.

[0094] This step may include: the scheduling system determines the data volume of the content data requested by the user request and the average download speed of the content data requested by the user request on the CDN side (referred to as the average download speed), determines the continuous service duration of the user request and the bandwidth resources required by the user request in each unit time period included in the continuous service duration, such as referred to as the download speed corresponding to each single time period. The download speed corresponding to each unit time period is the smaller value of the average download speed of the domain name requested by the user request and the remaining data volume of the requested content data in the unit time period.

[0095] The following description is made by taking the unit time period of 1 second as an example.

[0096] If the data size of the requested content data is less than the average download speed requested by the user within 1 second, the download speed for that second is the data size of the requested content data / second. Alternatively, if the data size of the requested content data is not less than the average download speed requested by the user within 1 second, the download speed for that second is the average download speed requested by the user. It should be noted that "the data size of the requested content data / second" here is the unit for converting the requested resource into the average download speed. When the unit of the average download speed changes, the conversion unit used here also changes accordingly. For example, when the average download speed is Mbps, the data size of the content data requested by the user will be converted into the data size of the content data requested within that second / millisecond.

[0097] Accordingly, the duration of the continuous service requested by the user is determined according to the determined download speed per second and the data volume of the requested content data.

[0098] For example, for different user requests, the corresponding download speed per second and continuous service duration of each user request are shown in Table 3:

[0099] Table 3

[0100]

[0101] Taking user request 1' as an example, the data volume of the content data requested is 5Mb, and the average download speed of the user request 1' is 10Mbps. The data volume of the remaining content data corresponding to the 1st second is 5Mb, 5Mbps<10Mbps, then the download speed within 1 second is 5Mbps, and the continuous service duration of the user request 1' is only 1 second.

[0102] Continuing with user request 2' as an example, the data volume of the requested content data is 20Mb, and the average download speed of this user request 2' is 10Mbps, the data volume of the remaining content data corresponding to the 1st second is 20Mb, 20Mbps>10Mbps, the download speed within the 1st second is 10Mbps, the download speed within the 1st second is 10Mbps, the data volume of the remaining content data corresponding to the 2nd second is 10Mb, 10Mbps=10Mbps, the download speed within the 2nd second is 10Mbps, and the continuous service duration of this user request 2' is 2 seconds.

[0103] Taking user request 3' as an example, the data volume of the requested content data is 15Mb, and the average download speed of the user request 3' is 10Mbps. The data volume of the remaining content data corresponding to the first second is 15Mb, 15Mbps>10Mbps, the download speed in the first second is 10Mbps, and the data volume of the remaining content data corresponding to the second second is 5Mb, 5Mbps<10Mbps, the download speed in the second second is 5Mbps, and the continuous service duration of the user request 3' is 2 seconds.

[0104] Please note that the continuous service duration of user request 2' in Table 3 is 2 seconds, but the download speed per second only shows one value, which means that the download speed of each second in the continuous service duration is the same, that is, the download speed of each second in the 2 seconds is 10 Mbps. The similarities will not be repeated below.

[0105] The CDN device can use the above method to calculate the remaining service time of the user request and the download speed in each unit time period of the remaining service time.

[0106] Step 502: The scheduling system obtains device information of one or more CDN devices.

[0107] In one embodiment, the process may include: the scheduling system determines the region where the client is located, and then obtains one or more CDN devices in the region, and selects a CDN device from the one or more CDN devices that meets the service quality requirements of the user request for bandwidth based on the device information of each CDN device in the one or more CDN devices, and records it as the first CDN device.

[0108] In one example, the scheduling system may manage CDN devices in multiple regions. In this case, the scheduling system can compare the IP address of the client (carried in the request sent by the client) with the IP addresses of multiple CDN devices to confirm one or more CDN devices in the same region as the client. Alternatively, the scheduling system determines the regional identifier of the client's IP address based on the correspondence between the IP address and the regional identifier, and queries one or more CDN devices that have a binding relationship with the region based on the regional identifier. A regional identifier is used to uniquely identify a region. Among them, one or more information such as the IP address of the CDN device, the correspondence between the IP address and the regional identifier, and the binding relationship between the regional identifier and the CDN device can be preset in the scheduling system according to actual needs or obtained by the scheduling system from other devices, without specific limitation.

[0109] In another example, a scheduling system can be used to manage CDN devices in a region. Specifically, the scheduling system is used to receive user requests from clients in the region and allocate CDN devices to the received user requests. In this case, the scheduling system does not need to perform regional matching, and can directly obtain information about CDN devices managed by the scheduling system. The information records multiple CDN devices in the region. The scheduling system can obtain device information of the multiple CDN devices and determine the first CDN device from the multiple CDN devices based on the device information of the multiple CDN devices.

[0110] In an optional manner, the scheduling system in this embodiment can also record the cache information of each CDN device, and the cache information is used to indicate what content data is cached in the multiple CDN devices managed by the scheduling system. In this way, the scheduling system can also perform an initial screening of the multiple CDN devices it manages based on the region and / or cache information, and then obtain the device information of the screened CDN devices. For example, Figure 1 The scheduling system 40 in the example is used to manage CDN devices 80-82. When the scheduling system 40 receives a user request from the client 101, the scheduling system selects CDN devices 80-81 based on the region to provide services for the user request. Optionally, the scheduling system can also combine the cache information and the content data requested by the user request (i.e., the content to be accessed) to continue to select CDN devices that cache the content to be accessed from CDN devices 80-81. For example, when CDN devices 80-81 all cache the content to be accessed, the scheduling system 40 respectively obtains the device information of CDN devices 80 and 81. For another example, when only CDN device 80 caches the content to be accessed, the scheduling system 40 can only obtain the device information of CDN device 80.

[0111] It should be noted that the device information obtained by the scheduling system here is the latest device information of the CDN device. The scheduling system stores the updated device information of each CDN device, that is, the latest device information of the CDN device. The latest device information may be reported by the CDN device, or it may be updated by the scheduling system based on the device information reported by the CDN device (or the device information of the CDN device stored by the scheduling system) and the user request assigned to the CDN device by the scheduling system. This will be explained in detail below and will not be repeated here.

[0112] It should be noted that, in some cases, there is no strict time sequence limitation between step 502 and step 501, such as step 502 can be executed before step 501, or step 501 can be executed between step 502, or step 501 and step 502 can be executed simultaneously.

[0113] In step 503, the scheduling system determines whether there is a CDN device (referred to as a candidate CDN device) among the one or more CDN devices that meets the bandwidth quality of service requirement of the user request based on the device information of the one or more CDN devices obtained. If so, step 504 is executed; otherwise, step 506 is executed.

[0114] Among them, the bandwidth resource status of one or more unit time periods of the candidate CDN device within the target time period (such as the first time period mentioned above) meets the service quality requirement of the user request for bandwidth. This step may include: the scheduling system selects a CDN (referred to as a candidate CDN device) with a download speed per second that meets the continuous service duration of the request from the one or more CDN devices according to the available bandwidth watermark value of the corresponding CDN device per second within the target time period indicated by the device information of each CDN device obtained.

[0115] Step 504: The scheduling system schedules the user request to the first CDN device.

[0116] Exemplarily, this step may include: the scheduling system returns the IP address of the first CDN device to the client corresponding to the user request, and the client sends the user request to the first CDN device based on the received IP address of the first CDN device. Correspondingly, the first CDN device receives the user request and provides services for the user request: for example, the first CDN device sends the content to be accessed requested by the user to the client. If the first CDN device does not cache the resources requested by the request, it can obtain the content to be accessed through a back-to-source request and send the obtained content to be accessed to the client. Alternatively, the first CDN device may also refuse to provide services for the user request, and the CDN node may subsequently provide services for the user request. In this embodiment, since the scheduling system can record the cache information of the CDN device and schedule the user request based on the cache information, in this implementation, the situation where the content to be accessed is not cached in the first CDN device is a low-probability event.

[0117] In one example, the number of the first CDN device is one, that is, the first CDN device is one of the candidate CDN devices of one or more candidate CDN devices. If the number of the candidate CDN devices is one, then the candidate CDN device is the first CDN device. Alternatively, if the number of the candidate CDN devices is multiple, the scheduling system can select one from the multiple candidate CDN devices as the first CDN device, which can be randomly selected, or selected according to a load balancing strategy, or selected according to other strategies. This embodiment does not limit the selection strategy.

[0118] In another example, there may be multiple first CDN devices, each of which is a candidate CDN device, that is, the scheduling system may schedule a user request to multiple CDN devices, and multiple CDN devices jointly provide services for the user request. This approach can improve the hit rate of user requests.

[0119] It should be noted that in order to improve bandwidth utilization of CDN devices, one user request is usually dispatched to one CDN device.

[0120] Step 505: The scheduling system updates the device information of the first CDN device.

[0121] The scheduling system updates the device information of the first CDN device according to the device information of the first CDN device obtained in step 502 and the bandwidth resources required by the user request. The updated device information can be used to indicate the amount of available bandwidth resources remaining in each second included in the scheduling period after the CDN device provides services for the request.

[0122] The above steps 503 to 505 are illustrated below in conjunction with Table 4.

[0123] For example, suppose there is only one CDN device in a certain region, such as Figure 1 Assuming that the client 103 initiates one user request per second in the first 4 seconds in a scheduling cycle (the first cycle), a total of 4 user requests, based on the bandwidth resources required for each user request, for the given available bandwidth water level value of the CDN device per second in the first cycle, the scheduling result of each user request determined by the scheduling system 40 is shown in Table 4 below. Figure 6 understand.

[0124] Table 4

[0125]

[0126] It should be noted that different user requests correspond to different target time periods. The target time period here can be a period of time after the scheduling system obtains the user request. The length of this period of time is the continuous service duration of the user request. The starting time of the target time period can be the moment when the user request is obtained or a moment after the user request is obtained. For example, Example 1: The user request is obtained at the third moment of the first cycle. The target time period corresponding to the user request can be the period from the third moment as the starting moment to the end of the continuous service duration of the user request. At this time, the target time period includes the unit time period where the third moment is located. For example, the third moment is any moment within the first second of the first cycle, and the duration of the user request is 1s, then the target time period can include the first second of the first cycle.

[0127] For another example, Example 2: the target time period corresponding to a user request can be one or more consecutive unit time periods after the unit time period in which the third moment is located. For example, the third moment is a moment within the 1st second of the first cycle, and the duration of the user request is 2s. The target time period can include the 2nd and 3rd seconds (2nd-3rd seconds) of the first cycle.

[0128] For a user request, if there is at least one unit time period in the target time period corresponding to the user request whose available bandwidth watermark value does not meet the download speed in the unit time period corresponding to the user request, it is determined that the CDN device does not meet the bandwidth service quality requirement of the user request.

[0129] For example, for user request a, the scheduling system 40 obtains the device information of the CDN device 82, which is the device information of the first cycle reported by the CDN device 80, and the device information indicates the available bandwidth water level value per second in the first cycle. For example, the device information in Table 4 indicates that the available bandwidth water level values ​​(in Mpbs) of the CDN device 82 per second in the first cycle are 10, 20, 30, 40, and 50. Assuming that the target time period corresponding to the user request a is the first second of the first cycle, the available bandwidth water level of 10 Mbps in the first second does not meet the download speed of 20 Mpbs of the user request a in the second, then the request 1 cannot be scheduled to the CDN device 82.

[0130] For another example, for user request b, the scheduling system 40 obtains the device information of the CDN device 82. Since user request a is not scheduled to the CDN device 82, the device information obtained here is still the device information of the first period reported by the CDN device 82, and the device information indicates that the available bandwidth water level of the CDN device per second in the scheduling period is 10, 20, 30, 40, and 50. Assume that the target time period corresponding to user request b is the 2nd to 4th second of the first period, wherein the available bandwidth water levels of the 2nd second (20Mbps), the 3rd second (30Mbps), and the 4th second (50Mbps) respectively meet the download speed of 10Mbps per second within the continuous service duration of user request b, therefore, user request b can be scheduled to the CDN device 82. Afterwards, the scheduling system 40 updates the device information of the CDN device 82 according to the currently stored device information of the CDN device 82 and the user request b. The updated device information (recorded as device information 1) is used to indicate the remaining available bandwidth water level per second in the first cycle after the CDN device 82 provides service for the user request b, such as 10, 10, 20, 30, and 50 respectively.

[0131] For another example, for user request c, the scheduling system 40 obtains the device information of the CDN device 82. At this time, the device information is based on the updated device information for user request b (i.e., device information 1), and the device information indicates that the available bandwidth water level of the CDN device 82 per second in the first cycle is 10, 10, 20, 30, and 50. Assume that the target time period corresponding to the user request c is the third second of the scheduling cycle, wherein the available bandwidth water level (20 Mbps) in the third second satisfies the download speed (12 Mbps) per second during the continuous service duration of the user request c, and therefore, the user request c can be scheduled to the CDN device 82. The scheduling system 40 updates the device information of the CDN device according to the currently stored device information of the CDN device (i.e., device information 1) and the user request c, and the updated device information (e.g., device information 2) is used to indicate that the remaining available bandwidth water level per second in the first cycle after the CDN device 82 provides services for the user request c is 10, 10, 8, 30, and 50.

[0132] It should be noted that the above updated device information is only an example. In this embodiment, the updated user information may also only include the unit time period of the current time and thereafter, without retaining the historical time. For example, device information 1 only includes the available bandwidth water level value of the 2nd to 5th seconds of the first cycle. Device information 2 only includes the available bandwidth water level value of the 3rd to 5th seconds of the first cycle.

[0133] Among them, the above-mentioned multiple user requests can request content data of different domain names, for example, user request b is used to request content data of domain name A, and user request c is used to request content data of domain name B. That is to say, the CDN device in this embodiment is not limited to providing services for a certain business, but can run mixed services, such as being used to transmit content data of domain name A and content data of domain name B. And which domain name the CDN device provides services for does not need to be manually configured, and can be dynamically changed according to user needs.

[0134] It should be noted that the units of the parameters listed in this article are only examples, and this embodiment does not limit this. It should also be noted that the above-mentioned method of determining the target time period is only an example. The target time period applicable to this embodiment can also be the period from a certain moment after the scheduling system 40 obtains the request to the end of the continuous service duration of the request, etc., without specific limitation.

[0135] Step 506: dispatch the user request to the CDN node.

[0136] If there is no CDN device that can provide services for the request, other scheduling strategies (such as traditional CDN scheduling processes) can be used to schedule the user request, for example, through the aforementioned public network DNS server 50 for scheduling, or the scheduling system can also schedule the request to schedule the request to a CDN node in the same region as the client, and the CDN node provides services for the request. The subsequent process can be referred to the aforementioned related introduction, which will not be repeated here.

[0137] It should be noted that step 506 is an optional step and is not a step that must be performed. For example, when the system does not include a CDN node, step 506 may not be performed. In addition, step 506 may be performed by the scheduling system 40 or by the public network DNS server 50, or by other devices, and this embodiment does not limit this.

[0138] Through the above design, taking the unit time period of 1 second as an example, the scheduling system of this embodiment obtains the device information of the CDN device, thereby obtaining the available bandwidth water level of the CDN device per second within the scheduling period, and for the user request obtained by the scheduling system within the scheduling period, determines the CDN device that meets the service quality requirements of the user request for bandwidth. Under the condition of meeting the service quality, the scheduling system can maximize the allocation of user requests to the CDN device according to the available bandwidth water level of the CDN device per second within the scheduling period, and the scheduling accuracy can reach the second level (when the unit time period is 1 millisecond, the scheduling accuracy can reach the millisecond level). That is, this embodiment can provide a second-level bandwidth planning and scheduling solution for small bandwidth devices. Compared with traditional CDN scheduling technology, it can maximize the bandwidth utilization of small bandwidth devices while ensuring the service quality. Compared with existing scheduling solutions, it can greatly improve bandwidth stability and utilization, and does not limit the type and number of services served on the CDN device, does not require manual configuration of the service model, provides service flexibility, and greatly reduces labor costs.

[0139] Based on the same inventive concept as the method embodiment, the embodiment of the present application also provides a scheduling system, which is used to execute the above Figure 3 and / or Figure 5 The method for scheduling system execution in the method embodiment. Figure 7 As shown, the scheduling system 700 includes an acquisition module 701 and a scheduling module 702; optionally, the scheduling system 700 may also include an update module 703. Specifically, in the scheduling system 700, each module is connected via a communication path.

[0140] The acquisition module 701 is used to acquire the first device information of each CDN device in the one or more CDN devices; wherein the first device information of the CDN device is used to indicate the available bandwidth resources of the CDN device in multiple unit time periods included in the scheduling cycle; for details, see Figure 3 The description of step 302 in the method embodiment, or, see Figure 5 The description of step 502 in the method embodiment will not be repeated here.

[0141] Scheduling module 702 is used to schedule the first user request obtained to the first CDN device among the one or more CDN devices according to the first device information of each CDN device, wherein the first user request is obtained by the scheduling system at the first moment, and the available bandwidth resources of the first CDN device in one or more unit time periods included in the first time period of the scheduling cycle meet the bandwidth service quality requirements of the first user request. For details, see Figure 5 The description of step 504 in the method embodiment will not be repeated here.

[0142] In a possible implementation, the service quality requirement of the first user request for bandwidth includes the continuous service duration required by the first user request and the bandwidth resources required in each unit time period included in the continuous service duration; the available bandwidth resources of the first CDN device in each unit time period of one or more unit time periods included in the first time period within the scheduling period are not less than the bandwidth resources required in the corresponding unit time period in the continuous service duration.

[0143] In a possible implementation, the update module 703 is further used to determine second device information of the first CDN device based on the first device information of the first CDN device and the first user request, where the second device information is used to indicate the remaining available bandwidth resources in each unit time period of one or more unit time periods included in the scheduling period after the first CDN device provides service for the first user request.

[0144] In a possible implementation, the acquisition module 701 is further configured to acquire updated device information of each CDN device in the one or more CDN devices, where the device information is the first device information or the second device information;

[0145] The scheduling module 702 is further configured to schedule the acquired second user request to the first CDN device according to the device information of each CDN device, and the remaining available bandwidth resources of the first CDN device indicated by the second device information in one or more unit time periods included in the second time period in the scheduling cycle meet the bandwidth service quality requirement of the second user request. The first time period and the second time period may be the same time period or different time periods.

[0146] In one possible implementation, the first user request is used to request content data of a first domain name, and the second user request is used to request content data of a second domain name; or the first user request is used to request content data of the first domain name, and the second user request is used to request content data of the first domain name.

[0147] In a possible implementation, the acquisition module 701 is further used to acquire a third user request;

[0148] The scheduling module is further configured to schedule the third user request to the CDN node when it is determined that the one or more CDN devices do not meet the bandwidth quality of service requirement of the third user request; and the bandwidth capacity of the CDN device is lower than the bandwidth capacity of the CDN node.

[0149] Based on the same inventive concept as the method embodiment, the present application embodiment also provides a computing device, which is used to execute the above Figure 3 and / or Figure 5 The method implemented by the CDN device in the method embodiment. Figure 8 As shown, the computing device 800 includes a determination module 801 and a sending module 802. Specifically, in the computing device 800, each module is connected via a communication path.

[0150] The determination module 801 is used to determine the first device information of the device in the scheduling period, where the first device information is used to indicate the available bandwidth resources of the device in each unit time period included in the scheduling period; for details, see Figure 5 The description of step 504 in the method embodiment will not be repeated here.

[0151] The sending module 802 is used to send the first device information to the scheduling system. Figure 3 The description of step 302 in the method embodiment will not be repeated here.

[0152] In a possible implementation, when determining the first device information of the device itself in a future scheduling period, the determination module 801 is specifically used to: determine the remaining service duration of each user request being served by the device at a first moment, and the bandwidth resources occupied in a unit time period included in the remaining service duration of each user request; the first moment is the starting moment of the scheduling period or a moment before the scheduling period; and determine the first device information based on the total bandwidth resources of the device in each unit time period and the bandwidth resources occupied in each unit time period included in the remaining service duration of each user request.

[0153] For example, the following takes the scheduling module 702 in the scheduling system 700 as an example to introduce the implementation of the scheduling module 702. Similarly, the implementation of the acquisition module 701, the update module 703, the determination module 801, and the sending module 802 can refer to the implementation of the scheduling module 702.

[0154] When implemented by software, the scheduling module 702 may be an application or a code block running on a computer device. The computer device may be at least one of a physical host, a virtual machine, a container, and other computing devices. Furthermore, the above-mentioned computer device may be one or more. For example, the scheduling module 702 may be an application running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the application may be distributed in the same availability zone (AZ) or in different AZs. The multiple hosts / virtual machines / containers used to run the application may be distributed in the same region or in different regions. Typically, a region may include multiple AZs.

[0155] Similarly, multiple hosts / virtual machines / containers for running the application can be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Typically, a region can include multiple VPCs, and a VPC can include multiple AZs.

[0156] When implemented by hardware, the scheduling module 702 may include at least one computing device, such as a server, etc. Alternatively, the scheduling module 702 may also be a device implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), etc. The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0157] The multiple computing devices included in the scheduling module 702 can be distributed in the same AZ or in different AZs. The multiple computing devices included in the scheduling module 702 can be distributed in the same region or in different regions. Similarly, the multiple computing devices included in the scheduling module 702 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0158] It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. The functional modules in the embodiments of the present application may be integrated into one module, or each module may exist physically separately, or two or more modules may be integrated into one module, for example, the acquisition module 701 and the scheduling module 702 are integrated into one module, or the scheduling module 702 and the update module 703 are the same module. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0159] The present application also provides a computing device 900. Fig. 9 As shown, the computing device 900 includes: a bus 902, a processor 904, a memory 906, and a communication interface 908. The processor 904, the memory 906, and the communication interface 908 communicate through the bus 902. The computing device 900 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the computing device 900.

[0160] The bus 902 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 9 The bus 902 may include a path for transmitting information between various components of the computing device 900 (eg, the memory 906, the processor 904, and the communication interface 908).

[0161] The processor 904 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

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

[0163] In one embodiment, the computing device 900 is used to execute the functions of the scheduling system 700, wherein the memory 906 stores executable program codes, and the processor 904 executes the executable program codes to respectively implement the functions of the aforementioned acquisition module 701, the scheduling module 702, and the update module 703, thereby implementing the scheduling method. That is, the memory 906 stores instructions for the computing device 900 to execute the scheduling method provided in the present application.

[0164] In another embodiment, the computing device 900 is used to execute the functions of the computing device 800, wherein the memory 906 stores an executable program code, and the processor 904 executes the executable program code to respectively implement the functions of the aforementioned determination module 801 and the sending module 802 ( Fig. 9That is, the memory 906 stores instructions for the computing device 900 to execute the scheduling method provided by the present application.

[0165] The communication interface 908 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 900 and other devices or communication networks.

[0166] The embodiment of the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device may be a server. In some embodiments, the computing device may also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0167] Take the computing device 900 executing the function of the scheduling system 700 as an example. Fig.10 As shown, the computing device cluster includes at least one computing device 900. The memory 906 in one or more computing devices 900 in the computing device cluster may store the same instructions for executing the scheduling method.

[0168] In some possible implementations, the memory 906 of one or more computing devices 900 in the computing device cluster may also store partial instructions for executing the scheduling method. In other words, the combination of one or more computing devices 900 may jointly execute instructions for executing the scheduling method.

[0169] It should be noted that the memory 906 in different computing devices 900 in the computing device cluster can store different instructions, which are respectively used to execute part of the functions of the computing device. That is, the instructions stored in the memory 906 in different computing devices 900 can implement the functions of one or more modules in the acquisition module 701, the scheduling module 702, and the update module 703.

[0170] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network. Fig.11 A possible implementation is shown. Fig.11 As shown, two computing devices 900A and 900B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 906 in the computing device 900A stores instructions for executing the functions of the acquisition module 701. At the same time, the memory 906 in the computing device 900B stores instructions for executing the functions of the scheduling module 702 and the updating module 703.

[0171] It should be understood that Fig.11The functions of the computing device 900A shown in FIG. 9A may also be completed by multiple computing devices 900. Similarly, the functions of the computing device 900B may also be completed by multiple computing devices 900.

[0172] The present application embodiment also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to that of Fig.10 and Fig.11 The connection mode of the computing device cluster is different in that the memory 906 in one or more computing devices 900 in the computing device cluster may store the same instructions for executing the scheduling method.

[0173] In some possible implementations, the memory 906 of one or more computing devices 900 in the computing device cluster may also store partial instructions for executing the scheduling method. In other words, the combination of one or more computing devices 900 may jointly execute instructions for executing the scheduling method.

[0174] The embodiment of the present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes the scheduling method.

[0175] The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the computing device to execute the scheduling method.

[0176] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0177] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server, data center, etc. that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)), etc.

[0178] The various illustrative logic units and circuits described in the embodiments of the present application can be implemented or operated by a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or the design of any combination of the above functions. The general-purpose processor can be a microprocessor, and optionally, the general-purpose processor can also be any traditional processor, controller, microcontroller or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration to implement.

[0179] The steps of the method or algorithm described in the embodiments of the present application can be directly embedded in the software unit executed by the hardware, the processor, or a combination of the two. The software unit can be stored in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM or other storage media of any form in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and can write information to the storage medium. Alternatively, the storage medium can also be integrated into the processor. The processor and the storage medium can be arranged in an ASIC.

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

[0181] Although the present application has been described in conjunction with specific features and embodiments thereof, it is obvious that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, a person skilled in the art may make various modifications and variations to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A scheduling method, characterized in that: The method is applied to a content distribution network (CDN) system, wherein the CDN system includes a scheduling system and one or more CDN devices. The method includes: The scheduling system obtains first device information of each CDN device in the one or more CDN devices; wherein the first device information of the CDN device is used to indicate the available bandwidth resources of the CDN device in multiple unit time periods included in the scheduling cycle; The scheduling system schedules the acquired first user request to a first CDN device among the one or more CDN devices according to the first device information of each CDN device, wherein available bandwidth resources of one or more unit time periods included in a first time period in the scheduling cycle of the first CDN device meet the service quality requirement of the first user request for bandwidth.

2. The method according to claim 1, characterized in that Before the scheduling system obtains the first device information of each CDN device in the one or more CDN devices, the scheduling system further includes: Each CDN device among the multiple CDN devices determines first device information of the CDN device itself within the scheduling period, and sends the first device information to the scheduling system.

3. The method according to claim 2, characterized in that Each CDN device determines the first device information of the CDN device itself within the scheduling period, including: The CDN device determines the remaining service duration of each user request being served by the CDN device itself at a first moment, and the bandwidth resources occupied in a unit time period included in the remaining service duration of each user request; the first moment is the start moment of the scheduling period or a moment before the scheduling period; The CDN device determines the first device information according to the total bandwidth resources of the CDN device itself in each unit time period and the bandwidth resources occupied in each unit time period included in the remaining service duration of each user request.

4. The method according to any one of claims 1 to 3, characterized in that: The service quality requirement of the first user request for bandwidth includes the continuous service duration required by the first user request and the bandwidth resources required in one or more unit time periods included in the continuous service duration; The available bandwidth resources of each unit time period in one or more unit time periods included in the period of time within the scheduling cycle of the first CDN device are not less than the bandwidth resources required by the first user request in the corresponding unit time period in the continuous service duration.

5. The method according to claim 4, characterized in that After dispatching the acquired first user request to the first CDN device, the method further includes: The scheduling system determines second device information of the first CDN device according to the first device information of the first CDN device and the first user request, where the second device information is used to indicate the remaining available bandwidth resources in one or more unit time periods included in the scheduling period after the first CDN device provides service for the first user request.

6. The method according to claim 5, characterized in that The method further comprises: The scheduling system acquires second device information of the first CDN device; The scheduling system schedules the acquired second user request to the first CDN device according to the second device information, and the remaining available bandwidth resources of the first CDN device indicated by the second device information in one or more unit time periods included in the second time period in the scheduling cycle meet the service quality requirement of the second user request for bandwidth.

7. The method according to claim 6, characterized in that The first user request requests content data of a first domain name, and the second user request requests content data of a second domain name; or The first user request is used to request content data of the first domain name, and the second user request is used to request content data of the first domain name.

8. The method according to any one of claims 1 to 7, characterized in that: The CDN system further comprises at least one CDN node, and the bandwidth capability of the CDN device is lower than the bandwidth capability of the CDN node; The method further comprises: The scheduling system obtains a third user request; When the scheduling system determines that the one or more CDN devices do not meet the bandwidth quality of service requirement of the third user request, the scheduling system schedules the third user request to the CDN node.

9. A scheduling system, characterized in that: The system comprises: An acquisition module, configured to acquire first device information of each CDN device in the one or more CDN devices; wherein the first device information of the CDN device is used to indicate available bandwidth resources of the CDN device in a plurality of unit time periods included in a scheduling period; A scheduling module is used to schedule the acquired first user request to a first CDN device among the one or more CDN devices according to the first device information of each CDN device, wherein the available bandwidth resources of one or more unit time periods included in the first time period of the scheduling cycle by the first CDN device meet the service quality requirement of the first user request for bandwidth.

10. The system according to claim 9, characterized in that The service quality requirement of the first user request for bandwidth includes the continuous service duration required by the first user request and the bandwidth resources required in one or more unit time periods included in the continuous service duration; The available bandwidth resources of the first CDN device in each of one or more unit time periods included in the first time period in the scheduling period are not less than the bandwidth resources required by the first user request in the corresponding unit time period included in the continuous service duration.

11. The system according to claim 10, characterized in that The system also includes an update module; The updating module is further used to determine second device information of the first CDN device according to the first device information of the first CDN device and the first user request, wherein the second device information is used to indicate the remaining available bandwidth resources in one or more unit time periods included in the scheduling period after the first CDN device provides service for the first user request.

12. The system according to claim 11, characterized in that The acquisition module is further used to acquire updated device information of each CDN device in the one or more CDN devices, where the device information is the first device information or the second device information; The scheduling module is further configured to schedule the acquired second user request to a second CDN device according to the device information of each CDN device, wherein the remaining available bandwidth resources of the second CDN device in one or more unit time periods included in the second time period in the scheduling cycle meet the bandwidth quality requirement of the second user request.

13. The system of claim 12, wherein: The first user request requests content data of a first domain name, and the second user request requests content data of a second domain name; or The first user request is used to request content data of the first domain name, and the second user request is used to request content data of the first domain name.

14. The system according to any one of claims 9 to 13, characterized in that: The acquisition module is further used to acquire a third user request; The scheduling module is further configured to schedule the third user request to the CDN node when it is determined that the one or more CDN devices do not meet the bandwidth quality of service requirement of the third user request; The bandwidth capability of the CDN device is lower than the bandwidth capability of the CDN node.

15. A computing device, characterized in that: The device comprises: A determination module, configured to determine first device information of the device within a scheduling period, wherein the first device information is used to indicate available bandwidth resources of the device in each unit time period included in the scheduling period; A sending module is used to send the first device information to a scheduling system.

16. The device according to claim 15, characterized in that When determining the first device information of the apparatus within the scheduling period, the determining module is specifically used to: Determine the remaining service duration of each user request being served by the device at a first moment, and the bandwidth resources occupied in a unit time period included in the remaining service duration of each user request; the first moment is the start moment of the scheduling period or a moment before the scheduling period; The first device information is determined according to the total bandwidth resources of the device in each unit time period and the bandwidth resources occupied in each unit time period included in the remaining service duration requested by each user.

17. A content distribution network CDN system, characterized in that: The system includes a scheduling system and at least one CDN device, wherein: The scheduling system is used to execute the method executed by the scheduling system as claimed in any one of claims 1 to 8; Each CDN device is used to execute the method executed by the CDN device as claimed in any one of claims 1 to 8.

18. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method executed by the scheduling system as described in any one of claims 1 to 8, or, the computing device cluster executes the method executed by the CDN device as described in any one of claims 1 to 8.

19. A computer program product comprising instructions, characterized in that When the instruction is executed by a computing device cluster, the computing device cluster executes the method executed by the scheduling system as described in any one of claims 1 to 8, or the computing device cluster executes the method executed by the CDN device as described in any one of claims 1 to 8.

20. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method executed by the scheduling system as claimed in any one of claims 1 to 8, or causes the computing device cluster to execute the method executed by the CDN device as claimed in any one of claims 1 to 8.

Citation Information

Cited By

  • Data transmission method, communication apparatus, and related product

    WO2026144634A1