WO2016086482A1 - 使用内容分发网络的网站的资源使用率保障方法和系统 - Google Patents

使用内容分发网络的网站的资源使用率保障方法和系统 Download PDF

Info

Publication number
WO2016086482A1
WO2016086482A1 PCT/CN2014/095483 CN2014095483W WO2016086482A1 WO 2016086482 A1 WO2016086482 A1 WO 2016086482A1 CN 2014095483 W CN2014095483 W CN 2014095483W WO 2016086482 A1 WO2016086482 A1 WO 2016086482A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
source station
website
address
website source
Prior art date
Application number
PCT/CN2014/095483
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 US15/528,342 priority Critical patent/US10361902B2/en
Priority to EP14907448.6A priority patent/EP3244589B1/en
Publication of WO2016086482A1 publication Critical patent/WO2016086482A1/zh

Links

Images

Classifications

    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • 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]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1029—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers using data related to the state of servers by a load balancer
    • 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/56—Provisioning of proxy services
    • 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/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/69—Types of network addresses using geographic information, e.g. room number
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0253—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using browsers or web-pages for accessing management information
    • 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/535—Tracking the activity of the user

Definitions

  • the present invention relates to the field of network technologies, and in particular, to a resource usage rate securing method and system for a website using a content distribution network.
  • the DNS (Domain Name System) system is used to name computers and network services organized into domain hierarchies. It is an important basic service system of the Internet. The emergence of DNS can make it easier for users to access the Internet without having to remember the IP strings that can be read directly by the machine. The conversion of domain names and IP strings is called domain name resolution. The host that performs this function is called a DNS server. When a user enters a domain name in an application, the DNS service can resolve the domain name into other related information, such as an IP address, to complete the website access.
  • the task of the CDN is mainly to deliver content from the source station to the client as quickly as possible.
  • the basic idea of CDN is to avoid the bottlenecks and links on the Internet that may affect the speed and stability of data transmission, so that content can be transmitted faster and better.
  • the CDN can redirect user access requests to the nearest and best user based on network traffic and the load of each edge node, as well as the distance to the user and the response time.
  • the CDN adds a global scheduling layer to the existing network architecture to distribute the source station content to the edge of the network closest to the user, so that the user can get the desired content nearby.
  • the CND can solve the congestion of the Internet network, improve the response speed of the user visiting the website, and solve the problem that the bandwidth of the source station outlet network is small, the user access is large, the network points are unevenly distributed, the complex carrier network, and the user access network bandwidth are small. The resulting slow response of users visiting the website.
  • CDN Code acceleration
  • no acceleration can not guarantee the quality of website access.
  • acceleration guarantees access quality, it leads to In most cases, website resource usage will be at a lower level, which is not what website operators expect.
  • the technical problem to be solved by the present invention is to provide a resource usage rate securing method and system for a website using a content distribution network, which can balance website resource usage rate and access quality.
  • the technical solution adopted by the present invention for solving the above technical problem is a resource usage rate securing method for a website using a content distribution network, comprising the steps of: receiving a domain name resolution request sent by a local domain name server; and monitoring corresponding to the domain name resolution request
  • the resource load of the website source station; using the monitoring data and determining the result of the domain name resolution request according to a predetermined policy is one of the address and content distribution network system of the website source station; and transmitting the domain name resolution result to the local domain name server.
  • the method is performed outside of the content distribution network system, and the parsing result is a domain name of the content distribution network system.
  • the method is performed within the content distribution network system and the result of the parsing is an address of one of the edge servers of the content distribution network system.
  • the step of using the monitoring data and determining the result of the domain name resolution request according to a predetermined policy to be the address of the website source station and the content distribution network system comprises: selecting a scheduling policy, where the scheduling policy is The parameter includes a preset upper limit and a preset lower limit of the resource load, and a website source station address; the decision is made according to the resource load and the selected scheduling policy, where: the domain name resolution request is initially parsed into an address of the website source station.
  • the resolution ratio is maintained; when the resource load of the website source station exceeds the preset upper limit, the resolution ratio is increased; When the resource load of the website source station is lower than the preset lower limit, the resolution ratio is reduced, wherein the resolution ratio is a ratio of parsing the domain name resolution request to the content distribution network system.
  • the amount of change in the resolution ratio is preset.
  • /F upper limit ; when the resource load of the website source station is lower than the preset lower limit and the resolution ratio is lowered, ⁇ R
  • the website source station includes a single address and utilizes monitoring data to root
  • the address of the website source station is the single address.
  • the website source station includes a plurality of addresses
  • the method further includes: obtaining an address of the local domain name server according to the domain name resolution request; identifying a geographic location and service providing of the local domain name server according to the address And wherein the address of the website source station is one or more of the plurality of addresses when the monitoring data is utilized and the result of the domain name resolution request is determined according to a predetermined policy.
  • the method further includes: selecting a corresponding scheduling policy according to a geographic location of the local domain name server and a service provider, where the parameters of the scheduling policy include: a service provider line, a region, a domain name, or a domain name group, Website source address.
  • the invention also provides a resource usage guarantee system for a website using a content distribution network, comprising: a domain name system module, receiving a domain name resolution request; a monitoring module, monitoring a resource load of a website source station corresponding to the domain name resolution request; and scheduling The module, using the monitoring data and determining the result of the domain name resolution request according to a predetermined policy, is one of an address and content distribution network system of the website source station.
  • the system is independent of the content distribution network system, and the analysis result is a domain name of the content distribution network system.
  • the system is configured in the content distribution network system, and the analysis result is an address of one of the edge servers of the content distribution network system.
  • the scheduling module is configured to perform the following steps: configuring a scheduling policy, where the parameters of the scheduling policy include a preset upper limit and a preset lower limit of the resource load, and a website source station address; according to the resource load And the selected scheduling policy is determined, wherein: the domain name resolution request is initially parsed into an address of the website source station; and when the resource load of the website source station is between the preset upper limit and the preset lower limit, the maintenance is maintained.
  • the resolution ratio is unchanged; when the resource load of the source station of the website exceeds the preset upper limit, the resolution ratio is increased; when the resource load of the source station of the website is lower than the preset lower limit, the resolution ratio is lowered, wherein the resolution ratio is The proportion of domain name resolution requests resolved to the content distribution network system.
  • the amount of change in the resolution ratio is preset.
  • / F upper limit ; when the resource load of the website source station is lower than the preset lower limit and the resolution ratio is lowered, ⁇ R
  • the website source station includes a plurality of addresses
  • the system further includes: an obtaining module, acquiring an address of the local domain name server according to the domain name resolution request; and an identifying module, identifying the geographical location of the local domain name server according to the address The location and service provider; and when the scheduling module determines the result of the domain name resolution request, the address of the website source station is one or more of the plurality of addresses.
  • the scheduling module is configured to select a corresponding scheduling policy according to a geographic location of the local domain name server and a service provider, where the parameters of the scheduling policy include: a service provider line, and a region, a domain name, or Domain group.
  • the system further includes a resource module for managing resources of the website source station, setting a monitoring mode, and saving related monitoring configuration information.
  • the present invention also provides a resource usage guarantee system for a website using a content distribution network, comprising: a module for receiving a domain name resolution request; a module for monitoring a resource load of a website source station corresponding to the domain name resolution request; The result of utilizing the monitoring data and determining the domain name resolution request according to a predetermined policy is a module of one of the address and content distribution network systems of the website source station.
  • the method and system for securing the website resource usage rate of the present invention organically combines the CDN service network with the resources of the website operator through intelligent scheduling, preferentially uses the website resources, and monitors the use of the website resources in real time. After the website resource usage rate exceeds the set value, modify the DNS resolution ratio, and gradually guide the traffic to the CDN service network to reduce the load pressure of the source station; when the website traffic access traffic is lower than the lower limit of the set value, modify the DNS resolution ratio. The traffic is then gradually guided back to the website to improve the website resource usage rate.
  • the website resource usage rate can be intelligently controlled within a reasonable range without degrading the access quality.
  • FIG. 1 is a schematic diagram of a network implementation environment according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for securing a website resource usage rate according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a traffic scheduling method according to an embodiment of the present invention.
  • FIG. 4 is a logic block diagram of a website resource usage guarantee system according to an embodiment of the present invention.
  • FIG. 5 is a structural block diagram of a scheduling module according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a network implementation environment according to another embodiment of the present invention.
  • FIG. 7 is a topological diagram of a CDN network in accordance with an embodiment of the present invention.
  • the website resource usage rate is mainly reflected in several indicators such as the amount of traffic and bandwidth usage. It is the goal pursued by website operators to ensure that the website resource usage rate is within a reasonable range. If the website resource usage rate is too low, the IT basic resources are not effectively configured, so that the website operation cost is relatively increased; if the website resource usage rate is too high, the service response is slow, the user experience is reduced, and the customer is lost.
  • CDN Content Distribute Network
  • Embodiments of the present invention propose a method of securing resource usage of a website using a CDN, which introduces monitoring and adjustment of resource usage of the website.
  • FIG. 1 is a schematic diagram of a network implementation environment according to an embodiment of the present invention.
  • the network implementation environment 100 includes a website source station 101, a local DNS (Domain Name System) server 102, an authoritative DNS server 103, a website resource usage guarantee system 104, a CDN system 105, and a client 106.
  • the website source station 101 is composed of one to a plurality of servers and is a website content storage subject, and can provide content to a plurality of clients 106.
  • the website source station 101 can have one or more addresses. Each address can correspond to one server or multiple servers. Due to the limitation of traffic load, the CDN system 105 is used to partially replace the website source station 101 in response to a content request by a portion of the client 106.
  • the network topology diagram of the CDN system can be referred to FIG.
  • a number of geographically dispersed edge node servers or clusters 710 are configured in the CDN system 105 to provide content to the near client 106.
  • the local DNS server 102 is responsible for receiving the domain name resolution request sent by the client 106 and forwarding the request of the client 106 to the destination site.
  • the destination site is the server of the website source station 101 or the CDN system 105, depending on the analysis result of the website resource usage guarantee system 104.
  • the CDN system 105 is the destination site, it will further forward the request to the edge node server.
  • the local DNS server 102 forwards the domain name resolution request to the authoritative DNS server 103.
  • the authoritative DNS server 103 can receive the domain name resolution request of the local DNS server 102 and send the domain name of the website resource usage guarantee system 104 to the local DNS server 102.
  • the local DNS server 102 can be turned to request the website resource usage guarantee system 104 to resolve the domain name.
  • Website resource usage guarantee system 104 The domain name resolution request for receiving the local DNS server 102, monitoring the resource usage of the website source station 101, and selecting the website source station 101 or the CDN system 105 as the destination site according to the policy and monitoring data, and transmitting the result to the local DNS server 102. .
  • a suitable traffic range can be set for the website source station 101 as a representation of the resource load.
  • the appropriate flow range can be defined by a preset flow upper limit and a preset flow lower limit.
  • the website resource usage guarantee system 104 obtains the traffic data of the website source station 101, and then makes a decision based on the traffic data and the selected scheduling policy.
  • the traffic of the website source station 101 When the traffic of the website source station 101 is lower than the preset traffic limit, it indicates that the resource usage rate of the website source station 101 is within the allowable range, and the domain name resolution request sent by the local DNS server 102 is resolved to the address of the website source station 101; When the traffic of the website source station 101 is not lower than (equal to or greater than) the preset traffic upper limit, indicating that the resource usage rate of the website source station 101 is too high, the resolution ratio is increased, and the resolution ratio refers to parsing the domain name resolution request to the CDN system. The ratio of 105.
  • the website resource usage guarantee system 104 preferentially directs traffic to the website source station 101 unless the resource usage rate of the website source station 101 is too high.
  • FIG. 6 is a schematic diagram of a network implementation environment according to another embodiment of the present invention.
  • the network implementation environment 600 includes a website source station 601, a local DNS server 602, an authoritative DNS server 603, a website resource usage guarantee system 604, a CDN system 605, and a client 606.
  • the embodiment of FIG. 6 differs from FIG. 1 in that the website resource usage guarantee system 604 is configured within the CDN system 605 rather than being independent of the CDN system 605.
  • the destination site is the server of the website source station 601 or the edge node server in the CDN system 605, depending on the analysis result of the website resource usage guarantee system 604.
  • FIG. 7 illustrates a network implementation environment according to an embodiment of the present invention.
  • a CDN system 605 may include a central decision server 701, a plurality of central scheduling servers 702, and a plurality of edge server clusters. 710, these devices are connected together via the Internet.
  • a plurality of servers 711 are arranged in each edge server cluster 710.
  • Many clients 720 can connect to the CDN system 605 to obtain the requested content.
  • the central decision server 701 and the central dispatch server 702 according to the location of the client The location and the requested content are returned to the client with a jump URL (Uniform Resource Locator) with an edge server cluster.
  • a jump URL Uniform Resource Locator
  • the strategy for traffic guidance in this embodiment can be the same as in the previous embodiment, which will be described below.
  • FIG. 2 is a flowchart of a method for securing a website resource usage rate according to an embodiment of the present invention.
  • the website resource usage guarantee method of this embodiment may be performed by the website resource usage guarantee system 104, and includes the following processes:
  • Step 201 Receive a domain name resolution request sent by the local DNS server 102.
  • the domain name resolution request of the local DNS server 102 may be obtained through a subdomain provided by the authoritative DNS server 103.
  • Step 202 Acquire an IP address of the local DNS server 102 according to the domain name resolution request.
  • Step 203 identifying the geographic location of the local DNS server 102 and the ISP (Network Service Provider) information by using the IP address.
  • ISP Network Service Provider
  • Step 204 monitoring the resource load of the website source station 101.
  • monitoring includes, but is not limited to, monitoring the performance load and traffic conditions of a web server or cluster. More specifically, for example, monitoring website server resource usage, CPU load, memory usage, number of website requests, number of website connections, and the like.
  • Step 205 Receive monitoring data and select an appropriate analysis result according to a predetermined policy, and the analysis result is a website source station IP address or a CDN system.
  • Step 206 Send the analysis result to the local DNS server 102.
  • steps 202 and 203 can be implemented if the website source station 101 contains multiple addresses.
  • an address may be selected from a plurality of addresses in accordance with a predetermined policy as the IP address of the website source station. If the website source station 101 contains only one address, then steps 202 and 203 Can be omitted.
  • the address can be directly used as the IP address of the website source station.
  • FIG. 3 is a flowchart of a traffic scheduling method according to an embodiment of the present invention.
  • step 205 may further include the following steps:
  • Step 301 Configure a traffic scheduling policy.
  • the parameters of the scheduling policy may include, but are not limited to, an A record (source station IP), a preset resource load upper limit, and a preset resource load lower limit.
  • Step 302 Timely acquire resource load monitoring data of the website source station 101.
  • the resource load can use a variety of different metrics including, but not limited to, resource percentages, traffic values, and the like.
  • Step 303 Determine whether the resource load exceeds a preset upper limit. If the preset upper limit is exceeded, proceed to step 304 to increase the proportion of the solution to the CDN system, and skip to step 310; if the resource load does not exceed the preset upper limit If the value is reached, go to step 305.
  • Step 305 it is determined whether the ratio of the resolution to the CDNCDN system is 0. If the ratio of the resolution to the CDN system is 0 (ie, the acceleration service is not used), the process goes to step 309 to resolve the domain name to the IP address of the website source station, otherwise skip to Step 306.
  • Step 306 If the resource load is lower than the preset lower limit, reduce the proportion of the resolution to the CDN system in step 307, and skip to step 310. Otherwise, the resource load is between the preset upper limit value and the lower limit value. In step 309, the existing domain name resolution ratio is maintained.
  • the analysis result is selected according to the domain name resolution ratio.
  • the initial resolution ratio can be set to 0, which resolves all domain name resolution requests to the address of the website source station. Then, the resolution ratio is re-determined according to the flow change.
  • the resolution ratio determination method is as follows:
  • R cdn is the ratio of the current resolution to the CDN system
  • R' cdn is the ratio of the last resolution to the CDN system
  • ⁇ R is the amount of change in the resolution to the CDN system.
  • ⁇ R has various determination methods, for example, it can be determined by the user or is a preset value of the system.
  • ⁇ R can also be calculated from the resource load of the source station, such as flow:
  • the resolution ratio needs to be increased.
  • the resolution ratio is reduced.
  • F is the lower limit of the preset limit traffic to your site source station
  • F upper limit is preset limit traffic website source station.
  • the traffic scheduling policy may be configured for different ISP lines and different geographical locations in step 301.
  • the parameters of the traffic scheduling policy may also include an ISP line, a region, a domain name (or a domain name group).
  • different ISP lines are allowed to share the same policy.
  • the website resource usage guarantee system 104 of the present embodiment may include a DNS module 401, an acquisition module 402, an identification module 403, a monitoring module 404, a resource module 405, and a scheduling module 406.
  • the DNS module 401 is responsive to the local DNS server 102 (refer to FIG. 1) request and returns the result to the local DNS server 102.
  • the obtaining module 402 is configured to obtain an IP address of the local DNS server 102.
  • the identification module 403 is configured as an optional module, and may be configured when the website source station has multiple addresses, and is used to obtain geographic location and ISP information according to the foregoing IP address.
  • the monitoring module 404 is configured to monitor the resource load situation of the website source station 101.
  • the resource module 405 is configured to manage website source station resources, set a monitoring mode, and save related monitoring configuration information.
  • the scheduling module 406 performs processing analysis based on existing information and policies, and gives appropriate analysis results.
  • the website resource usage assurance system 104 can be implemented as software, hardware, or a combination of hardware and software.
  • the embodiments described herein may be in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), A field programmable gate array (FPGA), processor, controller, microcontroller, microprocessor, other electronic device for performing the above functions, or a selected combination of the above devices is implemented. In some cases, such embodiments may be implemented by a controller.
  • the website resource usage assurance system 104 can include various software modules as above, stored in a server's memory, and loaded into memory for processor implementation. Or each software module may also be distributedly stored in the memory of multiple servers and loaded into the memory of the respective server for implementation by the processor. These servers coordinate the network to implement the functions of the website resource utilization guarantee system 104.
  • the scheduling module 406 is responsible for coordinating the work of the plurality of modules. Specifically, the scheduling module 406 can issue a monitoring task to the monitoring module 404.
  • the scheduling module 406 itself collects the network
  • the server of the station source station 101 runs data, and determines the domain name resolution rule according to the scheduling policy.
  • the domain name resolution rule includes the domain name resolution result and the corresponding resolution allocation ratio.
  • the scheduling module 406 can deliver the domain name resolution rule to the DNS module 401.
  • the monitoring mode set by the resource module 405 is, for example, an SNMP (Simple Network Management Protocol) mode or an embedded monitoring agent mode.
  • SNMP Simple Network Management Protocol
  • embedded monitoring agent mode for example, an SNMP (Simple Network Management Protocol) mode or an embedded monitoring agent mode.
  • FIG. 5 is a structural block diagram of a scheduling module according to an embodiment of the present invention.
  • the scheduling module 406 can include a task management unit 501 and an instruction unit 502.
  • the task management unit 501 is configured to manage policies, select appropriate resources, allocate monitoring tasks, and obtain access traffic of the website source station 101.
  • the command unit 502 can use the scheduling policy to calculate the resolution ratio according to the website source station access traffic, etc., and generate the analysis command and send it to the DNS module 401.
  • the DNS module 401 of the website resource usage guarantee system 104 is an authorized DNS server of the domain name www.a.com, and the alias of the DNS module 401 of www.a.com is www.a.lxdns.com.
  • the website www.a.com has registered the content service at the CDN service provider, and the CDN service provider has assigned the service domain name of www.a.cdn.com for the website.
  • the configuration of the policy and monitoring information can be done by the website operator. Assume that the scheduling policy configured by www.a.com is as shown in Table 1 below:
  • the browser requests the local DNS server 102 for resolution of www.a.com, and the local DNS server 102 sends the request to the authoritative DNS server 103, the authoritative DNS server. 103 returns the alias www.a.lxdns.com of the website www.a.com to the local DNS server 102, and the local DNS server 102 initiates the acquisition of www.a.lxdns.com from the DNS module 401 of the website resource usage guarantee system 104. IP address, DNS module 401 The IP address of the local DNS server 102 is obtained first, and the corresponding geographical location and ISP information are queried according to the IP address. It is assumed that the geographical location of the local DNS server 102 is Fujian and the ISP is "China Telecom".
  • the scheduling module 406 automatically sends the monitoring task for resource monitoring to 2.2.2.1 and 2.2.2.2 to the monitoring module 404 according to the scheduling policy table, and queries the monitoring result, and makes the following judgments according to the policy:
  • R cdn 0 +
  • /8Gbps*100% 12.5%.
  • www.a.lxdns.com will be resolved to www.a.cdn.com in a proportion of 12.5%, and 87.5% of the proportions will be resolved to IP addresses 2.2.2.1 and 2.2.2.2;
  • R cdn 1/2-
  • /6Gbps*100% 16.7%.
  • www.a.lxdns.com will be resolved to www.a.cdn.com at a rate of 16.7%, and the proportion of 83.3% will be resolved to IP addresses 2.2.2.1 and 2.2.2.2.
  • this example guides the traffic by controlling the domain name resolution, and preferentially flows the traffic to the resources of the website source station 101.
  • the traffic is directed to the CDN acceleration service in time, and the website source station 101 is lightened. Load.
  • the method and system for securing the website resource usage rate of the present invention organically combines the CDN service network with the resources of the website operator through intelligent scheduling, preferentially uses the website resources, and monitors in real time.
  • Website resource usage After the website resource usage rate exceeds the set value, modify the DNS resolution ratio, and gradually guide the traffic to the CDN service network to reduce the load pressure of the source station; when the website traffic access traffic is lower than the lower limit of the set value, modify the DNS resolution ratio. The traffic is then gradually guided back to the website to improve the website resource usage rate.
  • the website resource usage rate can be intelligently controlled within a reasonable range without degrading the access quality.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明涉及一种使用内容分发网络的网站的资源使用率保障方法和系统。该方法包括以下步骤：接收本地域名服务器发送的域名解析请求；监测该域名解析请求所对应的网站源站的资源负载；利用监测数据并根据预定策略决定该域名解析请求的结果为该网站源站的地址和内容分发网络系统之一；以及将域名解析结果发送该给本地域名服务器。

