DNS-based fusion CDN traffic scheduling method and device

Abstract

The application discloses a DNS-based fusion CDN traffic scheduling method and device, and relates to the technical field of Internet.The DNS-based fusion CDN traffic scheduling method comprises the following application steps: acquiring local DNS portrait information data files, edge service node data files of each CDN service provider and domain name cutting capacity proportion configuration data files, and sending the acquired data to an authoritative server at regular time intervals; and the authoritative DNS loads the data files into the memory, wherein the application analyzes the proportion of the traction capacity behind different local DNS servers, combines the different local DNS servers into domain name cutting capacity groups in proportion according to the proportion of the fusion CDN cutting capacity of each domain name on the authoritative DNS server, and responds to the CDN service node IP of a specific CDN service provider, so that the local DNS bandwidth is ensured to be stable, and the cutting capacity is accurately ensured.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, specifically to a DNS-based converged CDN traffic scheduling method and apparatus. Background Technology

[0002] Currently, there are numerous CDN service providers. Many enterprises with high traffic or high quality requirements may have multiple CDN service providers offering CDN acceleration services simultaneously. Considering bandwidth capacity limits and service quality costs, both these enterprises and CDN service providers need to control the bandwidth ratio carried by each CDN service provider. Systems that typically achieve this function are called converged CDN scheduling systems. Currently, converged CDN scheduling systems generally control bandwidth ratios through CNAME switching. The customer or CDN service provider pre-configures multiple CNAME (also known as alias) records on the authoritative DNS server for the customer's domain name (the CNAME record can be a mapping between the customer's domain name and the CNAME domain name), configuring different ratios to direct traffic to the customer's domain name.

[0003] Because local DNS servers have the ability to cache CNAMEs and CDN service node IPs, although the converged CDN scheduling system responds to local DNS servers with CNAMEs or CDN service node IPs globally according to the request granularity, the final towing ratio for a single local DNS server may have a large error, and there is also the problem of large bandwidth fluctuations. Due to the different towing volumes and caching durations of different local DNS servers, the global bandwidth traffic ratio will eventually become unbalanced, causing large bandwidth fluctuations. Therefore, we propose a DNS-based converged CDN traffic scheduling method and device to solve the above-mentioned problems. Summary of the Invention

[0004] Technical problems to be solved

[0005] To address the shortcomings of existing technologies, this invention provides a DNS-based converged CDN traffic scheduling method and apparatus. This method solves the problem of analyzing the torrent ratios behind different local DNS servers, combining different local DNS servers into domain name splitting groups based on the converged CDN splitting ratio of each domain name on the authoritative DNS server, and responding to the CDN service node IP of a specific CDN service provider. This achieves both stable local DNS bandwidth and accurate traffic splitting.

[0006] Technical solution

[0007] To achieve the above objectives, the present invention provides the following technical solution: a DNS-based converged CDN traffic scheduling method, comprising the following application steps:

[0008] Acquire local DNS profile information data files, edge service node data files of each CDN service provider, and domain name splitting ratio configuration data files, and periodically send the acquired data to the authoritative server;

[0009] Authoritative DNS loads the data files into memory;

[0010] Authoritative DNS generates splitting packets based on the domain splitting ratio and the local DNS traction ratio;

[0011] Match the domain name segmentation group to which the requested local DNS IP address belongs;

[0012] The response is based on the corresponding CDN edge service node IP address of the domain name splitting group.

[0013] Furthermore, the local DNS profile information data file is generated from the acquired local DNS profile data information.

[0014] Furthermore, the data information of the local DNS profile includes domain name, zone, local DNS IP address, and traffic share.

[0015] Furthermore, the domain name allocation ratio configuration data file is generated from the allocation ratio of different CDN service providers.

[0016] Furthermore, the edge service node data files of each CDN service provider are generated from the CDN edge service node IPs.

[0017] Furthermore, the segmentation grouping is obtained by an algorithm.

[0018] Furthermore, the specific algorithm for the segmentation grouping is as follows:

[0019] 1) Sort the local DNS list from largest to smallest according to the proportion of traffic;

[0020] 2) Sort CDN service providers from largest to smallest based on their traffic allocation ratio;

[0021] 3) Traverse the traffic ratio and select local DNS servers from the local DNS list in descending order of traffic ratio;

[0022] 4) Let the current required cutting volume ratio be M1, and create a new cutting volume group called cutting volume group G1;

[0023] The currently selected local DNS lead volume ratio is N1, and the sum of the local DNS lead volume ratios that have been added to the current cut volume group is S. If S + N1 >= M1, the local DNS allocation for cut volume group G1 ends; if S + N1 < M1, add this local DNS to the current cut volume group, and accumulate S = S + N1, then continue to select the next local DNS;

[0024] 5) Repeat step 4) until the allocation of all cut volume groups ends.

[0025] Further, the domain name cut volume group to which the match belongs is obtained from the authoritative DNS acquisition request.

[0026] Further, the CDN edge service node IP is the response of the authoritative DNS according to the domain name cut volume group.

[0027] A DNS-based integrated CDN traffic scheduling device includes:

[0028] An acquisition module that acquires the local DNS profile information data file, the edge service node data files of each CDN service provider, and the domain name cut volume ratio configuration data file, and regularly sends the acquired data to the authoritative server;

[0029] A loading module that the authoritative DNS loads the data files into memory;

[0030] A cut volume grouping module that the authoritative DNS generates cut volume groups according to the domain name cut volume ratio and the local DNS lead volume ratio;

[0031] A domain name cut volume group matching module that matches the domain name cut volume group to which it belongs according to the IP address of the requested local DNS;

[0032] A response module that responds with the corresponding CDN edge service node IP according to the domain name cut volume group.

[0033] Beneficial effects

[0034] The present invention has the following beneficial effects:

[0035] (1) This DNS-based integrated CDN traffic scheduling method controls the integrated CDN scheduling ratio by the local DNS lead volume ratio at the domain name request granularity. For the same local DNS server, it maintains responding to the CDN service node IP of one CDN service provider for a long time, without being affected by the local DNS cache duration, avoiding the switching of the traffic led by the local DNS among multiple CDN service providers, thus ensuring the stability of bandwidth and service quality and achieving the purpose of accurately controlling the traffic ratio among CDN service providers.

[0036] Of course, any product implementing this invention does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description

[0037] Figure 1 This is a schematic diagram of the scheduling process structure of the present invention. Detailed Implementation

[0038] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0039] In the description of this invention, it should be understood that the terms "opening", "upper", "lower", "thickness", "top", "middle", "length", "inner", "around", etc., which indicate orientation or positional relationship, are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the components or elements referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as limiting this invention.

[0040] Please see Figure 1 This invention provides a technical solution: a DNS-based converged CDN traffic scheduling method, comprising the following application steps:

[0041] S1: Obtain local DNS profile data, including domain name, zone, local DNS IP address, and traffic share;

[0042] S2: Periodically generate files from the local DNS profile data and synchronize them with the authoritative server;

[0043] S3: The authoritative DNS receives the local DNS profile data file sent by S2 in real time and loads it into memory;

[0044] S4: Configure the traffic allocation ratio of different CDN service providers for the domain name and the IP of CDN edge service nodes;

[0045] In practice, the specific format is as follows:

[0046] Domain name splitting service provider's share of splitting volume

[0047] www.a.com A70%

[0048] www.a.comB30%

[0049] S5: Periodically generate files containing the domain name allocation percentage and CDN edge service node IPs and synchronize them to the authoritative server;

[0050] S6: The authoritative DNS receives the traffic share ratio and the CDN edge service node IP data file sent by S5 in real time and loads them into the memory.

[0051] S7: The authoritative DNS calculates the traffic grouping of this area according to the traffic share ratio of the domain name and the local DNS profile information.

