WO2020206784A1 - 一种域名带宽调整方法及装置 - Google Patents

一种域名带宽调整方法及装置 Download PDF

Info

Publication number
WO2020206784A1
WO2020206784A1 PCT/CN2019/086059 CN2019086059W WO2020206784A1 WO 2020206784 A1 WO2020206784 A1 WO 2020206784A1 CN 2019086059 W CN2019086059 W CN 2019086059W WO 2020206784 A1 WO2020206784 A1 WO 2020206784A1
Authority
WO
WIPO (PCT)
Prior art keywords
bandwidth
domain name
target domain
duration
actual
Prior art date
Application number
PCT/CN2019/086059
Other languages
English (en)
French (fr)
Inventor
何锦龙
Original Assignee
网宿科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 网宿科技股份有限公司 filed Critical 网宿科技股份有限公司
Priority to EP19880923.8A priority Critical patent/EP3748925B1/en
Priority to US16/872,558 priority patent/US10958592B2/en
Publication of WO2020206784A1 publication Critical patent/WO2020206784A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/826—Involving periods of time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context

Definitions

  • This application relates to the field of Internet technology, and in particular to a domain name bandwidth adjustment method and device.
  • CDN Content Delivery Network
  • content delivery network Content Delivery Network
  • CDN Content Delivery Network
  • edge bandwidth will reduce users' access to CDN
  • return-to-source bandwidth will increase the pressure on the source station in the CDN system, which is likely to cause the instability of the entire CDN system.
  • the existing CDN system can limit the edge bandwidth or the back-to-source bandwidth according to GPC (Global Protection Control).
  • GPC Global Protection Control
  • the CDN system is prone to misjudgment.
  • the edge bandwidth or the return-to-source bandwidth decreases, the CDN system will directly release the speed limit on the edge bandwidth or the return-to-source bandwidth, which will easily cause the edge bandwidth or the return-to-source bandwidth to increase again.
  • the purpose of this application is to provide a domain name bandwidth adjustment method and device, which can avoid the problem of directly releasing the bandwidth restriction and causing the edge bandwidth or return-to-source bandwidth of the target domain name to increase again.
  • this application provides a domain name bandwidth adjustment method, which is applied to a CDN system.
  • the method includes: judging whether the CDN system triggers a bandwidth rate limiting strategy; if triggered, the CDN system serves In the domain name, determine the target domain name to be rate limited, and execute the bandwidth rate limit strategy for the target domain name; when the bandwidth rate limit policy is executed, determine the initial reference bandwidth of the target domain name, and observe Within the time period, the initial reference bandwidth and the actual bandwidth of the target domain name are compared to determine whether to perform a step adjustment on the initial reference bandwidth, and to determine whether to release the bandwidth rate limit strategy.
  • the domain name bandwidth adjustment device includes a rate limit determination unit for determining whether the CDN system triggers a bandwidth rate limit strategy. , And determine whether to cancel the bandwidth rate limit policy; a domain name identification unit, used to determine the target domain name to be rate limited among the domain names served by the CDN system after the bandwidth rate limit policy is triggered; a bandwidth adjustment unit, It is used to determine the initial reference bandwidth of the target domain name, and compare the initial reference bandwidth with the actual bandwidth of the target domain name within a specified observation time period to determine whether to adjust the initial reference bandwidth in steps.
  • the CDN system can automatically determine whether to trigger the bandwidth rate limit strategy according to the load situation of the edge node server or the transit node server, and when the bandwidth rate limit policy is triggered, the edge node server or Determine the target domain name that needs to be rate-limited in the domain name served by the transit node server, and then limit the edge bandwidth or return-to-origin bandwidth of the target domain name according to the set initial reference bandwidth. If the actual bandwidth of the target domain name is less than or equal to the initial reference bandwidth and the duration reaches the preset reference duration, the CDN system will adjust the initial reference bandwidth of the target domain name step by step, and gradually increase the target domain name throughout the entire reference bandwidth according to the adjusted reference bandwidth.
  • the available bandwidth in the CDN system to improve the user's access experience to the target domain name When the actual bandwidth of the target domain name is less than or equal to the initial reference bandwidth and the duration of the specified observation period is reached, the CDN system will lift the bandwidth rate limit strategy and completely release the bandwidth limit on the target domain name. It can be seen that the technical solution provided by this application can gradually restore the acceleration effect of the CDN system on the target domain name through the bandwidth step adjustment and speed limit observation of the target domain name, which not only improves the user experience of accessing the target domain name, but also avoids direct Releasing the bandwidth limit causes the edge bandwidth or return-to-origin bandwidth of the target domain name to increase again.
  • Fig. 1 is a flowchart of a domain name bandwidth adjustment method in an embodiment of the present application
  • FIG. 2 is a flowchart of determining whether to perform step adjustment on the initial reference bandwidth in an embodiment of the present application
  • FIG. 3 is a flowchart of step adjustment of the initial reference bandwidth in an embodiment of the present application.
  • FIG. 4 is a flowchart of determining whether to release the bandwidth speed limit strategy in the implementation of the present application
  • FIG. 5 is a schematic diagram of functional modules of a domain name bandwidth adjustment device in an embodiment of the present application.
  • Fig. 6 is a schematic structural diagram of a domain name bandwidth adjustment device in an embodiment of the present application.
  • a node is the most basic deployment unit in a CDN system, and each node is composed of a cache server cluster.
  • the primary goal of CDN system design is to minimize the user’s access response time.
  • the CDN system will try to store the content required by the user in the nearest location to the user, that is, the person responsible for providing content services to the user
  • the cache server should be deployed at a physical network edge location.
  • the foregoing network edge location may be called an edge node, and a cache server deployed at the edge node may be called an edge node server.
  • the equipment responsible for global management and control in the CDN system constitutes a central node.
  • the central node can not only monitor the various subsystems and equipment in the entire CDN network in real time, generate corresponding alarms for various faults, and can also monitor in real time.
  • the cache server deployed at the central node is referred to as a transit node server.
  • the transit node server stores the most complete copy of the content.
  • the edge node server does not cache the content accessed by the user, the edge node server will send a request to the transit node server. If the transit node server still does not cache the content accessed by the user, the transit node is required The server returns to the source site. If the transit node server fails or has insufficient service capacity, the edge node server needs to directly return to the source site.
  • the network bandwidth generated by the data exchange between the user and the edge node server is called the edge bandwidth
  • the network bandwidth generated by the data exchange between the transit node server and the source station is called the back-to-source bandwidth.
  • the method for adjusting domain name bandwidth may include the following steps.
  • S101 Determine whether the CDN system triggers the bandwidth rate limiting strategy, and if it is triggered, determine the target domain name to be rate limited in the domain names served by the CDN system, and execute the bandwidth rate limiting strategy on the target domain name.
  • the CDN system will determine whether to trigger the bandwidth limit strategy based on the load of the cache server and the load of the entire network bandwidth. Excessive load on the cache server or network bandwidth will cause the entire CDN system to work unstable and affect the CDN system to provide services to the outside world. Therefore, the CDN system will trigger the bandwidth rate limit strategy to limit the network bandwidth to reduce the load on the cache server and network bandwidth. . Since the CDN system will provide acceleration services for multiple domain names at the same time, when the bandwidth rate limit policy is triggered, the CDN system will identify the domain name with higher bandwidth among all the domain names it serves, that is, determine the target domain name to be rate limited, and Implement the bandwidth speed limit strategy for the target domain name to limit the access bandwidth of the target domain name.
  • the edge node server in the CDN system when the user accesses the target domain name, the edge node server that provides services for the target domain name has cached the content requested by the user, and the edge node server will directly return to the user The content of the request. If the amount of content data requested by the user is large, for example, the user needs to update the game version, download the video, etc., a larger edge bandwidth will be generated at this time, and the edge node server will also bear greater access pressure. At this time, the CDN system will enable the network bandwidth reserved by the edge node and the computing power reserved in the edge node server according to the preset redundant resource usage strategy to improve the service capacity of the edge node. The CDN system also calculates the performance indicators of edge node servers.
  • the above performance indicators include but are not limited to delay rate, stall rate, download speed, open speed, return to source rate, etc.
  • the CDN system will determine that the reserved network bandwidth and computing power cannot meet the user's access needs, and the CDN system will trigger the bandwidth rate limit strategy for the target domain name.
  • the transit node server in the CDN system when a user accesses the target domain name, there is neither an edge node server that provides services for the target domain name nor a transit node server that provides services for the foregoing edge node server.
  • the content requested by the user is cached, and the transit node server will issue an access request to the origin site. If the amount of content data requested by the user is large, for example, the user needs to update the game version, video download, etc., a large return-to-origin bandwidth will be generated at this time, and the transit node server and the origin site will also be under greater pressure.
  • the CDN system will call more network bandwidth and servers from the resource pool or backup pool according to the preset DNS scheduling strategy to improve the service capability of the transit node.
  • the transit node server is at the center of the entire network and converges the return-to-origin requests of each edge node server. If the load of the transit node server is too large, the CDN system directly limits the performance of the transit node server, which will result in a decline in the performance of the entire CDN system and seriously affect the acceleration service of the system. Therefore, when the load of the transit node server is too large, the CDN The system will not adjust the working status of the transit node server.
  • the CDN system Only when the load of the transit node server reaches a certain threshold and an alarm message is issued, the CDN system will adjust the working status of the transit node server. After the CDN system determines that the transit node server generates alarm information, the CDN system will trigger the bandwidth rate limit strategy for the target domain name.
  • the CDN system can also preset the alarm elimination strategy.
  • the CDN system determines that the relay node server generates alarm information, it automatically reduces the load of the relay node server to a safe level, and the relay node server eliminates the alarm information. After that, the bandwidth speed limit strategy is triggered on the target domain name to further improve the stability of the CDN system.
  • the relay node server after the relay node server sends out the alarm information, it can also be processed by manual intervention. For example, the operator can directly reduce the return-to-origin bandwidth of the target domain name on the relay node server, or directly reduce the service of the relay node server For the return-to-source bandwidth of all domain names, the operator can also determine whether the alarm information is a false alarm. If it is a false alarm, the operator can directly cancel the bandwidth rate limit policy of the target domain name.
  • the actual bandwidth value of the target domain name in the entire CDN system can be set when the bandwidth rate limit strategy is triggered.
  • the initial reference bandwidth can also be set to be less than the actual bandwidth value of the target domain name in the entire CDN system when the bandwidth rate limit policy is triggered, which is not limited in this application.
  • the CDN system After setting the initial reference bandwidth, the CDN system will compare the actual bandwidth of the target domain name in the entire CDN system with the size of the initial reference bandwidth in real time within the specified observation period, and determine whether the initial reference bandwidth of the target domain name is adjusted according to preset conditions. Refer to the bandwidth for step adjustment, and determine whether to lift the bandwidth rate limit strategy of the target domain name.
  • the above-mentioned designated observation time can be set according to empirical values, for example, set to 30 minutes.
  • the starting point of the above-mentioned designated observation time can be set to the time point when the CDN system triggers the bandwidth speed limit strategy, or it can be set to At any time after the CDN system triggers the bandwidth rate limit strategy, this application does not restrict it.
  • the initial reference bandwidth is denoted as C0 below.
  • the CDN system judging whether to adjust the initial reference bandwidth stepwise includes the following steps:
  • S201 Determine a proportional reference bandwidth according to the initial reference bandwidth and a preset proportional coefficient.
  • the preset scale factor can be set using empirical values, for example, the preset scale factor is set to 0.8, and the corresponding proportional reference bandwidth is set to 0.8C0.
  • the application does not limit the setting of the preset scale factor.
  • S202 Record the time node when the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth for the first time, and starting from the recorded time node, determine that the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth Whether the duration reaches the preset reference duration.
  • the CDN system will record the actual bandwidth of the target domain name in the entire CDN system in real time, and compare the actual bandwidth with the above proportional reference bandwidth in real time. When the actual bandwidth is less than or equal to the proportional reference bandwidth for the first time, the CDN system will record this moment From this point in time, it is determined whether the actual bandwidth of the target domain name is less than or equal to the duration of the proportional reference bandwidth and reaches the preset reference duration.
  • the above-mentioned preset reference time can be set according to empirical values, for example, the preset reference time is set to 5 minutes. This application does not limit the specific value of the preset reference time, but the preset reference time must Less than the specified observation time.
  • the CDN system will adjust the initial reference bandwidth of the target domain name in steps.
  • the CDN system will again record the actual bandwidth of the target domain name from the moment when the actual bandwidth of the target domain name is greater than the proportional reference bandwidth
  • the following example illustrates how the CDN system determines whether to adjust the initial reference bandwidth of the target domain name in steps.
  • the time node is 11:02, and the preset reference duration is 5 minutes.
  • the CDN system will use 11:02 as the time node and judge 11: During the period from 02 to 11:07, whether the actual bandwidth of the target domain name has been less than or equal to 0.8C0.
  • the CDN system will determine that the actual bandwidth of the target domain name is less than or equal to 0.8C0 and the duration reaches the preset reference time. The system will adjust the initial reference bandwidth (ie C0) of the target domain name step by step.
  • the CDN system will determine the target domain name.
  • the actual bandwidth is less than or equal to 0.8C0 and the duration is less than the preset reference duration.
  • the CDN system will maintain the initial reference bandwidth of the target domain name unchanged, continue to limit the target domain name, and set the time reset point at 11:04. Re-compare the relationship between the actual bandwidth of the target domain name and 0.8C0 after 11:04 in real time.
  • the CDN system will take 11:12 as the new time node and judge During the period from 11:12 to 11:17, is the actual bandwidth of the target domain name always less than or equal to 0.8C0. If during the period from 11:12 to 11:17, the actual bandwidth of the CDN target domain name is always less than or equal to 0.8C0, the CDN system will determine that the actual bandwidth of the target domain name is less than or equal to 0.8C0 and the duration reaches the preset reference time. The CDN system will adjust the initial reference bandwidth of the target domain name step by step.
  • the CDN system will determine that the actual bandwidth of the target domain name is less than or equal to 0.8C0 and the duration is less than the expected duration. Set the reference duration, the CDN system will maintain the initial reference bandwidth of the target domain name unchanged, continue to limit the target domain name, and use the moment when the actual bandwidth bursts again as the time reset point to repeat the above judgment process.
  • the CDN system when the actual bandwidth of the target domain name is less than or equal to 0.8C0 and the duration reaches the preset reference duration, the CDN system will perform a step adjustment on the initial reference bandwidth of the target domain name, and perform step adjustment on the initial reference bandwidth It includes the following steps:
  • S301 Determine the adjusted step reference bandwidth according to the initial reference bandwidth and the preset amplification coefficient, and record the time node when the bandwidth is adjusted.
  • the preset amplification factor can be set using empirical values, for example, the preset amplification factor is set to 1.1, and the corresponding step reference bandwidth after the first adjustment of the initial reference bandwidth will be 1.1C0,
  • the CDN system will also record the time node when the initial reference bandwidth was adjusted for the first time. It needs to be pointed out that every time the CDN system determines a new step reference bandwidth, the CDN system will synchronously record the time node when the bandwidth is adjusted.
  • S302 Starting from the time node when the bandwidth is adjusted, determine whether the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth and the duration reaches the preset reference duration.
  • the CDN system will record the actual bandwidth of the target domain name in real time, and start from the time node when the bandwidth is adjusted as recorded above, compare the actual bandwidth of the target domain name and the proportional reference bandwidth in real time, and determine the target Whether the actual bandwidth of the domain name is less than or equal to the aforementioned proportional reference bandwidth and the duration reaches the preset reference duration.
  • the CDN system will perform the initial reference bandwidth of the target domain name again according to the preset amplification coefficient of the stepped reference bandwidth. Adjustment means determining the new tiered reference bandwidth of the target domain name, and the CDN system will also record the time node when the initial reference bandwidth of the target domain name is adjusted again. It needs to be pointed out that every time the CDN system determines a new step reference bandwidth, the CDN system will synchronously record the time node when the bandwidth is adjusted.
  • the CDN system will record the time from the moment when the actual bandwidth of the target domain name is greater than the proportional reference bandwidth The actual bandwidth of the target domain name is less than or equal to the time node when the proportional reference bandwidth for the first time, and starting from the time node recorded again, it is determined whether the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth for the duration The preset reference duration.
  • the following example illustrates how the CDN system adjusts the initial reference bandwidth of the target domain name step by step.
  • the preset scaling factor is set to 0.8
  • the preset amplification factor is set to 1.1
  • the preset reference duration is 5 minutes.
  • the time node when the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth (ie 0.8C0) is 15 :00
  • the actual bandwidth of the target domain name is always less than or equal to 0.8C0
  • the CDN system judges that the actual bandwidth of the target domain name is less than or equal to 0.8C0 and the duration reaches the preset reference duration.
  • the CDN system will adjust the initial reference bandwidth (i.e. C0) of the target domain name step by step, and adjust the stepped reference bandwidth after the first adjustment to 1.1C0, and record the initial reference bandwidth for the first time adjustment. Time node (ie 15:05).
  • the CDN system will start at 15:05, compare the actual bandwidth of the target domain name after 15:05 and the size of 0.8C0 in real time, and judge whether the actual bandwidth of the target domain name has been less than 15:05 to 15:10. Or equal to 0.8C0.
  • the CDN system will determine that the actual bandwidth of the target domain name is less than or equal to 0.8C0 and the duration reaches the preset reference time length.
  • the system will adjust the initial reference bandwidth of the target domain name for the second time based on the first adjusted step reference bandwidth (i.e. 1.1C0) according to the above-mentioned preset increase coefficient, and refer to the second adjusted step reference bandwidth
  • the bandwidth is adjusted to 1.1*1.1C0 (that is, 1.21C0), that is, the new step reference bandwidth is determined, and the CDN system will also record the time node of the second bandwidth adjustment (that is, 15:10).
  • the step reference bandwidth after the second adjustment is greater than the step reference bandwidth after the first adjustment.
  • the CDN system further increases the available bandwidth of the target domain name in the entire CDN system, and the user's access experience of the target domain name will be further improved.
  • the CDN system will determine the target domain name The actual bandwidth is less than or equal to 0.8C0 and the duration is less than the preset reference duration. At this time, the CDN system will maintain the first adjusted step reference bandwidth unchanged (ie 1.1C0), continue to limit the target domain name rate, and set the rate at 15 :06 is the time reset point. Re-compare the relationship between the actual bandwidth of the target domain name and 0.8C0 after 15:06 in real time.
  • the CDN system will be 15:22 For the new time node, determine whether the actual bandwidth of the target domain name has been less than or equal to 0.8C0 during the period from 15:22 to 15:27. If during the period from 15:22 to 15:27, the actual bandwidth of the CDN target domain name is always less than or equal to 0.8C0, the CDN system will determine that the actual bandwidth of the target domain name is less than or equal to 0.8C0 and the duration reaches the preset reference time. The CDN system will adjust the initial reference bandwidth of the target domain name for the second time.
  • the CDN system will determine that the actual bandwidth of the target domain name is less than or equal to 0.8C0 and the duration is less than the expected duration. Set the reference duration. At this time, the CDN system will maintain the first adjusted step reference bandwidth unchanged (ie 1.1C0), continue to limit the target domain name, and use the moment when the actual bandwidth bursts again as the time reset point , Repeat the above judgment process.
  • step S302 will be repeated to further increase the available bandwidth of the target domain name in the entire CDN system, and gradually improve the user's access experience of the target domain name.
  • the CDN system after the CDN system performs a step adjustment on the initial reference bandwidth of the target domain name, it further includes the step of determining whether to release the bandwidth rate limit strategy, which specifically includes the following steps:
  • S401 Determine whether the actual bandwidth of the target domain name is less than or equal to the initial reference bandwidth for the duration of the specified observation period.
  • the CDN system When the CDN system triggers the bandwidth rate limit policy, the CDN system will start from the time when the bandwidth rate limit policy is triggered, and determine whether the actual bandwidth of the target domain name has been less than the specified observation time during this period. Or equal to the initial reference bandwidth.
  • the CDN system will determine that the actual bandwidth of the target domain name is less than or equal to the initial reference bandwidth and the duration of the specified observation period is reached.
  • the access demand has dropped, the bandwidth of the target domain name will not rise again, and the CDN system will lift the bandwidth rate limit strategy of the target domain name.
  • the CDN system will reset the step-adjusted reference bandwidth to the initial reference bandwidth, and re-calculate the initial reference bandwidth and the initial reference bandwidth within the specified observation duration.
  • the actual bandwidth of the target domain name is compared to determine whether to perform step adjustment on the initial reference bandwidth, and to determine whether to release the bandwidth rate limit strategy.
  • the following example illustrates how the CDN system determines whether to lift the bandwidth rate limit strategy of the target domain name.
  • the CDN system will compare the actual bandwidth of the target domain name from 12:08 to 12:38 with the initial reference bandwidth (That is, the size of C0).
  • the CDN system will determine that the actual bandwidth of the target domain name is less than or equal to C0 and the duration reaches the specified observation time.
  • the access demand of the target domain name has dropped, the bandwidth of the target domain name will not increase again, and the CDN system will lift the bandwidth rate limit strategy of the target domain name.
  • the CDN system will determine the target The actual bandwidth of the domain name is less than or equal to C0 and the duration is less than the specified observation time. The user's demand for access to the target domain name is still large, and the bandwidth of the target domain name may increase again. At this time, the CDN system will continue to implement the bandwidth rate limit strategy for the target domain name, and reset the adjusted step reference bandwidth of the target domain name to the initial reference bandwidth (ie C0), and use the actual bandwidth to burst at the moment (ie 12:30) ) Is the time reset point.
  • the bandwidth rate limit policy further includes determining the bandwidth limit value of the target domain name on each target cache server , And sending the bandwidth limit value to the corresponding target cache server.
  • the edge node server or transit node server that will provide acceleration services for the target domain name is called the target cache server Obviously, the available bandwidth of the target domain name in the entire CDN system is reflected by the available bandwidth of the target cache server in the entire CDN system. When the available bandwidth of the target cache server in the entire CDN system increases, it is reflected as the target domain name The available bandwidth in the entire CDN system increases.
  • the CDN system will count all target cache servers and calculate the initial bandwidth limit value of the target domain name on each target cache server based on the total preset bandwidth limit and the bandwidth ratio corresponding to the current target cache server, and calculate the initial bandwidth
  • the limit value is sent to the corresponding target cache server.
  • the CDN system After the CDN system adjusts the initial reference bandwidth of the target domain name in steps, the CDN system will readjust the total bandwidth limit of the target domain name according to the adjusted step reference bandwidth, and determine the target domain name in each target cache server according to the above bandwidth ratio The upper step bandwidth limit value.
  • the CDN system gradually increases the available bandwidth of the target cache server in the entire CDN system through the above-mentioned ladder bandwidth limit value, so as to improve the user's access experience of the target domain name.
  • the CDN system can count the actual bandwidth of the target domain name on each target cache server when triggering the bandwidth rate limit strategy of the target domain name, and calculate the ratio of the actual bandwidth among the target cache servers to determine The bandwidth ratio corresponding to the current target cache server.
  • the CDN system can set the total preset bandwidth limit according to the initial reference bandwidth.
  • the specific value of the preset total bandwidth limit can be set based on empirical values, but the total preset bandwidth limit must be less than or Equal to the initial reference bandwidth.
  • the CDN system can also set a preset total bandwidth limit according to the performance indicators of the origin site. For example, the maximum return-to-origin bandwidth that the origin site can bear is 10M, and the CDN system can Set the total preset bandwidth limit to 10M. Since a transit node server may provide acceleration services for multiple domain names at the same time, it may happen that the maximum return-to-source bandwidth that the origin site can withstand is greater than the initial reference bandwidth set by the CDN system. At this time, the total bandwidth limit is preset The initial reference bandwidth should be used as the reference standard for setting.
  • the adjustment coefficient of the total bandwidth limit value may refer to the preset amplification coefficient, or may be set according to an empirical value, which is not limited in this application.
  • the edge node servers in the entire CDN network that provide acceleration services for the target domain name, which are recorded as target cache server A and target cache server B, respectively.
  • the actual bandwidth of the target domain name on target cache server A is 20M
  • the actual bandwidth of the target domain name on target cache server B is 30M
  • the initial reference bandwidth is set to 50M
  • the target The bandwidth ratio corresponding to cache server A is 2/5
  • the bandwidth ratio corresponding to target cache server B is 3/5.
  • the preset bandwidth limit is set to 40M
  • the initial bandwidth limit value of the target domain name on target cache server A It is 16M
  • the initial bandwidth limit value of the target domain name on the target cache server B is 24M.
  • the adjustment coefficient of the total bandwidth limit is the preset increase coefficient.
  • the stepped reference bandwidth after the first adjustment is 55M, and the total bandwidth limit value of the corresponding target domain name will be adjusted at this time Is 44M, the tiered bandwidth limit value of the target domain name on the target cache server A will be adjusted to 17.6M, and the tiered bandwidth limit value of the target domain name on the target cache server B will be adjusted to 26.4M.
  • the CDN system can also calculate the bandwidth of each process in the target cache server according to the bandwidth limit value of the target cache server and the bandwidth ratio corresponding to the current process. Bandwidth limit value. After the bandwidth limit value of the target cache server is adjusted, the bandwidth limit value of each process mentioned above is adjusted accordingly.
  • this application also provides a domain name bandwidth adjustment device, which is applied in a CDN system, and the domain name bandwidth adjustment device includes:
  • a speed limit judging unit for judging whether the CDN system triggers a bandwidth speed limit strategy, and whether to cancel the bandwidth speed limit strategy
  • the domain name identification unit is configured to determine the target domain name to be rate limited among the domain names served by the CDN system after the bandwidth rate limiting policy is triggered;
  • the bandwidth adjustment unit is configured to determine the initial reference bandwidth of the target domain name, and compare the initial reference bandwidth with the actual bandwidth of the target domain name within a specified observation period, to determine whether to perform the initial reference bandwidth Step adjustment.
  • the judging rate limiting unit further includes:
  • the performance index calculation module is configured to calculate the performance index of the edge node server, and when the performance index is lower than a preset index threshold, trigger the bandwidth rate limit strategy.
  • the judging rate limiting unit further includes:
  • the alarm information judging module is used to judge whether the transit node server generates alarm information, and if so, trigger the bandwidth rate limit strategy.
  • the bandwidth adjustment unit determining whether to perform step adjustment on the initial reference bandwidth includes:
  • the duration is less than the preset reference duration, starting from the moment when the actual bandwidth of the target domain name is greater than the proportional reference bandwidth, record again that the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth for the first time Starting from the time node recorded again, determine whether the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth and the duration reaches the preset reference duration.
  • the rate limit determination unit determining whether to release the bandwidth rate limit strategy includes:
  • the bandwidth speed limit strategy is released
  • the duration is less than the specified observation duration, reset the step-adjusted reference bandwidth to the initial reference bandwidth, and re-calculate the initial reference bandwidth and the target domain name within the specified observation duration To compare the actual bandwidths to determine whether to perform step adjustment on the initial reference bandwidth, and to determine whether to release the bandwidth rate limit strategy.
  • the bandwidth adjustment unit includes:
  • a step bandwidth calculation module configured to determine an adjusted step reference bandwidth according to the initial reference bandwidth and a preset amplification coefficient, and determine a new step reference bandwidth according to the step reference bandwidth and the preset amplification coefficient, and Synchronously record the time node when the bandwidth is adjusted;
  • the step adjustment judgment module is used for judging whether the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth, starting from the time node when the bandwidth is adjusted, reaches the preset reference duration.
  • the step adjustment judgment module determines that the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth and the duration reaches the preset reference time length.
  • the bandwidth calculation module will determine a new step reference bandwidth according to the step reference bandwidth and the preset amplification coefficient, and record the time node when the bandwidth is adjusted.
  • the step adjustment determining module determines that the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth and the duration is less than the preset reference duration, and the bandwidth
  • the adjustment unit will re-record the time node when the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth for the first time from the moment when the actual bandwidth of the target domain name is greater than the proportional reference bandwidth, and start from the time when the time is again recorded.
  • the node starts to determine whether the actual bandwidth of the target domain name is less than or equal to the proportional reference bandwidth and the duration reaches the preset reference duration.
  • the domain name bandwidth adjustment device further includes:
  • the target cache server control unit is used to determine the bandwidth limit value of the target domain name on each target cache server, and send the bandwidth limit value to the corresponding target cache server.
  • the target cache server control unit includes:
  • An initial bandwidth limit value calculation module configured to determine the initial bandwidth limit value of the target domain name on the current target cache server according to the preset total bandwidth limit value and the bandwidth ratio corresponding to the current target cache server;
  • the stepped bandwidth limit value calculation module is configured to, after stepwise adjustment of the initial reference bandwidth, determine that the target domain name is in the current target domain name according to the adjusted reference bandwidth and the bandwidth ratio corresponding to the current target cache server Tiered bandwidth limit value on the target cache server.
  • the domain name bandwidth adjustment device includes a memory and a processor.
  • the memory is used to store a computer program, and the computer program is When the processor executes, it can implement the domain name bandwidth adjustment method as described above.
  • the domain name bandwidth adjustment device may include a processor, an internal bus, and a memory.
  • the memory may include memory and non-volatile memory.
  • the processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it.
  • the domain name bandwidth adjustment device may also include more or fewer components than shown in FIG. 6, for example, may also include other processing hardware, such as GPU (Graphics Processing Unit, image processor), or external communication port , Such as port 80, port 443, port 8080, etc.
  • processing hardware such as GPU (Graphics Processing Unit, image processor), or external communication port , Such as port 80, port 443, port 8080, etc.
  • this application does not exclude other implementations, such as logic devices or a combination of software and hardware.
  • the processor may include a central processing unit (CPU) or a graphics processing unit (GPU), of course, may also include other single-chip microcomputers, logic gate circuits, integrated circuits, etc. with logic processing capabilities, or appropriate combination.
  • the memory described in this embodiment may be a memory device for storing information.
  • the device that can store binary data can be a memory; in an integrated circuit, a circuit with storage function that has no physical form can also be a memory, such as RAM, FIFO, etc.; in the system, it has physical storage
  • the device can also be called a memory and so on.
  • the memory can also be implemented in the form of cloud storage, and the specific implementation manner is not limited in this specification.
  • the CDN system can automatically determine whether to trigger the bandwidth rate limit strategy according to the load situation of the edge node server or the transit node server, and when the bandwidth rate limit policy is triggered, the edge node server or Determine the target domain name that needs to be rate-limited in the domain name served by the transit node server, and then limit the edge bandwidth or return-to-origin bandwidth of the target domain name according to the set initial reference bandwidth. If the actual bandwidth of the target domain name is less than or equal to the initial reference bandwidth and the duration reaches the preset reference duration, the CDN system will adjust the initial reference bandwidth of the target domain name step by step, and gradually increase the target domain name throughout the entire reference bandwidth according to the adjusted reference bandwidth.
  • the available bandwidth in the CDN system to improve the user's access experience to the target domain name When the actual bandwidth of the target domain name is less than or equal to the initial reference bandwidth and the duration of the specified observation period is reached, the CDN system will lift the bandwidth rate limit strategy and completely release the bandwidth limit on the target domain name. It can be seen that the technical solution provided by this application can gradually restore the acceleration effect of the CDN system on the target domain name through the bandwidth step adjustment and speed limit observation of the target domain name, which not only improves the user experience of accessing the target domain name, but also avoids direct Releasing the bandwidth limit causes the edge bandwidth or return-to-origin bandwidth of the target domain name to increase again.
  • each implementation manner can be implemented by software plus a necessary general hardware platform, and of course, it can also be implemented by hardware.
  • the above technical solutions can be embodied in the form of software products, which can be stored in computer-readable storage media, such as ROM/RAM, magnetic A disc, an optical disc, etc., include a number of instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute the methods described in each embodiment or some parts of the embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种域名带宽调整方法及装置，其中，所述方法包括：判断所述CDN系统是否触发带宽限速策略，若触发，则在所述CDN系统服务的域名中，确定待限速的目标域名，并对所述目标域名执行所述带宽限速策略(101)；在所述带宽限速策略执行时，确定所述目标域名的初始参考带宽，并在指定观察时长内，对所述初始参考带宽和所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带宽进行阶梯调整，以及判断是否解除所述带宽限速策略(102)。本申请提供的技术方案，能够有效控制目标域名的带宽，并可以避免目标域名的带宽再次走高。

