CN109729186B

CN109729186B - Allocation strategy determination method and device

Info

Publication number: CN109729186B
Application number: CN201811646226.3A
Authority: CN
Inventors: 王志国
Original assignee: Beijing Kingsoft Cloud Network Technology Co Ltd; Beijing Kingsoft Cloud Technology Co Ltd
Current assignee: Beijing Kingsoft Cloud Network Technology Co Ltd; Beijing Kingsoft Cloud Technology Co Ltd
Priority date: 2018-12-29
Filing date: 2018-12-29
Publication date: 2021-08-27
Anticipated expiration: 2038-12-29
Also published as: CN109729186A

Abstract

The embodiment of the invention provides a method and a device for determining an allocation strategy, and relates to the technical field of networks. The method comprises the following steps: determining a non-solution scheduling unit in a scheduling unit set, then, for each non-solution scheduling unit, determining a historical CDN node used by the non-solution scheduling unit based on historical bandwidth data used by the non-solution scheduling unit, and then, determining an IP address allocation strategy of the non-solution scheduling unit according to the number of IP addresses available for the historical CDN node, the residual bandwidth of the historical CDN node and the required bandwidth of the non-solution scheduling unit. By adopting the invention, the IP address allocation strategy of the scheduling unit can be rapidly and automatically planned, and the waste of manpower is avoided.

Description

Allocation strategy determination method and device

Technical Field

The present invention relates to the field of network technologies, and in particular, to a method and an apparatus for determining an allocation policy.

Background

In order to ensure that a user can quickly obtain Network information, a Content Delivery Network (CDN) is often added between the user and a server of a website, and the speed of obtaining Content of the server of the website by the user is increased by the CDN.

In the prior art, a DNS (Domain Name System) server of the CDN prestores an IP (Internet Protocol) address allocation policy of a scheduling unit, where the scheduling unit records a regional operator and a Domain Name group, the IP address allocation policy includes a target IP address of a CDN node that allocates a bandwidth to the scheduling unit, and the IP address allocation policy is used to allocate a bandwidth to the scheduling unit. When a user accesses a certain domain name, the DNS server can determine a scheduling unit corresponding to the terminal where the user is located according to the region where the terminal where the user is located belongs, the operator to which the terminal where the user is located belongs and the domain name accessed by the user, and determine a target IP address corresponding to the terminal where the user is located according to the scheduling unit corresponding to the terminal where the user is located and a pre-stored IP address allocation strategy of the scheduling unit, wherein the terminal where the user is located accesses the domain name through the target IP address. In order to ensure that the bandwidth allocated to the scheduling unit meets the bandwidth required by the scheduling unit and that the quality of the CDN node to which the target IP address allocated to the scheduling unit belongs is good, a reasonable IP address allocation policy for planning the scheduling unit is required.

However, in the prior art, the IP address allocation strategy of each scheduling unit is manually planned according to the required bandwidth of the scheduling unit in the scheduling unit set and the upper limit bandwidth of each CDN node, so that the planning speed is slow, manpower is wasted, and iteration is continuously performed in the manual planning process, which results in a large amount of calculation and a slow planning speed.

Aiming at the problem that the speed of planning the IP address allocation strategy of each scheduling unit is slow in the prior art, a corresponding solution is not provided at present.

Disclosure of Invention

The embodiment of the invention aims to provide a method and a device for determining an allocation strategy, which can rapidly plan an IP address allocation strategy of a scheduling unit and improve the planning speed. The specific technical scheme is as follows:

in a first aspect, a provisioning policy determination method is provided, where the method includes:

determining a non-solution scheduling unit in a scheduling unit set; the non-solution scheduling unit is a scheduling unit which does not obtain an Internet Protocol (IP) address allocation strategy meeting a first allocation condition; the IP address allocation strategy is a strategy for allocating bandwidth to the non-solution scheduling unit; the first dosing condition comprises: the bandwidth distributed to the scheduling unit according to the IP address distribution strategy meets the required bandwidth of the scheduling unit, and the bandwidth distributed to each CDN node of the scheduling unit does not exceed the upper limit bandwidth of the CDN node;

for each non-solution scheduling unit, determining a historical CDN node used by the non-solution scheduling unit based on historical bandwidth data used by the non-solution scheduling unit;

and determining the IP address allocation strategy of the non-solution scheduling unit according to the number of available IP addresses of the historical CDN node, the residual bandwidth of the historical CDN node and the required bandwidth of the non-solution scheduling unit.

Optionally, the determining, for each non-solution scheduling unit, a historical CDN node used by the non-solution scheduling unit based on historical bandwidth data used by the non-solution scheduling unit includes:

determining the execution sequence of the non-solution scheduling unit according to the required bandwidth and the non-solution times of the non-solution scheduling unit;

according to the execution sequence of the non-solution scheduling units, for each non-solution scheduling unit, determining historical CDN nodes used by the non-solution scheduling units based on historical bandwidth data used by the non-solution scheduling units.

Optionally, after determining the IP address allocation policy of the non-deloading unit according to the number of available IP addresses of the historical CDN nodes, the remaining bandwidth of the historical CDN nodes, and the required bandwidth of the non-deloading unit, the method further includes:

determining an execution sequence of the scheduling units of which the IP allocation strategy is not determined in the scheduling unit set according to a first preset ordering strategy;

according to the execution sequence of the scheduling units of which the IP allocation strategy is not determined in the scheduling unit set, determining a first CDN node with a residual bandwidth from a first region corresponding to each scheduling unit;

and determining the IP address allocation strategy of the scheduling unit according to the number of available IP addresses of the first CDN node, the residual bandwidth of the first CDN node and the required bandwidth of the scheduling unit.