[0052] S8: After the authoritative DNS receives the request from the local DNS of the domain name, it obtains the IP address in the request and the traffic grouping to which the IP address belongs.

[0053] S9: The authoritative DNS responds according to the CDN edge service node IP in the traffic grouping matched in S8.

[0054] In implementation, when a request with the IP of 11.11.11.11 comes, the fixed response service node IP is 1.1.1.1.

[0055] Specifically, the specific algorithm for the traffic grouping of this area in S7 is as follows:

[0056] S71: Sort the local DNS list in descending order according to the traction volume ratio.

[0057] S72: Sort the CDN service providers in descending order according to the traffic share ratio.

[0058] S73: Traverse the traffic share ratio, and sequentially select the local DNS from the local DNS list in descending order according to the traction volume ratio.

[0059] S74: Let the ratio required by the current traffic be M1, and create a new traffic group as traffic grouping G1.

[0060] The traction volume ratio of the currently selected local DNS is N1, and the sum of the traction volume ratios of the local DNS that have been added to this traffic grouping is S. If S + N1 >= M1, the distribution of local DNS in traffic grouping G1 ends; if S + N1 < M1, add this local DNS to the current traffic grouping, and accumulate S = S + N1, and continue to select the next local DNS.

[0061] S75: Repeat step S74 until all traffic groupings are distributed.

[0062] In implementation, the specific grouping result is as follows:

[0063] CDN Service Provider Traffic Grouping Traffic Share Ratio IP Address of Local DNS Service Node IP

[0064] AG1 70% 11.11.11.11, 1.1.1.1

[0065] 22.22.22.22,

[0066] 33.33.33.33,

[0067] 44.44.44.44,

[0068] BG230%55.55.55.55,…2.2.2.2.

[0069] A DNS-based converged CDN traffic scheduling device includes:

[0070] The acquisition module acquires local DNS profile information data files, edge service node data files of each CDN service provider, and domain name splitting ratio configuration data files, and periodically sends the acquired data to the authoritative server;

[0071] The loading module, the authoritative DNS, loads the data file into memory;

[0072] The splitting group module generates splitting groups based on the domain splitting ratio and the local DNS traffic ratio from the authoritative DNS.

[0073] The domain name splitting group matching module matches the domain name splitting group to which the requested local DNS IP address belongs.

[0074] The response module responds to the corresponding CDN edge service node IP based on the domain name splitting group.

[0075] When in use, at the domain name request granularity, the fused CDN scheduling ratio is controlled by the proportion of local DNS traffic. For the same local DNS server, it maintains a response to the CDN service node IP of a CDN service provider for a longer period of time, without being affected by the local DNS cache duration. This avoids the local DNS traffic switching between multiple CDN service providers, thereby ensuring the stability of bandwidth and service quality and achieving the goal of accurately controlling the traffic ratio between various CDN service providers.

[0076] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0077] It should be understood that when an element is referred to as "fixed to" or "set on" another element, it may be directly on the other element or may have an intervening element present at the same time; when an element is referred to as "connected to" another element, it may be directly connected to the other element or may have an intervening element present at the same time. In addition, the term "connected" as used herein may include wireless connections; the word "and / or" as used includes any unit and all combinations of one or more of the associated listed items.

[0078] Any process or method description in the flowchart or otherwise herein can be understood as: representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the function involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0079] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0080] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0081] Those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium. When the program is executed, it includes the following steps (steps of the method). The storage medium is, for example, ROM / RAM, magnetic disk, optical disk, etc.

[0082] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0083] The storage media mentioned above can be read-only memory, disk, or optical disk, etc.