Description

一种域名带宽调整方法及装置
交叉引用
本申请引用于2019年04月12日递交的名称为“一种域名带宽调整方法及装置”的第201910293699.8号中国专利申请，其通过引用被全部并入本申请。
技术领域
本申请涉及互联网技术领域，特别涉及一种域名带宽调整方法及装置。
背景技术
随着互联网的发展，CDN(Content Delivery Network，即内容分发网络)系统被越来越多地部署在网络中，用于提高人们访问网站的速度。随着网络中数据流量的激增，特别是针对游戏类、视频类网站，这些网站在进行数据更新时，往往会产生较大的边缘带宽和回源带宽，边缘带宽的持续走高会降低用户访问CDN系统中其它网站的速度，而回源带宽的持续走高则会增加CDN系统中源站的压力，容易引起整个CDN系统的不稳定。
针对上述问题，现有的CDN系统可以根据GPC(Global Protection Control，即全局防护控制系统)对边缘带宽或者回源带宽进行限速，但是在限速状态下，CDN系统容易产生误判，即在边缘带宽或者回源带宽降低时，CDN系统会直接放开对边缘带宽或者回源带宽的限速，容易导致边缘带宽或者回源带宽再次走高。
鉴于此，有必要提供一种新的域名带宽调整方法及装置以解决上述不足。
发明内容
本申请的目的在于提供一种域名带宽调整方法及装置，能够避免直接放开带宽限制，导致目标域名的边缘带宽或者回源带宽再次走高的问题。
为实现上述目的，本申请一方面提供一种域名带宽调整方法，应用于CDN系统中，所述方法包括：判断所述CDN系统是否触发带宽限速策略，若触发，则在所述CDN系统服务的域名中，确定待限速的目标域名，并对所述目标域名执行所述带宽限速策略；在所述带宽限速策略执行时，确定所述目标域名的初始参考带宽，并在指定观察时长内，对所述初始参考带宽和所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带宽进行阶梯调整，以及判断是否解除所述带宽限速策略。
为实现上述目的，本申请另一方面还提供一种域名带宽调整装置，应用于CDN系统中，所述域名带宽调整装置包括限速判断单元，用于判断所述CDN系统是否触发带宽限速策略，以及判断是否解除所述带宽限速策略；域名识别单元，用于在触发所述带宽限速策略后，在所述CDN系统服务的域名中，确定待限速的目标域名；带宽调整单元，用于确定所述目标域名的初始参考带宽，并在指定观察时长内，对所述初始参考带宽和所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带宽进行阶梯调整。
由此可见，本申请提供的技术方案，CDN系统可以根据边缘节点服务器或者中转节点服务器的负载情况，自动判断是否触发带宽限速策略，并在触发带宽限速策略时，自动在边缘节点服务器或者中转节点服务器服务的域名中确定需要进行限速的目标域名，然后根据设定的初始参考带宽对目标域名的边缘带宽或者回源带宽进行限速。如果目标域名的实际带宽小于或者等于初始参考带宽的持续时间达到预设参考时长，CDN系统将会对目标域名的初始参考带宽进行阶梯调整，并根据调整后的参考带宽，逐步增加目标域名在整个CDN系统中的可用带宽，以提高用户对目标域名的访问体验。当目标域名的实际带宽小于或者等于初始参考带宽的持续时间达到指定观察时长时，CDN系统会解除带宽限速策略，彻底放开对目标域名的带宽限制。由此可见，本申请提供的技术方案，通过对目标域名进行带宽阶梯调整和限速观察，可以逐步恢复CDN系统对目标 域名的加速效果，既提高了用户访问目标域名的体验，又可以避免直接放开带宽限制，导致目标域名的边缘带宽或者回源带宽再次走高。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施方式中域名带宽调整方法的流程图；
图2是本申请实施方式中判断是否对初始参考带宽进行阶梯调整的流程图；
图3是本申请实施方式中对初始参考带宽进行阶梯调整的流程图；
图4是本申请实施方式中判断是否解除带宽限速策略的流程图；
图5是本申请实施方式中域名带宽调整装置的功能模块示意图；
图6是本申请实施方式中域名带宽调整装置的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
节点是CDN系统中最基本的部署单元，每个节点都是由缓存服务器集群组成。CDN系统设计的首要目标是尽量减少用户的访问响应时间，为达到这一目标，CDN系统会尽量将用户所需要的内容存放在距离用户最近的位置，也就是说，负责为用户提供内容服务的缓存服务器应部署在物理上的网络边缘位置，上述网络边缘位置可以称为边缘节点，部署在边缘节点的缓存服务器可以称为边缘节点服务器。同时，CDN系统中负责全局性管理和控制的设备组成中心节点，中心节点不仅能对整个CDN网络中的各个子系统和设备进行实时监控，对各种故障产生相应的告警，还可以实时监测到系统中总的流量和各边缘节点的流量， 在本申请中，将部署在中心节点的缓存服务器称为中转节点服务器。中转节点服务器保存着最完善的内容副本，当边缘节点服务器未缓存用户访问的内容时，边缘节点服务器会向中转节点服务器发送请求，如果中转节点服务器仍未缓存用户访问的内容，则需要中转节点服务器向源站回源，如果中转节点服务器故障或者服务能力不足，则需要边缘节点服务器直接向源站回源。在本申请中，将用户与边缘节点服务器之间交换数据产生的网络带宽称为边缘带宽，将中转节点服务器与源站之间交换数据产生的网络带宽称为回源带宽。
请一并参阅图1至图4，本申请提供的一种域名带宽调整方法，可以包括以下步骤。
S101：判断CDN系统是否触发带宽限速策略，若触发，则在所述CDN系统服务的域名中，确定待限速的目标域名，并对所述目标域名执行所述带宽限速策略。
在本实施方式中，CDN系统将根据缓存服务器的负载情况、整个网络带宽的负载情况，判断是否触发带宽限速策略。缓存服务器或者网络带宽负载过大，将导致整个CDN系统工作不稳定，影响CDN系统对外提供服务，所以CDN系统会触发带宽限速策略，对网络带宽进行限制，以降低缓存服务器和网络带宽的负载。由于CDN系统会同时为多个域名提供加速服务，所以在触发带宽限速策略时，CDN系统会在所服务的所有域名中识别出带宽跑高的域名，即确定待限速的目标域名，并对目标域名执行带宽限速策略，限制目标域名的访问带宽。
在一个实施方式中，针对所述CDN系统中的边缘节点服务器，当用户访问目标域名时，为目标域名提供服务的边缘节点服务器中已经缓存了用户请求的内容，边缘节点服务器将直接向用户返回请求的内容。如果用户请求的内容数据量较大，例如用户需要进行游戏版本更新、视频下载等，此时会产生较大的边缘带宽，边缘节点服务器也会承受较大的访问压力。此时CDN系统会根据预先设置的冗余资源使用策略，启用边缘节点预留的网络带宽及边缘节点服务器中预留的计算能力，以提高边缘节点的服务能力。CDN系统同时会计算边缘节点服务器的性能指标，上述性能指标包括但不限于延时率、卡顿率、下载速度、 打开速度、回源率等，当上述性能指标低于预设指标阈值时，CDN系统将判断预留的网络带宽及计算能力不能满足用户的访问需求，CDN系统将对目标域名触发带宽限速策略。
在另一个实施方式中，针对所述CDN系统中的中转节点服务器，当用户访问目标域名时，为目标域名提供服务的边缘节点服务器，以及为上述边缘节点服务器提供服务的中转节点服务器中都没有缓存用户请求的内容，中转节点服务器将会向源站发出访问请求。如果用户请求的内容数据量较大，例如用户需要进行游戏版本更新、视频下载等，此时会产生较大的回源带宽，中转节点服务器和源站也会承受较大的压力。此时CDN系统会根据预先设置的DNS调度策略，从资源池或者备用池中调用更多的网络带宽和服务器，以提高中转节点的服务能力。在CDN系统中，中转节点服务器处于整个网络的中心位置，对各个边缘节点服务器的回源请求进行收敛。如果在中转节点服务器负载过大时，CDN系统直接对中转节点服务器的性能进行限制，将会导致整个CDN系统性能的下降，严重影响系统的加速服务，所以在中转节点服务器负载过大时，CDN系统不会对中转节点服务器的工作状态进行调整，只有在中转节点服务器的负载达到一定阈值，发出告警信息后，CDN系统才会对中转节点服务器的工作状态进行调整。当CDN系统判断所述中转节点服务器产生告警信息后，CDN系统将对目标域名触发带宽限速策略。
在本实施方式中，在CDN系统中还可以预设消警策略，当CDN系统判断所述中转节点服务器产生告警信息后，自动降低中转节点服务器的负载至安全水平，待中转节点服务器消除告警信息后，再对目标域名触发带宽限速策略，以进一步提高CDN系统的稳定性。
在本实施方式中，当中转节点服务器发出告警信息后，还可以采取人工介入的方式进行处理，例如操作员可以直接降低目标域名在中转节点服务器上的回源带宽，或者直接降低中转节点服务器服务的所有域名的回源带宽，操作员还可以判断告警信息是否为误报，如果是误报，操作员可以直接解除目标域名的带宽限速策略。
S102：在所述带宽限速策略执行时，确定所述目标域名的初始参考带宽，并在指定观察时长内，对所述初始参考带宽和所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带宽进行阶梯调整，以及判断是否解除所述带宽限速策略。
由于CDN系统可以实时监测到目标域名在整个系统中的流量和各边缘节点的流量，所以在本实施方式中，可以将触发带宽限速策略时，目标域名在整个CDN系统中的实际带宽值设定为初始参考带宽，并将上述初始参考带宽设定为目标域名在整个CDN系统中的可用带宽，以避免目标域名的网络带宽无限跑高，影响CDN系统对其它域名的服务质量。需要特别指出的是，也可以将初始参考带宽设定为小于触发带宽限速策略时目标域名在整个CDN系统中的实际带宽值，本申请对此不作限制。
在设定初始参考带宽后，CDN系统将在指定观察时长内，实时比较目标域名在整个CDN系统中的的实际带宽和初始参考带宽的大小，并根据预设的条件判断是否对目标域名的初始参考带宽进行阶梯调整，以及判断是否解除目标域名的带宽限速策略。需要特别指出的是，上述指定观察时长可以根据经验值进行设定，例如设定为30分钟，上述指定观察时长的起点可以设置为CDN系统触发带宽限速策略时的时间点，也可以设置为CDN系统触发带宽限速策略之后任一时间点，本申请对此不作限制。
为便于叙述，下文将初始参考带宽记为C0。
在本实施方式中，CDN系统判断是否对初始参考带宽进行阶梯调整包括以下步骤：
S201：根据所述初始参考带宽和预设比例系数，确定比例参考带宽。
预设比例系数的设定可以采用经验值，例如将预设比例系数设定为0.8，相应的比例参考带宽设定为0.8C0，本申请对预设比例系数的设定不作限制。
S202：记录所述目标域名的实际带宽首次小于或者等于所述比例参考带宽时的时间节点，并从记录的所述时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到预设参考时长。
CDN系统将实时记录目标域名在整个CDN系统中的实际带宽，并实时比较上述实际带宽与上述比例参考带宽的大小关系，当首次出现实际带宽小于或者等于比例参考带宽时，CDN系统将记录下此刻的时间点，并从该时间点开始，判断目标域名的实际带宽小于或者等于比例参考带宽的持续时间是否达到预设参考时长。
需要特别指出的是，上述预设参考时长可以根据经验值进行设定，例如将预设参考时长设定为5分钟，本申请对预设参考时长的具体数值不作限制，但是预设参考时长必须小于指定观察时长。
S203：若所述持续时间达到所述预设参考时长，则对所述初始参考带宽进行阶梯调整。
如果目标域名的实际带宽小于或者等于比例参考带宽的持续时间达到预设参考时长，CDN系统将对目标域名的初始参考带宽进行阶梯调整。
如果目标域名的实际带宽小于或者等于比例参考带宽的持续时间小于所述预设参考时长，CDN系统将从所述目标域名的实际带宽大于比例参考带宽的时刻起，再次记录所述目标域名的实际带宽首次小于或者等于比例参考带宽时的时间节点，并从再次记录的时间节点开始，判断所述目标域名的实际带宽小于或者等于比例参考带宽的持续时间是否达到所述预设参考时长。
下面举例说明CDN系统如何判断是否对目标域名的初始参考带宽进行阶梯调整。
假设目标域名首次出现实际带宽小于或者等于比例参考带宽(假设为0.8C0)的时间节点为11:02，预设参考时长为5分钟，CDN系统将会以11:02为时间节点，判断11:02至11:07这段时长内，目标域名的实际带宽是否一直小于或者等于0.8C0。
如果在11:02至11:07这段时长内，目标域名的实际带宽一直小于或者等于0.8C0，CDN系统将判断目标域名的实际带宽小于或者等于0.8C0的持续时间达到预设参考时长，CDN系统将会对目标域名的初始参考带宽(即C0)进行阶梯调整。
如果在11:02至11:07这段时长内，目标域名的实际带宽出现突发，例如在11:04目标域名的实际带宽出现突发，实际带宽大于0.8C0，CDN系统将判断目标域名的实际带宽小于或者等于0.8C0的持续时间小于预设参考时长，此时CDN系统会维持目标域名的初始参考带宽不变，继续对目标域名进行限速，并以11:04为时间重置点，重新实时比较11:04之后目标域名的实际带宽与0.8C0的大小关系，假设在11:12再次出现实际带宽小于或者等于0.8C0，CDN系统将会以11:12为新的时间节点，并判断11:12至11:17这段时长内，目标域名的实际带宽是否一直小于或者等于0.8C0。如果在11:12至11:17这段时长内，CDN目标域名的实际带宽一直小于或者等于0.8C0，CDN系统将判断目标域名的实际带宽小于或者等于0.8C0的持续时间达到预设参考时长，CDN系统将会对目标域名的初始参考带宽进行阶梯调整。如果在11:12至11:17这段时长内，目标域名的实际带宽再次出现突发，导致实际带宽大于0.8C0，CDN系统将判断目标域名的实际带宽小于或者等于0.8C0的持续时间小于预设参考时长，CDN系统会维持目标域名的初始参考带宽不变，继续对目标域名进行限速，并以实际带宽再次出现突发的时刻为时间重置点，重复进行上述判断过程。
在本实施方式中，当目标域名的实际带宽小于或者等于0.8C0的持续时间达到预设参考时长，CDN系统将会对目标域名的初始参考带宽进行阶梯调整，对所述初始参考带宽进行阶梯调整包括以下步骤：
S301：根据所述初始参考带宽和预设增幅系数，确定调整后的阶梯参考带宽，并记录带宽调整时的时间节点。
在本实施方式中，预设增幅系数的设定可以采用经验值，例如将预设增幅系数设定为1.1，相应的对初始参考带宽进行第一次调整后的阶梯参考带宽将为1.1C0，CDN系统将同时记录对初始参考带宽进行第一次调整时的时间节点。需要特别指出的是，当CDN系统每确定一次新的阶梯参考带宽，CDN系统都将同步记录带宽调整时的时间节点。
显然将预设增幅系数设定为1.1，会使调整后的目标域名的阶梯参考带宽大于初始参考带宽，相当于CDN系统增加了目标域名在整个CDN系统中的可 用带宽，用户在访问目标域名时可以获得更快的速度，访问体验会更好。
S302：从所述带宽调整时的时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到所述预设参考时长。
在本实施例中，CDN系统将实时记录目标域名的实际带宽，并从上述记录到的带宽调整时的时间节点开始，实时比较目标域名的实际带宽与上述比例参考带宽的大小关系，并判断目标域名的实际带宽小于或者等于上述比例参考带宽的持续时间是否达到预设参考时长。
S303：若所述持续时间达到所述预设参考时长，则根据所述阶梯参考带宽和所述预设增幅系数，确定新的阶梯参考带宽，并记录带宽调整时的时间节点。
如果目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间达到所述预设参考时长，CDN系统将根据所述阶梯参考带宽所述预设增幅系数，再次对目标域名的初始参考带宽进行调整，即确定目标域名新的阶梯参考带宽，CDN系统将同时记录下再次对目标域名的初始参考带宽进行调整时的时间节点。需要特别指出的是，当CDN系统每确定一次新的阶梯参考带宽，CDN系统都将同步记录带宽调整时的时间节点。
如果目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间小于所述预设参考时长，CDN系统将从所述目标域名的实际带宽大于所述比例参考带宽的时刻起，再次记录所述目标域名的实际带宽首次小于或者等于所述比例参考带宽时的时间节点，并从再次记录的时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到所述预设参考时长。
下面举例说明CDN系统如何对目标域名的初始参考带宽进行阶梯调整。
假设预设比例系数设定为0.8，预设增幅系数设定为1.1，预设参考时长为5分钟，假设目标域名首次出现实际带宽小于或者等于比例参考带宽(即0.8C0)的时间节点为15:00，在15:00至15:05这段时长内，目标域名的实际带宽一直小于或者等于0.8C0，CDN系统判断目标域名的实际带宽小于或者等 于0.8C0的持续时间达到预设参考时长，CDN系统将会对目标域名的初始参考带宽(即C0)进行阶梯调整，并将第一次调整后的阶梯参考带宽调整为1.1C0，并同时记录下对初始参考带宽进行第一次调整时的时间节点(即15:05)。
CDN系统将以15:05为起点，实时比较15:05之后目标域名的实际带宽与0.8C0的大小关系，并判断15:05至15:10这段时长内，目标域名的实际带宽是否一直小于或者等于0.8C0。
如果在15:05至15:10这段时长内，目标域名的实际带宽一直小于或者等于0.8C0，CDN系统将判断目标域名的实际带宽小于或者等于0.8C0的持续时间达到预设参考时长，CDN系统将会以第一次调整后的阶梯参考带宽(即1.1C0)为基础，根据上述预设增幅系数对目标域名的初始参考带宽进行第二次调整，并将第二次调整后的阶梯参考带宽调整为1.1*1.1C0(即1.21C0)，，亦即确定新的阶梯参考带宽，CDN系统将同时记录下第二次带宽调整时的时间节点(即15:10)。
显然第二次调整后的阶梯参考带宽大于第一次调整后的阶梯参考带宽，CDN系统进一步增加了目标域名在整个CDN系统中的可用带宽，用户对目标域名的访问体验会进一步提高。
如果在15:05至15:10这段时长内，目标域名的实际带宽出现突发，例如在15:06目标域名的实际带宽出现突发，实际带宽大于0.8C0，CDN系统将判断目标域名的实际带宽小于或者等于0.8C0的持续时间小于预设参考时长，此时CDN系统会维持第一次调整后的阶梯参考带宽不变(即1.1C0)，继续对目标域名进行限速，并以15:06为时间重置点，重新实时比较15:06之后目标域名的实际带宽与0.8C0的大小关系，假设在15:22再次出现实际带宽小于或者等于0.8C0，CDN系统将会以15:22为新的时间节点，判断15:22至15:27这段时长内，目标域名的实际带宽是否一直小于或者等于0.8C0。如果在15:22至15:27这段时长内，CDN目标域名的实际带宽一直小于或者等于0.8C0，CDN系统将判断目标域名的实际带宽小于或者等于0.8C0的持续时间达到预设参考时长，CDN系统将会对目标域名的初始参考带宽进行第二次调整。如果在15:22至15:27 这段时长内，目标域名的实际带宽再次出现突发，导致实际带宽大于0.8C0，CDN系统将判断目标域名的实际带宽小于或者等于0.8C0的持续时间小于预设参考时长，此时CDN系统会维持第一次调整后的阶梯参考带宽不变(即1.1C0)，继续对目标域名进行限速，并以实际带宽再次出现突发的时刻为时间重置点，重复进行上述判断过程。
需要特别指出的是，如果在上述判断过程中目标域名的实际突发带宽大于C0，出于系统稳定性考虑，可以将调整后的阶梯参考带宽重置为初始参考带宽(即C0)，并以C0为基础，重新对目标域名进行阶梯调整。CDN系统在确定新的阶梯参考带宽，并记录带宽调整时的时间节点后，将重复进行步骤S302，以进一步增加目标域名在整个CDN系统中的可用带宽，逐步提高用户对目标域名的访问体验。
在本实施方式中，在CDN系统对目标域名的初始参考带宽进行阶梯调整后，还包括判断是否解除所述带宽限速策略的步骤，具体的包括以下步骤：
S401：判断所述目标域名的实际带宽小于或者等于所述初始参考带宽的持续时间是否达到所述指定观察时长。
当CDN系统触发所述带宽限速策略后，CDN系统将以触发带宽限速策略时的时间点为起点，根据设定的指定观察时长，判断在这段时间内目标域名的实际带宽是否一直小于或者等于所述初始参考带宽。
S402：若所述持续时间达到所述指定观察时长，则解除所述带宽限速策略。
如果目标域名的实际带宽在所述指定观察时长内，一直小于或者等于初始参考带宽，CDN系统将判断目标域名的实际带宽小于或者等于初始参考带宽的持续时间达到指定观察时长，用户对目标域名的访问需求已经下降，目标域名的带宽不会再次走高，CDN系统将解除目标域名的带宽限速策略。
若所述持续时间小于所述指定观察时长，CDN系统会将阶梯调整后的参考带宽重置为所述初始参考带宽，并在所述指定观察时长内，重新对所述初始参考带宽和所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带 宽进行阶梯调整，以及判断是否解除所述带宽限速策略。
下面举例说明CDN系统是如何判断是否解除目标域名的带宽限速策略。
假设指定观察时长为30分钟，CDN系统触发带宽限速策略时的时间点为12:08，CDN系统将会对比12:08至12:38这段时长内目标域名的实际带宽和初始参考带宽(即C0)的大小。
如果在12:08至12:38这段时长内，目标域名的实际带宽一直小于或者等于C0，CDN系统将判断目标域名的实际带宽小于或者等于C0的持续时间达到指定观察时长，用户对目标域名的访问需求已经下降，目标域名的带宽不会再次走高，CDN系统将解除目标域名的带宽限速策略。
如果在12:08至12:38这段时长内，目标域名的实际带宽出现突发，例如在12:30目标域名的实际带宽出现突发，并且实际突发带宽大于C0，CDN系统将判断目标域名的实际带宽小于或者等于C0的持续时间小于指定观察时长，用户对目标域名的访问需求仍然较大，目标域名的带宽可能会再次走高。此时CDN系统会继续对目标域名执行带宽限速策略，并将目标域名调整后的阶梯参考带宽重置为初始参考带宽(即C0)，并以实际带宽出现突发的时刻(即12:30)为时间重置点，重新对比12:30至13:00这段时长内目标域名的实际带宽和初始参考带宽(即C0)的大小，以判断是否对目标域名的初始参考带宽进行阶梯调整，以及判断是否解除目标域名的带宽限速策略。
在本实施方式中，针对所述CDN系统中为所述目标域名提供服务的目标缓存服务器，所述带宽限速策略还包括确定所述目标域名在每一个所述目标缓存服务器上的带宽限制值，并将所述带宽限制值发送至对应的所述目标缓存服务器的步骤。
在CDN系统中，通常会有多个边缘节点服务器或者中转节点服务器同时为目标域名提供加速服务，在本申请中，将为目标域名提供加速服务的边缘节点服务器或者中转节点服务器称为目标缓存服务器，显然，目标域名在整个CDN系统中的可用带宽是通过目标缓存服务器在整个CDN系统中的可用带宽来体现的，当目标缓存服务器在整个CDN系统中的可用带宽增加时，即体现为目标域 名在整个CDN系统中的可用带宽增加。CDN系统将统计所有的目标缓存服务器，并根据预设带宽限制总值和当前的目标缓存服务器对应的带宽比例，计算目标域名在每一个目标缓存服务器上的初始带宽限制值，并将上述初始带宽限制值发送至对应的目标缓存服务器上。当CDN系统对目标域名的初始参考带宽进行阶梯调整后，CDN系统将根据调整后的阶梯参考带宽，重新调整目标域名的带宽限制总值，并根据上述带宽比例确定目标域名在每一个目标缓存服务器上的阶梯带宽限制值。CDN系统通过上述阶梯带宽限制值，逐步增加目标缓存服务器在整个CDN系统中的可用带宽，以提高用户对目标域名的访问体验。
在本实施方式中，CDN系统可以在触发目标域名的带宽限速策略时，统计目标域名在各个目标缓存服务器上的实际带宽，并计算上述各个目标缓存服务器间的实际带宽的比值，以此确定当前的目标缓存服务器对应的带宽比例。
在本实施方式中，CDN系统可以根据初始参考带宽对预设带宽限制总值进行设定，预设带宽限制总值的具体数值可以根据经验值进行设置，但是预设带宽限制总值必须小于或者等于初始参考带宽。
在本实施方式中，针对CDN系统中的中转节点服务器，CDN系统还可以根据源站的性能指标来设置预设带宽限制总值，例如源站可以承受的最大回源带宽为10M，CDN系统可以将预设带宽限制总值设定为10M。由于一个中转节点服务器可能同时为多个域名提供加速服务，在某种情况下可能会出现源站可以承受的最大回源带宽大于CDN系统设定的初始参考带宽，此时预设带宽限制总值应当以初始参考带宽为参考标准进行设定。
需要说明的是，带宽限制总值的调整系数可以参考所述预设增幅系数，也可以根据经验值进行设定，本申请对此不作限制。
举例来说，整个CDN网络中只有两台边缘节点服务器为目标域名提供加速服务，分别记为目标缓存服务器A和目标缓存服务器B。假设CDN系统触发目标域名带宽限速策略时，目标域名在目标缓存服务器A上的实际带宽为20M,目标域名在目标缓存服务器B上的实际带宽为30M，初始参考带宽设定为50M，则目标缓存服务器A对应的带宽比例为2/5，目标缓存服务器B对应的带宽比例为 3/5，如果预设带宽限制总值设置为40M，则目标域名在目标缓存服务器A上的初始带宽限制值为16M，目标域名在目标缓存服务器B上的初始带宽限制值为24M。带宽限制总值的调整系数取预设增幅系数，当CDN系统对初始参考带宽进行阶梯调整，第一次调整后的的阶梯参考带宽为55M，此时相应的目标域名的带宽限制总值将调整为44M，目标域名在目标缓存服务器A上的阶梯带宽限制值将调整为17.6M，目标域名在目标缓存服务器B上的阶梯带宽限制值将调整为26.4M。
由于目标缓存服务器对目标域名的加速服务是通过软件进程实现的，而每一个目标缓存服务器中会有多个加速进程同时为目标域名提供服务。为进一步提高目标缓存服务器的工作效率，针对目标缓存服务器中的多组进程，CDN系统还可以根据目标缓存服务器的带宽限制值、当前的进程对应的带宽比例，计算目标缓存服务器中每一个进程的带宽限制值。在目标缓存服务器的带宽限制值调整后，相应的对上述每一个进程的带宽限制值进行调整。
请参阅图5，本申请还提供一种域名带宽调整装置，应用于CDN系统中，所述域名带宽调整装置包括：
限速判断单元，用于判断所述CDN系统是否触发带宽限速策略，以及判断是否解除所述带宽限速策略；
域名识别单元，用于在触发所述带宽限速策略后，在所述CDN系统服务的域名中，确定待限速的目标域名；
带宽调整单元，用于确定所述目标域名的初始参考带宽，并在指定观察时长内，对所述初始参考带宽和所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带宽进行阶梯调整。
在一个实施方式中，针对所述CDN系统中的边缘节点服务器，所述判断限速单元还包括：
性能指标计算模块，用于计算所述边缘节点服务器的性能指标，当所述性能指标低于预设指标阈值时，触发所述带宽限速策略。
在一个实施方式中，针对所述CDN系统中的中转节点服务器，所述判断 限速单元还包括：
告警信息判断模块，用于判断所述中转节点服务器是否产生告警信息，若产生，则触发所述带宽限速策略。
在一个实施方式中，带宽调整单元判断是否对所述初始参考带宽进行阶梯调整包括：
根据所述初始参考带宽和预设比例系数，确定比例参考带宽；
记录所述目标域名的实际带宽首次小于或者等于所述比例参考带宽时的时间节点，并从记录的所述时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到预设参考时长；
若所述持续时间达到所述预设参考时长，则对所述初始参考带宽进行阶梯调整；
若所述持续时间小于所述预设参考时长，则从所述目标域名的实际带宽大于所述比例参考带宽的时刻起，再次记录所述目标域名的实际带宽首次小于或者等于所述比例参考带宽时的时间节点，并从再次记录的时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到所述预设参考时长。
在一个实施方式中，限速判断单元判断是否解除所述带宽限速策略包括：
判断所述目标域名的实际带宽小于或者等于所述初始参考带宽的持续时间是否达到所述指定观察时长；
若所述持续时间达到所述指定观察时长，则解除所述带宽限速策略；
若所述持续时间小于所述指定观察时长，则将阶梯调整后的参考带宽重置为所述初始参考带宽，并在所述指定观察时长内，重新对所述初始参考带宽和所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带宽进行阶梯调整，以及判断是否解除所述带宽限速策略。
在一个实施方式中，所述带宽调整单元包括：
阶梯带宽计算模块，用于根据所述初始参考带宽和预设增幅系数，确定调整后的阶梯参考带宽，以及根据所述阶梯参考带宽和所述预设增幅系数，确 定新的阶梯参考带宽，以及同步记录带宽调整时的时间节点；
阶梯调整判断模块，用于从所述带宽调整时的时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到所述预设参考时长。
在本实施方式中，若从所述带宽调整时的时间节点开始，阶梯调整判断模块判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间达到所述预设参考时长，阶梯带宽计算模块将根据所述阶梯参考带宽和所述预设增幅系数，确定新的阶梯参考带宽，并记录带宽调整时的时间节点。
在本实施方式中，若从所述带宽调整时的时间节点开始，阶梯调整判断模块判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间小于所述预设参考时长，带宽调整单元将从所述目标域名的实际带宽大于所述比例参考带宽的时刻起，再次记录所述目标域名的实际带宽首次小于或者等于所述比例参考带宽时的时间节点，并从再次记录的时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到所述预设参考时长。
在一个实施方式中，针对所述CDN系统中为所述目标域名提供服务的目标缓存服务器，所述域名带宽调整装置还包括：
目标缓存服务器控制单元，用于确定所述目标域名在每一个所述目标缓存服务器上的带宽限制值，并将所述带宽限制值发送至对应的所述目标缓存服务器。
在一个实施方式中，所述目标缓存服务器控制单元包括：
初始带宽限制值计算模块，用于根据预设带宽限制总值和当前的目标缓存服务器对应的带宽比例，确定所述目标域名在所述当前的目标缓存服务器上的初始带宽限制值；
阶梯带宽限制值计算模块，用于在对所述初始参考带宽进行阶梯调整后，根据调整后的参考带宽和所述当前的目标缓存服务器对应的带宽比例，确定所述目标域名在所述当前的目标缓存服务器上的阶梯带宽限制值。
请参阅图6，本申请还提供一种域名带宽调整装置，应用于CDN系统中，所述域名带宽调整装置包括存储器和处理器，所述存储器用于存储计算机程序，所述计算机程序被所述处理器执行时，可以实现如上述的域名带宽调整方法。具体地，在硬件层面，该域名带宽调整装置可以包括处理器、内部总线和存储器。所述存储器可以包括内存以及非易失性存储器。处理器从非易失性存储器中读取对应的计算机程序到内存中然后运行。本领域普通技术人员可以理解，图6所示的结构仅为示意，其并不对上述识别装置的结构造成限定。例如，所述域名带宽调整装置还可包括比图6中所示更多或者更少的组件，例如还可以包括其他的处理硬件，如GPU(Graphics Processing Unit，图像处理器)，或者对外通信端口，如80端口、443端口、8080端口等。当然，除了软件实现方式之外，本申请并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等。
本实施方式中，所述的处理器可以包括中央处理器(CPU)或图形处理器(GPU)，当然也可以包括其他的具有逻辑处理能力的单片机、逻辑门电路、集成电路等，或其适当组合。本实施方式所述的存储器可以是用于保存信息的记忆设备。在数字系统中，能保存二进制数据的设备可以是存储器；在集成电路中，一个没有实物形式的具有存储功能的电路也可以为存储器，如RAM、FIFO等；在系统中，具有实物形式的存储设备也可以叫存储器等。实现的时候，该存储器也可以采用云存储器的方式实现，具体实现方式，本说明书不做限定。
需要说明的是，本说明书中的域名带宽调整装置，具体的实现方式可以参照方法实施方式的描述，在此不作一一赘述。
由此可见，本申请提供的技术方案，CDN系统可以根据边缘节点服务器或者中转节点服务器的负载情况，自动判断是否触发带宽限速策略，并在触发带宽限速策略时，自动在边缘节点服务器或者中转节点服务器服务的域名中确定需要进行限速的目标域名，然后根据设定的初始参考带宽对目标域名的边缘带宽或者回源带宽进行限速。如果目标域名的实际带宽小于或者等于初始参考带宽的持续时间达到预设参考时长，CDN系统将会对目标域名的初始参考带宽进 行阶梯调整，并根据调整后的参考带宽，逐步增加目标域名在整个CDN系统中的可用带宽，以提高用户对目标域名的访问体验。当目标域名的实际带宽小于或者等于初始参考带宽的持续时间达到指定观察时长时，CDN系统会解除带宽限速策略，彻底放开对目标域名的带宽限制。由此可见，本申请提供的技术方案，通过对目标域名进行带宽阶梯调整和限速观察，可以逐步恢复CDN系统对目标域名的加速效果，既提高了用户访问目标域名的体验，又可以避免直接放开带宽限制，导致目标域名的边缘带宽或者回源带宽再次走高。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到各实施方式可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件来实现。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
以上所述仅为本申请的较佳实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (15)

  1. 一种域名带宽调整方法，应用于CDN系统中，其中，所述方法包括：
    判断所述CDN系统是否触发带宽限速策略，若触发，则在所述CDN系统服务的域名中，确定待限速的目标域名，并对所述目标域名执行所述带宽限速策略；
    在所述带宽限速策略执行时，确定所述目标域名的初始参考带宽，并在指定观察时长内，对所述初始参考带宽和所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带宽进行阶梯调整，以及判断是否解除所述带宽限速策略。
  2. 根据权利要求1所述的方法，其中，针对所述CDN系统中的边缘节点服务器，判断所述CDN系统是否触发带宽限速策略包括：
    计算所述边缘节点服务器的性能指标，当所述性能指标低于预设指标阈值时，触发所述带宽限速策略。
  3. 根据权利要求1所述的方法，其中，针对所述CDN系统中的中转节点服务器，判断所述CDN系统是否触发带宽限速策略包括：
    判断所述中转节点服务器是否产生告警信息，若产生，则触发所述带宽限速策略。
  4. 根据权利要求1至3中任一所述的方法，其中，判断是否对所述初始参考带宽进行阶梯调整包括：
    根据所述初始参考带宽和预设比例系数，确定比例参考带宽；
    记录所述目标域名的实际带宽首次小于或者等于所述比例参考带宽时的时间节点，并从记录的所述时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到预设参考时长；
    若所述持续时间达到所述预设参考时长，则对所述初始参考带宽进行阶梯调整。
  5. 根据权利要求4所述的方法，其中，判断是否对所述初始参考带宽进行 阶梯调整还包括：
    若所述持续时间小于所述预设参考时长，则从所述目标域名的实际带宽大于所述比例参考带宽的时刻起，再次记录所述目标域名的实际带宽首次小于或者等于所述比例参考带宽时的时间节点，并从再次记录的时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到所述预设参考时长。
  6. 根据权利要求4所述的方法，其中，对所述初始参考带宽进行阶梯调整包括：
    根据所述初始参考带宽和预设增幅系数，确定调整后的阶梯参考带宽，并记录带宽调整时的时间节点；
    从所述带宽调整时的时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到所述预设参考时长；
    若所述持续时间达到所述预设参考时长，则根据所述阶梯参考带宽和所述预设增幅系数，确定新的阶梯参考带宽，并记录带宽调整时的时间节点。
  7. 根据权利要求6所述的方法，其中，对所述初始参考带宽进行阶梯调整还包括：
    若所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间小于所述预设参考时长，则从所述目标域名的实际带宽大于所述比例参考带宽的时刻起，再次记录所述目标域名的实际带宽首次小于或者等于所述比例参考带宽时的时间节点，并从再次记录的时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到所述预设参考时长。
  8. 根据权利要求1所述的方法，其中，判断是否解除所述带宽限速策略包括：
    判断所述目标域名的实际带宽小于或者等于所述初始参考带宽的持续时间是否达到所述指定观察时长；
    若所述持续时间达到所述指定观察时长，则解除所述带宽限速策略；
    若所述持续时间小于所述指定观察时长，则将阶梯调整后的参考带宽重置为所述初始参考带宽，并在所述指定观察时长内，重新对所述初始参考带宽和 所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带宽进行阶梯调整，以及判断是否解除所述带宽限速策略。
  9. 根据权利要求1所述的方法，其中，针对所述CDN系统中为所述目标域名提供服务的目标缓存服务器，所述带宽限速策略包括：
    确定所述目标域名在每一个所述目标缓存服务器上的带宽限制值，并将所述带宽限制值发送至对应的所述目标缓存服务器。
  10. 根据权利要求9所述的方法，其中，确定所述目标域名在每一个所述目标缓存服务器上的带宽限制值包括：
    根据预设带宽限制总值和当前的目标缓存服务器对应的带宽比例，确定所述目标域名在所述当前的目标缓存服务器上的初始带宽限制值；
    在对所述初始参考带宽进行阶梯调整后，根据调整后的参考带宽和所述当前的目标缓存服务器对应的带宽比例，确定所述目标域名在所述当前的目标缓存服务器上的阶梯带宽限制值。
  11. 一种域名带宽调整装置，应用于CDN系统中，其中，所述域名带宽调整装置包括：
    限速判断单元，用于判断所述CDN系统是否触发带宽限速策略，以及判断是否解除所述带宽限速策略；
    域名识别单元，用于在触发所述带宽限速策略后，在所述CDN系统服务的域名中，确定待限速的目标域名；
    带宽调整单元，用于确定所述目标域名的初始参考带宽，并在指定观察时长内，对所述初始参考带宽和所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带宽进行阶梯调整。
  12. 根据权利要求11所述的域名带宽调整装置，其中，判断是否对所述初始参考带宽进行阶梯调整包括：
    根据所述初始参考带宽和预设比例系数，确定比例参考带宽；
    记录所述目标域名的实际带宽首次小于或者等于所述比例参考带宽时的时间节点，并从记录的所述时间节点开始，判断所述目标域名的实际带宽小于或 者等于所述比例参考带宽的持续时间是否达到预设参考时长；
    若所述持续时间达到所述预设参考时长，则对所述初始参考带宽进行阶梯调整。
  13. 根据权利要求12所述的域名带宽调整装置，其中，所述带宽调整单元包括：
    阶梯带宽计算模块，用于根据所述初始参考带宽和预设增幅系数，确定调整后的阶梯参考带宽，以及根据所述阶梯参考带宽和所述预设增幅系数，确定新的阶梯参考带宽，以及同步记录带宽调整时的时间节点；
    阶梯调整判断模块，用于从所述带宽调整时的时间节点开始，判断所述目标域名的实际带宽小于或者等于所述比例参考带宽的持续时间是否达到所述预设参考时长。
  14. 根据权利要求11所述的域名带宽调整装置，其中，判断是否解除所述带宽限速策略包括：
    判断所述目标域名的实际带宽小于或者等于所述初始参考带宽的持续时间是否达到所述指定观察时长；
    若所述持续时间达到所述指定观察时长，则解除所述带宽限速策略；
    若所述持续时间小于所述指定观察时长，则将阶梯调整后的参考带宽重置为所述初始参考带宽，并在所述指定观察时长内，重新对所述初始参考带宽和所述目标域名的实际带宽进行比较，以判断是否对所述初始参考带宽进行阶梯调整，以及判断是否解除所述带宽限速策略。
  15. 一种域名带宽调整装置，应用于CDN系统中，其中，所述域名带宽调整装置包括存储器和处理器，所述存储器用于存储计算机程序，当所述计算机程序被所述处理器执行时，实现如权利要求1至10中任一权利要求所述的方法。
