Scheduling method and device of content distribution network, computer equipment and storage medium

Abstract

The invention relates to the technical field of content distribution networks, and discloses a scheduling method and device for a content distribution network, computer equipment and a storage medium, and the method comprises the steps: dividing physical equipment in the content distribution network, generating a plurality of service platforms, and configuring scheduling domains of the service platforms; setting corresponding service features for each service platform, wherein the service features comprise features of a customer dimension and features of a domain name dimension; determining a corresponding target service platform according to the service characteristics corresponding to the target domain name of the target customer, and associating the target domain name to a scheduling domain of the target service platform to generate a scheduling strategy; and issuing the scheduling strategy to a domain name server, and indicating the domain name server to perform scheduling control on an access request according to the scheduling strategy. According to the method and the device, the requirements of different services can be met, the isolation among the different services is realized, and the mutual influence can be reduced.

Description

Technical Field

[0001] The present disclosure relates to the technical field of content distribution networks, and in particular to a scheduling method, apparatus, computer equipment and storage medium of a content distribution network. Background Art

[0002] CDN (Content Delivery Network) is a distributed network of servers deployed around the world to accelerate content transmission and delivery services on the Internet. When a user requests to access a website or application, CDN can select the server closest to the user to provide content based on the user's location, thereby reducing loading time and improving website performance.

[0003] CDN generally contains a large number of nodes, and the nodes are generally open to multiple customers, which may cause mutual impact between different customers. For example, the domain name of a customer may be affected by a malicious attack from another customer's domain name, or an important customer may request a node upgrade, which may affect the normal business of other customers. Summary of the invention

[0004] In view of this, the present disclosure provides a content distribution network scheduling method, apparatus, computer equipment and storage medium to solve the problem that domain names are prone to affect each other.

[0005] In a first aspect, the present disclosure provides a scheduling method for a content distribution network, comprising:

[0006] Dividing the physical devices in the content distribution network to generate multiple service platforms, and configuring the scheduling domains of the service platforms; the scheduling domains include at least one IP address of the physical device;

[0007] Setting corresponding business features for each of the business platforms, wherein the business features include features in customer dimension and features in domain name dimension;

[0008] Determine the corresponding target business platform according to the business characteristics corresponding to the target domain name of the target customer, and associate the target domain name with the scheduling domain of the target business platform to generate a scheduling strategy;

[0009] The scheduling policy is sent to the domain name server, instructing the domain name server to schedule and control the access request according to the scheduling policy.

[0010] In a second aspect, the present disclosure provides a scheduling device for a content distribution network, including:

[0011] A partitioning module, used to partition the physical devices in the content distribution network, generate multiple service platforms, and configure the scheduling domain of the service platform; the scheduling domain includes an IP address of at least one of the physical devices;

[0012] A setting module, used to set corresponding business features for each of the business platforms, wherein the business features include features in the customer dimension and features in the domain name dimension;

[0013] An allocation module, used to determine a corresponding target business platform according to the business characteristics corresponding to the target domain name of the target customer, and associate the target domain name with the scheduling domain of the target business platform to generate a scheduling strategy;

[0014] The scheduling module is used to send the scheduling policy to the domain name server, and instruct the domain name server to schedule and control the access request according to the scheduling policy.

[0015] In a third aspect, the present disclosure provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the scheduling method for a content distribution network of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0016] In a fourth aspect, the present disclosure provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the content distribution network scheduling method of the first aspect or any corresponding embodiment thereof.

[0017] In a fifth aspect, the present disclosure provides a computer program product, including computer instructions, where the computer instructions are used to enable a computer to execute the content distribution network scheduling method of the first aspect or any corresponding implementation manner thereof.

[0018] The present disclosure divides the business platforms corresponding to the corresponding business characteristics according to the business characteristics such as the characteristics of the customer dimension and the characteristics of the domain name dimension, and associates the customer's domain name with the scheduling domain of the business platform to generate a scheduling strategy, so that when the user initiates an access request for the domain name, the scheduling domain corresponding to the domain name can be determined based on the scheduling strategy, and then the appropriate physical device can be located to achieve the scheduling management of the domain name according to the business characteristics. By dividing the physical devices into business platforms with certain business characteristics, different businesses can be allocated to different platforms, which can meet the needs of different businesses, and achieve isolation between different businesses, which can reduce the impact on each other; when the domain name of a certain business is attacked or needs to be blocked, the impact on other businesses can be minimized. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the related technologies, the drawings required for use in the specific embodiments or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0020] Figure 1 is a schematic diagram of a user accessing a CDN node according to an embodiment of the present disclosure;

[0021] Figure 2 is a flow chart of a scheduling method for a content distribution network according to an embodiment of the present disclosure;

[0022] Figure 3 is a schematic diagram of dividing a service platform according to an embodiment of the present disclosure;

[0023] Figure 4 is a schematic diagram of managing domain name access by using a scheduling domain according to an embodiment of the present disclosure;

[0024] Figure 5 is a schematic diagram of a process of a user accessing a corresponding service platform according to an embodiment of the present disclosure;

[0025] Figure 6 is a flow chart of another content distribution network scheduling method according to an embodiment of the present disclosure;

[0026] Figure 7 is a schematic diagram of a process of switching a domain name platform according to an embodiment of the present disclosure;

[0027] Figure 8 is a structural block diagram of a scheduling device for a content distribution network according to an embodiment of the present disclosure;

[0028] Fig. 9 It is a schematic diagram of the hardware structure of the computer device of the embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present disclosure.