Optionally, the determining, according to the first preset ordering policy, an execution order of the scheduling units in the scheduling unit set for which the IP provisioning policy is not determined includes:

and determining the execution sequence of the scheduling units according to the importance of the domain name group corresponding to the scheduling unit of which the IP allocation strategy is not determined in the scheduling unit set.

Optionally, after determining the IP address allocation policy of the scheduling unit according to the number of available IP addresses of the first CDN node, the remaining bandwidth of the first CDN node, and the required bandwidth of the scheduling unit, the method further includes:

if a first scheduling unit which does not determine the IP address allocation strategy exists in the scheduling unit set, determining the execution sequence of the first scheduling unit according to the first preset ordering strategy;

according to the execution sequence of the first scheduling units, for each first scheduling unit, determining a second CDN node with a remaining bandwidth from a second region corresponding to the first scheduling unit, where the second region corresponding to the first scheduling unit includes a first region corresponding to the first scheduling unit and a region adjacent to the first region;

and determining the IP address allocation strategy of the first scheduling unit according to the number of available IP addresses of the second CDN node, the residual bandwidth of the second CDN node and the required bandwidth of the first scheduling unit.

Optionally, after determining the IP address allocation policy of the first scheduling unit according to the number of available IP addresses of the second CDN node, the remaining bandwidth of the second CDN node, and the required bandwidth of the first scheduling unit, the method further includes:

if a second scheduling unit which does not determine the IP address allocation strategy exists in the scheduling unit set, determining the execution sequence of the second scheduling unit according to the first preset ordering strategy;

according to the execution sequence of the second scheduling units, for each second scheduling unit, determining a third CDN node with a remaining bandwidth from a third region corresponding to the second scheduling unit, where the third region corresponding to the second scheduling unit includes multiple regions, and the multiple regions include a second region corresponding to the second scheduling unit;

and determining the IP address allocation strategy of the second scheduling unit according to the number of available IP addresses of the third CDN node, the residual bandwidth of the third CDN node and the required bandwidth of the second scheduling unit.

Optionally, after determining the IP address allocation policy of the second scheduling unit according to the number of available IP addresses of the third CDN node, the remaining bandwidth of the third CDN node, and the required bandwidth of the second scheduling unit, the method further includes:

if a third scheduling unit which does not determine the IP address assignment strategy exists in the scheduling unit set, clearing the IP address assignment strategy of each scheduling unit in the scheduling unit set, and returning to the step of determining the non-solution scheduling unit in the scheduling unit set.

Optionally, the determining a non-solution scheduling unit in the scheduling unit set includes:

for a scheduling unit of which the IP allocation policy is not determined in a scheduling unit set, sequentially traversing a first region, a second region and a third region corresponding to the scheduling unit according to a preset bandwidth allocation policy, and determining the IP allocation policy of the scheduling unit, where the second region corresponding to the scheduling unit includes the first region corresponding to the scheduling unit and a region adjacent to the first region, the third region corresponding to the scheduling unit includes a plurality of regions, and the plurality of regions includes the second region corresponding to the scheduling unit;

and if the scheduling unit which does not determine the IP address allocation strategy exists in the scheduling unit set, taking the scheduling unit which does not determine the IP address allocation strategy as a non-solution scheduling unit, and recording the non-solution times of the non-solution scheduling unit.

In a second aspect, there is provided a provisioning policy determination apparatus, the apparatus comprising:

a first determining module, configured to determine a non-solution scheduling unit in a scheduling unit set; the non-solution scheduling unit is a scheduling unit which does not obtain an Internet Protocol (IP) address allocation strategy meeting a first allocation condition; the IP address allocation strategy is a strategy for allocating bandwidth to the non-solution scheduling unit; the first dosing condition comprises: the bandwidth distributed to the scheduling unit according to the IP address distribution strategy meets the required bandwidth of the scheduling unit, and the bandwidth distributed to each CDN node of the scheduling unit does not exceed the upper limit bandwidth of the CDN node;

a second determining module, configured to determine, for each non-solution scheduling unit, a historical CDN node used by the non-solution scheduling unit based on historical bandwidth data used by the non-solution scheduling unit;

and a third determining module, configured to determine the IP address allocation policy of the non-deloading unit according to the number of available IP addresses of the historical CDN nodes, the remaining bandwidth of the historical CDN nodes, and the required bandwidth of the non-deloading unit.

Optionally, the second determining module is configured to:

Optionally, the apparatus further comprises:

a fourth determining module, configured to determine, according to the first preset ordering policy, an execution order of the scheduling units in the scheduling unit set for which the IP allocation policy is not determined;

a fifth determining module, configured to determine, for each scheduling unit, a first CDN node with a remaining bandwidth from a first area corresponding to the scheduling unit according to an execution order of the scheduling unit in the scheduling unit set for which the IP provisioning policy is not determined;

a sixth determining module, configured to determine the IP address allocation policy of the scheduling unit according to the number of available IP addresses of the first CDN node, the remaining bandwidth of the first CDN node, and the required bandwidth of the scheduling unit.

Optionally, the fourth determining module is configured to:

Optionally, the apparatus further comprises:

a seventh determining module, configured to determine, if a first scheduling unit for which the IP address assignment policy is not determined exists in the scheduling unit set, an execution order of the first scheduling unit according to the first preset ordering policy;

an eighth determining module, configured to determine, for each first scheduling unit according to an execution order of the first scheduling unit, a second CDN node with a remaining bandwidth from a second region corresponding to the first scheduling unit, where the second region corresponding to the first scheduling unit includes a first region corresponding to the first scheduling unit and a region adjacent to the first region;

a ninth determining module, configured to determine the IP address provisioning policy of the first scheduling unit according to the number of available IP addresses of the second CDN node, a remaining bandwidth of the second CDN node, and a required bandwidth of the first scheduling unit.