PCT/CN2019/086059 2019-04-12 2019-05-08 一种域名带宽调整方法及装置 WO2020206784A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19880923.8A EP3748925B1 (en) 2019-04-12 2019-05-08 Domain name bandwidth adjustment method and device
US16/872,558 US10958592B2 (en) 2019-04-12 2020-05-12 Domain name bandwidth adjustment method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910293699.8 2019-04-12
CN201910293699.8A CN110048968B (zh) 2019-04-12 2019-04-12 一种域名带宽调整方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/872,558 Continuation US10958592B2 (en) 2019-04-12 2020-05-12 Domain name bandwidth adjustment method and apparatus

Publications (1)

Publication Number Publication Date
WO2020206784A1 true WO2020206784A1 (zh) 2020-10-15

Family

ID=67276959

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/086059 WO2020206784A1 (zh) 2019-04-12 2019-05-08 一种域名带宽调整方法及装置

Country Status (3)

Country Link
EP (1) EP3748925B1 (zh)
CN (1) CN110048968B (zh)
WO (1) WO2020206784A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112953846A (zh) * 2021-02-07 2021-06-11 上海七牛信息技术有限公司 域名带宽成本优化式投放方法、装置及计算机设备
CN113067731A (zh) * 2021-03-18 2021-07-02 北京金山云网络技术有限公司 节点带宽调整方法、装置、设备和存储介质
CN113852570A (zh) * 2021-09-23 2021-12-28 北京金山云网络技术有限公司 推荐节点带宽生成方法、装置、设备和计算机可读介质
CN113852493A (zh) * 2021-09-03 2021-12-28 中盈优创资讯科技有限公司 一种stn弹性带宽专线智能调速方法及装置
CN114338705A (zh) * 2021-11-24 2022-04-12 阿里巴巴（中国）有限公司 内容分发网络cdn节点的资源水位控制方法、设备及介质
CN114915559A (zh) * 2021-02-08 2022-08-16 北京金山云网络技术有限公司 Cdn节点带宽规划方法、装置及存储介质
CN115396244A (zh) * 2021-05-08 2022-11-25 北京金山云网络技术有限公司 带宽调度管理方法、装置、电子设备及存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110519183B (zh) 2019-09-29 2022-12-02 北京金山云网络技术有限公司 一种节点限速的方法、装置、电子设备及存储介质
CN111147299A (zh) * 2019-12-26 2020-05-12 杭州迪普科技股份有限公司 一种限速策略的测试方法及装置
CN112260962B (zh) * 2020-10-16 2023-01-24 网宿科技股份有限公司 一种带宽控制方法及装置
CN112804110B (zh) * 2021-03-19 2023-05-09 上海七牛信息技术有限公司 基于内容分发网络指标系统的带宽精准控制方法及装置
CN113193991B (zh) * 2021-04-15 2023-05-19 网宿科技股份有限公司 一种带宽限速方法及决策装置、计算机可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106034083A (zh) * 2015-03-12 2016-10-19 阿里巴巴集团控股有限公司 Cdn网络系统及其限速控制方法、cdn节点和服务器
CN109412977A (zh) * 2018-10-18 2019-03-01 网宿科技股份有限公司 一种域名带宽调节方法及相关设备
CN109547517A (zh) * 2017-09-22 2019-03-29 贵州白山云科技股份有限公司 一种带宽资源调度方法和装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100512210C (zh) * 2005-06-24 2009-07-08 中国长城计算机深圳股份有限公司 一种实现对上网用户带宽进行缓冲控制的方法
CN103391585B (zh) * 2012-05-07 2019-06-18 中兴通讯股份有限公司 带宽的调整方法及装置
US9769074B2 (en) * 2013-03-15 2017-09-19 International Business Machines Corporation Network per-flow rate limiting
CN104348753B (zh) * 2013-07-26 2018-10-12 华为技术有限公司 数据包转发方法以及数据包转发装置
CN109067607B (zh) * 2018-11-07 2020-09-18 网宿科技股份有限公司 一种调整额定带宽的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106034083A (zh) * 2015-03-12 2016-10-19 阿里巴巴集团控股有限公司 Cdn网络系统及其限速控制方法、cdn节点和服务器
CN109547517A (zh) * 2017-09-22 2019-03-29 贵州白山云科技股份有限公司 一种带宽资源调度方法和装置
CN109412977A (zh) * 2018-10-18 2019-03-01 网宿科技股份有限公司 一种域名带宽调节方法及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3748925A4 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112953846A (zh) * 2021-02-07 2021-06-11 上海七牛信息技术有限公司 域名带宽成本优化式投放方法、装置及计算机设备
CN114915559A (zh) * 2021-02-08 2022-08-16 北京金山云网络技术有限公司 Cdn节点带宽规划方法、装置及存储介质
CN114915559B (zh) * 2021-02-08 2024-01-23 北京金山云网络技术有限公司 Cdn节点带宽规划方法、装置及存储介质
CN113067731A (zh) * 2021-03-18 2021-07-02 北京金山云网络技术有限公司 节点带宽调整方法、装置、设备和存储介质
CN113067731B (zh) * 2021-03-18 2023-04-07 北京金山云网络技术有限公司 节点带宽调整方法、装置、设备和存储介质
CN115396244A (zh) * 2021-05-08 2022-11-25 北京金山云网络技术有限公司 带宽调度管理方法、装置、电子设备及存储介质
CN115396244B (zh) * 2021-05-08 2024-02-20 北京金山云网络技术有限公司 带宽调度管理方法、装置、电子设备及存储介质
CN113852493A (zh) * 2021-09-03 2021-12-28 中盈优创资讯科技有限公司 一种stn弹性带宽专线智能调速方法及装置
CN113852570A (zh) * 2021-09-23 2021-12-28 北京金山云网络技术有限公司 推荐节点带宽生成方法、装置、设备和计算机可读介质
CN114338705A (zh) * 2021-11-24 2022-04-12 阿里巴巴（中国）有限公司 内容分发网络cdn节点的资源水位控制方法、设备及介质
CN114338705B (zh) * 2021-11-24 2023-12-01 阿里巴巴（中国）有限公司 内容分发网络cdn节点的资源水位控制方法、设备及介质