[0084] The preferred embodiments of the present invention disclosed above are merely illustrative of the invention. These preferred embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A DNS-based converged CDN traffic scheduling method, characterized in that: It includes the following application steps: Obtain the local DNS portrait information data file, the edge service node data files of each CDN service provider, and the domain name traffic splitting ratio configuration data file, and regularly send the obtained data to the authoritative server; wherein, the local DNS portrait information data file is generated from the data information of the obtained local DNS portrait; the data information of the local DNS portrait includes domain name, region, the IP address of the local DNS, and the traffic volume ratio; The authoritative DNS loads the data file into memory; The authoritative DNS generates traffic splitting groups according to the domain name traffic splitting ratio and the local DNS traffic volume ratio; Match the domain name traffic splitting group to which it belongs according to the IP address of the requested local DNS; Respond with the corresponding CDN edge service node IP according to the domain name traffic splitting group; Among them, the traffic splitting group is obtained by an algorithm; the specific algorithm for the traffic splitting group is as follows: 1). Sort the local DNS list in descending order according to the traffic volume ratio; 2). Sort the CDN service providers in descending order according to the traffic splitting ratio; 3). Traverse the traffic splitting ratio, and sequentially select local DNS from the local DNS list in descending order according to the traffic volume ratio; 4). Let the current traffic splitting requirement ratio be M1, and create a new traffic splitting group as traffic splitting group G1; The current selected local DNS traffic volume ratio is N1, and the sum of the local DNS traffic volume ratios that have been added to this traffic splitting group is S. If S + N1 >= M1, the allocation of local DNS in traffic splitting group G1 ends; if S + N1 < M1, add this local DNS to the current traffic splitting group, and accumulate S = S + N1, and continue to select the next local DNS; 5). Repeat step 4) until the allocation of all traffic splitting groups ends.

2. The DNS-based converged CDN traffic scheduling method according to claim 1, characterized in that: The domain name traffic splitting ratio configuration data file is generated from the traffic splitting ratios of different CDN service providers.

3. The DNS-based converged CDN traffic scheduling method according to claim 1, characterized in that: The edge service node data files of each CDN service provider are generated from the CDN edge service node IPs.

4. The DNS-based converged CDN traffic scheduling method according to claim 1, characterized in that: The matching of the domain name traffic splitting group to which it belongs is obtained by the authoritative DNS from the request.

5. The DNS-based converged CDN traffic scheduling method according to claim 1, characterized in that: The CDN edge service node IP is responded by the authoritative DNS according to the domain name traffic splitting group.

6. A DNS-based converged CDN traffic scheduling device, characterized in that, It includes: An acquisition module, which acquires the local DNS portrait information data file, the edge service node data files of each CDN service provider, and the domain name traffic splitting ratio configuration data file, and regularly sends the acquired data to the authoritative server; wherein, the local DNS portrait information data file is generated from the data information of the acquired local DNS portrait; the data information of the local DNS portrait includes domain name, region, the IP address of the local DNS, and the traffic volume ratio; A loading module, where the authoritative DNS loads the data file into memory; A traffic splitting group generation module, where the authoritative DNS generates traffic splitting groups according to the domain name traffic splitting ratio and the local DNS traffic volume ratio; A domain name traffic splitting group matching module, which matches the domain name traffic splitting group to which it belongs according to the IP address of the requested local DNS; A response module, which responds with the corresponding CDN edge service node IP according to the domain name traffic splitting group; Among them, the traffic splitting group is obtained by an algorithm; the specific algorithm for the traffic splitting group is as follows: 1), Sort the local DNS list in descending order according to the traction volume ratio; 2), Sort the CDN service providers in descending order according to the traffic cut ratio; 3), Traverse the traffic cut ratio, and sequentially select local DNS from the local DNS list in descending order according to the traction volume ratio; 4), Set the current traffic cut requirement ratio as M1, and create a new traffic cut group as traffic cut group G1; The current selected local DNS traction volume ratio is N1, and the sum of the traction volume ratios of the local DNS that have been added to this traffic cut group is S. If S + N1 >= M1, the distribution of local DNS in traffic cut group G1 ends; if S + N1 < M1, add this local DNS to the current traffic cut group, and accumulate S = S + N1, then continue to select the next local DNS; 5), Repeat step 4) until the distribution of all traffic cut groups ends.

Images