Optionally, the apparatus further comprises:

a tenth determining module, configured to determine, if a second scheduling unit for which the IP address assignment policy is not determined exists in the scheduling unit set, an execution order of the second scheduling unit according to the first preset ordering policy;

an eleventh determining module, configured to determine, for each second scheduling unit according to an execution order of the second scheduling unit, a third CDN node having a remaining bandwidth from a third area corresponding to the second scheduling unit, where the third area corresponding to the second scheduling unit includes multiple areas, and the multiple areas include a second area corresponding to the second scheduling unit;

a twelfth determining module, configured to determine the IP address provisioning policy of the second scheduling unit according to the number of available IP addresses of the third CDN node, a remaining bandwidth of the third CDN node, and a required bandwidth of the second scheduling unit.

Optionally, the apparatus further comprises:

and a clearing module, configured to clear the IP address allocation policy of each scheduling unit in the scheduling unit set if a third scheduling unit for which the IP address allocation policy is not determined exists in the scheduling unit set, and return to the step of determining no solution scheduling unit in the scheduling unit set.

Optionally, the first determining module is configured to:

In a third aspect, there is provided a server comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: the method steps of the first aspect are implemented.

In a fourth aspect, a computer-readable storage medium is provided, having stored thereon a computer program which, when being executed by a processor, carries out the method steps of the first aspect.

The allocation policy determining method and device provided by the embodiment of the invention can determine the non-solution scheduling unit in the scheduling unit set. The non-solution scheduling unit is a scheduling unit which does not obtain an Internet Protocol (IP) address allocation policy meeting a first allocation condition, the IP address allocation policy is a policy for allocating bandwidth to the non-solution scheduling unit, and the first allocation condition includes: the bandwidth distributed to the scheduling unit according to the IP address distribution strategy meets the required bandwidth of the scheduling unit, and the bandwidth distributed to each CDN node of the scheduling unit does not exceed the upper limit bandwidth of the CDN node. Then, for each non-solution scheduling unit, determining a historical CDN node used by the non-solution scheduling unit based on historical bandwidth data used by the non-solution scheduling unit, and then determining an IP address allocation strategy of the non-solution scheduling unit according to the number of available IP addresses of the historical CDN node, the residual bandwidth of the historical CDN node and the required bandwidth of the non-solution scheduling unit. Compared with the prior art, the IP address allocation strategy of the non-solution scheduling unit can be preferentially determined based on historical bandwidth data in the process of planning the IP address allocation strategy of each scheduling unit, namely, the non-solution scheduling unit can be allocated based on the historical bandwidth, namely, the bandwidth allocation of the scheduling units of a fixed part is fixed, so that the solution fluctuation in the process of the IP address allocation strategy of each scheduling unit can be reduced, the iteration times are reduced, the allocation speed of each scheduling unit is improved, and the problem that the speed of planning the IP address allocation strategy of each scheduling unit is low in the prior art is solved.

Of course, not all of the advantages described above need to be achieved at the same time in the practice of any one product or method of the invention.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a flowchart of a provisioning policy determining method according to an embodiment of the present application;

fig. 2 is a flowchart of a provisioning policy determining method according to an embodiment of the present application;

fig. 3 is a flowchart of a provisioning policy determining method according to an embodiment of the present application;

fig. 4 is a flowchart of a provisioning policy determining method according to an embodiment of the present application;

fig. 5 is a flowchart of a provisioning policy determining method according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a provisioning policy determining apparatus according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The embodiment of the application provides a method for determining an allocation strategy, which is applied to a scheduling server in a CDN (content distribution network), wherein the scheduling server can determine a non-solution scheduling unit in a scheduling unit set, then, for each non-solution scheduling unit, a historical CDN node used by the non-solution scheduling unit is determined based on historical bandwidth data used by the non-solution scheduling unit, and then, an IP address allocation strategy of the non-solution scheduling unit is determined according to the number of available IP addresses of the historical CDN node, the residual bandwidth of the historical CDN node and the required bandwidth of the non-solution scheduling unit. Compared with the prior art, the IP address allocation strategy of the non-solution scheduling unit can be preferentially determined based on historical bandwidth data in the process of planning the IP address allocation strategy of each scheduling unit, namely, the non-solution scheduling unit can be allocated based on the historical bandwidth, namely, the bandwidth allocation of the scheduling units of a fixed part is fixed, so that the solution fluctuation in the process of the IP address allocation strategy of each scheduling unit can be reduced, the iteration times are reduced, the allocation speed of each scheduling unit is improved, and the problem that the speed of planning the IP address allocation strategy of each scheduling unit is low in the prior art is solved.

The following describes a provisioning policy determining method provided in an embodiment of the present application in detail with reference to specific embodiments, as shown in fig. 1, the specific steps are as follows:

step 101, determining a non-solution scheduling unit in a scheduling unit set.

The scheduling units in the scheduling unit set may include an identifier of the first area, an identifier of the first operator, and a domain name group. The first region may be a provincial administrative district such as Shanghai city, Jiangsu province, Zhejiang province, Anhui province, Fujian province, Jiangxi province, or Shandong province. The first operator is a provider providing network services, such as china telecom, china mobile or china unicom. The domain name group is a set of domain names, such as a set of domain names of a company.

The non-solution scheduling unit is a scheduling unit which does not obtain an internet protocol IP address allocation strategy meeting the first allocation condition, namely the scheduling unit which does not determine the IP address strategy in the process of determining the IP address strategy of the scheduling unit in the scheduling unit set last time. The IP address allocation strategy is a strategy for allocating bandwidth to the non-solution scheduling unit. The IP address allocation strategy comprises an identifier of a target CDN node for allocating an IP address for the scheduling unit and the IP address allocated to the scheduling unit by the target CDN node. The first dosing condition includes: the bandwidth distributed to the scheduling unit according to the IP address distribution strategy meets the required bandwidth of the scheduling unit, and the bandwidth distributed to each CDN node of the scheduling unit does not exceed the upper limit bandwidth of the CDN node.