Also Published As

Publication number Publication date
EP3748925B1 (en) 2022-01-19
CN110048968B (zh) 2021-06-22
EP3748925A1 (en) 2020-12-09
CN110048968A (zh) 2019-07-23
EP3748925A4 (en) 2020-12-09

Similar Documents

Publication Publication Date Title
WO2020206784A1 (zh) 一种域名带宽调整方法及装置
US10958592B2 (en) Domain name bandwidth adjustment method and apparatus
US11601512B2 (en) System and method for throttling service requests having non-uniform workloads
CN110022268B (zh) 一种数据传输控制方法、装置及存储介质
US11582163B2 (en) System for early system resource constraint detection and recovery
JP6430462B2 (ja) バーチャルマシン通信トラフィックを成形すること
US9419904B2 (en) System and method for throttling service requests using work-based tokens
US10768823B2 (en) Flow control for unaligned writes in network storage device
US6961341B1 (en) Adaptive bandwidth throttling for network services
US20160112275A1 (en) Automatic detection and prevention of network overload conditions using sdn
US20090034551A1 (en) System and method for receive queue provisioning
WO2017031958A1 (zh) 一种写策略控制方法和装置
WO2018121334A1 (zh) 一种提供网页应用服务的方法、装置、电子设备及系统
US11797076B2 (en) Using network interface controller (NIC) queue depth for power state management
BR112016010801B1 (pt) Método e sistema de controle de tráfego entre uma pluralidade de dispositivos eletrônicos e um ou mais serviços
US20140173221A1 (en) Cache management
CN109815204B (zh) 一种基于拥塞感知的元数据请求分发方法及设备
CN114785739B (zh) 逻辑卷服务质量的控制方法、装置、设备及介质
US11861176B2 (en) Processing of input/ouput operations by a distributed storage system based on latencies assigned thereto at the time of receipt
US20070106774A1 (en) Computer system controlling bandwidth according to priority state
WO2022001430A1 (zh) 一种高吞吐量流处理方法、装置及计算机可读存储介质
CN115914236A (zh) 存储空间的分配调整方法、装置、电子设备及存储介质
WO2022048674A1 (zh) 基于服务器机柜的虚拟机管理方法及装置
US9871732B2 (en) Dynamic flow control in multicast systems
US8301735B1 (en) Variable AAA load distribution for PDSN

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2019880923

Country of ref document: EP

Effective date: 20200511

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19880923

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE