CDN acceleration resource planning method, device, equipment and storage medium
By obtaining the service information of the target domain name area, determining the minimum number of cluster groups and planning the same number of cluster groups for each node, the problem of existing CDN acceleration resource planning dependence on existing results and planning imbalance is achieved, and the global Balanced and targeted accelerate resource allocation.
Patent Information
- Application Number
- CN202111580220.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-22
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-12-22
AI Technical Summary
The existing CDN accelerated resource planning depends on existing planning results, making it difficult to achieve global balance and strong targeting, resulting in unbalanced planning and poor targeting.
By obtaining the business information of the target domain name area, determining the minimum number of cluster groups, and according to the relationship between the number and the number of nodes to be planned, the same number of cluster groups are planned for each node to ensure the balance and targeted planning, and avoiding the Overload or waste of resources.
A global balanced planning based on business needs is realized, ensuring that each node evenly allocates accelerated service resources to meet user needs, while avoiding resource overload or waste, improving the pertinence and efficiency of the planning.
Smart Images

Figure CN114448809B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to the field of Internet technology, and in particular to a CDN acceleration resource planning method, device, equipment and storage medium. Background Art
[0002] In the process of responding to user content requests, the content delivery network (CDN) needs the central platform to call the corresponding acceleration resources from the acceleration resources planned in advance for the area based on the user's location to provide acceleration services to the user. Among them, the acceleration resources planned for the area are usually obtained by manually initially planning the acceleration resources and adjusting the initial planning results according to the characteristics of different scenarios.
[0003] However, manual planning usually requires reference to existing regional resource planning, which makes it difficult to make global planning. Reference to existing regional resource planning will result in the inability to adapt to the actual business needs of the domain name area and lack of pertinence. Failure to make global planning will lead to unbalanced planning results. Even if adjustments are made based on the scenario later, there will still be problems of unbalanced planning and lack of pertinence. Summary of the invention
[0004] The purpose of the embodiments of the present invention is to provide a CDN acceleration resource planning method, device, equipment and storage medium, so as to overcome the dependence on existing planning results and perform global balanced and targeted planning for acceleration resources in domain name areas.
[0005] To achieve the above-mentioned purpose, an embodiment of the present invention provides a planning method for CDN acceleration service resources, including: obtaining business information of a target domain name area; determining the minimum number of cluster groups that need to be planned for the target domain name area based on the business information; the acceleration service resources of a node to be planned in the target domain name area include at least one cluster group; detecting whether the minimum number of cluster groups is greater than the number of nodes to be planned in the target domain name area; when the minimum number of cluster groups is greater than the number of nodes to be planned, planning a first target number of cluster groups for each node to be planned, the first target number being the number of cluster groups contained in the node to be planned that contains the least number of cluster groups; when the minimum number of cluster groups is not greater than the number of nodes to be planned, planning one cluster group for each node to be planned.
[0006] To achieve the above-mentioned purpose, an embodiment of the present invention further provides a planning device for CDN acceleration service resources, comprising: an acquisition module for acquiring business information of a target domain name area; a determination module for determining the minimum number of cluster groups that need to be planned for the target domain name area based on the business information; the acceleration service resources of a node to be planned in the target domain name area include at least one cluster group; a detection module for detecting whether the minimum number of cluster groups is greater than the number of nodes to be planned in the target domain name area; a first planning module for planning a first target number of cluster groups for each node to be planned when the minimum number of cluster groups is greater than the number of nodes to be planned, the first target number being the number of cluster groups contained in the node to be planned that contains the least number of cluster groups; a second planning module for planning one cluster group for each node to be planned when the minimum number of cluster groups is not greater than the number of nodes to be planned.
[0007] To achieve the above-mentioned purpose, an embodiment of the present invention also provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the planning method of CDN acceleration service resources as described above.
[0008] To achieve the above objectives, an embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the above-mentioned method for planning CDN acceleration service resources.
[0009] The CDN acceleration service resource planning method provided by the embodiment of the present invention determines the minimum number of cluster groups that need to be planned for the target domain name area according to the business information of the target domain name area, and then determines the planning method that is compatible with the business needs of the target domain name area according to the size relationship between the minimum number of cluster groups and the number of nodes to be planned in the target domain name area, so as to realize targeted planning based on different business needs of the target domain name area and the scale of the nodes to be planned, without relying on the existing planning. Wherein, when the minimum number of cluster groups is greater than the number of nodes to be planned in the target domain name area, a first target number of cluster groups are planned for each node to be planned, so that each node to be planned is planned with the same number of cluster groups, and each node can plan as many cluster groups as possible, so that when the user accesses the domain name area, the entire domain name area has enough acceleration service resources to meet the user's needs and avoid overload; when the minimum number of cluster groups is not greater than the number of nodes to be planned in the target domain name area, a cluster group is planned for each node to be planned, so that each node to be planned is planned with the same number of cluster groups, and the number of cluster groups planned for each node will not be too many, so that when the user accesses the domain name area, there are enough acceleration service resources to meet the user's needs and will not occupy too many acceleration service resources. Therefore, no matter which planning method is used, the same number of clusters can be planned for each node to be planned in the domain name area, avoiding the situation where too many acceleration service resources are planned for some nodes while the acceleration service resources of other nodes are not planned, thus achieving balanced planning. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.
[0011] Figure 1 is a flow chart of a method for planning CDN acceleration service resources provided in one embodiment of the present invention;
[0012] Figure 2 is a flow chart of a method for planning CDN acceleration service resources including a step of planning a device cluster provided in another embodiment of the present invention;
[0013] Figure 3 is a flow chart of a CDN acceleration service resource planning method including a step of re-planning at least one cluster group provided in another embodiment of the present invention;
[0014] Figure 4 It is a structural schematic diagram of a CDN acceleration service resource planning device provided in another embodiment of the present invention;
[0015] Figure 5It is a schematic structural diagram of an electronic device provided in another embodiment of the present invention. DETAILED DESCRIPTION
[0016] As can be seen from the background technology, the current planning of CDN acceleration resources has the following problems: it needs to rely on existing planning results, the planning is unbalanced, and the planning is not targeted enough.
[0017] To solve the above problems, an embodiment of the present invention provides a planning method for CDN acceleration service resources, including: obtaining business information of a target domain name area; determining the minimum number of cluster groups that need to be planned for the target domain name area according to the business information; the acceleration service resources of a node to be planned in the target domain name area include at least one cluster group; detecting whether the minimum number of cluster groups is greater than the number of nodes to be planned in the target domain name area; when the minimum number of cluster groups is greater than the number of nodes to be planned, planning a first target number of cluster groups for each node to be planned, the first target number being the number of cluster groups contained in the node to be planned that contains the least number of cluster groups; when the minimum number of cluster groups is not greater than the number of nodes to be planned, planning one cluster group for each node to be planned.
[0018] The CDN acceleration service resource planning method provided in the embodiment of the present invention determines the minimum number of cluster groups that need to be planned for each target domain name area based on the business information of the target domain name area to meet the business needs of the domain name area, and then plans the same number of cluster groups for each node with the goal that the number of cluster groups planned for the target domain name area is not less than the minimum number of cluster groups, ensuring that each node will be planned, and the entire process does not need to refer to the existing plan but is planned in a targeted manner based on the business characteristics of the target domain name area, thereby achieving global balance and targeted planning. In particular, when the minimum number of cluster groups is greater than the number of nodes to be planned in the target domain name area, since planning one cluster group for each node can achieve the goal of planning at least the minimum number of cluster groups for the target domain name area, Therefore, a cluster group can be planned for each node, and redundant cluster groups can also provide acceleration resources beyond business needs, so that the target domain name area can provide acceleration services normally even under abnormal circumstances; when the minimum number of cluster groups is not greater than the number of nodes to be planned in the target domain name area, since planning a cluster group for each node may not achieve the goal of planning at least the minimum number of cluster groups for the target domain name area, as many cluster groups of the same number as possible can be planned for each node, and due to the limitation of planning the same number of cluster groups for each node, only the number of cluster groups with the least number of nodes to be planned can be planned, and redundant cluster groups may also provide acceleration resources beyond business needs, so that the target domain name area can provide acceleration services normally even under abnormal circumstances. It overcomes the dependence on the planning results of the domain name area that has been planned, and can automatically and pre-plan the global balanced planning for the different business needs of the target domain name area and the scale of the nodes to be planned.
[0019] In order to make the purpose, technical scheme and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it can be understood by those skilled in the art that in the embodiments of the present invention, many technical details are provided to enable readers to better understand the present invention. However, even without these technical details and various changes and modifications based on the following embodiments, the technical scheme claimed in the present invention can be implemented.
[0020] The following embodiments are divided for the convenience of description and shall not constitute any limitation on the specific implementation of the present invention. The embodiments may be combined with each other and referenced to each other without contradiction.
[0021] In one aspect, an embodiment of the present invention provides a method for planning CDN acceleration service resources, which is applied to a server, which may be a background server, a monitoring server or a central platform server of a CDN system. Figure 1 As shown, the process of the CDN acceleration service resource planning method at least includes:
[0022] Step 101, obtaining business information of the target domain name zone.
[0023] In this embodiment, the service information mainly includes traffic bandwidth information of the service.
[0024] In some examples, the business information is the overall traffic bandwidth of all businesses in the target domain name, so that the acceleration resources are subsequently planned for the overall business traffic bandwidth of the target domain name area, which can reduce planning complexity and improve planning efficiency.
[0025] In other examples, different types of services have different acceleration resource planning requirements. For example, the main business indicator of live broadcast services is network performance. Therefore, when planning acceleration resources for live broadcast services, acceleration resources in the same province or region are usually selected. That is, when planning cluster groups for each node, cluster groups in the same province or region can be planned for each node first. Download services do not need to pay too much attention to network performance. The traffic bandwidth of such services can use cross-region acceleration resources. That is, when planning cluster groups for each node, the association relationship of the location of cluster groups does not need to be considered. Therefore, business information can also be the traffic bandwidth of different types of services, that is, the traffic bandwidth information of the target domain name area is distinguished according to the business type, so that subsequent planning can plan acceleration resources with better business capabilities according to the characteristics of different businesses, realize balanced planning based on business types, improve the pertinence of planning in the business type dimension, and improve the quality of services provided by the target domain name area for different businesses in the future, thereby improving customer experience.
[0026] It should be noted that, when the service information is the traffic bandwidth of different types of services, acceleration resource planning can be performed separately for different types of services. In particular, the nodes to be planned when performing acceleration resource planning for different types of services may be different. For example, when performing acceleration resource planning for live broadcast type services, the nodes to be planned in the target domain name area are the nodes that meet certain network performance quality requirements in the target domain name area, while the nodes to be planned in the target domain name area when performing acceleration resource planning for download type services are the nodes that are not defined as unplannable in the target domain name area, etc.
[0027] Of course, the above are only specific examples. In other examples, the service information may also be traffic bandwidth information of customers of different levels, which will not be described in detail here.
[0028] In this embodiment, the target domain name zone includes at least one domain name zone to be planned. The domain name zone to be planned may be specified by the customer or may be a domain name zone detected by the server where the current plan does not match the actual service scenario.
[0029] In particular, in some examples, it is considered that the same node may serve several domain name areas at the same time, which may cause the planning of different domain name areas to affect each other. Therefore, the target domain name area may include not only the designated domain name area to be planned, but also other domain name areas served by the nodes to be planned in the domain name area to be planned. That is to say, after determining the domain name area to be planned that needs to be accelerated resource planning, on the basis of taking the domain name area to be planned as the target domain name area for accelerated resource planning, the nodes to be planned in the domain name area to be planned are also determined, and then it is determined whether these nodes to be planned also serve other domain name areas. If there are nodes to be planned that serve other domain name areas, the other domain name areas served by the nodes to be planned are also taken as the target domain name areas for accelerated resource planning.
[0030] It is worth mentioning that the domain name areas that may be affected during the planning process are planned together, which avoids the adverse impact of the current planning on the existing planning and realizes the optimal planning in the CDN dimension.
[0031] Step 102: Determine the minimum number of cluster groups that need to be planned for the target domain name area according to the business information.
[0032] In this embodiment, the acceleration service resources of a node to be planned in the target domain name area include at least one cluster group. The number of cluster groups included in different nodes to be planned can be the same or different.
[0033] In some examples, the service information is S, that is, the overall service traffic bandwidth of the target domain name area is S, and the average value of the rated bandwidth of all cluster groups included in each node to be planned in the target domain name area is T, then ([S / T]+1) is used as the minimum number of cluster groups, where [S / T] represents the rounding operation of the result of S / T. Of course, in other examples, T can also be the median of the rated bandwidth of all cluster groups included in each node to be planned in the target domain name area.
[0034] In other examples, the service information is {S1, S2, ..., Si}, that is, the service traffic bandwidth of the first category in the target domain name area is S1, the service traffic bandwidth of the second category in the target domain name area is S2... The service traffic bandwidth of the i-th category in the target domain name area is Si, and the average value of the rated bandwidth of all cluster groups contained in the nodes that meet the requirements of the first category of the target domain name area is T1, then ([S1 / T1]+1) is taken as the minimum number of cluster groups, where [S1 / T1] represents rounding the result of S1 / T1... and finally i minimum number of cluster groups are obtained.
[0035] It should be noted that this embodiment mainly emphasizes meeting the demand for the lower limit of business traffic in the target domain name area. In some cases, in the planning process, not only the minimum number of cluster groups but also the maximum number of cluster groups need to be considered. For example, the customer specifies the cluster groups that can be planned, resulting in planning based only on the cluster groups that can be planned, or the traffic bandwidth of the target domain name area is limited, resulting in the number of cluster groups exceeding a certain value, which will cause the bandwidth to exceed the limit, etc. Therefore, in some examples, on the basis of determining the minimum number of cluster groups that need to be planned for the target domain name area, the maximum number of cluster groups that can be planned for the target domain name area can also be determined, so as to increase the restriction condition that the number of planned cluster groups is less than the maximum number of cluster groups in the subsequent planning process.
[0036] Step 103 , detecting whether the minimum number of cluster groups is greater than the number of nodes to be planned in the target domain name area, if so, executing step 104 , if not, executing step 105 .
[0037] In this embodiment, the node to be planned is a node that has been determined to need to perform accelerated resource planning.
[0038] It should be noted that the nodes in the target domain name area may not necessarily be planned and may not necessarily participate in the planning. For example, some special nodes provide acceleration services for the services or specific content of certain specific customers. Unless the node settings are changed, other services cannot be received, and acceleration services cannot be provided for the services of other customers. Therefore, the node cannot be planned and does not belong to the nodes to be planned. Alternatively, if the customer specifies that planning should only be performed on certain nodes, other nodes will not participate in the planning and do not belong to the nodes to be planned. This embodiment does not limit the method of determining the nodes that need to be accelerated resource planning.
[0039] In some examples, before detecting whether the minimum number of cluster groups is greater than the number of nodes to be planned in the target domain name area, the planning method of CDN acceleration service resources determines the nodes to be planned in the target area, which can be implemented in the following way: obtaining the cost information and node feature information of all nodes in the target domain name area and the customer business information of the target domain name area, wherein the node feature information may include the type of service that the node can provide, the service quality information when providing the corresponding service, the network status information of the node, etc.; screening all nodes in the target domain name area according to the cost information, node feature information and customer business information to obtain the nodes to be planned. Thus, in the process of planning acceleration resources, the influence of customer business information, node cost information and node business information on nodes is considered to screen out the nodes to be planned, so that when providing acceleration services, it can better meet customer needs, with lower costs and better customer experience, and avoids incorrect planning of nodes that cannot be planned.
[0040] Step 104 , planning a first target number of cluster groups for each node to be planned, where the first target number is the number of cluster groups included in the node to be planned that includes the least number of cluster groups.
[0041] In this embodiment, firstly, a first target number of cluster groups are selected from the cluster groups included in each node to be planned, and then the selected cluster groups are planned to the corresponding node to be planned. This embodiment does not limit how to select the first target number of cluster groups, which can be selected randomly, or according to the performance, cost, or number of times the cluster groups have been planned to the node in historical planning.
[0042] In some examples, planning a first target number of cluster groups for each node to be planned can be achieved in the following manner: for each node to be planned, randomly selecting a first target number of cluster groups from the included cluster groups, and planning the selected cluster groups to the node to be planned.
[0043] In other examples, planning the first target number of cluster groups for each node to be planned can also be achieved in the following manner: for each node to be planned, sort the cluster groups contained in each node to be planned from low to high according to the difference between the required bandwidth and the rated bandwidth or the ratio of the required bandwidth to the rated bandwidth, select the first M cluster groups in each sequence, and plan the selected cluster groups to the corresponding nodes to be planned, where M is the value of the first target number. In this way, a cluster group that can provide the maximum available bandwidth is planned for each node to be planned, avoiding overload when providing acceleration services based on the planning results later.
[0044] In some other examples, planning the first target number of cluster groups for each node to be planned can also be achieved in the following way: for each node to be planned, sort the included cluster groups from low to high according to the bandwidth cost, select the first M cluster groups in the sequence, and plan the selected cluster groups to the node to be planned, where M is the value of the first target number. The bandwidth cost is the traffic cost when the cluster groups evenly share the service traffic bandwidth according to the billing cycle and billing method signed by the node maintainer and the operator. In this way, a cluster group with a lower cost is planned for each node to be planned, so that the planning result can achieve the global cost optimization.
[0045] Of course, in other examples, the physical device type of the node to be planned can also be considered. Different devices serve different types of services. They can be planned as much as possible on nodes with devices that have already deployed related services to reduce resource consumption for cluster group deployment of services. Alternatively, the above-mentioned multiple factors can be considered comprehensively, which will not be elaborated here one by one.
[0046] It is understandable that the number of cluster groups contained in each node to be planned is usually not exactly the same. For a node to be planned that contains a first target number of cluster groups, planning the first target number of cluster groups is actually planning all the contained cluster groups to the node to be planned. Only for a node to be planned that contains a number of cluster groups exceeding the first target number, does selecting the first target number of cluster groups have practical significance. Therefore, for a node to be planned that contains a first target number of cluster groups, all the cluster groups it contains can be planned, and for a node to be planned that contains a number of cluster groups exceeding the first target number, the first target number of nodes will be selected first and then planned.
[0047] Step 105: plan a cluster group for each node to be planned.
[0048] In this embodiment, a cluster group may be randomly planned from the included cluster groups to simplify the implementation process and reduce the difficulty of implementation, or a cluster group with the largest difference between the required bandwidth and the rated bandwidth or the ratio of the required bandwidth to the rated bandwidth may be planned for each node to be planned, thereby planning a cluster group with the largest available bandwidth for each node to be planned to avoid overload when providing subsequent acceleration services. It is not difficult to see that step 105 is substantially the same as step 104 when the first target number is 1, and will not be described one by one here.
[0049] It should be noted that, since the correspondence between domain name zones and nodes is many-to-many, when the target domain name zone includes several domain name zones to be planned, it is possible that at least one node provides services for at least two domain name zones at the same time, such as node A is both a node to be planned for domain name zone B and a node to be planned for domain name zone C. At this time, additional planning cluster group conditions can be added to the nodes to be planned with the aforementioned characteristics according to actual needs. Take the example that node A contains five cluster groups, and when participating in the acceleration resource planning of domain name area B, node A needs to be planned with two cluster groups, and when participating in the acceleration resource planning of domain name area C, the cluster groups planned are three cluster groups: if it is expected that the acceleration resources planned for each node are as balanced as possible, then when the node participates in the acceleration resource planning of different domain name areas, the acceleration resources planned in different domain name areas are overlapped as much as possible, that is, two cluster groups are selected from the three cluster groups planned for node A in the planning of domain name area C as the cluster groups planned for node A in the planning of domain name area B; if it is expected that each node will not be overloaded as much as possible after planning, then when the node participates in the acceleration resource planning of different domain name areas, the acceleration resources planned in different domain name areas are overlapped as much as possible, that is, two cluster groups other than the three cluster groups planned for node A in the planning of domain name area C are used as the cluster groups planned for node A in the planning of domain name area B.
[0050] It can be understood that by planning the same number of cluster groups for each node to be planned in the target domain name area, the acceleration resources planned for each node to be planned are balanced in the cluster group dimension. However, the cluster group is actually composed of at least one device cluster, that is, starting from the node of the CDN domain name area, the acceleration service resources in the domain name area are layered, the first level is the node, a domain name area contains at least one node, the second level is the cluster group, the cluster group is the acceleration service resource of the next level of the node, such as a physical server cluster, a node contains at least one cluster group, the third level is the device cluster, the device cluster is the acceleration service resource of the next level of the cluster group, a cluster group contains at least one device cluster, and the device cluster is a service cluster divided according to different services. In some examples, a cabinet containing multiple devices constitutes a device cluster, a cabinet group composed of multiple cabinets constitutes a cluster group, and multiple cabinet groups constitute a node. Furthermore, considering that the number of device clusters contained in different cluster groups may be different, it is also possible to continue to plan device clusters for the cluster groups planned for each node to be planned, so as to achieve balance in the device cluster dimension and further enhance the balance of planning.
[0051] Based on this, another aspect of the embodiment of the present invention further provides a method for planning CDN acceleration service resources, which is applied to a server, which may be a background server, a monitoring server or a central platform server of a CDN system. Figure 2 As shown, the process of the CDN acceleration service resource planning method also includes:
[0052] Step 106 , detecting whether the service information meets a preset service threshold condition, if so, executing step 107 , if not, executing step 108 .
[0053] In this embodiment, the preset business threshold condition can be that the bandwidth peak of the target domain name area is less than the specified level, or that the minimum number of device clusters determined based on the business information of the target domain name area is less than the number of cluster groups, etc. This is mainly to distinguish the needs of the target domain name area in terms of device clusters, and will not be elaborated here.
[0054] Step 107: plan a device cluster for each planned cluster group.
[0055] In this embodiment, the acceleration service resources of a cluster group include at least one device cluster, that is, the acceleration resources in the target domain name area are divided into cluster group levels under nodes and device cluster levels under cluster groups.
[0056] In some examples, planning a device cluster for each planned cluster group can be achieved in the following way: planning a device cluster with the highest priority for each planned cluster group, the device cluster within the cluster group has a higher priority than the device cluster that can be planned outside the cluster group, and the device cluster within the cluster group that has been planned in the historical plan has a higher priority than other device clusters within the cluster group. That is to say, first try to plan a device cluster that has been planned in the historical plan among the device clusters included in the cluster group for the planned cluster group. In the case that there is no device cluster that has been planned in the historical plan, try to plan a device cluster included in the cluster group for the cluster group. When the cluster group does not contain a device cluster, plan a device cluster that can be planned outside the cluster group for the cluster group. It can be understood that the device cluster outside the planned cluster group will be added to the cluster group through the current planning operation. In the planning process, the change of the status of whether the currently planned cluster is planned is avoided to the greatest extent, and the waste of resources caused by the status change is reduced.
[0057] In particular, when there are multiple device clusters in the cluster group that have been planned in historical planning, one device cluster can be selected from the multiple device clusters planned in historical planning and planned for the cluster group based on the number of times each device cluster has been planned in historical planning, the cost, the difference between the required bandwidth and the rated bandwidth, and other information, or a device cluster planned in historical planning can be randomly selected and planned for the cluster group; in the case where there is no device cluster planned in historical planning, when the cluster group contains multiple device clusters, one device cluster can be selected from the multiple device clusters included and planned for the cluster group based on the cost of each device cluster, the difference between the required bandwidth and the rated bandwidth, and other information, or a device cluster can be randomly selected and planned for the cluster group; in the case where the cluster group does not contain a device cluster, when there are multiple plannable device clusters outside the cluster group, one device cluster can be selected from the plannable device clusters outside the cluster group based on the cost of each plannable device cluster outside the cluster group, the difference between the required bandwidth and the rated bandwidth, and other information, or a plannable device cluster outside the cluster group can be randomly selected and planned for the cluster group.
[0058] Step 108 : planning a second target number of device clusters for each planned cluster group, where the second target number is the number of device clusters included in the cluster group with the least number of device clusters.
[0059] In this embodiment, step 108 is substantially the same as step 107, and the difference lies mainly in the number of device clusters planned for each cluster group, which will not be described in detail here.
[0060] It is worth mentioning that this embodiment ensures that the number of device clusters planned for each planned cluster group is the same, so that the acceleration service resources planned for each cluster group are the same, further improving the balance of planning.
[0061] It can also be understood that the minimum number of cluster groups is determined based on the business information of the target domain name area, and the business needs of the target domain name area are mainly considered, but the planning result will also be affected by the bearing capacity of each node to be planned. When it is determined based on the current plan that the bandwidth required to be provided by the cluster group planned for each node to be planned exceeds its rated bandwidth, the quality of the acceleration service provided by the cluster group is affected due to overload. When the overload time is too long, it will also affect the performance of the equipment in the cluster group and even cause equipment failure. Therefore, in some embodiments, the bandwidth factor of each cluster group is also considered in the planning process.
[0062] Based on this, another aspect of the embodiment of the present invention further provides a method for planning CDN acceleration service resources, which is applied to a server, which may be a background server, a monitoring server or a central platform server of a CDN system. Figure 3 As shown, the process of the CDN acceleration service resource planning method also includes:
[0063] Step 109, when the required bandwidth of at least one planned cluster group exceeds the rated bandwidth, plan at least one cluster group for each node to be planned from the cluster groups or resource pools included in the node to be planned, so as to reduce the required bandwidth of each planned cluster group to not exceed the rated bandwidth.
[0064] In this embodiment, the required bandwidth is determined according to the currently planned cluster group. The resource pool maintains unactivated acceleration resources, and in particular, the acceleration resources in the resource pool can be activated through planning.
[0065] It is worth mentioning that re-planning the cluster groups of each node to be planned according to their bandwidth conditions can avoid overload of each cluster group when providing acceleration services in the future, which will affect the quality of the services provided and the performance of the equipment.
[0066] It is understandable that not only the cluster group may be overloaded, but also each device cluster within the cluster group may be overloaded. Therefore, similar to the processing of the cluster group, after planning the device clusters for each planned cluster group, it also includes: when the required bandwidth of at least one planned device cluster exceeds the rated bandwidth, at least one device cluster is planned for each planned cluster group from the device clusters or resource pools included in the planned cluster group to reduce the required bandwidth of each planned device cluster to not exceed the rated bandwidth.
[0067] The step division of the above methods is only for the purpose of clear description. When implemented, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent; adding insignificant modifications to the algorithm or process or introducing insignificant designs without changing the core design of the algorithm and process are all within the scope of protection of this patent.
[0068] Another aspect of the present invention is to provide a CDN acceleration service resource planning device. Figure 4 As shown, including:
[0069] The acquisition module 401 is used to acquire the service information of the target domain name zone.
[0070] The determination module 402 is used to determine the minimum number of cluster groups that need to be planned for the target domain name area according to the business information, and the acceleration service resources of a node to be planned in the target domain name area include at least one cluster group.
[0071] The detection module 403 is used to detect whether the minimum number of cluster groups is greater than the number of nodes to be planned in the target domain name area.
[0072] The first planning module 404 is used to plan a first target number of cluster groups for each node to be planned when the minimum number of cluster groups is greater than the number of nodes to be planned, wherein the first target number is the number of cluster groups included in the node to be planned that includes the minimum number of cluster groups.
[0073] The second planning module 405 is used to plan a cluster group for each node to be planned when the minimum number of cluster groups is not greater than the number of nodes to be planned.
[0074] It is not difficult to find that this embodiment is a device embodiment corresponding to the method embodiment, and this embodiment can be implemented in conjunction with the method embodiment. The relevant technical details mentioned in the method embodiment are still valid in this embodiment, and in order to reduce repetition, they are not repeated here. Accordingly, the relevant technical details mentioned in this embodiment can also be applied in the method embodiment.
[0075] It is worth mentioning that all modules involved in this embodiment are logic modules. In practical applications, a logic unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. In addition, in order to highlight the innovative part of the present invention, this embodiment does not introduce units that are not closely related to solving the technical problem proposed by the present invention, but this does not mean that there are no other units in this embodiment.
[0076] Another aspect of the present invention is to provide an electronic device, such as Figure 5As shown, it includes: at least one processor 501; and a memory 502 that is communicatively connected to the at least one processor 501; wherein the memory 502 stores instructions that can be executed by the at least one processor 501, and the instructions are executed by the at least one processor 501 so that the at least one processor 501 can execute the CDN acceleration service resource planning method described in any of the above method embodiments.
[0077] The memory 502 and the processor 501 are connected in a bus manner, and the bus may include any number of interconnected buses and bridges, and the bus connects various circuits of one or more processors 501 and the memory 502 together. The bus can also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on a transmission medium. The data processed by the processor 501 is transmitted on a wireless medium via an antenna, and further, the antenna also receives data and transmits the data to the processor 501.
[0078] The processor 501 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management and other control functions. The memory 502 can be used to store data used by the processor 501 when performing operations.
[0079] Another aspect of the present invention is to provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the CDN acceleration service resource planning method described in any of the above method embodiments.
[0080] That is, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium, including several instructions for making a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.
[0081] Those skilled in the art will appreciate that the above embodiments are specific embodiments for implementing the present invention, and that in actual applications, various changes may be made in form and detail without departing from the spirit and scope of the present invention.
Claims
1. A method for planning CDN acceleration service resources, characterized in that: include: Obtain business information of the target domain name area; Determine the minimum number of cluster groups that need to be planned for the target domain name area according to the business information; The acceleration service resources of a node to be planned in the target domain name area include at least one cluster group; Detecting whether the minimum number of cluster groups is greater than the number of nodes to be planned in the target domain name area; In the case where the minimum number of cluster groups is greater than the number of nodes to be planned, planning a first target number of cluster groups for each node to be planned, the first target number being the number of cluster groups included in the node to be planned that includes the least number of cluster groups; When the minimum number of cluster groups is not greater than the number of nodes to be planned, planning one cluster group for each node to be planned; Wherein, the method further comprises: In the case where the required bandwidth of at least one of the planned cluster groups exceeds the rated bandwidth, planning at least one more cluster group for each of the nodes to be planned from the cluster groups or resource pools included in the node to be planned, so as to reduce the required bandwidth of each of the planned cluster groups to not exceed the rated bandwidth, wherein the required bandwidth is determined according to the currently planned cluster groups; The target domain name area includes the domain name area to be planned and other domain name areas served by the node to be planned within the domain name area to be planned; Planning the cluster group for the node to be planned is achieved by planning the acceleration service resources provided by the cluster group as the acceleration service resources of the node to be planned.
2. The CDN acceleration service resource planning method according to claim 1, characterized in that: The method further comprises: Detecting whether the service information meets a preset service threshold condition; In the case where the target domain name zone meets the service threshold condition, planning a device cluster for each of the planned cluster groups, and the acceleration service resources of one of the cluster groups include at least one of the device clusters; When the target domain name zone does not meet the service threshold condition, a second target number of device clusters is planned for each planned cluster group, where the second target number is the number of device clusters included in the cluster group that includes the least number of device clusters.
3. The CDN acceleration service resource planning method according to claim 2, characterized in that: The step of planning a device cluster for each of the planned cluster groups includes: A device cluster with the highest priority is planned for each planned cluster group. The device cluster within the cluster group has a higher priority than the device cluster that can be planned outside the cluster group. The device cluster within the cluster group that has been planned in historical planning has a higher priority than other device clusters within the cluster group.
4. The CDN acceleration service resource planning method according to claim 1, characterized in that: The planning of a cluster group for each of the nodes to be planned includes: A cluster group having the largest difference between the required bandwidth and the rated bandwidth is planned for each of the nodes to be planned.
5. The method for planning CDN acceleration service resources according to any one of claims 1 to 3, characterized in that: The method further comprises: Obtaining cost information and node feature information of all nodes in the target domain name area and customer service information of the target domain name area; All nodes in the target domain name area are screened according to the cost information, the node feature information and the customer service information to obtain the node to be planned.
6. A CDN acceleration service resource planning device, characterized in that: include: An acquisition module is used to obtain business information of a target domain name area; A determination module, configured to determine the minimum number of cluster groups required to be planned for the target domain name area according to the business information; The acceleration service resources of a node to be planned in the target domain name area include at least one cluster group; A detection module, used to detect whether the minimum number of cluster groups is greater than the number of nodes to be planned in the target domain name area; A first planning module, configured to plan a first target number of cluster groups for each node to be planned when the minimum number of cluster groups is greater than the number of nodes to be planned, the first target number being the number of cluster groups included in the node to be planned that includes the least number of cluster groups; A second planning module, configured to plan one cluster group for each node to be planned when the minimum number of cluster groups is not greater than the number of nodes to be planned; The CDN acceleration service resource planning device is further used for planning at least one cluster group for each node to be planned from the cluster group or resource pool included in the node to be planned, when the required bandwidth of at least one of the planned cluster groups exceeds the rated bandwidth, so as to reduce the required bandwidth of each of the planned cluster groups to not exceed the rated bandwidth, and the required bandwidth is determined according to the currently planned cluster group; The target domain name area includes the domain name area to be planned and other domain name areas served by the node to be planned within the domain name area to be planned; Planning the cluster group for the node to be planned is achieved by planning the acceleration service resources provided by the cluster group as the acceleration service resources of the node to be planned.
7. An electronic device, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the CDN acceleration service resource planning method as described in any one of claims 1 to 5.
8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method for planning CDN acceleration service resources according to any one of claims 1 to 5 is implemented.