In this embodiment of the present application, the scheduling server may determine a set of scheduling units of a certain provincial administrative area, or the scheduling server may determine a set of scheduling units of a certain large area, where the large area is an area including a plurality of provincial administrative areas, such as a east China area, or the scheduling server may determine a set of scheduling units across the country. Taking the example of obtaining the set of scheduling units in the north Hebei province, the scheduling server may obtain each domain name group stored in advance, and then determine the set of scheduling units in the north Hebei province according to the identifier of the north Hebei province, the identifier of the first operator, and each domain name group. For example, the identifier of north river province is a1, the identifier of the first operator is B1, the domain name groups stored in advance are C1, C2 and C3, and the scheduling units in the scheduling unit set of north river province are (a1, B1, C1), (a1, B1, C2) and (a1, B1, C3), respectively.

Then, the scheduling server may determine a non-solution scheduling unit in the scheduling unit set, and the specific determination method may be: for a scheduling unit of which the IP allocation strategy is not determined in the scheduling unit set, the scheduling server sequentially traverses a first region, a second region and a third region corresponding to the scheduling unit according to a preset bandwidth allocation strategy to determine the IP allocation strategy of the scheduling unit; and if the scheduling unit with the undetermined IP address allocation strategy exists in the scheduling unit set, the scheduling server takes the scheduling unit with the undetermined IP address allocation strategy as a non-solution scheduling unit and records the non-solution times of the non-solution scheduling unit.

The second region corresponding to the scheduling unit includes a first region corresponding to the scheduling unit and a region adjacent to the first region, the third region corresponding to the scheduling unit includes a plurality of regions, and the plurality of regions includes the second region corresponding to the scheduling unit. For example, the first region corresponding to the scheduling unit may be Jiangsu province, the second region corresponding to the scheduling unit may be Jiangsu province and Zhejiang province, and the third region corresponding to the scheduling unit may be east China.

And 102, determining historical CDN nodes used by the non-solution scheduling units based on historical bandwidth data used by the non-solution scheduling units for each non-solution scheduling unit.

In the embodiment of the application, for each non-solution scheduling unit, the scheduling server may obtain historical bandwidth data used by the non-solution scheduling unit, and then the scheduling server determines a historical CDN node used by the non-solution scheduling unit according to the historical bandwidth data.

Optionally, for each non-solution scheduling unit, the specific processing procedure of determining the historical CDN node used by the non-solution scheduling unit based on the historical bandwidth data used by the non-solution scheduling unit may be: and determining an execution sequence of the non-solution scheduling units according to the required bandwidth and the non-solution times of the non-solution scheduling units, and then determining historical CDN nodes used by the non-solution scheduling units for each non-solution scheduling unit according to the execution sequence of the non-solution scheduling units and based on historical bandwidth data used by the non-solution scheduling units.

In the embodiment of the application, for each non-solution scheduling unit, the scheduling server may calculate a product of a required bandwidth of the non-solution scheduling unit and a non-solution frequency, and then, the scheduling server sorts the non-solution scheduling units according to the product to obtain an execution sequence of the non-solution scheduling units. The larger the product of the required bandwidth and the number of times of non-solution scheduling, the earlier the execution sequence of the non-solution scheduling.

Then, the scheduling server performs the following processing to each scheduling unit in sequence according to the execution sequence of the non-solution scheduling unit: the scheduling server obtains historical bandwidth data used by the non-delocalization unit, then determines a historical CDN node used by the non-delocalization unit according to the historical bandwidth data, and then determines an IP address allocation strategy of the non-delocalization unit according to the number of available IP addresses of the historical CDN node, the residual bandwidth of the historical CDN node and the required bandwidth of the non-delocalization unit.

Step 103, determining an IP address allocation strategy of the non-deloading unit according to the number of available IP addresses of the historical CDN nodes, the residual bandwidth of the historical CDN nodes and the required bandwidth of the non-deloading unit.

In the embodiment of the application, the number of the historical CDN nodes may be multiple, and the number of the IP addresses of the historical CDN nodes may be multiple. The scheduling server may determine all IP proportional solutions of the non-solution scheduling units according to the historical CDN nodes and the number of IP addresses of each historical CDN node, where the IP proportional solutions include the number of IP addresses allocated to the non-solution scheduling units by each historical CDN node. For example, the historical CDN nodes are CDN1 and CDN2, respectively, the number of IP addresses of CDN1 is 2, and the number of IP addresses of CDN2 is 2, then the scheduling server may determine that all IP proportions of non-solution scheduling units are: 1. the number of IP addresses allocated to the non-solution scheduling unit by CDN1 is 1; 2. the number of IP addresses allocated to the non-solution scheduling unit by CDN1 is 1 and the number of IP addresses allocated to the non-solution scheduling unit by CDN2 is 1; 3. the number of IP addresses allocated to the non-solution scheduling unit by CDN1 is 1 and the number of IP addresses allocated to the non-solution scheduling unit by CDN2 is 2; 4. the number of IP addresses allocated to the non-solution scheduling unit by CDN1 is 2; 5. the number of IP addresses allocated to the non-solution scheduling unit by CDN1 is 2 and the number of IP addresses allocated to the non-solution scheduling unit by CDN2 is 1; 6. the number of IP addresses assigned by CDN1 to no-demoduling units is 2 and the number of IP addresses assigned by CDN2 to no-demoduling units is 2.

Then, for each IP proportional solution, the scheduling server may determine, according to the required bandwidth of the non-solution scheduling unit and the number of IP addresses allocated to the non-solution scheduling unit by each historical CDN node in the IP proportional solution, the bandwidth that each historical CDN node needs to allocate to the non-solution scheduling unit, where the specific determination manner is: dividing the required bandwidth of the non-solution scheduling unit by the sum of the numbers of the IP addresses allocated to the non-solution scheduling unit by each historical CDN node in the IP proportional solution to obtain the bandwidth represented by each IP address, and then calculating the product of the number of the IP addresses allocated to the non-solution scheduling unit by the historical CDN node and the bandwidth represented by each IP address for each historical CDN node corresponding to the IP proportional solution to obtain the bandwidth required to be allocated to the non-solution scheduling unit by the historical CDN node. For example, the IP ratio solution of the non-solution scheduling unit is: the number of the IP addresses allocated to the non-solution scheduling unit by the CDN1 is 1, the number of the IP addresses allocated to the non-solution scheduling unit by the CDN2 is 2, the required bandwidth of the non-solution scheduling unit is 30G, the bandwidth that the CDN1 node needs to allocate to the non-solution scheduling unit is 10G, and the bandwidth that the CDN2 node needs to allocate to the non-solution scheduling unit is 20G.

Then, for each IP proportional solution, determining a first IP proportional solution according to the bandwidth which is required to be allocated to the non-solution scheduling unit by each historical CDN node corresponding to the IP proportional solution and the residual bandwidth of each historical CDN node, wherein the bandwidth which is required to be allocated to the non-solution scheduling unit by the historical CDN node corresponding to the first IP proportional solution does not exceed the residual bandwidth of the historical CDN node, namely the bandwidth allocated by the historical CDN node does not exceed the upper limit bandwidth of the historical CDN node.

Then, the scheduling server may use the determined first IP ratio solution as a target IP ratio solution, or the scheduling server further determines the number of historical CDN nodes corresponding to the first IP ratio solution, where the historical CDN nodes corresponding to the first IP ratio solution belong to a first region, and then the scheduling server determines the target IP ratio solution from the first IP ratio solution, where the number of the historical CDN nodes corresponding to the target IP ratio solution is smaller than a preset first number or/and the historical nodes corresponding to the target IP ratio solution belong to the same first region CDN.

And then, according to the number of IP addresses distributed to the non-solution scheduling unit by each historical CDN node in the determined target IP proportional solution, selecting an IP address from the IP addresses of each historical CDN node to obtain an IP address distribution strategy of the non-solution scheduling unit. For example, the number of the IP addresses allocated to the non-solution scheduling unit by the historical CDN node a in the target IP ratio solution is 2, and the number of the IP addresses allocated to the non-solution scheduling unit by the historical CDN node B is 1, so that the scheduling server arbitrarily selects 2 IP addresses from the IP addresses of the historical CDN node a, arbitrarily selects 1 IP address from the IP addresses of the historical CDN node B, and allocates the selected IP addresses as the IP addresses of the non-solution scheduling unit to the target IP addresses in the policy.

Therefore, in the process of planning the IP address allocation strategy of each scheduling unit, the IP address allocation strategy of the non-solution scheduling unit can be preferentially determined based on historical bandwidth data, namely, the non-solution scheduling unit can be allocated based on historical bandwidth, namely, the bandwidth allocation of the scheduling units of a fixed part is fixed, so that the solution fluctuation in the process of the IP address allocation strategy of each scheduling unit can be reduced, the iteration times are reduced, the allocation speed of each scheduling unit is improved, and the problem that the speed of planning the IP address allocation strategy of each scheduling unit is slow in the prior art is solved.

Optionally, as shown in fig. 2, after determining an IP address allocation policy of a non-deloading unit according to the number of available IP addresses of the historical CDN nodes, the remaining bandwidth of the historical CDN nodes, and the required bandwidth of the non-deloading unit, the IP address allocation policy of a scheduling unit of which the IP allocation policy is not determined in the scheduling unit set may also be determined by:

step 201, determining an execution sequence of a scheduling unit of the scheduling unit set for which the IP allocation policy is not determined according to the first preset ordering policy.

And the scheduling unit of which the IP allocation strategy is not determined in the scheduling unit set is a scheduling unit except the non-solution scheduling unit of which the IP allocation strategy is determined in the scheduling unit set.

In this embodiment of the present application, according to the first preset ordering policy, a specific processing procedure of the scheduling server determining the execution order of the scheduling unit of which the IP allocation policy is not determined in the scheduling unit set may be: and determining the execution sequence of the scheduling units according to the importance of the domain name group corresponding to the scheduling unit of which the IP allocation strategy is not determined in the scheduling unit set.

In the embodiment of the application, when the first areas corresponding to the scheduling units in which the IP assignment policy is not determined in the scheduling unit set are the same, the scheduling server stores the importance of each domain name group in advance, where the importance of the domain name group may be set by a technician. The scheduling server may obtain the importance of the domain name group corresponding to each scheduling unit in the scheduling unit set, and then determine the execution sequence corresponding to the scheduling unit in the scheduling unit set according to the importance of the domain name group corresponding to each scheduling unit in the scheduling unit set. For example, the scheduling units in the scheduling unit set are (a1, B1, C1), (a1, B1, C2) and (a1, B1, C3), the domain name groups corresponding to the scheduling units are C1, C2 and C3, the importance degrees of C1, C2 and C3 are 2,3 and 1, respectively, and the domain name groups are arranged in the order of the importance degrees, that is, C2, C1 and C3, and the scheduling units in the scheduling unit set are (a1, B1, C2), (a1, B1, C1), (a1, B1 and C3).

When the first regions corresponding to the scheduling units for which the IP allocation policy is not determined in the scheduling unit set are different, the scheduling server may determine a required bandwidth of a first operator in the first region corresponding to the scheduling unit, and then sort the scheduling units according to the required bandwidth of the first operator in the first region corresponding to the scheduling unit, so as to obtain a first scheduling unit sequence, where the larger the required bandwidth of the first operator in the first region corresponding to the scheduling unit is, the more ahead the sorting is. Then, the scheduling server sequences the scheduling units with the same required bandwidth of the first operator in the first region corresponding to the scheduling unit according to the importance of the domain name group corresponding to the scheduling unit, so as to obtain the execution sequence of the scheduling unit of which the IP allocation policy is not determined in the scheduling unit set.

Step 202, according to the execution sequence of the scheduling units of which the IP allocation policy is not determined in the scheduling unit set, for each scheduling unit, determining a first CDN node having a remaining bandwidth from a first region corresponding to the scheduling unit.

In this embodiment of the application, the scheduling server may determine, according to a first region and a first operator corresponding to the scheduling unit, CDN nodes belonging to the first operator in the first region, and then the scheduling server determines, from the determined CDN nodes, the first CDN node having the remaining bandwidth.

Step 203, determining an IP address allocation strategy of the scheduling unit according to the number of available IP addresses of the first CDN node, the remaining bandwidth of the first CDN node, and the required bandwidth of the scheduling unit.

In the embodiment of the application, the scheduling server determines an IP address allocation strategy of the scheduling unit according to the number of available IP addresses of the first CDN node, the remaining bandwidth of the first CDN node, and the required bandwidth of the scheduling unit. For a specific implementation, refer to step 103, which is not described herein again.

Optionally, as shown in fig. 3, after determining an IP address provisioning policy of a scheduling unit according to the number of available IP addresses of the first CDN node, the remaining bandwidth of the first CDN node, and the required bandwidth of the scheduling unit, if there is a first scheduling unit for which an IP address provisioning policy is not determined in the scheduling unit set, the IP address provisioning policy of the first scheduling unit may also be determined through the following steps:

step 301, determining an execution order of the first scheduling unit according to a first preset ordering policy.

In this embodiment of the application, the scheduling server may determine an execution order of the first scheduling unit according to a first preset ordering policy. For a specific implementation, refer to step 201, and details of the embodiment of the present application are not described herein.

Step 302, according to the execution sequence of the first scheduling units, for each first scheduling unit, determining a second CDN node with a remaining bandwidth from a second region corresponding to the first scheduling unit.

The second region corresponding to the first scheduling unit comprises a first region corresponding to the first scheduling unit and a region adjacent to the first region. For example, the first region corresponding to the scheduling unit is Jiangsu province, and the second region corresponding to the scheduling unit may be Jiangsu province and Zhejiang province.

In this embodiment of the application, the scheduling server may determine, according to a second area and a first operator corresponding to the first scheduling unit, a second CDN node with a remaining bandwidth, which belongs to the first operator, in the second area.

Step 303, determining an IP address allocation policy of the first scheduling unit according to the number of available IP addresses of the second CDN node, the remaining bandwidth of the second CDN node, and the required bandwidth of the first scheduling unit.

In the embodiment of the application, the scheduling server determines an IP address allocation strategy of the first scheduling unit according to the number of available IP addresses of the second CDN node, the remaining bandwidth of the second CDN node, and the required bandwidth of the first scheduling unit. For a specific implementation, refer to step 103, which is not described herein again.

Optionally, as shown in fig. 4, after determining an IP address allocation policy of the first scheduling unit according to the number of available IP addresses of the second CDN node, the remaining bandwidth of the second CDN node, and the required bandwidth of the first scheduling unit, if there is a second scheduling unit for which an IP address allocation policy is not determined in the scheduling unit set, the IP address allocation policy of the second scheduling unit may also be determined through the following steps:

step 401, determining an execution sequence of the second scheduling unit according to the first preset ordering policy.

In this embodiment of the application, the scheduling server may determine an execution order of the second scheduling unit according to the first preset ordering policy. For a specific implementation, refer to step 201, and details of the embodiment of the present application are not described herein.

Step 402, according to the execution sequence of the second scheduling units, for each second scheduling unit, determining a third CDN node with a remaining bandwidth from a third area corresponding to the second scheduling unit.

The third area corresponding to the second scheduling unit includes a plurality of areas, and the plurality of areas include the second area corresponding to the second scheduling unit. For example, the first region corresponding to the second scheduling unit may be jiangsu province, the second region corresponding to the second scheduling unit may be jiangsu province and zhejiang province, and the third region corresponding to the second scheduling unit may be east China.

In this embodiment of the application, the scheduling server may determine, according to a third area and a first operator corresponding to the first scheduling unit, a third CDN node with a remaining bandwidth, which belongs to the first operator, in the third area.

Step 403, determining an IP address allocation policy of the second scheduling unit according to the number of available IP addresses of the third CDN node, the remaining bandwidth of the third CDN node, and the required bandwidth of the second scheduling unit.

In the embodiment of the application, the scheduling server determines an IP address allocation strategy of the second scheduling unit according to the number of available IP addresses of the third CDN node, the remaining bandwidth of the third CDN node, and the required bandwidth of the second scheduling unit. For a specific implementation, refer to step 103, which is not described herein again.

Optionally, after determining an IP address allocation policy of the second scheduling unit according to the number of available IP addresses of the third CDN node, the remaining bandwidth of the third CDN node, and the required bandwidth of the second scheduling unit, if a first scheduling unit for which the IP address allocation policy is not determined still exists in the scheduling unit set, if a third scheduling unit for which the IP address allocation policy is not determined still exists in the scheduling unit set, the IP address allocation policy of each scheduling unit in the scheduling unit set is cleared, and a step of determining a non-solution scheduling unit in the scheduling unit set is returned.

Therefore, the IP address allocation strategy of the non-solution scheduling unit can be preferentially determined according to the historical bandwidth data of the non-solution scheduling unit, and then the IP address allocation strategies of the scheduling units except the non-solution scheduling unit determining the IP address allocation strategy in the scheduling unit set are sequentially determined in the first region, the second region and the third region, so that CDN nodes with better bandwidth allocation quality can be allocated to the scheduling units, and the IP address allocation strategy of the scheduling units can be rapidly planned.

As shown in fig. 5, an example of a provisioning policy determining method is further provided in the embodiments of the present application, and the specific process is as follows:

step 501, determining a non-solution scheduling unit in a scheduling unit set.

Step 502, determining the execution sequence of the non-solution scheduling unit according to the required bandwidth and the non-solution times of the non-solution scheduling unit.

Step 502 may refer to the detailed description of step 102, which is not described herein again.

Step 503, according to the execution sequence of the non-solution scheduling units, determining, for each non-solution scheduling unit, a historical CDN node used by the non-solution scheduling unit based on the historical bandwidth data used by the non-solution scheduling unit.

Step 503 may refer to the detailed description of step 102, which is not described herein again.

Step 504, determining an IP address allocation strategy of the non-deloading unit according to the number of available IP addresses of the historical CDN nodes, the remaining bandwidth of the historical CDN nodes, and the required bandwidth of the non-deloading unit.

Step 504 may refer to the detailed description of step 103, which is not described herein again.

In the initial cycle, no non-solution scheduling unit exists in the scheduling unit set, and steps 501-504 do not need to be executed.

And 505, determining the execution sequence of the scheduling units of which the IP allocation policy is not determined in the scheduling unit set according to a preset first sequencing policy.

Step 505 may refer to the detailed description of step 201, which is not described herein again.

Step 506, according to the execution sequence of the scheduling units of which the IP provisioning policy is not determined in the scheduling unit set, for each scheduling unit, determining a first CDN node having a remaining bandwidth from a first region corresponding to the scheduling unit.

Step 506 may refer to the detailed description of step 202, which is not described herein again.

Step 507, determining an IP address allocation strategy of the first scheduling unit according to the number of available IP addresses of the first CDN node, the remaining bandwidth of the first CDN node, and the required bandwidth of the scheduling unit.

Step 507 may refer to the detailed description of step 203, which is not described herein again.

Step 508, determine whether there is a first scheduling unit in the scheduling unit set for which the IP address assignment policy is not determined.

If the first scheduling unit of which the IP address allocation strategy is not determined does not exist in the scheduling unit set, ending the execution; if there is a first scheduling unit in the scheduling unit set for which the IP address assignment policy is not determined, step 509 is performed.

In step 509, the execution sequence of the first scheduling unit is determined according to the first preset ordering policy.

Step 509 may refer to the detailed description of step 301, which is not described herein again.

Step 510, according to the execution sequence of the first scheduling units, for each first scheduling unit, determining a second CDN node with a remaining bandwidth from a second region corresponding to the first scheduling unit.

Step 510 may refer to the detailed description of step 302, which is not described herein again.

Step 511, determining an IP address allocation policy of the first scheduling unit according to the number of available IP addresses of the second CDN node, the remaining bandwidth of the second CDN node, and the required bandwidth of the first scheduling unit.

Step 511 may refer to the detailed description of step 303, which is not described herein again.

Step 512, determine whether there is a second scheduling unit in the first scheduling unit for which the IP address assignment policy is not determined.

If the first scheduling unit does not have a second scheduling unit which does not determine the IP address allocation strategy, the execution is finished; if there is a second scheduling unit in the first scheduling unit for which the IP address provisioning policy is not determined, step 513 is performed.

Step 513, determining an execution order of the second scheduling unit according to the first preset ordering policy.

Step 513 may refer to the detailed description of step 401, and is not described herein again in this embodiment of the present application.

Step 514, according to the execution sequence of the second scheduling units, for each second scheduling unit, determining a third CDN node with a remaining bandwidth from a third area corresponding to the second scheduling unit.

Step 514 may refer to the detailed description of step 402, which is not described herein again in this embodiment of the present application.

Step 515, determining an IP address allocation policy of the second scheduling unit according to the number of available IP addresses of the third CDN node, the remaining bandwidth of the third CDN node, and the required bandwidth of the second scheduling unit.

Step 515 may refer to the detailed description of step 403, and is not described herein again in this embodiment of the present application.

Step 516, determine whether there is a third scheduling unit in the second scheduling unit for which the IP address assignment policy is not determined.

If the second scheduling unit does not have a third scheduling unit which does not determine the IP address allocation strategy, the execution is finished; if there is a third scheduling unit in the second scheduling unit for which the IP address provisioning policy is not determined, step 517 is performed.

Step 517, clearing the IP address allocation strategy of each scheduling unit in the scheduling unit set, taking the third scheduling unit as a non-solution scheduling unit, recording the non-solution times of the non-solution scheduling unit, and returning to step 501.

It should be noted that, the scheduling server executes the above method, so as to achieve the purpose of automatically planning the IP address allocation policy of the scheduling unit, reduce the participation of manpower, and greatly improve the planning speed.

Based on the same technical concept, as shown in fig. 6, an embodiment of the present application further provides a provisioning policy determining apparatus, where the provisioning policy determining apparatus is applied to a scheduling server, and the provisioning policy determining apparatus includes:

a first determining module 601, configured to determine a non-solution scheduling unit in the scheduling unit set; the non-solution scheduling unit is a scheduling unit which does not obtain an Internet Protocol (IP) address allocation strategy meeting a first allocation condition; the IP address allocation strategy is a strategy for allocating bandwidth to the non-solution scheduling unit; the first dosing condition comprises: the bandwidth distributed to the scheduling unit according to the IP address distribution strategy meets the required bandwidth of the scheduling unit, and the bandwidth distributed to each CDN node of the scheduling unit does not exceed the upper limit bandwidth of the CDN node;

a second determining module 602, configured to determine, for each non-solution scheduling unit, a historical CDN node used by the non-solution scheduling unit based on historical bandwidth data used by the non-solution scheduling unit;

a third determining module 603, configured to determine the IP address allocation policy of the non-deloading unit according to the number of available IP addresses of the historical CDN nodes, the remaining bandwidth of the historical CDN nodes, and the required bandwidth of the non-deloading unit.

Optionally, the second determining module 602 is configured to:

Optionally, the apparatus further comprises:

Optionally, the fourth determining module is configured to:

Optionally, the apparatus further comprises:

Optionally, the first determining module 601 is configured to:

An embodiment of the present invention further provides an electronic device, as shown in fig. 7, including a processor 701, a communication interface 702, a memory 703 and a communication bus 704, where the processor 701, the communication interface 702, and the memory 703 complete mutual communication through the communication bus 704,

a memory 703 for storing a computer program;

the processor 701, when configured to execute the program stored in the memory 703, may implement any of the method steps described above, and optionally, in an embodiment of the present invention, may implement the following steps:

The communication bus mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.

The communication interface is used for communication between the electronic equipment and other equipment.

The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.

The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

In a further embodiment of the present invention, a computer-readable storage medium is further provided, in which a computer program is stored, which, when being executed by a processor, implements the steps of any of the above provisioning policy determination methods.

In a further embodiment of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the steps of any of the above described provisioning policy determination methods.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may 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 loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, 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, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.

Claims

1. A provisioning policy determination method, the method comprising:

and determining an IP address allocation strategy of the non-solution scheduling unit, which meets the first allocation condition, according to the number of available IP addresses of the historical CDN nodes, the residual bandwidth of the historical CDN nodes and the required bandwidth of the non-solution scheduling unit.

2. The method of claim 1, wherein the determining, for each of the non-solution scheduling units, a historical CDN node used by the non-solution scheduling unit based on historical bandwidth data used by the non-solution scheduling unit comprises:

3. The method of claim 1, wherein after determining the IP address provisioning policy for the non-delocalized unit according to the number of IP addresses available for the historical CDN nodes, the remaining bandwidth of the historical CDN nodes, and the required bandwidth of the non-delocalized unit, the method further comprises:

determining an execution sequence of the scheduling units of which the IP address allocation strategy is not determined in the scheduling unit set according to a first preset ordering strategy;

according to the execution sequence of the scheduling units of which the IP address allocation strategy is not determined in the scheduling unit set, determining a first CDN node with residual bandwidth from a first region corresponding to each scheduling unit;

4. The method according to claim 3, wherein the determining, according to the first predetermined ordering policy, an execution order of the scheduling units in the scheduling unit set for which the IP address assignment policy is not determined comprises:

and determining the execution sequence of the scheduling units according to the importance of the domain name group corresponding to the scheduling unit which does not determine the IP address assignment strategy in the scheduling unit set.

5. The method of claim 3, wherein after determining the IP address provisioning policy for the scheduling unit according to the number of IP addresses available to the first CDN node, the remaining bandwidth of the first CDN node, and the required bandwidth of the scheduling unit, the method further comprises:

6. The method of claim 5, wherein after determining the IP address provisioning policy for the first scheduling unit according to the number of IP addresses available to the second CDN node, the remaining bandwidth of the second CDN node, and the required bandwidth of the first scheduling unit, the method further comprises:

7. The method of claim 6, wherein after determining the IP address provisioning policy for the second scheduling unit according to the number of IP addresses available to the third CDN node, the remaining bandwidth of the third CDN node, and the required bandwidth of the second scheduling unit, the method further comprises:

8. The method of claim 1, wherein the determining the non-solution scheduling unit in the set of scheduling units comprises:

for a scheduling unit of which the IP address assignment policy is not determined in a scheduling unit set, sequentially traversing a first region, a second region and a third region corresponding to the scheduling unit according to a preset bandwidth assignment policy, and determining the IP address assignment policy of the scheduling unit, where the second region corresponding to the scheduling unit includes the first region corresponding to the scheduling unit and a region adjacent to the first region, the third region corresponding to the scheduling unit includes a plurality of regions, and the plurality of regions includes the second region corresponding to the scheduling unit;

9. An provisioning policy determination apparatus, said apparatus comprising:

and a third determining module, configured to determine, according to the number of available IP addresses of the historical CDN node, the remaining bandwidth of the historical CDN node, and the required bandwidth of the non-solution scheduling unit, an IP address provisioning policy, which satisfies the first provisioning condition, of the non-solution scheduling unit.

10. The apparatus of claim 9, wherein the second determining module is configured to:

11. The apparatus of claim 9, further comprising:

a fourth determining module, configured to determine, according to a first preset ordering policy, an execution order of a scheduling unit in the scheduling unit set for which the IP address allocation policy is not determined;

a fifth determining module, configured to determine, for each scheduling unit, a first CDN node with a remaining bandwidth from a first area corresponding to the scheduling unit according to an execution order of the scheduling unit in the scheduling unit set for which the IP address provisioning policy is not determined;

12. The apparatus of claim 11, wherein the fourth determining module is configured to:

13. The apparatus of claim 11, further comprising:

14. The apparatus of claim 13, further comprising:

15. The apparatus of claim 14, further comprising:

16. The apparatus of claim 9, wherein the first determining module is configured to:

17. A server comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: carrying out the method steps of any one of claims 1 to 8.

18. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of the claims 1-8.