[0030] The working principle of CDN is to cache the website's static resources such as pictures, videos, CSS (Cascading Style Sheets), JavaScript files, etc. on servers located in different geographical locations. When users request to access these resources, CDN will automatically transmit the content from the nearest server to the user instead of loading it directly from the original server. This can reduce network congestion, reduce latency, increase page loading speed, and thus improve user experience.

[0031] like Figure 1 As shown in the figure, users can access the required resources through clients such as browsers and mobile terminals; if CDN node 1 (edge ​​node) stores the resource, it can return the resource to the user. If CDN node 1 does not have the resource, it can jump inside the CDN until it returns to the source station. Figure 1 As shown, there are a large number of CDN nodes in front of the source station. These nodes can effectively help the source station share the pressure and speed up the speed at which the client obtains the results.

[0032] In a CDN, there are generally a large number of CDN nodes (machines); for any mature CDN vendor, the number of machines in its CDN can easily reach tens of thousands, and one or some nodes are generally open to multiple customers.

[0033] For such a large and complex CDN network architecture, the following problems are often encountered:

[0034] 1. Since the same node can be open to different customers, if a customer's domain name is vulnerable to malicious attacks, and the domain name of another secure customer shares the same node with that user, the malicious attack may affect the secure user.

[0035] 2. When important customers are involved in important activities (for example, e-commerce customers will hold promotional activities on certain dates, etc.), they often ask CDN manufacturers to block the network (for example, suspend software release and upgrade) to avoid affecting them; if the node involving the important user is directly blocked, it may affect the normal business of other customers and may even affect the entire CDN platform.

[0036] A scheduling method for a content distribution network provided by an embodiment of the present disclosure divides physical devices in a CDN into multiple business platforms, and allocates each customer's domain name to a scheduling domain of a corresponding business platform according to the business characteristics of the domain name itself, so that the domain name access request of the client can be scheduled according to the corresponding scheduling domain, and the IP address of the physical device in the corresponding business platform can be returned to the client, thereby achieving isolation between different domain names at the physical level and reducing mutual influence between domain names.

[0037] According to an embodiment of the present disclosure, an embodiment of a scheduling method for a content distribution network is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0038] In this embodiment, a scheduling method for a content distribution network is provided, which can be applied to a central node in a content distribution network. The central node is a node for providing central services such as scheduling management and domain name management. Figure 2 is a flowchart of a scheduling method for a content distribution network according to an embodiment of the present disclosure, such as Figure 2 As shown, the process includes the following steps.

[0039] Step S201, divide the physical devices in the content distribution network, generate multiple service platforms, and configure the scheduling domains of the service platforms; the scheduling domain includes the IP address of at least one physical device.

[0040] In a content distribution network, multiple CDN nodes are set up in different locations, and each CDN node generally has multiple servers, which can be, for example, RS (Resource Server) for managing resources. Among them, a CDN node can be roughly considered equivalent to a "computer room".

[0041] In this embodiment, when dividing the service platform, the server can be used as the smallest unit of division, that is, the servers in the CDN can be divided, so that multiple service platforms can be generated. Alternatively, several servers can be grouped into a cluster, for example, servers with similar performance or adjacent geographical locations can be grouped into a cluster; when dividing the service platform, the cluster can also be used as the smallest unit, that is, the clusters in the CDN can be divided, so that multiple service platforms can be generated;

[0042] Figure 3 A schematic diagram of dividing a service platform is shown, and the clusters in the CDN nodes are logically divided to generate multiple service platforms. Figure 3 As shown, the clusters are divided according to the business types of each cluster in CDN node 1 and CDN node 2, and a picture cluster involving picture business and a on-demand cluster involving on-demand business can be determined; the picture clusters in the two CDN nodes can be combined into a business platform, namely, a picture platform, and the on-demand clusters in the two CDN nodes can be combined into a business platform, namely, a on-demand platform.

[0043] In addition, due to the large number of CDN nodes, corresponding scheduling domains are set to control which nodes the client accesses. In this embodiment, a corresponding scheduling domain can be configured for each service platform according to the physical devices corresponding to the service platform. Among them, the scheduling domain includes the IP (Internet Protocol) address of the physical device belonging to the service platform, that is, the scheduling domain manages which physical devices the user access request can access. For a service platform, one scheduling domain can be configured for it, or multiple scheduling domains can be configured, which can be determined based on actual conditions.

[0044] For example, you can set up access scheduling domains, back-to-source scheduling domains, etc. Among them, the access scheduling domain controls which node IPs are spit out by the DNS authoritative server, and the back-to-source scheduling domain controls the access policy between CDN nodes and what kind of IP addresses should be accessed.

[0045] Figure 4 FIG. 1 shows a schematic diagram of using a scheduling domain to manage domain name access. Figure 4 As shown, when the client accesses www.a.com / 1.mp4, it first queries www.a.com from the DNS authoritative server and obtains the accessible IP address. This process can implement access control based on the access scheduling domain. If the IP address is the IP address of CDN edge node 1, CDN edge node 1 can be accessed.

[0046] If the CDN edge node 1 does not have the resources required by the client, it needs to go back to the upper layer to get the cache, or go back to the source, etc. Figure 4 As shown, CDN edge node 1 can query the www.a.com back-to-origin policy from the back-to-origin scheduling server and obtain the back-to-origin policy and next-hop IP address. This process can implement access control based on the back-to-origin scheduling domain. If the next-hop IP address is the IP address of CDN intermediate node 2, CDN intermediate node 2 can be accessed continuously until the resources required by the client are obtained.

[0047] Step S202: Set corresponding business features for each business platform. Business features include features in the customer dimension and features in the domain name dimension.

[0048] In this embodiment, in order to allocate appropriate service platforms to different customers, appropriate service features are set for each service platform, and the service features specifically include service features of customer dimension and domain name dimension.

[0049] As the name implies, the features of the customer dimension are features related to the customer, for example, the features of the customer dimension may include customer level, customer identification, etc. The features of the domain name dimension are features related to the domain name, for example, the features of the domain name dimension may include domain name business type, domain name naming rules, etc. Among them, the customer level can be a designated level for different customers, for example, it can be calculated according to certain rules, and the specific rules depend on the division strategy of the CDN manufacturer, which will not be described in detail here.

[0050] Optionally, regional characteristics may also be set for the business platform according to the regions mainly involved in the customer's business, that is, the business characteristics may also include regional characteristics.

[0051] For example, service features include customer level, acceleration area, and domain name service type; Table 1 below shows the service features set for each service platform. Among them, customer level is divided into KA (Key Account) and longtail (mid- and long-tail customers, referring to customers with relatively small visits or monthly active users), acceleration area is divided into domestic and overseas, and domain name service type is divided into on-demand, download, web page, competitive tuning, etc.

[0052] Table 1

[0053]

[0054] As shown in Table 1, various business platforms can be divided into mid- and long-tail platforms, high-traffic platforms, etc. according to different business scenarios.

[0055] Among them, the mid- and long-tail platforms mainly serve mid- and long-tail customers in the domestic area. Although the overall traffic is small, there are more attacks on this type of business, and the platform needs to have high defense capabilities.

[0056] Large-traffic platform: mainly serves domestic areas, and provides services such as on-demand and downloading with large files and large traffic. The nodes on the platform need to have a high storage capacity.

[0057] Image platform: It mainly serves domestic areas and small-file, low-traffic businesses such as web pages and images. The nodes on the platform need to have high performance to cope with high Qps (Queries-per-second) scenarios.

[0058] Racing platform: mainly serves large customers in the domestic area, with comprehensive node coverage and lower access latency than other platforms, and can be used for business speed regulation and racing.

[0059] Overseas mid- and long-tail platforms: They mainly serve mid- and long-tail customers in overseas regions. Although the overall traffic volume is relatively small, there are many types of business attacks, so the platform needs to have high defense capabilities.

[0060] Overseas high-traffic platform: mainly serves overseas regions, and provides services such as on-demand and downloading with large files and high-traffic. The nodes on the platform need to have a high storage capacity.

[0061] Overseas image platform: mainly serves overseas regions, and is used for small-text, small-traffic businesses such as web pages and images. The nodes on the platform need to have high performance to cope with high Qps scenarios.

[0062] Overseas Speed ​​Racing Platform: It mainly serves large customers in overseas regions. It has comprehensive node coverage and lower access latency than other platforms. It can be used for business speed regulation and speed racing.

[0063] It can be understood that when dividing the service platform, the physical devices can also be divided according to the business characteristics of the business that the physical devices are suitable for; Figure 3 As shown, picture clusters suitable for picture services can be divided to form a picture platform.

[0064] Step S203, determining the corresponding target service platform according to the service characteristics corresponding to the target domain name of the target customer, and associating the target domain name with the scheduling domain of the target service platform to generate a scheduling strategy.

[0065] In this embodiment, for the convenience of description, the customer who needs to be assigned a business platform is called a target customer, and the corresponding domain name is called a target domain name. For the target domain name of the target customer, the characteristics of the customer dimension and the domain name dimension can be determined, that is, the business characteristics of the target domain name of the target customer can be determined. Therefore, based on the business characteristics corresponding to the target domain name of the target customer, the target domain name can be assigned to the corresponding business platform, that is, the target business platform; and the target domain name is associated with the scheduling domain of the target business platform, so that the access request of the target domain name can be directed to the physical device of the target business platform in the future.

[0066] For each domain name, platform allocation and scheduling domain association can be performed in the manner of step S203, and a corresponding scheduling policy can be generated. The scheduling policy can include the association relationship between each domain name and the scheduling domain.

[0067] Step S204: Send the scheduling policy to the domain name server, instructing the domain name server to schedule and control the access request according to the scheduling policy.

[0068] In this embodiment, the central node can send the scheduling policy to the domain name server, so that when the domain name server receives the access request initiated by the client, it can perform corresponding scheduling control based on the scheduling policy to return a suitable IP address. For example, the domain name server can be a DNS authoritative server, etc. The DNS authoritative server can perform domain name resolution on the access request based on the scheduling policy to return the IP address corresponding to the accessed domain name to the client.

[0069] Figure 5 Figure 1 shows a schematic diagram of the process of a user accessing a corresponding service platform. Figure 5 As shown, the central node of CDN has functions such as domain name management and scheduling management. After generating the scheduling strategy, it can send the scheduling strategy to the domain name server, such as the DNS authoritative server. When the user needs to access www.a.com / 1.mp4 based on the client, he can initiate an access request to the domain name server to query the IP address of www.a.com; the domain name server determines the scheduling domain associated with the domain name www.a.com according to the scheduling strategy. If the domain name is associated with the scheduling domain of the on-demand platform, the IP address in the scheduling domain associated with the domain name is the IP address of the on-demand cluster. At this time, the domain name server can return the appropriate IP address to the client, for example, return the IP address of the on-demand cluster closest to the client to the client, so that the client can access the corresponding on-demand cluster based on the returned IP address.