Description

使用内容分发网络的网站的资源使用率保障方法和系统 技术领域
本发明涉及网络技术领域，尤其是涉及一种使用内容分发网络的网站的资源使用率保障方法和系统。
背景技术
DNS(Domain Name System，域名系统)系统用于命名组织到域层次结构中的计算机和网络服务，是Internet的重要基础服务系统。DNS的出现，能够使用户更方便的访问互联网，而不用去记住能够被机器直接读取的IP数串。域名与IP数串的转换工作称为域名解析，执行此项功能的主机被称为DNS服务器。当用户在应用程序中输入域名时，DNS服务可将此域名解析成与之对应的其他相关信息，如IP地址，完成网站访问。
CDN(Content Distribute Network，内容分发网络)的任务主要是内容从源站尽可能快的传递到用户端。CDN的基本思想就是尽可能避开互联网上有可能影响数据传输速度和稳定性的瓶颈和环节，使内容传输得更快、更好。CDN通过在网络各处放置边缘节点服务器，能够实时地根据网络流量和各边缘节点的负载情况、以及到用户的距离和响应时间等综合信息将用户的访问请求重定向至离用户最近且最好的边缘节点上。CDN在现有网络架构上增加一个全局调度层，将源站内容分发到最接近用户的网络边缘，使用户可以就近取得所需内容。由此CND可解决Internet网络拥挤的状况，提高用户访问网站的响应速度，解决因源站出口网络带宽小、用户访问量大、网点分布不均、复杂的运营商网络、用户接入网络带宽小所造成的用户访问网站响应速度慢的问题。
依靠CDN虽然可以提高网站的访问速度，改善用户体验，却可能会降低网站资源使用率，极端情况下甚至会出现网站回源流量越来越小，大部分流量均通过CDN网络来承载的情况。现有CDN供应商提供的CDN服务模式仅有“使用加速”，“不使用加速”两种模式，“不使用加速”无法保证网站访问质量，“使用加速”虽能保障访问质量，但导致在大部分情况下网站资源使用率会处于一个较低的水平，这并非网站运营者所期望的。
发明内容
本发明所要解决的技术问题是提供一种使用内容分发网络的网站的资源使用率保障方法和系统，其能够兼顾网站资源使用率及访问质量。
本发明为解决上述技术问题而采用的技术方案是一种使用内容分发网络的网站的资源使用率保障方法，包括以下步骤：接收本地域名服务器发送的域名解析请求；监测该域名解析请求所对应的网站源站的资源负载；利用监测数据并根据预定策略决定该域名解析请求的结果为该网站源站的地址和内容分发网络系统之一；以及将域名解析结果发送给该本地域名服务器。
在本发明的一实施例中，该方法在该内容分发网络系统之外执行，且该解析结果为该内容分发网络系统的域名。
在本发明的一实施例中，该方法在该内容分发网络系统之内执行，且该解析结果为该内容分发网络系统的边缘服务器之一的地址。
在本发明的一实施例中，利用监测数据并根据预定策略决定该域名解析请求的结果为该网站源站的地址和该内容分发网络系统之一的步骤包括：选择调度策略，该调度策略的参数包括该资源负载的预设上限和预设下限、以及网站源站地址；根据该资源负载及所选调度策略进行决策，其中：在初始时将该域名解析请求解析为该网站源站的地址；当该网站源站的资源负载位于该预设上限与该预设下限之间时，维持解析比例不变；当该网站源站的资源负载超过该预设上限时，则提高解析比例；当该网站源站的资源负载低于该预设下限时，降低解析比例，其中解析比例是将域名解析请求解析至内容分发网络系统的比例。
在本发明的一实施例中，所述解析比例的变化量是预设的。
在本发明的一实施例中，所述解析比例的变化量△R是根据以下方式计算：当网站源站的资源负载超过预设上限，提高解析比例时，△R＝|Fnow-F上限|/F上限；当网站源站的资源负载低于预设下限，降低解析比例时，△R＝|Fnow-F下限|/F上限；其中Fnow为当前时刻网站源站的资源负载，F下限是网站源站的资源负载预设下限，F上限是网站源站的资源负载预设上限。
在本发明的一实施例中，该网站源站包括单个地址，且利用监测数据并根 据预定策略决定该域名解析请求的结果时，该网站源站的地址为该单个地址。
在本发明的一实施例中，该网站源站包括多个地址，该方法还包括：根据该域名解析请求获取该本地域名服务器的地址；根据该地址识别该本地域名服务器的地理位置及服务提供商；且其中利用监测数据并根据预定策略决定该域名解析请求的结果时，该网站源站的地址为该多个地址中的一个或多个。
在本发明的一实施例中，上述方法还包括根据该本地域名服务器的地理位置和服务提供商选择对应的调度策略，该调度策略的参数包括：服务提供商线路，地域、域名或域名组，网站源站地址。
本发明还提出一种使用内容分发网络的网站的资源使用率保障系统，包括：域名系统模块，接收域名解析请求；监测模块，监测该域名解析请求所对应的网站源站的资源负载；以及调度模块，利用监测数据并根据预定策略决定该域名解析请求的结果为该网站源站的地址和内容分发网络系统之一。
在本发明的一实施例中，上述系统是独立于该内容分发网络系统，且该解析结果为该内容分发网络系统的域名。
在本发明的一实施例中，上述系统是配置于该内容分发网络系统之内，且该解析结果为该内容分发网络系统的边缘服务器之一的地址。
在本发明的一实施例中，该调度模块被配置为执行以下步骤：配置调度策略，该调度策略的参数包括资源负载的预设上限和预设下限、以及网站源站地址；根据该资源负载及所选调度策略进行决策，其中：在初始时将该域名解析请求解析为该网站源站的地址；当该网站源站的资源负载位于该预设上限与该预设下限之间时，维持解析比例不变；当该网站源站的资源负载超过该预设上限时，则提高解析比例；当该网站源站的资源负载低于该预设下限时，降低解析比例，其中解析比例是将域名解析请求解析至内容分发网络系统的比例。
在本发明的一实施例中，所述解析比例的变化量是预设的。
在本发明的一实施例中，所述解析比例的变化量是根据以下方式计算：当网站源站的资源负载超过预设上限，提高解析比例时，△R＝|Fnow-F上限|/F上限；当网站源站的资源负载低于预设下限，降低解析比例时，△R＝|Fnow-F下限|/F上限；其中Fnow为当前时刻网站源站的资源负载，F下限是网站源站的资源负载预设下限，F上限是网站源站的资源负载预设上限。
在本发明的一实施例中，该网站源站包括多个地址，该系统还包括：获取模块，根据该域名解析请求获取本地域名服务器的地址；识别模块，根据该地址识别本地域名服务器的地理位置及服务提供商；且该调度模块决定该域名解析请求的结果时，该网站源站的地址为多个地址中的一个或多个。
在本发明的一实施例中，该调度模块被配置为根据该本地域名服务器的地理位置和服务提供商选择对应的调度策略，该调度策略的参数包括：服务提供商线路，以及地域、域名或域名组。
在本发明的一实施例中，上述系统还包括资源模块，用于管理网站源站的资源，设定监测模式，并保存相关的监测配置信息。
本发明还提出一种使用内容分发网络的网站的资源使用率保障系统，包括：用于接收域名解析请求的模块；用于监测该域名解析请求所对应的网站源站的资源负载的模块；以及用于利用监测数据并根据预定策略决定该域名解析请求的结果为该网站源站的地址和内容分发网络系统之一的模块。
本发明的网站资源使用率保障方法和系统，是通过智能调度将CDN服务网络与网站运营商自身的资源有机结合起来，优先使用网站资源，并实时监测网站资源使用情况。当网站资源使用率超过设定值之后，修改DNS解析比例，将流量逐步引导至CDN服务网络，减轻源站负载压力；当网站流量访问流量低于设定值下限时，修改DNS解析比例，将流量再逐步引导回网站，提高网站资源使用率。通过本方法和系统，能够在不降低访问质量的前提下智能地将网站资源使用率控制在一个合理范围之内。
附图概述
本发明的特征、性能由以下的实施例及其附图进一步描述。
图1是本发明一实施例的网络实施环境示意图。
图2是本发明一实施例的网站资源使用率保障方法的流程图。
图3是本发明一实施例的流量调度方法流程图。
图4是本发明一实施例的网站资源使用率保障系统逻辑框图。
图5是本发明一实施例的调度模块结构框图。
图6是本发明另一实施例的网络实施环境示意图。
图7是根据本发明一实施例的CDN网络拓扑图。
本发明的实施方式
网站资源使用率主要体现在访问量、带宽占用等几个指标，保障网站资源使用率处于一个合理的范围是网站运营者所追求的目标。如果网站资源使用率过低，IT基础资源得不到有效配置，使网站运营成本相对提高；如果网站资源使用率过高则会导致服务响应缓慢，降低用户体验，导致客户流失。
CDN(Content Distribute Network，内容分发网络)虽然可以提高网站的访问速度，改善用户体验，却不考虑网站资源使用率。因而使用CDN可能会降低网站资源使用率，使大部分流量均通过CDN网络来承载。
本发明的实施例提出一种保障使用CDN的网站的资源使用率的方法，其引入对网站的资源使用率的监测和调节。
图1是本发明一实施例的网络实施环境示意图。参考图1所示，网络实施环境100包括网站源站101、本地DNS(Domain Name System，域名系统)服务器102、权威DNS服务器103、网站资源使用率保障系统104、CDN系统105以及客户端106。网站源站101由一个到多个服务器组成，是网站内容存放主体，可以向多个客户端106提供内容。网站源站101可以具有一个或多个地址。每个地址可以对应一个服务器，也可以对应多个服务器。由于流量负载的限制，使用CDN系统105来部分地代替网站源站101，响应部分客户端106的内容请求。CDN系统的网络拓扑图可以参考图7所示。CDN系统105中配置许多地理上分散的边缘节点服务器或集群710，以就近向客户端106提供内容。本地DNS服务器102负责接收客户端106发送的域名解析请求，并将客户端106的请求转发到目的站点。在本实施例中，目的站点为网站源站101的服务器或者CDN系统105，取决于网站资源使用率保障系统104的解析结果。当然，当CDN系统105为目的站点时，其会进一步将请求转发到边缘节点服务器。本地DNS服务器102会将域名解析请求转发给权威DNS服务器103。权威DNS服务器103可以接收本地DNS服务器102的域名解析请求，并将网站资源使用率保障系统104的域名发送给本地DNS服务器102。本地DNS服务器102可以转为向网站资源使用率保障系统104请求解析域名。网站资源使用率保障系统104 用于接收本地DNS服务器102的域名解析请求，监测网站源站101的资源使用情况，且根据策略及监测数据选择网站源站101或CDN系统105作为目的站点，并将结果发送给本地DNS服务器102。
具体地说，可以为网站源站101设置合适流量范围，作为资源负载的表征。合适流量范围可以由预设流量上限和预设流量下限来界定。网站资源使用率保障系统104获取网站源站101的流量数据，然后根据该流量数据及所选调度策略进行决策。当网站源站101的流量低于预设流量上限时，表明网站源站101的资源使用率在可允许范围内，将本地DNS服务器102发来的域名解析请求解析为网站源站101的地址；当网站源站101的流量不低于(等于或大于)预设流量上限时，表明网站源站101的资源使用率过高，则提高解析比例，解析比例是指将域名解析请求解析至CDN系统105的比例。当网站源站101的流量若回落并低于预设流量下限时，表明网站源站101的资源使用率过低，则降低将域名解析请求解析至CDN系统105的比例；如果网站源站101的流量未回落至预设流量下限，则维持解析比例不变。也就是说，网站资源使用率保障系统104优先将流量引导至网站源站101，除非网站源站101的资源使用率过高。
图6是本发明另一实施例的网络实施环境示意图。参考图6所示，网络实施环境600包括网站源站601、本地DNS服务器602、权威DNS服务器603、网站资源使用率保障系统604、CDN系统605以及客户端606。图6所示实施例于图1的不同之处在于，网站资源使用率保障系统604配置在CDN系统605内而不是独立于CDN系统605。相应地，在本实施例中，目的站点为网站源站601的服务器或者CDN系统605内的边缘节点服务器，取决于网站资源使用率保障系统604的解析结果。
也就是说，网站资源使用率保障系统604会在域名解析到CDN系统605时，进一步决定应该解析到哪一边缘服务器或集群。具体来说，图7示出根据本发明一实施例的网络实施环境，参考图7所示，CDN系统605内可包括一个中心决策服务器701，多个中心调度服务器702，以及多个边缘服务器集群710，这些装置通过互联网连接在一起。各边缘服务器集群710中配置有多个服务器711。许多客户端720可以连接到CDN系统605，从而获得所请求的内容。通过中心决策服务器701和中心调度服务器702的配合，可以根据客户端所在的地 理位置及请求内容，向客户端返回一个带有边缘服务器集群的跳转URL(Uniform Resource Locator，统一资源定位器)。
本实施例在流量引导方面的策略可以和前一实施例相同，下文将一并予以描述。
图2是本发明一实施例的网站资源使用率保障方法的流程图。参考图2所示，本实施例的网站资源使用率保障方法可由网站资源使用率保障系统104执行，其包括以下流程：
步骤201，接收本地DNS服务器102发送的域名解析请求。
本地DNS服务器102的域名解析请求可能是通过权威DNS服务器103提供的子域名获得。
步骤202，根据域名解析请求获取本地DNS服务器102的IP地址。
步骤203，利用IP地址识别出本地DNS服务器102的地理位置及ISP(网络服务提供商)信息。
步骤204，监测网站源站101的资源负载。
例如，监测包括但不限于监测网站服务器或集群的性能负载及流量情况。更具体地说，例如监测网站服务程序资源使用率，CPU负载情况、内存使用情况、网站请求数、网站连接数等。
步骤205，接收监测数据并根据预定策略选择合适的解析结果，解析结果是网站源站IP地址或CDN系统。
对于图1所示实施例来说，由于网站资源使用率保障系统104的流程在CDN系统之外执行，当解析结果CDN系统时，实际指向的是CDN系统的域名，即CDN系统的服务商提供的域名。
对于图2所示实施例来说，由于网站资源使用率保障系统104的流程在CDN系统之内执行，当解析结果CDN系统时，实际指向的是CDN系统的边缘服务器的地址。
步骤206，将解析结果发送给本地DNS服务器102。
需要指出的是，步骤202和203可以在网站源站101包含多个地址的情况下才实施。在这一情况下，在步骤205可以根据预定策略从多个地址中选择一个地址，作为网站源站的IP地址。如果网站源站101仅包含一个地址，则步骤202和203 可以省略。在步骤205可以直接以该地址作为网站源站的IP地址。
图3是本发明一实施例的流量调度方法流程图。参考图3所示，在一实施例中，步骤205可进一步包括如下步骤：
步骤301，配置流量调度策略。
调度策略的参数可以包括但不限于A记录(源站IP)、预设资源负载上限以及预设资源负载下限。
步骤302，定时获取网站源站101的资源负载监测数据。在此，资源负载可以使用各种不同的量度，包括但不限于资源百分比，流量数值等。
步骤303，判断资源负载是否超过预设上限值，若超过预设上限值，则进入步骤304，提高解析至CDN系统的比例，并跳至步骤310；若资源负载未超过预设上限值，则跳至步骤305。
步骤305，判断解析至CDNCDN系统的比例是否为0，若解析至CDN系统的比例为0(即未使用加速服务)，跳至步骤309，将域名解析成网站源站的IP地址，否则跳至步骤306。
步骤306，若资源负载低于预设下限值，则在步骤307降低解析至CDN系统的比例，并跳至步骤310，否则意味着资源负载位于预设上限值和下限值之间，在步骤309维持现有域名解析比例不变。
在步骤310，根据域名解析比例选择解析结果。
初始解析比例可以设为0，即将所有域名解析请求都解析为网站源站的地址。然后再根据流量变化重新确定解析比例。
在一实施例中，解析比例确定方法如下：
Rcdn＝R'cdn±△R    (公式1)
Rcdn为当前解析至CDN系统的比例，R'cdn为上一次解析至CDN系统的比例，△R表示解析至CDN系统比例变化量。
△R有多种确定方法，例如可以由用户确定或者为系统预设值。
△R还可以通过源站的资源负载，例如流量计算得出：
当源站流量超过预设流量上限需提高解析比例时，
△R＝|Fnow-F上限|/F上限    (公式2)
源站流量低于预设流量下限需降低解析比例时，
△R＝|Fnow-F下限|/F上限    (公式3)
其中Fnow为当前时刻网站源站流量，F下限是网站源站的预设流量下限，F上限是网站源站的预设流量上限。
在较佳实施例中，在步骤301中可以为不同的ISP线路和不同地理位置的请求配置流量调度策略，这样，流量调度策略的参数还可包括ISP线路、地域、域名(或域名组)。在此，允许不同的ISP线路共用相同的策略。
图4是本发明一实施例的网站资源使用率保障系统逻辑框图。参考图4所示，本实施例的网站资源使用率保障系统104可包括DNS模块401、获取模块402、识别模块403、监测模块404、资源模块405以及调度模块406。DNS模块401用于响应本地DNS服务器102(参考图1)请求，并将结果返回给本地DNS服务器102。获取模块402用于获取本地DNS服务器102的IP地址。识别模块403作为一个可选模块，可以在网站源站具有多个地址时配置，用于根据前述IP地址获取地理位置及ISP信息。监测模块404用于监测网站源站101的资源负载情况。资源模块405用于管理网站源站资源，设定监测模式，并保存相关监测配置信息。调度模块406根据现有信息及策略进行处理分析，给出合适解析结果。
在本发明的实施例中，网站资源使用率保障系统104可实施为软件、硬件或软硬件的结合。对于硬件实施而言，本文中所描述的实施例可在一个或多个专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理器件(DAPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、处理器、控制器、微控制器、微处理器、用于执行上述功能的其它电子装置或上述装置的选择组合来加以实施。在部分情况下，这类实施例可以通过控制器进行实施。对软件实施而言，网站资源使用率保障系统104可以包括如上的各个软件模块，其储存在一个服务器的存储器中，并可载入到内存中供处理器实施。或者各个软件模块，也可以分布地储存在多个服务器的存储器中，并可载入到各自服务器的内存中供处理器实施。这些服务器之间通过网络协调来共同实现网站资源使用率保障系统104的功能。
在一实施例中，可由调度模块406负责协调多个模块的工作。具体地说，调度模块406可以向监测模块404下发监测任务。调度模块406本身会采集网 站源站101的服务器运行数据，并根据调度策略确定域名解析规则。域名解析规则包括域名解析结果及对应解析分配比例。调度模块406可将域名解析规则下发至DNS模块401。
举例来说，资源模块405设定的监测模式例如是SNMP(Simple Network Management Protocol，简单网络管理协议)模式或内嵌监测代理程序模式。
图5是本发明一实施例的调度模块结构框图。参考图5所示，调度模块406可包括任务管理单元501和指令单元502。如图5所示，任务管理单元501用于管理策略，选取合适资源，分配监测任务及获取网站源站101的访问流量。指令单元502可利用调度策略，根据网站源站访问流量等计算出解析比例，生成解析指令并下发给DNS模块401。
下面举例说明上述方法的具体实现过程，假设我们要保障域名为www.a.com的资源使用率及访问质量。网站资源使用率保障系统104的DNS模块401为域名www.a.com的授权DNS服务器，www.a.com在DNS模块401的别名为www.a.lxdns.com。网站www.a.com已在CDN服务商处注册内容服务，CDN服务商分配www.a.cdn.com的服务域名供网站使用。策略及监测信息的配置可以由网站运营商来完成，假设www.a.com配置的调度策略如下表1所示：
Figure PCTCN2014095483-appb-000001
表1
当用户在自己的浏览器中输入网址www.a.com时，浏览器向本地DNS服务器102请求对www.a.com的解析，本地DNS服务器102将请求发到权威DNS服务器103，权威DNS服务器103将网站www.a.com的别名www.a.lxdns.com返回给本地DNS服务器102，本地DNS服务器102向网站资源使用率保障系统104的DNS模块401发起获取www.a.lxdns.com的IP地址，DNS模块401 先获取本地DNS服务器102的IP地址，并根据IP地址查询到对应的地理位置和ISP信息，假设本地DNS服务器102的地理位置是福建，ISP为“中国电信”。
调度模块406根据调度策略表，自动将对2.2.2.1，2.2.2.2进行资源监测的监测任务下发到监测模块404，并查询监测结果，根据策略做出以下几种判断：
当网站源站流量超过预设流量上限8Gbps时，假定当前网站源站流量为9Gbps且www.a.lxdns.com均解析至源站，根据所述公式1及公式2可得：
Rcdn＝0+|9Gbps–8Gbps|/8Gbps*100％＝12.5％。
则此时www.a.lxdns.com将按12.5％的比例解析至www.a.cdn.com,87.5％的比例解析至IP地址2.2.2.1及2.2.2.2；
当网站源站流量低于预设流量下限6Gbps时，假定当前测得的网站源站流量为4Gbps，且www.a.lxdns.com按60％的比例解析至www.a.cdn.com。根据所述公式1及公式3可得：
Rcdn＝1/2-|4Gbps–6Gbps|/6Gbps*100％＝16.7％。
则此时www.a.lxdns.com将按16.7％的比例解析至www.a.cdn.com，83.3％的比例解析至IP地址2.2.2.1及2.2.2.2。
因此这一实例通过对域名解析的控制来引导流量，使流量优先流向网站源站101的资源，当网站源站101的资源无法满足需求时及时将流量引导至CDN加速服务，减轻网站源站101的负载。
从本发明的上述实施例可以看出，本发明的网站资源使用率保障方法和系统，是通过智能调度将CDN服务网络与网站运营商自身的资源有机结合起来，优先使用网站资源，并实时监测网站资源使用情况。当网站资源使用率超过设定值之后，修改DNS解析比例，将流量逐步引导至CDN服务网络，减轻源站负载压力；当网站流量访问流量低于设定值下限时，修改DNS解析比例，将流量再逐步引导回网站，提高网站资源使用率。通过本方法和系统，能够在不降低访问质量的前提下智能地将网站资源使用率控制在一个合理范围之内。

Claims (19)

  1. 一种使用内容分发网络的网站的资源使用率保障方法，包括以下步骤：
    接收本地域名服务器发送的域名解析请求；
    监测该域名解析请求所对应的网站源站的资源负载；
    利用监测数据并根据预定策略决定该域名解析请求的结果为该网站源站的地址和内容分发网络系统之一；
    将域名解析结果发送给该本地域名服务器。
  2. 如权利要求1所述的方法，其特征在于，该方法在该内容分发网络系统之外执行，且该解析结果为该内容分发网络系统的域名。
  3. 如权利要求1所述的方法，其特征在于，该方法在该内容分发网络系统之内执行，且该解析结果为该内容分发网络系统的边缘服务器之一的地址。
  4. 如权利要求1所述的方法，其特征在于，利用监测数据并根据预定策略决定该域名解析请求的结果为该网站源站的地址和该内容分发网络系统之一的步骤包括：
    选择调度策略，该调度策略的参数包括该资源负载的预设上限和预设下限、以及网站源站地址；
    根据该资源负载及所选调度策略进行决策，其中：
    在初始时将该域名解析请求解析为该网站源站的地址；
    当该网站源站的资源负载位于该预设上限与该预设下限之间时，维持解析比例不变；
    当该网站源站的资源负载超过该预设上限时，则提高解析比例；
    当该网站源站的资源负载低于该预设下限时，降低解析比例，其中解析比例是将域名解析请求解析至内容分发网络系统的比例。
  5. 如权利要求4所述的方法，其特征在于，所述解析比例的变化量是预设的。
  6. 如权利要求4所述的方法，其特征在于，所述解析比例的变化量ΔR是根据以下方式计算：
    当网站源站的资源负载超过预设上限，提高解析比例时，
    ΔR＝|Fnow-F上限|/F上限
    当网站源站的资源负载低于预设下限，降低解析比例时，
    ΔR＝|Fnow-F下限|/F上限
    其中Fnow为当前时刻网站源站的资源负载，F下限是网站源站的资源负载预设下限，F上限是网站源站的资源负载预设上限。
  7. 如权利要求1所述的方法，其特征在于，该网站源站包括单个地址，且利用监测数据并根据预定策略决定该域名解析请求的结果时，该网站源站的地址为该单个地址。
  8. 如权利要求1所述的方法，其特征在于，该网站源站包括多个地址，该方法还包括：
    根据该域名解析请求获取该本地域名服务器的地址；
    根据该地址识别该本地域名服务器的地理位置及服务提供商；
    且其中利用监测数据并根据预定策略决定该域名解析请求的结果时，该网站源站的地址为该多个地址中的一个或多个。
  9. 如权利要求8所述的方法，其特征在于，还包括根据该本地域名服务器的地理位置和服务提供商选择对应的调度策略，该调度策略的参数包括：服务提供商线路，地域、域名或域名组，网站源站地址。
  10. 一种使用内容分发网络的网站的资源使用率保障系统，包括：
    域名系统模块，接收域名解析请求；
    监测模块，监测该域名解析请求所对应的网站源站的资源负载；以及
    调度模块，利用监测数据并根据预定策略决定该域名解析请求的结果为该网站源站的地址和内容分发网络系统之一。
  11. 如权利要求10所述的系统，其特征在于，是独立于该内容分发网络系统，且该解析结果为该内容分发网络系统的域名。
  12. 如权利要求10所述的系统，其特征在于，是配置于该内容分发网络系统之内，且该解析结果为该内容分发网络系统的边缘服务器之一的地址。
  13. 如权利要求10所述的系统，其特征在于，该调度模块被配置为执行以下步骤：
    配置调度策略，该调度策略的参数包括资源负载的预设上限和预设下限、以及网站源站地址；
    根据该资源负载及所选调度策略进行决策，其中：
    在初始时将该域名解析请求解析为该网站源站的地址；
    当该网站源站的资源负载位于该预设上限与该预设下限之间时，维持解析比例不变；
    当该网站源站的资源负载超过该预设上限时，则提高解析比例；
    当该网站源站的资源负载低于该预设下限时，降低解析比例，其中解析比例是将域名解析请求解析至内容分发网络系统的比例。
  14. 如权利要求13所述的系统，其特征在于，所述解析比例的变化量是预设的。
  15. 如权利要求13所述的系统，其特征在于，所述解析比例的变化量是根据以下方式计算：
    当网站源站的资源负载超过预设上限，提高解析比例时，
    ΔR＝|Fnow-F上限|/F上限
    当网站源站的资源负载低于预设下限，降低解析比例时，
    ΔR＝|Fnow-F下限|/F上限
    其中Fnow为当前时刻网站源站的资源负载，F下限是网站源站的资源负载预设下限，F上限是网站源站的资源负载预设上限。
  16. 如权利要求10所述的系统，其特征在于，该网站源站包括多个地址，该系统还包括：
    获取模块，根据该域名解析请求获取本地域名服务器的地址；
    识别模块，根据该地址识别本地域名服务器的地理位置及服务提供商；
    且该调度模块决定该域名解析请求的结果时，该网站源站的地址为多个地址中的一个或多个。
  17. 如权利要求16所述的系统，其特征在于，该调度模块被配置为根据该本地域名服务器的地理位置和服务提供商选择对应的调度策略，该调度策略的参数包括：服务提供商线路，以及地域、域名或域名组。
  18. 如权利要求10所述的系统，其特征在于，还包括资源模块，用于管理网站源站的资源，设定监测模式，并保存相关的监测配置信息。
  19. 一种使用内容分发网络的网站的资源使用率保障系统，包括：
    用于接收域名解析请求的模块；
    用于监测该域名解析请求所对应的网站源站的资源负载的模块；以及
    用于利用监测数据并根据预定策略决定该域名解析请求的结果为该网站源站的地址和内容分发网络系统之一的模块。
PCT/CN2014/095483 2014-12-02 2014-12-30 使用内容分发网络的网站的资源使用率保障方法和系统 WO2016086482A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/528,342 US10361902B2 (en) 2014-12-02 2014-12-30 Method and system for guaranteeing resource utilization rate of website using content distribution network
EP14907448.6A EP3244589B1 (en) 2014-12-02 2014-12-30 Method and system for guaranteeing resource utilization rate of website using content distribution network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410720273.3 2014-12-02
CN201410720273.3A CN104363313B (zh) 2014-12-02 2014-12-02 使用内容分发网络的网站的资源使用率保障方法和系统

Publications (1)

Publication Number Publication Date
WO2016086482A1 true WO2016086482A1 (zh) 2016-06-09

Family

ID=52530539

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/095483 WO2016086482A1 (zh) 2014-12-02 2014-12-30 使用内容分发网络的网站的资源使用率保障方法和系统

Country Status (4)

Country Link
US (1) US10361902B2 (zh)
EP (1) EP3244589B1 (zh)
CN (1) CN104363313B (zh)
WO (1) WO2016086482A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112968939A (zh) * 2017-01-05 2021-06-15 创新先进技术有限公司 一种移动端资源加载方法和装置

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106487840A (zh) * 2015-08-27 2017-03-08 中国移动通信集团公司 一种内容服务器的确定方法、平台及调度服务器
CN106301966B (zh) * 2016-10-25 2019-08-06 北京云端智度科技有限公司 一种基于域名的按比例分配流量的方法
CN106992938B (zh) * 2017-05-15 2020-03-31 网宿科技股份有限公司 一种网络流量动态调度分配方法及系统
CN109257451B (zh) * 2017-07-14 2021-10-26 阿里巴巴集团控股有限公司 对应关系解析方法及设备
CN107980217B (zh) * 2017-07-14 2021-06-01 达闼机器人有限公司 获取本地域名服务器地址的方法、装置和权威域名服务器
CN108702397B (zh) * 2017-08-08 2021-07-06 达闼机器人有限公司 一种获取并收集客户端本地dns服务器的方法以及系统
CN110392123B (zh) * 2018-04-23 2022-06-14 阿里巴巴集团控股有限公司 检测出口ip地址的方法、装置和系统
CN111937318B (zh) 2018-05-16 2022-07-08 瑞典爱立信有限公司 频分双工(fdd)系统中存在干扰源时的辐射图修改
CN108881509A (zh) * 2018-05-31 2018-11-23 网宿科技股份有限公司 一种基于httpdns的dns查询方法及装置
CN110719306B (zh) * 2018-07-11 2022-07-05 阿里巴巴集团控股有限公司 一种网络请求限制方法、计算机设备、存储介质
CN109067926A (zh) * 2018-10-11 2018-12-21 平安科技（深圳）有限公司 负载均衡方法、装置、计算机设备及存储介质
CN109412977B (zh) 2018-10-18 2022-05-17 网宿科技股份有限公司 一种域名带宽调节方法及相关设备
US10972576B2 (en) * 2018-11-14 2021-04-06 International Business Machines Corporation Content acceleration for cross-site resources by CDN
US10855596B2 (en) * 2018-11-20 2020-12-01 Microsoft Technology Licensing, Llc Load balancing among multiple endpoint computing systems of a domain
CN109639533B (zh) * 2019-01-08 2022-06-10 深圳市网心科技有限公司 一种区域调度策略的测试方法、系统及终端设备
CN110445886B (zh) * 2019-07-05 2020-11-06 网宿科技股份有限公司 一种实现域名访问加速的方法和系统
CN110401731B (zh) * 2019-07-25 2024-05-07 北京百度网讯科技有限公司 用于分配内容分发节点的方法和装置
CN116366656A (zh) 2019-08-18 2023-06-30 朗德万斯公司 用于形成设备网络的方法及系统
CN110602270B (zh) * 2019-11-01 2022-10-14 北京博睿宏远数据科技股份有限公司 域名解析方法、装置、计算机设备及存储介质
WO2022018466A1 (en) * 2020-07-22 2022-01-27 Citrix Systems, Inc. Determining server utilization using upper bound values
CN114157635B (zh) * 2020-09-07 2023-08-15 中国移动通信集团湖南有限公司 内容分发网络的域名回源方法和装置、设备和存储介质
CN113132479B (zh) * 2021-04-16 2023-05-09 北京百度网讯科技有限公司 流量切换、模型生成方法、装置、设备、存储介质及程序
CN113596105B (zh) * 2021-07-06 2023-12-26 深圳市华曦达科技股份有限公司 内容的获取方法、边缘节点及计算机可读存储介质
CN113608877B (zh) * 2021-08-13 2023-11-10 牙木科技股份有限公司 一种内容商ipv4和ipv6资源池负载均衡调度方法
CN116137624A (zh) * 2021-11-18 2023-05-19 中兴通讯股份有限公司 负载均衡方法、设备及计算机可读存储介质
CN114338705B (zh) * 2021-11-24 2023-12-01 阿里巴巴（中国）有限公司 内容分发网络cdn节点的资源水位控制方法、设备及介质
CN116382809B (zh) * 2023-05-26 2023-10-20 荣耀终端有限公司 应用程序启动方法和电子设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196060A (zh) * 2011-06-15 2011-09-21 北京蓝汛通信技术有限责任公司 一种Cache服务器选择源站的方法和系统
CN102355596A (zh) * 2011-10-11 2012-02-15 浪潮电子信息产业股份有限公司 一种适用于视频服务的缓存服务器部署方法

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7363361B2 (en) * 2000-08-18 2008-04-22 Akamai Technologies, Inc. Secure content delivery system
US8635305B1 (en) * 2001-12-19 2014-01-21 Cisco Technology, Inc. Mechanisms for providing differentiated services within a web cache
US7330880B1 (en) * 2002-04-22 2008-02-12 Network Appliance, Inc. Method and apparatus for reliable download to a network cache while limiting origin server load
US7136922B2 (en) * 2002-10-15 2006-11-14 Akamai Technologies, Inc. Method and system for providing on-demand content delivery for an origin server
US7657622B1 (en) * 2003-12-23 2010-02-02 At&T Intellectual Property Ii, L.P. Unified web hosting and content distribution system and method for assuring predetermined performance levels
US8145908B1 (en) * 2004-10-29 2012-03-27 Akamai Technologies, Inc. Web content defacement protection system
US20080208961A1 (en) * 2007-02-23 2008-08-28 Hostway Corporation Parallel retrieval system
CN101764747B (zh) * 2009-12-24 2012-05-02 北京云快线软件服务有限公司 内容分发网络流量智能调度方法、装置及系统
US8856281B2 (en) * 2010-03-22 2014-10-07 At&T Intellectual Property I, L.P. Internet protocol version 6 content routing
US8504723B2 (en) * 2011-06-15 2013-08-06 Juniper Networks, Inc. Routing proxy for resource requests and resources
CN103297472B (zh) * 2012-03-01 2018-09-04 上海盛大网络发展有限公司 一种应用于内容分发网络的重定向方法及内容分发节点
JP6323163B2 (ja) * 2014-05-16 2018-05-16 富士ゼロックス株式会社 中継装置、システム及びプログラム
US20150370490A1 (en) * 2014-06-24 2015-12-24 Nec Europe Ltd. Optimizing ssd-based content caches in content delivery networks

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196060A (zh) * 2011-06-15 2011-09-21 北京蓝汛通信技术有限责任公司 一种Cache服务器选择源站的方法和系统
CN102355596A (zh) * 2011-10-11 2012-02-15 浪潮电子信息产业股份有限公司 一种适用于视频服务的缓存服务器部署方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112968939A (zh) * 2017-01-05 2021-06-15 创新先进技术有限公司 一种移动端资源加载方法和装置
CN112968939B (zh) * 2017-01-05 2023-12-05 创新先进技术有限公司 一种移动端资源加载方法和装置

Also Published As

Publication number Publication date
US10361902B2 (en) 2019-07-23
US20170331667A1 (en) 2017-11-16
EP3244589B1 (en) 2019-09-18
CN104363313A (zh) 2015-02-18
EP3244589A1 (en) 2017-11-15
EP3244589A4 (en) 2018-07-18
CN104363313B (zh) 2018-09-18

Similar Documents

Publication Publication Date Title
WO2016086482A1 (zh) 使用内容分发网络的网站的资源使用率保障方法和系统
CN112087312B (zh) 一种提供边缘服务的方法、装置和设备
US10757037B2 (en) Method and system for dynamic scheduling and allocation of network traffic
US20190182351A1 (en) Route selection method and system, network acceleration node, and network acceleration system
KR101019982B1 (ko) 그리드 컴퓨팅 인프라구조에서의 최적화된 데이터 다운로드 방법과, 다운로드 데이터를 업로드, 분배, 관리 및 제어하는 방법과, 컴퓨터 판독가능한 기록 매체와, 장치
JP5150769B2 (ja) 要求ルーティングおよびクライアントロケーション情報を利用したルーティング情報の更新
US9158586B2 (en) Systems and methods for managing cloud computing resources
CA2699852C (en) A method and system for client-side scaling of web server farm architectures in a cloud data center
CN103825975B (zh) Cdn节点分配服务器及系统
US20040073596A1 (en) Enterprise content delivery network having a central controller for coordinating a set of content servers
US20150236962A1 (en) Method and system for using dynamic bandwidth detection to drive quality of service control refinement
JP2022521839A (ja) マルチクラスタイングレス
US9032081B1 (en) System and method for load balancing cloud-based accelerated transfer servers
WO2016074323A1 (zh) 内容分发网络的http调度系统和方法
US10541901B2 (en) Methods, systems and computer readable media for optimizing placement of virtual network visibility components
US20210352138A1 (en) Software defined wide area network uplink selection for a cloud service
WO2015039475A1 (zh) 一种域名解析方法、服务器及系统
US20140143427A1 (en) Providing Resources in a Cloud
JP2005182641A (ja) 動的負荷分散システム及び動的負荷分散方法
WO2011075899A1 (zh) 实现多web应用请求调度的方法、装置及系统
CN109120953B (zh) 基于sdn及ec技术的自适应流视频处理系统及方法
US9826066B2 (en) System for dynamic selection and application of TCP congestion avoidance flavors
JP2011180820A (ja) データ転送管理装置、データ転送管理方法およびデータ転送管理プログラム
JP2012169789A (ja) 負荷分散サーバ及びサーバ選択方法及びサーバ選択プログラム
JP2013538383A (ja) 複数基準の選択を有するトポロジサーバを用いて通信アーキテクチャにわたって分散されたノードのネットワークへのアクセス

Legal Events

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

Ref document number: 14907448

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15528342

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014907448

Country of ref document: EP