Abnormal processing method and device for content distribution network and content distribution network
By configuring exclusive service addresses for content providers, the problem of inability to timely locate and defend against cache server abnormalities in the content distribution network is solved, and the stability of the service and the timely handling of abnormal traffic is achieved.
Patent Information
- Application Number
- CN202010125892.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-02-27
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-02-27
AI Technical Summary
In the content distribution network, when an exception occurs in a cache server, if it suffers from a DDoS attack, it will not be able to locate the attacked content provider in time, resulting in the inability to defend in time and affect the services of other content providers.
By configuring a service address associated with the content provider only for the provider, the cache server uses the service address to distribute content to the provider, when an exception is detected, quickly locate the target content provider and switch the abnormal traffic to other caches. Server, realize timely defense and processing.
It realizes service stability and availability of the cache server, prevents abnormal traffic in a timely manner, and avoids service interruptions caused by cache server exceptions.
Smart Images

Figure CN113315646B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of content distribution networks, and in particular to an exception handling method and device for content distribution networks, and a content distribution network. Background Art
[0002] With the rapid development of network communication technology and the increasing richness of the information it carries, the Internet has become an important infrastructure of human society, and a large number of content providers provide content and services to users through the network.
[0003] In order to speed up users' access to their content, content providers usually choose to use content distribution networks. Content delivery networks (CDNs) refer to a computer network system that is interconnected through the Internet. Using the cache server closest to each user, content such as music, pictures, videos, applications and other files can be sent to users faster and more reliably, avoiding access delays caused by network congestion, regions, operators and other factors, effectively improving download speeds, reducing response times, and providing a smooth user experience.
[0004] Among them, the cache server provides content distribution services via IP addresses. Due to the limited IP address resources, a cache server usually uses only one IP address to provide services to many content providers. In this case, if the cache server is abnormal, such as being attacked by a distributed denial of service (DDoS) attack that only targets the IP address, it is impossible to find the attacked content provider in time because it does not contain any domain name information, and it is even more impossible to defend in time. At the same time, the cache server's services to other content providers will also be affected.
[0005] Therefore, it is desirable to provide an exception handling solution for a content distribution network to solve the problems that when an exception occurs in a cache server, the attacked content provider cannot be located in time and defense cannot be provided in time. Summary of the invention
[0006] To this end, the embodiments of the present invention provide an exception handling method and device for a content distribution network and a content distribution network, in an effort to solve or at least alleviate the above problems.
[0007] According to one aspect of an embodiment of the present invention, there is provided an exception handling method for a content distribution network, the content distribution network comprising a cache server for distributing content and a scheduling server for resolving domain names, the cache server using a service address associated with a content provider to distribute content to the content provider, the method comprising: when an exception is detected in a first cache server, determining a target content provider corresponding to the exception; and sending a service update instruction to the scheduling server, the service update instruction instructing the scheduling server to point the scheduling domain name of the target content provider to a second cache server, the second cache server replacing the first cache server to distribute content to the target content provider.
[0008] Optionally, the exception handling method according to the embodiment of the present invention further includes: receiving access information of each cache server in the content distribution network; and monitoring whether an exception occurs in each cache server based on the access information.
[0009] Optionally, in the exception handling method according to an embodiment of the present invention, the cache server has at least one service address, the exception includes an exception in access to the service address, and the step of determining the target content provider corresponding to the exception includes: determining the first service address of the first cache server corresponding to the exception; determining the target content provider associated with the first service address.
[0010] Optionally, in the exception handling method according to the embodiment of the present invention, the step of determining the target content provider associated with the first service address includes: determining a source server domain name of the target content provider associated with the first service address.
[0011] Optionally, the exception handling method according to the embodiment of the present invention further includes: determining a second cache server to replace the first cache server based on the exception.
[0012] Optionally, in the exception handling method according to an embodiment of the present invention, the scheduling domain name includes the total scheduling domain name corresponding to the target content provider, the service update instruction includes the first service address, the second service address and the total scheduling domain name of the target content provider, the first cache server uses the first service address to distribute content to the target content provider, and the second cache server uses the second service address to distribute content to the target content provider.
[0013] Optionally, in the exception handling method according to an embodiment of the present invention, the scheduling domain name includes a sub-scheduling domain name corresponding to the source server domain name of the target content provider, the service update instruction includes a first service address, a second service address and a sub-scheduling domain name corresponding to the source server domain name, the first cache server uses the first service address to distribute content as the source server domain name of the target content provider, and the second cache server uses the second service address to distribute content as the source server domain name of the target content provider.
[0014] Optionally, in the exception handling method according to an embodiment of the present invention, it also includes: receiving a service configuration instruction from a content provider; in response to the service configuration instruction, allocating a scheduling domain name and multiple cache servers for distributing content to the content provider; and allocating a service address associated with the content provider to each cache server allocated to the content provider, so that each cache server uses the associated service address to distribute content to the content provider.
[0015] Optionally, in the exception handling method according to an embodiment of the present invention, the step of allocating a scheduling domain name to a content provider includes: allocating a total scheduling domain name corresponding to the content provider, so as to obtain sub-scheduling domain names corresponding to each source server domain name of the content provider based on the total scheduling domain name.
[0016] Optionally, in the exception handling method according to the embodiment of the present invention, the step of allocating multiple cache servers for distributing content to the content provider includes: allocating multiple cache servers for distributing content to the source server domain name of the content provider.
[0017] Optionally, the exception handling method according to an embodiment of the present invention further includes: configuring a resolution record corresponding to the scheduling domain name based on the scheduling domain name assigned to the content provider, the service addresses of each cache server and their association; and sending the resolution record to the scheduling server.
[0018] Optionally, the exception handling method according to the embodiment of the present invention further includes: sending the scheduling domain name assigned to the content provider, the service addresses of each cache server and their association to the scheduling server, so that the scheduling server configures the resolution record corresponding to the scheduling domain name.
[0019] Optionally, the exception handling method according to an embodiment of the present invention also includes: when it is monitored that access to the second service address has returned to normal, sending a service recovery instruction to the scheduling server to instruct the scheduling server to redirect the total scheduling domain name corresponding to the target content provider or the sub-scheduling domain name corresponding to the source server domain name of the target content provider to the first cache server.
[0020] Optionally, in the exception handling method according to the embodiment of the present invention, the service address is a virtual IP address.
[0021] Optionally, in the exception handling method according to the embodiment of the present invention, the attack protection capability and / or traffic processing capability of the second cache server is higher than that of the first cache server.
[0022] According to another aspect of an embodiment of the present invention, there is provided an exception handling method for a content distribution network, wherein the content distribution network comprises a cache server for distributing content and a scheduling server for resolving domain names, wherein the cache server uses a service address associated with a content provider to distribute content to the content provider, and the method comprises: the scheduling server receives a service update instruction; and in response to the service update instruction, replaces a first cache server originally pointed to by a scheduling domain name of a target content provider with a second cache server, and the second cache server replaces the first cache server to distribute content to the target content provider.
[0023] Optionally, in an exception handling method according to an embodiment of the present invention, the scheduling server stores multiple resolution records, the resolution record includes the scheduling domain name and the service address of the cache server to which it points, the service update instruction includes the first service address and the second service address, the first cache server uses the first service address to distribute content to the target content provider, and the second cache server uses the second service address to distribute content to the target content provider, and the step of replacing the first cache server originally pointed to by the scheduling domain name of the target content provider with the second cache server includes: querying the resolution record including the scheduling domain name of the target content provider and the first service address, and updating the first service address recorded in the queried resolution record to the second service address.
[0024] According to another aspect of an embodiment of the present invention, there is provided an exception handling method, comprising: when an exception is detected in a first cache server, determining a target content provider corresponding to the exception; and sending a service update instruction to a scheduling server, wherein the service update instruction instructs the scheduling server to point the scheduling domain name of the target content provider to a second cache server, so that the second cache server replaces the first cache server to distribute content to the target content provider.
[0025] According to another aspect of an embodiment of the present invention, there is provided an exception handling device for a content distribution network, wherein the content distribution network comprises a cache server for distributing content and a scheduling server for resolving domain names, wherein the cache server uses a service address associated with a content provider to distribute content to the content provider, and the device comprises: an exception locating unit, adapted to determine a target content provider corresponding to the exception when an exception is detected in a first cache server; and a service updating unit, adapted to send a service updating instruction to the scheduling server, wherein the service updating instruction instructs the scheduling server to point the scheduling domain name of the target content provider to a second cache server, and the second cache server replaces the first cache server to distribute content to the target content provider.
[0026] According to another aspect of an embodiment of the present invention, there is provided an exception handling device for a content distribution network, wherein the content distribution network comprises a cache server for distributing content and a scheduling server for resolving domain names, wherein the cache server uses a service address associated with a content provider to distribute content to the content provider, and the device comprises: an instruction receiving unit, adapted to receive a service update instruction; and a record updating unit, adapted to replace a first cache server originally pointed to by a scheduling domain name of a target content provider with a second cache server in response to the service update instruction, wherein the second cache server replaces the first cache server to distribute content to the target content provider.
[0027] According to another aspect of an embodiment of the present invention, there is provided a content distribution network, comprising: a cache server, adapted to distribute content to a content provider using a service address associated with the content provider; a scheduling server, comprising an exception handling device according to an embodiment of the present invention, and adapted to resolve a scheduling domain name of the content provider to obtain a service address pointed to by the scheduling domain name; and a control server, comprising the exception handling device according to an embodiment of the present invention.
[0028] According to another aspect of an embodiment of the present invention, a computing device is provided, comprising: one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for executing the exception handling method according to an embodiment of the present invention.
[0029] According to another aspect of an embodiment of the present invention, a computer-readable storage medium storing one or more programs is provided, wherein the one or more programs include instructions that, when executed by a computing device, cause the computing device to execute an exception handling method according to an embodiment of the present invention.
[0030] According to the exception handling method for a content distribution network of an embodiment of the present invention, by configuring a service address associated only with the content provider for the cache server assigned to the content provider, the cache server uses the service address associated only with the content provider to distribute content to the content provider. In this way, when an exception occurs in the cache server, the target content provider can be quickly located based on the service address corresponding to the exception, and the abnormal traffic of the target content provider can be switched to other cache servers, thereby achieving timely defense and processing of abnormal traffic and ensuring stable and available services of the cache server.
[0031] Furthermore, by configuring the cache server with a service address associated only with the source server domain name of the content provider, the cache server uses the service address associated only with the source server domain name of the content provider to distribute content for the source server domain name. In this way, when an abnormality is detected in the cache server, the source server domain name of the target content provider can be quickly and accurately located based on the service address corresponding to the abnormality, and the abnormal traffic of the source server domain name can be switched to other cache servers, thereby achieving timely defense and processing of abnormal traffic for a specific source server domain name.
[0032] The above description is only an overview of the technical solution of the embodiment of the present invention. In order to more clearly understand the technical means of the embodiment of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present invention more obvious and easy to understand, the specific implementation method of the embodiment of the present invention is specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] To achieve the above and related purposes, certain illustrative aspects are described herein in conjunction with the following description and accompanying drawings, which indicate various ways in which the principles disclosed herein can be practiced, and all aspects and their equivalents are intended to fall within the scope of the claimed subject matter. The above and other purposes, features and advantages of the present disclosure will become more apparent by reading the following detailed description in conjunction with the accompanying drawings. Throughout the present disclosure, the same reference numerals generally refer to the same parts or elements.
[0034] Figure 1 A schematic diagram of a content distribution network 100 according to an embodiment of the present invention is shown;
[0035] Figure 2 A schematic diagram showing the operation of a content distribution network 100 according to an embodiment of the present invention is shown;
[0036] Figure 3 A schematic diagram of a computing device 300 according to one embodiment of the present invention is shown;
[0037] Figure 4 An interactive flow chart of an exception handling method 400 according to an embodiment of the present invention is shown;
[0038] Figure 5 An interactive flow chart of a service configuration method 500 according to an embodiment of the present invention is shown;
[0039] Figure 6 A flowchart of an exception handling method 600 according to an embodiment of the present invention is shown; and
[0040] Figure 7 A flowchart of an exception handling method 700 according to an embodiment of the present invention is shown. DETAILED DESCRIPTION
[0041] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.
[0042] Generally speaking, content providers provide content to users through network servers they deploy. Users access the network server via the domain name of the network server and obtain content. Currently, in order to speed up user access to content, a large number of content providers choose to use content distribution networks.
[0043] The content distribution network can provide content distribution services for content providers, that is, using the cache server closest to the user to send the content provider's content to the user. For ease of description, the network server deployed by the content provider itself is referred to as the source server, and the domain name of the source server is referred to as the source server domain name. The content provider can use one or more source server domain names to provide content to users.
[0044] Figure 1 FIG. 1 is a schematic diagram of a content distribution network 100 according to an embodiment of the present invention. Figure 1 As shown, the content distribution network 100 includes a plurality of cache servers 140, such as cache servers 140A-140N. The cache servers 140 can store content provided by content providers and distribute the content to clients 120, such as clients 120A-120N.
[0045] The cache server 140 has a service address, which includes but is not limited to an IP address, a virtual IP address, etc. The cache server 140 distributes content through the service address. The cache server 140 can distribute various types of content, including but not limited to web pages and their page elements, streaming media, downloadable media, application data, program code intended to be executed at the client, etc.
[0046] Client 120 may represent or correspond to various clients or users and may be distributed in any suitable location or region. In one embodiment, client 120 may be configured to run a browser program or other application program that consumes content from content distribution network 100. For example, client 120 may run a web browser that generates an HTTP or HTTPS (Hypertext Transfer Protocol) request to obtain content from content distribution network 100.
[0047] like Figure 2 As further shown, the content distribution network 100 also includes a control server 160 and a scheduling server 180 (also referred to as a domain name server in the content distribution network 100). In addition, each component (e.g., each server) in the content distribution network 100 is communicatively coupled to the client 120 via a network 190. The network 190 may include wired and / or wireless communication paths, such as, but not limited to, the Internet, a local area network, a satellite path, an optical fiber path, a cable path, or any other suitable wired or wireless communication path or a combination of such paths.
[0048] In some embodiments, the control server 160 may configure content distribution services for content providers, and may also manage the scheduling server 160 and / or cache server 140. For example, the control server 160 may receive a service configuration instruction from a content provider 120, and in response to the service configuration instruction, allocate a scheduling domain name and multiple cache servers 140 that store and distribute the content of the content provider to the content provider.
[0049] Specifically, the allocated dispatching domain name is also called a dispatching alias (CNAME), which can uniquely identify the content provider and / or the source server domain name of the content provider in the content distribution network 100. The dispatching domain name that uniquely identifies the content provider is called the total dispatching domain name, and the dispatching domain name that uniquely identifies the source server domain name of the content provider is called the sub-dispatching domain name. For example, a total dispatching domain name that uniquely identifies the content provider can be allocated to the content provider, and then the sub-dispatching domain name uniquely corresponding to each source server domain name can be obtained naturally based on the total dispatching domain name and each source server domain name owned by the content provider.
[0050] In some implementations, the sub-dispatching domain name may be a secondary domain name (i.e., a sub-domain name) of the general dispatching domain name. For example, a content provider has two source server domain names, testa1.com and testa2.com, and the general dispatching domain name assigned to the content provider is cdna.com. Then, the sub-dispatching domain name corresponding to the source server domain name testa1.com is testa1.cdna.com, and the sub-dispatching domain name corresponding to the source server domain name testa2.com is testa2.cdna.com.
[0051] The control server 160 can send the scheduling domain name assigned to the content provider and the service address of each cache server to the scheduling server 180, so that the scheduling server 180 configures the resolution record corresponding to the scheduling domain name. The resolution record stores the scheduling domain name and the service address of the cache server pointed to by the scheduling domain name for subsequent domain name resolution. In some embodiments, the resolution record of the scheduling domain name may include the resolution record of the total scheduling domain name and / or the resolution record of the sub-scheduling domain name. It should be understood that the resolution record of the total scheduling domain name is a pan-domain name resolution record, which can point at least part of the sub-scheduling domain names based on the total scheduling domain name to the same cache server.
[0052] For example, for the general dispatch domain name cdna.com, the configured wildcard domain name resolution record can be as follows:
[0053]
[0054] According to the wildcard domain name resolution record, at least some of the sub-dispatching domain names (such as testa1.cdna.com, testa2.cdna.com and other sub-domain names) of the total dispatching domain name cdna.com can be matched to the record, pointing to the service address of the cache server in the record.
[0055] In addition, you can also configure a resolution record for a sub-dispatching domain name based on the general dispatching domain name. For example, for the sub-dispatching domain name testa1.cdna.com, the configured resolution record can be as follows:
[0056] Scheduling domain name Record Value testa1.cdna.com Service Address 1
[0057] When resolving a domain name, you can first check whether there is a resolution record for a matching sub-dispatching domain name. If not, then match the resolution record for the corresponding general dispatching domain name.
[0058] After configuring the content distribution service, the content provider can point its source server domain name to the sub-scheduling domain name corresponding to the source server domain name in the content distribution network 100, so that the domain name resolution request for the source server domain name can be sent to the scheduling server 180 in the content distribution network 100, and the scheduling server 180 performs the domain name resolution. For example, the resolution record of the source server domain name on the corresponding authoritative domain name server (also called the authoritative DNS server) can be modified to point the source server domain name to the corresponding sub-scheduling domain name.
[0059] Figure 2 FIG. 1 shows a schematic diagram of the operation of a content distribution network 100 according to an embodiment of the present invention. Figure 2As shown, when the client 120A sends an access request to the source server domain name, the client 120A sends a domain name resolution request for the source server domain name to the local DNS server 121. The local DNS server 121 can query the sub-scheduling domain name corresponding to the source server domain name (for example, it can be queried on the corresponding authoritative domain name server 122), and then send a domain name resolution request for the sub-scheduling domain name to the scheduling server 180.
[0060] The scheduling server 180 receives a domain name resolution request for a sub-scheduling domain name, and can query the resolution record corresponding to the sub-scheduling domain name. If there is a resolution record corresponding to the sub-scheduling domain name, the cache server pointed to by the sub-scheduling domain name is obtained. If there is no resolution record corresponding to the sub-scheduling domain name, the wildcard domain name resolution record corresponding to the total scheduling domain name can be queried to obtain the cache server pointed to by the total scheduling domain name. The scheduling server 180 can select a cache server 140A suitable for the client 120A (for example, the closest to the client 120A) according to some scheduling strategies, and return the service address of the cache server 140A in the resolution record to the local domain name server 121, so that the local domain name server 121 returns it to the client 120A. Then, the client 120A can send an access request to the cache server 140A via the service address to request the content of the source server domain name. Among them, the embodiment of the present invention does not limit the specific scheduling strategy, which can be, for example, scheduling according to region and / or operator, or other suitable strategies or combinations of strategies.
[0061] As described above, the cache server 140 processes the client's access and distributes content to the client through its service address. However, due to limited address resources, a cache server 140 usually uses one service address to provide services to many content providers, that is, one service address corresponds to multiple content providers. In this case, if an abnormality occurs in the cache server, such as an attack such as a distributed denial of service (DDoS) attack that only targets an IP address, because such attacks do not contain any domain name information, it is impossible to find the attacked content provider in time, let alone to defend in time. At the same time, the cache server's services to other content providers will also be affected, or even unavailable.
[0062] In order to solve the above problem, the content distribution network 100 according to the embodiment of the present invention can configure a service address that is only associated with the content provider for the cache server assigned to the content provider, so that the cache server only uses the service address to distribute content to the content provider. In this way, when an abnormality is detected in a cache server, the specific content provider can be quickly located based on the service address corresponding to the abnormality, so as to handle it in time. For example, in Figure 2 In the example, the service address of the cache server 140A obtained by the client 120A through the resolution of the scheduling server 180 is only associated with a certain content provider.
[0063] According to an embodiment of the present invention, each component (eg, each server) in the above-mentioned content distribution network 100 may be implemented by a computing device 300 as described below.
[0064] Figure 3 FIG. 3 is a schematic diagram of a computing device 300 according to an embodiment of the present invention. Figure 3 As shown, in a basic configuration 302, computing device 300 typically includes a system memory 306 and one or more processors 304. A memory bus 308 may be used for communication between processor 304 and system memory 306.
[0065] Depending on the desired configuration, the processor 304 can be any type of processor, including but not limited to: a microprocessor (μP), a microcontroller (μC), a digital information processor (DSP), or any combination thereof. The processor 304 can include one or more levels of cache such as a primary cache 310 and a secondary cache 312, a processor core 314, and registers 316. An example processor core 314 can include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP core), or any combination thereof. An example memory controller 318 can be used with the processor 304, or in some implementations, the memory controller 318 can be an internal part of the processor 304.
[0066] Depending on the desired configuration, system memory 306 may be any type of memory, including but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. System memory 306 may include an operating system 320, one or more applications 322, and program data 324. In some implementations, application 322 may be arranged to execute instructions on the operating system by one or more processors 304 using program data 324.
[0067] The computing device 300 may also include an interface bus 340 that facilitates communication from various interface devices (e.g., output devices 342, peripheral interfaces 344, and communication devices 346) to the basic configuration 302 via the bus / interface controller 330. Example output devices 342 include a graphics processing unit 348 and an audio processing unit 350. They can be configured to facilitate communication with various external devices such as a display or speakers via one or more A / V ports 352. Example peripheral interfaces 344 may include a serial interface controller 354 and a parallel interface controller 356, which may be configured to facilitate communication with external devices such as input devices (e.g., keyboards, mice, pens, voice input devices, touch input devices) or other peripherals (e.g., printers, scanners, etc.) via one or more I / O ports 358. Example communication devices 346 may include a network controller 360, which may be arranged to facilitate communication with one or more other computing devices 362 via a network communication link via one or more communication ports 364.
[0068] A network communication link can be an example of a communication medium. Communication media can generally be embodied as computer-readable instructions, data structures, program modules in a modulated data signal such as a carrier wave or other transmission mechanism, and can include any information delivery medium. A "modulated data signal" can be a signal in which one or more of its data sets or its changes can be carried out in a manner that encodes information in the signal. As non-limiting examples, communication media can include wired media such as a wired network or a dedicated line network, and various wireless media such as sound, radio frequency (RF), microwave, infrared (IR) or other wireless media. The term computer-readable medium used herein can include both storage media and communication media.
[0069] The computing device 300 can be implemented as a server, such as a database server, an application server, a WEB server, etc., or as a personal computer including a desktop computer and a notebook computer. Of course, the computing device 300 can also be implemented as at least a part of a small-sized portable (or mobile) electronic device.
[0070] In an embodiment according to the present invention, the computing device 300 may be implemented as a control server 160 and a scheduling server 180, and is configured to execute the methods 600 and 700 according to the embodiments of the present invention. The application 322 of the computing device 300 includes a plurality of instructions for executing the methods 600 / 700 according to the embodiments of the present invention, and the program data 324 may also store the configuration data of the content distribution network 100 and other contents. The methods 600 / 700 will be described below in conjunction with Figure 6 to Figure 7 Further describe each.
[0071] Figure 4 The interactive flow chart of an exception handling method 400 for a content distribution network 100 according to an embodiment of the present invention is shown. The exception handling method 400 can be executed in the content distribution network 100 and starts with step S410.
[0072] like Figure 4 As shown, in step S410, the control server 160 may receive access information of each cache server 140 (e.g., the first cache server 140A) in the content distribution network 100. The access information may be uploaded to the control server 160 by the cache server 140 (e.g., at predetermined intervals), and / or may be pulled from the cache server 140 by the control server 160. The access information of each cache server 140 may record access to all service addresses of the cache server 140.
[0073] Next, in step S420, the control server 160 may monitor whether an abnormality occurs in each cache server 140 (e.g., the first cache server 140A) based on the received access information. The abnormality may generally include an abnormality in access to one or more service addresses of a cache server. The types of abnormalities include, but are not limited to, network attacks against addresses such as DDoS attacks, indicator abnormalities such as address access exceeding a threshold, and the like. The embodiment of the present invention does not limit the specific abnormal content and type.
[0074] When it is detected that, for example, the first cache server 140A has an abnormality, the control server 160 may determine the target content provider corresponding to the abnormality in step S430. For example, as described in detail below, the service address used by the cache server 140 to distribute content to the content provider may only be associated with the content provider, so the service address of the first cache server 140A corresponding to the abnormality may be determined first. For ease of description, the corresponding address is referred to as the first service address. Then, the target content provider associated with the first service address is determined.
[0075] It can be understood that the first service address is only associated with the target content provider, and the first cache server 140A uses the first service address to distribute content only to the target content provider (other service addresses may be used to distribute content to other content providers).
[0076] In some embodiments, the source server domain name of the target content provider corresponding to the exception can also be determined. For example, as described in detail below, in some cases, among the multiple cache servers assigned to a certain content provider, some cache servers are configured to distribute content only for the specified source server domain name of the content provider, and the service addresses used by these cache servers when distributing content for the specified source server domain name of the content provider are only associated with the specified source server domain name of the content provider. Therefore, the first service address of the first cache server 140A corresponding to the exception can be determined first, and then the source server domain name of the target content provider associated with the first service address can be determined. Of course, in some cases, if there is no associated source server domain name for the first service address, then the associated target content provider can be determined.
[0077] It can be understood that if the first service address has an associated source server domain name of a target content provider, then the first service address is only associated with the source server domain name of the target content provider, and the first cache server 140A uses the first service address to distribute content only to the source server domain name of the target content provider (other service addresses can be used to distribute content to other source server domain names of the target content provider and other content providers).
[0078] After determining the target content provider or the source server domain name of the target content provider corresponding to the exception, the control server 160 can determine the scheduling domain name of the service to be updated. For example, if the exception corresponds to the target content provider (not a source server domain name of the target content provider), the scheduling domain name of the service to be updated can be determined to be the total scheduling domain name corresponding to the target content provider. If the exception corresponds to the source server domain name of the target content provider, the scheduling domain name of the service to be updated can be determined to be the sub-scheduling domain name corresponding to the source server domain name.
[0079] Meanwhile, the control server 160 may determine, in step S440, based on the exception, a second cache server 140B to replace the first cache server 140A. The second cache server 140B may replace the first cache server 140A to distribute content to the target content provider corresponding to the exception or the source server domain name of the target content provider.
[0080] In some embodiments, the second cache server 140B can be determined based on the type of anomaly. For example, if the anomaly is a network attack such as DDoS, a cache server with higher attack protection capability and / or traffic cleaning capability (for example, higher than the first cache server 140A) can be selected. If the anomaly is an indicator anomaly such as the address access volume exceeding a threshold, a cache server with higher traffic processing capability (for example, higher than the first cache server 140A) can be selected. The embodiment of the present invention does not limit the selection strategy of the specific second cache server 140B. Among them, the control server 160 can select the second cache server 140B from the cache servers that have been assigned to the target content provider (if there is a second cache server 140B that meets the selection strategy). And / or, the control server 160 can also assign a new cache server that meets the selection strategy as the second cache server 140B (for example, when there is no second cache server 140B that meets the selection strategy among the cache servers assigned to the target content provider), and reallocate the service address associated with the target content provider or the source server domain name of the target content provider (hereinafter referred to as the second service address) to the second cache server 140B.
[0081] Next, the control server 160 may generate a service update instruction in step S450, wherein the service update instruction instructs the scheduling server 180 to point the scheduling domain name (eg, the above-mentioned general scheduling domain name or sub-scheduling domain name) of the target content provider to the second cache server 140B.
[0082] For example, if the exception corresponds to a target content provider rather than a source server domain name of the target content provider, the service update instruction may instruct the scheduling server 180 to point the target content provider's total scheduling domain name to the second cache server 140B. If the exception corresponds to the target content provider's source server domain name, the service update instruction may instruct the scheduling server 180 to point the sub-scheduling domain name corresponding to the source server domain name to the second cache server 140B. As described above, the sub-scheduling domain name may be obtained based on the target content provider's source server domain name and the total scheduling domain name.
[0083] Specifically, the service update instruction may include the first service address of the first cache server 140A, the second service address of the second cache server 140B, and the total dispatch domain name or sub-dispatching domain name of the target content provider determined above, which may indicate to replace the first service address originally pointed to by the total dispatch domain name or sub-dispatching domain name of the target content provider with the second service address. The second service address is a service address assigned to the second cache server 140B and associated with the target content provider or the source server domain name of the target content provider, and the second cache server 140B uses the second service address to distribute content to the target content provider or the source server domain name of the target content provider.
[0084] The control server 160 may send the service update instruction to the scheduling server 180 in step S460. The control server 160 may also generate a service stop instruction and send it to the first cache server 140A in step S461. The first cache server 140A receives the service stop instruction and may, in step S462, stop distributing content using the source server domain name of the target provider or target content provider in response to the service stop instruction.
[0085] In some cases, the control server 160 may also generate a service activation instruction in step S463 and send it to the second cache server 140B (for example, when the second cache server 140B is newly assigned to the target content provider). The second cache server 140B receives the service activation instruction and may, in step S464, respond to the service activation instruction and start distributing content using the second service address as the target provider or the source server domain name of the target content provider.
[0086] The scheduling server 180 receives the service update instruction and can, in step S470, respond to the service update instruction by pointing the scheduling domain name (such as the above-mentioned general scheduling domain name or sub-scheduling domain name) carried by the service update instruction to the second cache server 140B. The second cache server 140B replaces the first cache server 140A originally pointed to by the scheduling domain name to distribute content for the target content provider or the source server domain name of the target content provider.
[0087] Specifically, the scheduling server 180 can query the resolution record including the scheduling domain name and the first service address carried by the service update instruction, and update the first service address recorded in the resolution record to the second service address. If the scheduling domain name carried by the service update instruction is the total scheduling domain name of the target content provider, then the wildcard domain name resolution record corresponding to the total scheduling domain name can be searched, and the first service address recorded in the wildcard domain name resolution record can be updated to the second service address. If the scheduling domain name carried by the service update instruction is a sub-scheduling domain name of the source server domain name of the target content provider, then the resolution record corresponding to the sub-scheduling domain name can be searched, and the first service address recorded in the resolution record can be updated to the second service address.
[0088] After the scheduling server 180 updates the resolution record, it may also return a feedback message indicating that the service update is complete to the control server 160. Accordingly, the control server 160 may also update the association relationship between the target content provider (and / or the source server domain name of the target content provider), the cache server assigned to the target content provider, and its service address stored therein (described in detail later), for example, the part of the association relationship of the target content provider involving the first cache server 140A and the second cache server 140B may be updated.
[0089] In this way, the abnormal access traffic to the first cache server 140A is directed to the second cache server 140B, ensuring the stability and availability of the first cache server 140A. Meanwhile, the second cache server 140B can also timely defend and process the abnormal access traffic.
[0090] According to one embodiment of the present invention, after the service update is completed, the control server 160 may also monitor whether the access to the second service address of the second cache server 140B has returned to normal based on the access information of the second cache server 140B. When it is monitored that the access to the second service address has returned to normal, the control server 160 may send a service recovery instruction to the scheduling server 180, instructing the scheduling server 180 to redirect the scheduling domain name (e.g., the main scheduling domain name or the sub-scheduling domain name) of the target content provider to the first cache server 140A, so that the first cache server 140A can reuse the first service address to distribute content for the source server domain name of the target provider or the target content provider.
[0091] Of course, the control server 160 can also respond to the corresponding instruction of the target content provider and send a service recovery instruction to the scheduling server 180 to redirect the scheduling domain name of the target content provider to the first cache server. The principle of the scheduling server 180 restoring the service is similar to the principle of updating the service, which will not be repeated here.
[0092] According to an embodiment of the present invention, before monitoring whether the cache server sends an exception and processing it, the exception handling method 400 may further include a service configuration method 500. The service configuration method 500 is used to configure content distribution services for content providers.
[0093] Figure 5 The interactive flow chart of the service configuration method 500 according to one embodiment of the present invention is shown. The service configuration method 500 is suitable for being executed in the content distribution network 100 and starts with step S510.
[0094] like Figure 5 As shown, in step S510, the control server 160 may receive a service configuration instruction from a content provider. Then, in step S520, the control server 160 may allocate a scheduling domain name and multiple cache servers for distributing content to the content provider in response to the service configuration instruction. For example, a general scheduling domain name may be allocated to the content provider so that the sub-scheduling domain names corresponding to the domain names of each source server of the content provider are obtained based on the general scheduling domain name.
[0095] Generally, the control server 160 configures the content distribution service uniformly for all source server domain names of the content provider by default, that is, all cache servers allocated to the content provider can distribute content for each source server domain name of the content provider. At this time, the total scheduling domain name of the content provider can point to all cache servers allocated to the content provider.
[0096] However, in some cases (e.g., under the special instructions of the content provider), the control server 160 can also configure content distribution services for one or more source server domain names of the content provider, that is, the control server 160 can allocate multiple cache servers for distributing content to the source server domain name of the content provider. In this case, the sub-scheduling domain name corresponding to the source server domain name can point to the cache server assigned to the source server domain name, and the total scheduling domain name can point to the cache server assigned to the content provider instead of the specific source server domain name.
[0097] Next, the control server 160 may, in step S530, allocate a service address associated with the content provider and only associated with the content provider to each cache server allocated to the content provider (including allocating the source server domain name of the content provider), so that each cache server may subsequently use only the allocated service address associated only with the content provider to distribute content for the content provider or the source server domain name of the content provider. It should be noted that the allocated service address associated with the content provider only belongs to the content provider (that is, after these service addresses are allocated to the content provider and associated with the content provider, they will not be allocated to other content providers and associated with other content providers). These service addresses may be physical IP addresses, but preferably, they may be virtual IP addresses. According to an embodiment of the present invention, the cache server 140 may have one or more service addresses.
[0098] In this way, the control server 160 can store content providers (for example, including the source server domain name of the content provider), scheduling domain names assigned to the content provider (for example, the overall scheduling domain name and / or sub-scheduling domain name), each cache server and the service address of each cache server, as well as the association relationship between them.
[0099] The following is an example of an association relationship:
[0100]
[0101] The example scheduling domain names cdna.com and cdhb.com are general scheduling domain names, that is, in this example, the content distribution service is not configured separately for the source server domain name of the content provider.
[0102] Virtual IP addresses A1-An are virtual IP addresses associated only with provider A, and cache servers 140A-140N use their respective virtual IP addresses associated only with provider A to distribute content only to provider A. Virtual IP addresses B1-Bn are virtual IP addresses associated only with provider B, and cache servers 140A-140N use their respective virtual IP addresses associated only with provider B to distribute content only to provider B.
[0103] It can be seen that although the cache servers allocated to supplier A and supplier B are the same (both 140A-140N), supplier A or supplier B can be uniquely located via the virtual IP address used by the cache server.
[0104] Here is another example of an association relationship:
[0105]
[0106]
[0107] Among them, the example scheduling domain name testa.cdna.com is a sub-scheduling domain name corresponding to the source server domain name testa.com of supplier A, and is a sub-domain name of the general scheduling domain name cdna.com. Obviously, in this example, the content distribution service is configured separately for the source server domain name testa.com of supplier A. The example scheduling domain name testb.cdnb.com is a sub-scheduling domain name corresponding to the source server domain name testb.com of supplier B, and is a sub-domain name of the general scheduling domain name cdnb.com. In this example, the content distribution service is also configured separately for the source server domain name testb.com of supplier B.
[0108] Virtual IP addresses A1-An are virtual IP addresses associated only with provider A, and virtual IP address A1 is associated only with the source server domain name testa.com of provider A. Cache server 140A uses virtual IP address A1 associated only with the source server domain name testa.com of provider A to distribute content only for the source server domain name testa.com of provider A. Cache servers 140B-140N use their respective virtual IP addresses associated only with provider A to distribute content only for other source server domain names of provider A.
[0109] Virtual IP addresses B1-Bn are virtual IP addresses associated only with provider B, and virtual IP address B1 is associated only with the source server domain name testb.com of provider B. Cache server 140A uses virtual IP address B1 associated only with the source server domain name testb.com of provider B to distribute content only to the source server domain name testb.com of provider B. Cache servers 140B-140N use their respective virtual IP addresses associated only with provider B to distribute content only to provider B.
[0110] It can be seen that in this example, although the cache servers assigned to supplier A and supplier B are the same (both 140A-140N), some virtual IP addresses (such as virtual IP addresses A2-An) used by the cache servers can uniquely locate supplier A or supplier B, and some virtual IP addresses (such as virtual IP address A1) can uniquely locate the source server domain name of supplier A or supplier B.
[0111] In actual applications, content providers can usually configure content distribution services for their key source server domain names separately, and configure content distribution services for non-key source servers uniformly. In this way, when an abnormality occurs in access to a key source server domain name, the key source server domain name can be quickly located and handled in a timely manner, and when an abnormality occurs in access to a non-key source server domain name, the content provider can be quickly located and handled in a timely manner.
[0112] Then, in step S540, the control server 160 may send the dispatching domain name assigned to the content provider (which may sometimes include the domain name of the source server of the content provider), the service addresses of each cache server and their association to the dispatching server 180, so that the dispatching server 180 configures the resolution record corresponding to the dispatching domain name. Alternatively, the control server 160 may first configure the resolution record corresponding to the dispatching domain name based on the dispatching domain name assigned to the content provider, the service addresses of each cache server and their association, and then send the resolution record to the dispatching server 180. It should be noted that the resolution record may also record the region and / or operator where the cache server is located.
[0113] Accordingly, the scheduling server 180 may configure or store a resolution record corresponding to the scheduling domain name in step S550 for use in subsequent domain name resolution.
[0114] In addition, after allocating the cache server and its service address to the content provider or the source server domain name of the content provider, the control server 160 can also generate a service activation instruction and send it to each cache server, so that each cache server responds to the service activation instruction and starts distributing content for the target provider or the source server domain name of the target content provider using the allocated service address.
[0115] At this point, the content distribution service configuration for the content provider and / or the source server domain name of the content provider is completed.
[0116] The exception handling method 600 executed in the control server 160 and the exception handling method 700 executed in the scheduling server 180 are described below respectively.
[0117] Figure 6 FIG. 6 is a flowchart of an exception handling method 600 for a content distribution network 100 according to an embodiment of the present invention. Figure 6 As shown, the exception handling method 600 begins with step S610 .
[0118] In step S610, when an abnormality is detected in the first cache server 140A, the target content provider corresponding to the abnormality is determined. For example, access information of each cache server 140 in the content distribution network 100 may be received, and based on the access information, whether an abnormality occurs in each cache server 140 is monitored. The service address may generally be a virtual IP address.
[0119] The cache server 140 has at least one service address, and the exception may generally include an exception in access to the service address. Therefore, the first service address of the first cache server 140A corresponding to the exception may be determined first, and then the target content provider associated with the first service address may be determined.
[0120] In some embodiments, the source server domain name of the target content provider corresponding to the exception and associated with the first service address may also be directly determined.
[0121] After determining the target content provider or its source server domain name corresponding to the anomaly, a second cache server 140B can be determined based on the anomaly to replace the first cache server 140A. The attack protection capability and / or traffic processing capability of the second cache server 140B is usually higher than that of the first cache server 140A.
[0122] Next, in step S620, a service update instruction may be sent to the scheduling server 180, which may instruct the scheduling server 180 to point the scheduling domain name of the target content provider to the second cache server 140B, and the second cache server 140B replaces the first cache server 140A to distribute content for the target content provider.
[0123] In some embodiments, the scheduling domain name of the target content provider here can be the total scheduling domain name corresponding to the target content provider. At this time, the service update instruction includes the first service address, the second service address and the total scheduling domain name of the target content provider. The first cache server 140A uses the first service address to distribute content to the target content provider, and the second cache server 140B uses the second service address to distribute content to the target content provider.
[0124] In other embodiments, the scheduling domain name of the target content provider here can be a sub-scheduling domain name corresponding to the source server domain name of the target content provider corresponding to the exception. At this time, the service update instruction includes the first service address, the second service address and the sub-scheduling domain name corresponding to the source server domain name. The first cache server 140A uses the first service address as the source server domain name of the target content provider to distribute content, and the second cache server 140B uses the second service address as the source server domain name of the target content provider to distribute content.
[0125] In addition, in one embodiment of the present invention, when it is monitored that access to the second service address has returned to normal, a service recovery instruction can be sent to the scheduling server 180 to instruct the scheduling server 180 to redirect the total scheduling domain name corresponding to the target content provider or the sub-scheduling domain name corresponding to the source server domain name of the target content provider to the first cache server 140A.
[0126] It should be noted that before performing exception handling, it is necessary to first configure the content distribution service for the content provider. For example, a service configuration instruction of a content provider can be received, and in response to the service configuration instruction, a scheduling domain name and multiple cache servers for distributing content are allocated to the content provider. Among them, allocating a scheduling domain name to a content provider may include: allocating a total scheduling domain name corresponding to the content provider, so as to obtain a sub-scheduling domain name corresponding to each source server domain name of the content provider based on the total scheduling domain name. Allocating multiple cache servers for distributing content to a content provider may also include: allocating multiple cache servers for distributing content to the source server domain name of the content provider.
[0127] Next, each cache server assigned to a content provider (which may sometimes include the source server domain name of the content provider) is assigned a service address associated only with the content provider, so that each cache server uses the associated service address to distribute content for the content provider.
[0128] Finally, the resolution record corresponding to the scheduling domain name can be configured based on the scheduling domain name assigned to the content provider, the service addresses of each cache server and their association, and the resolution record is sent to the scheduling server. Alternatively, the scheduling domain name assigned to the content provider, the service addresses of each cache server and their association can be sent to the scheduling server 180 so that the scheduling server 180 can configure the resolution record corresponding to the scheduling domain name.
[0129] For detailed processing logic and implementation process of each step in the exception handling method 600, please refer to the above combined Figure 1-Figure 5 The descriptions of the content distribution network 100, the exception handling method 400 and the service configuration method 500 are not repeated here.
[0130] Figure 7 FIG. 7 is a flow chart of an exception handling method 700 for a content distribution network 100 according to an embodiment of the present invention. Figure 7 As shown, the exception handling method 700 begins with step S710 .
[0131] In step S710, a service update instruction is received. Then in step S720, in response to the service update instruction, the first cache server 140A originally pointed to by the dispatch domain name of the target content provider is replaced by the second cache server 140B, and the second cache server 140B can replace the first cache server 140A to distribute content for the target content provider.
[0132] Specifically, the scheduling server 180 stores multiple resolution records, the resolution record includes the scheduling domain name and the service address of the cache server it points to, and the service update instruction includes the scheduling domain name of the target content provider, the first service address of the first cache server 140A, and the second service address of the second cache server 140B. Then, the resolution record including the scheduling domain name and the first service address of the target content provider can be queried, and the first service address recorded in the queried resolution record can be updated to the second service address. Among them, the scheduling domain name of the target content provider can be the total scheduling domain name corresponding to the target content provider or the sub-scheduling domain name corresponding to the source server domain name of the target content provider. It can be understood that the second cache server 140B only uses the second service address to distribute content for the target content provider or its source server domain name, and the first cache server 140A only uses the first service address to distribute content for the target content provider or its source server domain name.
[0133] In summary, the exception handling method for a content distribution network according to an embodiment of the present invention configures a service address associated only with the content provider for the cache server assigned to the content provider, so that the cache server uses the service address associated only with the content provider to distribute content to the content provider. In this way, when an exception occurs in the cache server, the target content provider can be quickly located based on the service address corresponding to the exception, and the abnormal traffic of the target content provider can be switched to other cache servers, thereby achieving timely defense and processing of abnormal traffic and ensuring stable availability of the cache server service.
[0134] Furthermore, by configuring the cache server with a service address associated only with the source server domain name of the content provider, the cache server uses the service address associated only with the source server domain name of the content provider to distribute content for the source server domain name. In this way, when an abnormality is detected in the cache server, the source server domain name of the target content provider can be quickly and accurately located based on the service address corresponding to the abnormality, and the abnormal traffic of the source server domain name can be switched to other cache servers, thereby achieving timely defense and processing of abnormal traffic for a specific source server domain name.
[0135] Corresponding to the above-described exception handling method 600, the embodiment of the present invention accordingly discloses an exception handling device for the content distribution network 100. The exception handling device resides in the control server 160 and may include an exception locating unit and a service updating unit.
[0136] The abnormality locating unit is adapted to determine the target content provider corresponding to the abnormality when an abnormality is detected in the first cache server 140A. The service updating unit is coupled to the abnormality locating unit and is adapted to send a service updating instruction to the scheduling server 180, the service updating instruction instructing the scheduling server 180 to point the scheduling domain name of the target content provider to the second cache server, and the second cache server replaces the first cache server to distribute content for the target content provider.
[0137] For the detailed processing logic and implementation process of each unit in the exception handling device, please refer to the previous article combined with Figure 1-Figure 6 The descriptions of the content distribution network 100 and the exception handling methods 400 , 600 and the service configuration method 500 are not repeated here.
[0138] Corresponding to the exception handling method 700 described above, the embodiment of the present invention accordingly discloses an exception handling device for the content distribution network 100. The exception handling device resides in the scheduling server 180 and may include an instruction receiving unit and a record updating unit.
[0139] The instruction receiving unit is adapted to receive a service update instruction. The record updating unit is coupled to the instruction receiving unit and adapted to respond to the service update instruction and replace the first cache server originally pointed to by the dispatch domain name of the target content provider with the second cache server, so that the second cache server replaces the first cache server to distribute content for the target content provider.
[0140] For the detailed processing logic and implementation process of each unit in the exception handling device, please refer to the previous article combined with Figure 1-Figure 7 The descriptions of the content distribution network 100 and the exception handling methods 400 , 700 and the service configuration method 500 are not repeated here.
[0141] It should be noted that the exception handling method according to the embodiment of the present invention can be used not only in content distribution networks, but also in other suitable network environments. Therefore, the present invention also discloses an exception handling method, comprising the following steps: first, when an exception is detected in the first cache server, the target content provider corresponding to the exception is determined. Then, a service update instruction is sent to the scheduling server, and the service update instruction instructs the scheduling server to point the scheduling domain name of the target content provider to the second cache server, so that the second cache server replaces the first cache server to distribute content for the target content provider.
[0142] For the detailed processing logic and implementation process of each step in this exception handling method, please refer to the previous article combined with Figure 1-Figure 7 The descriptions of the exception handling methods 400, 700 and the service configuration method 500 are not repeated here.
[0143] The various embodiments of the mechanisms disclosed herein may be implemented in hardware, software, firmware, or a combination of these implementation methods. Embodiments of the present invention may be implemented as a computer program or program code executed on a programmable system, the programmable system comprising at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.
[0144] In the description provided herein, a large number of specific details are described. However, it is understood that the embodiments of the embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.
[0145] Similarly, it should be understood that in order to streamline the present disclosure and aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of embodiments of the present invention, the various features of embodiments of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, this disclosed method should not be interpreted as reflecting the following intention: that the claimed embodiments of the present invention require more features than the features explicitly recited in each claim. More specifically, as reflected in the claims below, inventive aspects lie in less than all the features of the single embodiment disclosed above. Therefore, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, with each claim itself as a separate embodiment of an embodiment of the present invention.
[0146] Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in the devices described in the embodiment, or alternatively may be located in one or more devices different from the devices in the examples. The modules in the foregoing examples may be combined into one module or may be divided into multiple submodules.
[0147] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition they may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.
[0148] In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of embodiments of the present invention and to form different embodiments. For example, in the claims below, any one of the claimed embodiments may be used in any combination.
[0149] In addition, some of the above-described embodiments are described herein as a combination of methods or method elements that can be implemented by a processor of a computer system or by other devices that perform the above-described functions. Therefore, a processor with necessary instructions for implementing the above-described methods or method elements forms a device for implementing the methods or method elements. In addition, the elements described herein of the device embodiments are examples of devices that are used to implement the functions performed by the elements for the purpose of implementing the invention.
[0150] As used herein, unless otherwise specified, the use of ordinal numbers "first," "second," "third," etc. to describe common objects merely indicates that different instances of similar objects are involved, and is not intended to imply that the objects so described must have a given order in time, space, order, or in any other manner.
[0151] Although embodiments of the present invention have been described according to a limited number of embodiments, it will be apparent to those skilled in the art, with the benefit of the above description, that other embodiments may be envisioned within the scope of the embodiments of the present invention thus described. In addition, it should be noted that the language used in this specification is selected primarily for readability and teaching purposes, rather than for explaining or limiting the subject matter of the embodiments of the present invention. Therefore, many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the appended claims. With respect to the scope of the embodiments of the present invention, the disclosure of the embodiments of the present invention is illustrative and not restrictive, and the scope of the embodiments of the present invention is defined by the appended claims.
Claims
1. An exception handling method for a content distribution network, the content distribution network comprising a cache server for distributing content and a dispatch server for resolving domain names, the cache server storing content provided by a content provider and using a service address associated with the content provider to distribute content to a client of the content provider, the method include: When an abnormality is detected in the first cache server, determining a target content provider corresponding to the abnormality; as well as Sending a service update instruction to the scheduling server, wherein the service update instruction instructs the scheduling server to point the scheduling domain name of the target content provider to the second cache server, and the second cache server replaces the first cache server to distribute content to the client of the target content provider; In response to a service configuration instruction of a content provider, allocating a scheduling domain name and a plurality of cache servers for distributing content to the content provider; The scheduling domain name assigned to the content provider, the service addresses of the multiple cache servers and their associations are sent to the scheduling server so that the scheduling server configures the resolution record corresponding to the scheduling domain name; the resolution record stores the scheduling domain name and the service addresses of the multiple cache servers pointed to by the scheduling domain name.
2. The method according to claim 1, further comprising: include: Receiving access information of each cache server in the content distribution network; Based on the access information, each cache server is monitored to see whether an abnormality occurs.
3. The method according to claim 1, wherein the cache server has at least one service address, the anomaly comprises an abnormality in access to the service address, and the step of determining a target content provider corresponding to the anomaly include: Determine a first service address of the first cache server corresponding to the exception; The target content provider associated with the first service address is determined.
4. The method according to claim 3, in, The step of determining the target content provider associated with the first service address comprises: A source server domain name of the target content provider associated with the first service address is determined.
5. The method according to claim 1, further comprising: include: Based on the exception, the second cache server is determined to replace the first cache server.
6. The method according to claim 3, in, The scheduling domain name includes the total scheduling domain name corresponding to the target content provider, the service update instruction includes the first service address, the second service address and the total scheduling domain name of the target content provider, the first cache server uses the first service address to distribute content to the target content provider, and the second cache server uses the second service address to distribute content to the target content provider.
7. The method according to claim 4, in, The scheduling domain name includes a sub-scheduling domain name corresponding to the source server domain name of the target content provider, the service update instruction includes the first service address, the second service address and the sub-scheduling domain name corresponding to the source server domain name, the first cache server uses the first service address to distribute content for the source server domain name of the target content provider, and the second cache server uses the second service address to distribute content for the source server domain name of the target content provider.
8. The method of claim 1, further comprising: include: receiving a service configuration instruction from a content provider; In response to the service configuration instruction, a service address associated with the content provider is allocated to each cache server allocated to the content provider, so that each cache server distributes content for the content provider using the associated service address.
9. The method according to claim 8, in, The step of allocating a scheduling domain name to the content provider includes: A general scheduling domain name corresponding to the content provider is allocated so as to obtain sub-scheduling domain names corresponding to each source server domain name of the content provider based on the general scheduling domain name.
10. The method according to claim 9, in, The step of allocating a plurality of cache servers for distributing content to the content provider comprises: Multiple cache servers for distributing content are allocated to the source server domain name of the content provider.
11. The method according to claim 8, in, Also includes: Based on the scheduling domain name assigned to the content provider, the service addresses of the cache servers and their associations, configure a resolution record corresponding to the scheduling domain name; The parsing record is sent to the scheduling server.
12. The method of claim 7, further comprising: include: When it is monitored that access to the second service address has returned to normal, a service recovery instruction is sent to the scheduling server to instruct the scheduling server to redirect the total scheduling domain name corresponding to the target content provider or the sub-scheduling domain name corresponding to the source server domain name of the target content provider to the first cache server.
13. The method of claim 1, in, The service address is a virtual IP address.
14. The method of claim 1, in, The attack protection capability and / or traffic processing capability of the second cache server is higher than that of the first cache server.
15. An exception handling method for a content distribution network, the content distribution network comprising a cache server for distributing content and a dispatch server for resolving domain names, the cache server storing content provided by a content provider and distributing content to a client of the content provider using a service address associated with the content provider, the method include: The scheduling server receives a service update instruction; as well as In response to the service update instruction, replacing the first cache server originally pointed to by the dispatch domain name of the target content provider with a second cache server, and the second cache server replaces the first cache server to distribute content to the client of the target content provider; Receiving the dispatching domain name of the content provider and the service addresses of multiple cache servers sent by the control server; According to the scheduling domain name, the service addresses of the multiple cache servers and their associations, configure a resolution record corresponding to the scheduling domain name; The resolution record stores the dispatch domain name and the service addresses of multiple cache servers pointed to by the dispatch domain name; The control server is further used to allocate a scheduling domain name and a plurality of cache servers for distributing content to the content provider in response to a service configuration instruction of the content provider.
16. The method of claim 15, in, The scheduling server stores a plurality of resolution records, the resolution records include a scheduling domain name and a service address of a cache server pointed to by the scheduling domain name, the service update instruction includes a first service address and a second service address, the first cache server uses the first service address to distribute content to the target content provider, and the second cache server uses the second service address to distribute content to the target content provider, The step of replacing the first cache server originally pointed to by the dispatch domain name of the target content provider with the second cache server includes: A resolution record including the scheduling domain name of the target content provider and the first service address is queried, and the first service address recorded in the queried resolution record is updated to the second service address.
17. An exception handling method, include: When an exception is detected in the first cache server, a target content provider corresponding to the exception is determined through a service address used by the first cache server, and the first cache server stores content provided by the content provider; as well as Sending a service update instruction to the scheduling server, wherein the service update instruction instructs the scheduling server to point the scheduling domain name of the target content provider to the second cache server, so that the second cache server replaces the first cache server to distribute content for the target content provider; In response to a service configuration instruction of a content provider, allocating a scheduling domain name and a plurality of cache servers for distributing content to the content provider; The scheduling domain name assigned to the content provider, the service addresses of the multiple cache servers and their associations are sent to the scheduling server so that the scheduling server configures the resolution record corresponding to the scheduling domain name; the resolution record stores the scheduling domain name and the service addresses of the multiple cache servers pointed to by the scheduling domain name.
18. An exception handling device for a content distribution network, the content distribution network comprising a cache server for distributing content and a dispatch server for resolving domain names, the cache server storing content provided by a content provider and using a service address associated with the content provider to distribute content to a client of the content provider, the device include: an abnormality locating unit, adapted to determine a target content provider corresponding to the abnormality when an abnormality is detected in the first cache server; as well as a service update unit, adapted to send a service update instruction to the scheduling server, wherein the service update instruction instructs the scheduling server to point the scheduling domain name of the target content provider to a second cache server, and the second cache server replaces the first cache server to distribute content to the client of the target content provider; The device is also used for: In response to a service configuration instruction of a content provider, allocating a scheduling domain name and a plurality of cache servers for distributing content to the content provider; The scheduling domain name assigned to the content provider, the service addresses of the multiple cache servers and their associations are sent to the scheduling server so that the scheduling server configures the resolution record corresponding to the scheduling domain name; the resolution record stores the scheduling domain name and the service addresses of the multiple cache servers pointed to by the scheduling domain name.
19. An exception handling device for a content distribution network, the content distribution network comprising a cache server for distributing content and a dispatch server for resolving domain names, the cache server storing content provided by a content provider and using a service address associated with the content provider to distribute content to a client of the content provider, the device include: An instruction receiving unit, adapted to receive a service update instruction; as well as a record updating unit, adapted to replace the first cache server originally pointed to by the dispatching domain name of the target content provider with a second cache server in response to the service update instruction, wherein the second cache server replaces the first cache server to distribute content to the client of the target content provider; The device is also used for: In response to a service configuration instruction of a content provider, allocating a scheduling domain name and a plurality of cache servers for distributing content to the content provider; The scheduling domain name assigned to the content provider, the service addresses of the multiple cache servers and their associations are sent to the scheduling server so that the scheduling server configures the resolution record corresponding to the scheduling domain name; the resolution record stores the scheduling domain name and the service addresses of the multiple cache servers pointed to by the scheduling domain name.
20. A content distribution network system, include: a cache server adapted to distribute content for a content provider using a service address associated with the content provider; A scheduling server, comprising the exception handling device as claimed in claim 19, and adapted to resolve the scheduling domain name of the content provider to obtain the service address pointed to by the scheduling domain name; as well as A control server comprising the exception handling device as claimed in claim 18.
21. A computing device, include: one or more processors; and Memory; One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for executing any one of the exception handling methods according to claims 1-17.
22. A computer-readable storage medium storing one or more programs, wherein the one or more programs include instructions, and when a computing device executes the instructions, the computing device executes any one of the exception handling methods according to claims 1-17.