[0070] The scheduling method of the content distribution network provided in this embodiment divides the business platforms corresponding to the corresponding business characteristics according to the business characteristics such as the characteristics of the customer dimension and the characteristics of the domain name dimension, and associates the customer's domain name with the scheduling domain of the business platform to generate a scheduling strategy, so that when the user initiates an access request for the domain name, the scheduling domain corresponding to the domain name can be determined based on the scheduling strategy, and then the appropriate physical device can be located to achieve the scheduling management of the domain name according to the business characteristics. By dividing the physical devices into business platforms with certain business characteristics, different businesses can be allocated to different platforms, which can meet the needs of different businesses, and achieve isolation between different businesses, which can reduce the impact on each other; when the domain name of a certain business is attacked or needs to be blocked, the impact on other businesses can be minimized.

[0071] In this embodiment, another content distribution network scheduling method is provided, which can be applied to a central node in a content distribution network. The central node is a node for providing central services such as scheduling management and domain name management. Figure 6 is a flowchart of a scheduling method for a content distribution network according to an embodiment of the present disclosure, such as Figure 6 As shown, the process includes the following steps.

[0072] Step S601, divide the physical devices in the content distribution network, generate multiple service platforms, and configure the scheduling domains of the service platforms; the scheduling domain includes the IP address of at least one physical device.

[0073] For details, please see Figure 2 Step S201 of the illustrated embodiment will not be described in detail here.

[0074] Step S602, setting corresponding business features for each business platform, the business features include features in the customer dimension and features in the domain name dimension.

[0075] For details, please see Figure 2 Step S202 of the illustrated embodiment will not be described in detail here.

[0076] Step S603, determining the corresponding target service platform according to the service characteristics corresponding to the target domain name of the target customer, and associating the target domain name with the scheduling domain of the target service platform to generate a scheduling strategy.

[0077] For details, please see Figure 2 Step S203 of the illustrated embodiment will not be described in detail here.

[0078] In some optional implementations, the method may further include step A1.

[0079] Step A1: Allocate the customized customer to the corresponding customized service platform, and associate the domain name of the customized customer with the scheduling domain of the customized service platform.

[0080] Specifically, the step A1 "assigning the customized customer to the corresponding customized service platform, and associating the domain name of the customized customer to the scheduling domain of the customized service platform" may include steps A11 to A12.

[0081] Step A11, setting a correspondence between customized features and customized business platforms for customized customers, and assigning customized customers to corresponding customized business platforms according to the correspondence; customized features include features in customer dimension and / or features in domain name dimension.

[0082] Step A12: When the domain name dimension in the customized feature includes a domain name naming rule, the domain name that belongs to the customized customer and complies with the domain name naming rule is associated with the scheduling domain of the customized business platform.

[0083] In this embodiment, for customized customers, such as relatively important large customers, a suitable business platform, i.e., a customized business platform, can be manually assigned to them, specifically by setting a customized policy for the customized customer. The customized policy specifically includes the correspondence between customized features and customized business platforms. Based on the customized policy, it is determined which scheduling domain the domain name of the customized user needs to be associated with.

[0084] Specifically, personalized platform allocation strategies can be formulated for different types of customers and different types of businesses to optimize and adapt specific business scenarios. The supported customized features include customer dimension features and / or domain dimension features, and other features, such as regional features, which can be added or deleted based on actual needs.

[0085] For example, the customized features supported by this embodiment may include the dimensions shown in the following Table 2.

[0086] Table 2

[0087]

[0088] In this embodiment, appropriate customized features may be set according to the features of some or all dimensions shown in Table 2, and appropriate customized service platforms may be allocated to customized customers, thereby establishing a corresponding relationship between customized features and customized service platforms.

[0089] If, in the customized features, the features of the domain name dimension include domain name naming rules, when associating the domain name with the scheduling domain, the domain name that complies with the domain name naming rules needs to be associated with the scheduling domain of the customized business platform.

[0090] For example, if the customization features of a certain customization strategy are shown in Table 3 below, the service platform to which it is connected is the racing platform, that is, the customized service platform is the racing platform.

[0091] Table 3

[0092]

[0093]

[0094] If an access domain name of the customized customer is www.abc.com, the domain name naming meets the domain name naming rule of *.abc.com, so the domain name is allocated and connected to the racing platform, and it is associated with the scheduling domain of the racing platform.

[0095] In this embodiment, by allowing customized customers to customize personalized allocation strategies, a suitable business platform can be personalized allocated to the customized customer's domain name. After the business platform is determined for the domain name, access to the domain name can be requested to the corresponding platform cluster, which can meet the business needs of different customers.

[0096] Step S604: Send the scheduling policy to the domain name server, instructing the domain name server to schedule and control the access request according to the scheduling policy.

[0097] For details, please see Figure 2 Step S204 of the illustrated embodiment will not be described in detail here.

[0098] Step S605, obtaining a platform switching instruction; the platform switching instruction is used to switch the domain name to be switched from the first service platform to the second service platform.

[0099] In this embodiment, during the operation process, it may be necessary to dynamically adjust the service platform accessed by the domain name to adapt to the development needs of customers and services.

[0100] When switching platforms for a domain name or all domain names of a customer, the domain name is used as the domain name to be switched, and a corresponding platform switching instruction can be generated to switch the domain name to be switched from the old first service platform to the new second service platform.

[0101] The platform switching instruction can be automatically generated or manually generated. That is, the platform for domain name allocation can be automatically switched, and administrators can also manually switch the platform for domain name allocation. For example, if the business characteristics of a customer's domain name change in any dimension, such as the customer level changes from "longtail" to "KA", the domain name business type changes from "on-demand" to "web page", or the acceleration area changes from "domestic" to "overseas", etc., it may trigger the automatic switching process.

[0102] In some optional embodiments, if customers are allowed to personalize the assigned business platform, for example, the method also includes the above-mentioned step A1 "assigning the customized customer to the corresponding customized business platform, and associating the customized customer's domain name to the scheduling domain of the customized business platform", then for the customized customer's domain name, in order to avoid business confusion caused by automatic switching, generally only manual switching is allowed.

[0103] Specifically, the above step S605 "obtaining a platform switching instruction" may include step B1, or step B2.

[0104] Step B1, obtaining a manually input platform switching instruction.

[0105] Step B2, determine the domain name whose business characteristics have changed, and judge whether the domain name whose business characteristics have changed belongs to a customized customer; if it does not belong to a customized customer, treat the domain name whose business characteristics have changed as a domain name to be switched, and automatically generate a corresponding platform switching instruction.

[0106] In this embodiment, if the platform switching instruction is manually input, it is not necessary to determine whether a customized customer is involved, and the subsequent step S606 can be directly executed. If the system automatically determines that a platform switching may be required, it is necessary to further determine whether a customized customer is involved.

[0107] Specifically, as shown in the above step B2, when the business characteristics of a domain name change, it is necessary to further determine whether the domain name is a customized customer's domain name; if the domain name is a customized customer's domain name, the process ends and the subsequent platform switching process is not executed. If the domain name is not a customized customer's domain name, the platform switching of the domain name can be performed, that is, the platform switching instruction of the domain name is automatically generated, and the domain name is a domain name to be switched.

[0108] For example, if the business platform is divided as shown in Table 1, the automatic platform switching action triggered by certain domain names due to business characteristics may be shown in Table 4 below.

[0109] Table 4

[0110]

[0111]

[0112] As shown in Table 4 above, even if the customer level of the domain name www.d.com changes, it will not trigger the automatic switching logic because it has a customized policy, that is, it is a customized customer. If the domain name www.d.com needs to switch platforms, a manual switching policy needs to be executed. For example, the CDN operation and maintenance personnel are responsible for executing the manual switching policy and manually executing the switching action for several domain names that need to switch platforms.

[0113] Step S606: Switch the scheduling domain associated with the domain name to be switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform.

[0114] In this embodiment, whether the platform switching instruction is triggered manually or automatically, it involves the old first business platform and the new second business platform. By switching the scheduling domain associated with the switching domain name, that is, switching from the scheduling domain of the first business platform to the scheduling domain of the second business platform, the platform switching of the domain name to be switched can be achieved.

[0115] In some optional implementations, the above step S606 "switching the scheduling domain associated with the domain name to be switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform" specifically includes steps C1 to C5.

[0116] Step C1: Send the domain name configuration of the domain name to be switched to each physical device of the second service platform, and refresh the cache of the domain name to be switched of each physical device in the second service platform.

[0117] In this embodiment, when it is necessary to perform platform switching on the domain name to be switched, each physical device in the new second service platform is pre-configured to ensure that the second service platform meets the access requirements of the domain name to be switched.

[0118] Specifically, the configuration can be triggered to send the domain name configuration to each physical device of the second business platform. The domain name configuration may include, for example, the domain name cache time, request header, other conventional configurations, etc. The domain name configuration may also include the source station of the domain name back to the source, the specific cache strategy, etc. In addition, the cache of the domain name to be switched on each physical device in the second business platform is also refreshed. Through cache refresh, part or all of the URL cache of the domain name to be switched can be cleared to avoid cache invalidation and other problems, depending on the refresh strategy.

[0119] Step C2: performing a first acceptance operation on the second service platform.

[0120] In this embodiment, before switching the scheduling domain, it is necessary to perform acceptance on the second service platform, that is, the first acceptance operation, to ensure that the second service platform preliminarily meets the requirements for platform switching.

[0121] Optionally, the step C2 of “performing a first acceptance operation on the second service platform” may specifically include steps C21 and C22.

[0122] Step C21 , performing a detection scan on multiple physical devices under test in the second service platform according to the detection URL, and determining the detection result of each physical device under test.

[0123] Step C22, when each physical device in the second business platform is provided with a domain name configuration of the domain name to be switched, each physical device in the second business platform completes cache refresh, and the detection results of each tested physical device are consistent, it is determined that the second business platform has passed the first acceptance operation.

[0124] In this embodiment, the URL of a resource in the domain name to be switched is used as the detection URL, and some physical devices in the second business platform are used as the physical devices to be tested. Based on the detection URL, these physical devices to be tested are probed and scanned to determine the detection results of each physical device to be tested. The detection results can indicate whether the domain name to be switched can be accessed normally.

[0125] If each physical device in the second service platform is configured with the domain name to be switched, and each physical device in the second service platform completes the cache refresh, it can be considered that the second service platform preliminarily meets the domain name access requirements. In addition, if the detection results returned by each tested physical device are consistent, for example, the summaries of each detection result (for example, md5 code, etc.) are the same, it can be determined that each detection result is consistent, and at this time, the second service platform can be artificially allowed to access the domain name to be switched normally.

[0126] It can be understood that generally, each physical device in the second service platform is provided with a domain name configuration of the domain name to be switched, and after each physical device in the second service platform completes cache refresh, verification is performed based on the detection URL.

[0127] Among them, when performing the first acceptance operation, the alarm sensitivity of the domain name to be switched can also be improved, such as increasing the HTTP error status code, decreasing bandwidth, access delay and other indicators, so as to detect problems in time.

[0128] Step C3, when the second service platform passes the first acceptance operation, the scheduling domain associated with the domain name to be switched is switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform.

[0129] In this embodiment, if the second service platform passes the first acceptance operation, the scheduling domain can be switched.

[0130] Optionally, the above step S606, or step C3 "switching the scheduling domain associated with the domain name to be switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform" may include the following steps C31 to C33.

[0131] Step C31, setting the grayscale range for platform switching.

[0132] Step C32: Switch the scheduling domain in the grayscale range associated with the domain name to be switched from the first scheduling domain in the grayscale range in the first service platform to the second scheduling domain in the grayscale range in the second service platform.

[0133] Step C33, monitoring the scheduling status of the physical device corresponding to the second scheduling domain for the domain name to be switched, and when the scheduling status meets the requirements, performing full switching on the scheduling domain associated with the domain name to be switched.

[0134] In this embodiment, in order to avoid problems in the switching process and ensure that the switching process is smooth and has minimal impact on users, a part of the full range of platform switching is first used as the grayscale range, and the scheduling domain of the grayscale range is switched first. If there is no problem with the grayscale range switching, the scheduling domain of the full range is fully switched.

[0135] For example, a part of the range can be divided as a grayscale range according to geographical location (province, city, etc.), operator, etc., and the platform switching is first performed on the grayscale range.

[0136] For example, if the traffic of a province A to the domain name to be switched is relatively small, the range corresponding to the province A can be used as the grayscale range. For the scheduling domain associated with the domain name to be switched, part of the scheduling domain belonging to the province A, namely the first scheduling domain, corresponds to the IP address of the physical device located in the province A in the first business platform; switch this part of the scheduling domain and adjust it to the IP address of the physical device located in the province A in the second business platform, thereby switching to the second scheduling domain to achieve platform switching in the grayscale range.

[0137] By monitoring the physical devices corresponding to the second scheduling domain, the scheduling of these physical devices for the domain name to be switched can be determined, and then the stability, performance and other scheduling conditions can be determined to meet the requirements. If the grayscale range is successfully switched, the full release can be carried out, that is, the scheduling domain associated with the domain name to be switched can be fully switched.

[0138] If the switching within the grayscale range does not meet the requirements, a rollback is required, that is, the first business platform continues to process the access request of the domain name to be switched and reports an error.

[0139] It can be understood that multiple grayscale ranges can be set, and this embodiment does not limit the number and size of the grayscale ranges.

[0140] Step C4, performing a second acceptance operation on the second service platform.

[0141] In this embodiment, after the full switching, the previous switching operation is checked again, that is, the second checking operation is performed to ensure that the switching process is stable and reliable.

[0142] Optionally, step C4 “performing a second acceptance operation on the second service platform” may specifically include steps C41 to C42.

[0143] Step C41, determining whether the traffic of the second service platform meets expectations, and determining whether the first service platform is switched completely.

[0144] Step C42, when the traffic of the second service platform is as expected and the first service platform is completely switched, it is determined that the second service platform has passed the second acceptance operation.

[0145] In this embodiment, it can be determined whether the traffic of the second service platform meets expectations. For example, it can be determined whether the traffic of the domain name to be switched in the second service platform is basically consistent with the traffic of the domain name to be switched in the first service platform. If the two are consistent, it can be considered that the traffic of the second service platform meets expectations.

[0146] In addition, it is determined whether the old first business platform has been completely switched, that is, whether the DNS has been effective in the entire network to avoid omissions and other problems. If the traffic of the second business platform is as expected and the first business platform has been completely switched, it can be determined that the second acceptance operation has passed, and then the second business platform can fully respond to access requests for the domain name to be switched.

[0147] Step C5: when the second service platform passes the second acceptance operation, the domain name configuration of the domain name to be switched in the first service platform is deleted.

[0148] Finally, the domain name configuration of the domain name to be switched in the first service platform may be deleted to achieve resource recovery.

[0149] Figure 7 A schematic diagram of the process of switching the domain name platform is shown. Figure 7 As shown, after manually or automatically initiating a domain name platform switch, the input information can be determined according to the needs of the switching process. The input information includes: the domain name to be switched, the target platform to be switched (i.e., the second business platform), the scheduling domain of the target platform to be switched, the detection URL, etc.

[0150] For example, the domain name to be switched is www.a.com; if the platform A needs to be switched to the platform B, the target platform is platform B; the scheduling domain of the target platform to be switched is the scheduling domain of platform B, for example, plat-b.sched.volcgslb.com; the detection URL is https: / / www.a.com / 1.txt.

[0151] When executing the platform switching process, domain name management updates can be performed, and the configuration delivery and cache refresh steps can be performed in parallel. For example, configuration delivery can be triggered to deliver the domain name configuration to the target platform, that is, platform B; and the cache of the domain name www.a.com on platform B can be refreshed to prevent the domain name from being affected by the old cache on platform B.

[0152] After that, the first acceptance action is carried out, which includes:

[0153] 1. Ensure that the cache on platform B has been refreshed;

[0154] 2. Ensure that the domain name configuration has been successfully issued on platform B, and all physical devices on platform B are configured with the domain name www.a.com;

[0155] 3. Select several physical devices to perform detection URL scanning to confirm that the md5 of the URL content between the physical devices is consistent to ensure cache consistency;

[0156] 4. Improve the sensitivity of domain name alerts to ensure timely detection of problems.

[0157] After all the first acceptance actions have passed, the subsequent steps can be continued after confirmation by the operation and maintenance personnel.

[0158] Specifically, the switching action of the scheduling domain is executed to switch the domain name scheduling domain to the new platform B. The process specifically includes: selecting the scope to be grayscaled, such as provinces / cities, operators, etc., and issuing grayscale; after the grayscale steps are completed and confirmed to be full, the full amount is released.

[0159] The second acceptance action may include: ensuring that all traffic on the old platform has been cut off and that the traffic on the new platform meets expectations; and observing whether the scheduling of the old platform has been completely switched and that DNS has taken effect on the entire network.

[0160] After all the second acceptance actions have passed and have been confirmed by the operation and maintenance personnel, the subsequent steps can be continued, that is, the domain name configuration on the old platform (ie, platform A) is recovered and deleted, thereby completing the domain name switching process.

[0161] The content distribution network scheduling method provided in this embodiment supports the division and allocation strategy of multiple platforms on CDN. It can meet the needs of different businesses by means of reasonable and efficient means to divide the platforms, and can allocate different businesses to different platforms according to specific strategies, thereby reducing the mutual influence between domain names. In addition, it supports the platform switching strategy and corresponding capabilities under the CDN multi-platform architecture, and can ensure the smoothness and stability of the switching process through operations such as multi-no verification and grayscale distribution, and the domain name traffic is not interrupted, thereby reducing the impact on customer business operations.

[0162] In the present embodiment, a scheduling device for a content distribution network is also provided, and the device is used to implement the above-mentioned embodiment and preferred implementation mode, and the descriptions that have been made are not repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware is also possible and conceived.

[0163] This embodiment provides a scheduling device for a content distribution network, such as Figure 8 As shown, including:

[0164] The division module 801 is used to divide the physical devices in the content distribution network, generate multiple service platforms, and configure the scheduling domain of the service platform; the scheduling domain includes the IP address of at least one of the physical devices;

[0165] A setting module 802, used to set corresponding business features for each of the business platforms, wherein the business features include features in the customer dimension and features in the domain name dimension;

[0166] The allocation module 803 is used to determine the corresponding target business platform according to the business characteristics corresponding to the target domain name of the target customer, and associate the target domain name with the scheduling domain of the target business platform to generate a scheduling strategy;

[0167] The scheduling module 804 is used to send the scheduling policy to the domain name server, and instruct the domain name server to schedule and control the access request according to the scheduling policy.

[0168] In some optional embodiments, the device further includes a switching module, configured to:

[0169] Obtaining a platform switching instruction; the platform switching instruction is used to switch the domain name to be switched from the first service platform to the second service platform;

[0170] The scheduling domain associated with the domain name to be switched is switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform.

[0171] In some optional implementations, the switching module switches the scheduling domain associated with the domain name to be switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform, including:

[0172] Sending the domain name configuration of the domain name to be switched to each physical device of the second service platform, and refreshing the cache of the domain name to be switched of each physical device in the second service platform;

[0173] Performing a first acceptance operation on the second service platform;

[0174] If the second service platform passes the first acceptance operation, switching the scheduling domain associated with the domain name to be switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform;

[0175] Performing a second acceptance operation on the second service platform;

[0176] When the second service platform passes the second acceptance operation, the domain name configuration of the domain name to be switched in the first service platform is deleted.

[0177] In some optional implementations, the switching module performs a first acceptance operation on the second service platform, including:

[0178] Performing a detection scan on a plurality of physical devices under test in the second service platform according to the detection URL, and determining a detection result of each of the physical devices under test;

[0179] When each physical device in the second service platform is provided with a domain name configuration of the domain name to be switched, each physical device in the second service platform completes cache refresh, and the detection results of each of the tested physical devices are consistent, it is determined that the second service platform passes the first acceptance operation;

[0180] The switching module performs a second acceptance operation on the second service platform, including:

[0181] Determine whether the traffic of the second service platform meets expectations, and determine whether the first service platform is completely switched;

[0182] When the traffic of the second service platform is as expected and the first service platform is completely switched, it is determined that the second service platform has passed the second acceptance operation.

[0183] In some optional implementations, the switching module switches the scheduling domain associated with the domain name to be switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform, including:

[0184] Set the grayscale range for platform switching;

[0185] Switching the scheduling domain associated with the domain name to be switched and belonging to the grayscale range from the first scheduling domain belonging to the grayscale range in the first service platform to the second scheduling domain belonging to the grayscale range in the second service platform;

[0186] The scheduling status of the domain name to be switched by the physical device corresponding to the second scheduling domain is monitored, and when the scheduling status meets the requirements, the scheduling domain associated with the domain name to be switched is fully switched.

[0187] In some optional implementations, the setting module 802 is further configured to:

[0188] Allocating customized customers to corresponding customized service platforms, and associating the domain names of the customized customers to the scheduling domains of the customized service platforms;

[0189] The partitioning module 801 obtains a platform switching instruction, including:

[0190] Get manually input platform switching instructions;

[0191] Alternatively, determining a domain name whose service characteristics have changed, and judging whether the domain name whose service characteristics have changed belongs to a customized customer;

[0192] In the case of not being a customized customer, the domain name with the changed business characteristics is taken as the domain name to be switched, and a corresponding platform switching instruction is automatically generated.

[0193] In some optional implementations, the setting module 802 is further configured to:

[0194] Allocating customized customers to corresponding customized service platforms, and associating the domain names of the customized customers to the scheduling domains of the customized service platforms;

[0195] Furthermore, allocating the customized customer to the corresponding customized service platform and associating the domain name of the customized customer to the scheduling domain of the customized service platform includes:

[0196] Setting a correspondence between customized features and customized business platforms for the customized customers, and assigning the customized customers to corresponding customized business platforms according to the correspondence; the customized features include features in the customer dimension and / or features in the domain name dimension;

[0197] In the case where the feature of the domain name dimension in the customization feature includes a domain name naming rule, the domain name belonging to the customization customer and conforming to the domain name naming rule is associated with the scheduling domain of the customization service platform.

[0198] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0199] The scheduling device of the content distribution network in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, including a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0200] The present disclosure also provides a computer device having the above Figure 8 A scheduling device for a content distribution network is shown.

[0201] See also Fig. 9 , Fig. 9 is a schematic diagram of a computer device provided by an optional embodiment of the present disclosure, such as Fig. 9As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Fig. 9 A processor 10 is taken as an example.

[0202] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0203] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0204] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0205] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0206] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0207] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0208] A part of the present disclosure may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present disclosure through the operation of the computer. Those skilled in the art should understand that the existence of computer program instructions in computer-readable media includes, but is not limited to, source files, executable files, installation package files, etc., and accordingly, the way in which computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to the computer.

[0209] Although the embodiments of the present disclosure are described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations should all be included in the protection scope of the present disclosure.

Claims

1. A scheduling method for a content distribution network, characterized in that: The method comprises: Dividing the physical devices in the content distribution network to generate multiple service platforms, and configuring the scheduling domains of the service platforms; the scheduling domains include at least one IP address of the physical device; Setting corresponding business features for each of the business platforms, wherein the business features include features in customer dimension and features in domain name dimension; Determine the corresponding target business platform according to the business characteristics corresponding to the target domain name of the target customer, and associate the target domain name with the scheduling domain of the target business platform to generate a scheduling strategy; The scheduling policy is sent to the domain name server, instructing the domain name server to schedule and control the access request according to the scheduling policy.

2. The method according to claim 1, characterized in that The method further comprises: Obtaining a platform switching instruction; the platform switching instruction is used to switch the domain name to be switched from the first service platform to the second service platform; The scheduling domain associated with the domain name to be switched is switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform.

3. The method according to claim 2, characterized in that The step of switching the scheduling domain associated with the domain name to be switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform includes: Sending the domain name configuration of the domain name to be switched to each physical device of the second service platform, and refreshing the cache of the domain name to be switched of each physical device in the second service platform; Performing a first acceptance operation on the second service platform; If the second service platform passes the first acceptance operation, switching the scheduling domain associated with the domain name to be switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform; Performing a second acceptance operation on the second service platform; When the second service platform passes the second acceptance operation, the domain name configuration of the domain name to be switched in the first service platform is deleted.

4. The method according to claim 3, characterized in that The performing a first acceptance operation on the second service platform includes: Performing a detection scan on a plurality of physical devices under test in the second service platform according to the detection URL, and determining a detection result of each of the physical devices under test; When each physical device in the second service platform is provided with a domain name configuration of the domain name to be switched, each physical device in the second service platform completes cache refresh, and the detection results of each of the tested physical devices are consistent, it is determined that the second service platform passes the first acceptance operation; The performing a second acceptance operation on the second service platform includes: Determine whether the traffic of the second service platform meets expectations, and determine whether the first service platform is completely switched; When the traffic of the second service platform is as expected and the first service platform is completely switched, it is determined that the second service platform has passed the second acceptance operation.

5. The method according to any one of claims 2 to 4, characterized in that The step of switching the scheduling domain associated with the domain name to be switched from the scheduling domain of the first service platform to the scheduling domain of the second service platform includes: Set the grayscale range for platform switching; Switching the scheduling domain associated with the domain name to be switched and belonging to the grayscale range from the first scheduling domain belonging to the grayscale range in the first service platform to the second scheduling domain belonging to the grayscale range in the second service platform; The scheduling status of the domain name to be switched by the physical device corresponding to the second scheduling domain is monitored, and when the scheduling status meets the requirements, the scheduling domain associated with the domain name to be switched is fully switched.

6. The method according to claim 2, characterized in that The method further comprises: Allocating customized customers to corresponding customized service platforms, and associating the domain names of the customized customers to the scheduling domains of the customized service platforms; The obtaining of the platform switching instruction includes: Get manually input platform switching instructions; Alternatively, determining a domain name whose service characteristics have changed, and judging whether the domain name whose service characteristics have changed belongs to a customized customer; In the case of not being a customized customer, the domain name with the changed business characteristics is taken as the domain name to be switched, and a corresponding platform switching instruction is automatically generated.

7. The method according to claim 1, characterized in that The method further comprises: Allocating customized customers to corresponding customized service platforms, and associating the domain names of the customized customers to the scheduling domains of the customized service platforms; Furthermore, allocating the customized customer to the corresponding customized service platform and associating the domain name of the customized customer to the scheduling domain of the customized service platform includes: Setting a correspondence between customized features and customized business platforms for the customized customers, and assigning the customized customers to corresponding customized business platforms according to the correspondence; the customized features include features in the customer dimension and / or features in the domain name dimension; In the case where the feature of the domain name dimension in the customization feature includes a domain name naming rule, the domain name belonging to the customization customer and conforming to the domain name naming rule is associated with the scheduling domain of the customization service platform.

8. A scheduling device for a content distribution network, characterized in that: The device comprises: A partitioning module, used to partition the physical devices in the content distribution network, generate multiple service platforms, and configure the scheduling domain of the service platform; the scheduling domain includes an IP address of at least one of the physical devices; A setting module, used to set corresponding business features for each of the business platforms, wherein the business features include features in the customer dimension and features in the domain name dimension; An allocation module, used to determine a corresponding target business platform according to the business characteristics corresponding to the target domain name of the target customer, and associate the target domain name with the scheduling domain of the target business platform to generate a scheduling strategy; The scheduling module is used to send the scheduling policy to the domain name server, and instruct the domain name server to schedule and control the access request according to the scheduling policy.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the content distribution network scheduling method according to any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the content distribution network scheduling method according to any one of claims 1 to 7.

11. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to cause a computer to execute the content distribution network scheduling method according to any one of claims 1 to 7.

Images