CN110830564A - CDN scheduling method, apparatus, system, and computer-readable storage medium - Google Patents

Abstract

The present invention provides a CDN scheduling method, device, system and computer-readable storage medium, and relates to the field of Internet technology. By acquiring target scheduling requirement information carried in an access request from a client, the scheduling unit indicated by the target scheduling requirement information It is smaller than the scheduling unit composed of the request domain name and the area; the target edge server is determined based on the target scheduling requirement information, and then the client is scheduled to the target edge server, which realizes the scheduling according to the target scheduling requirement information, which is different from the prior art that can only Compared with scheduling based on region and request domain name, the granularity of scheduling is improved, thereby alleviating the user's refined scheduling requirements.

Description

CDN scheduling method, apparatus, system, and computer-readable storage medium

technical field

The present invention relates to the field of Internet technologies, and in particular, to a CDN scheduling method, device, system, and computer-readable storage medium.

Background technique

The full name of CDN is Content Delivery Network, that is, Content Delivery Network. CDN is a content distribution network built on the network, relying on edge servers deployed in various places, through the load balancing, content distribution, scheduling and other functional modules of the central platform, so that users can obtain the desired content nearby, reduce network congestion, and improve user access. Response speed and hit rate.

The CDN scheduling system schedules users' access requests to CDN edge nodes (ie, CDN edge nodes) according to certain scheduling strategies, such as CDN's GSLB (global server load balance) scheduling system based on nearby scheduling, quality priority, cost priority and other strategies. edge server).

HTTP (Hypertext Transfer Protocol, Hypertext Transfer Protocol) scheduling is a common scheduling method in a CDN scheduling system. The scheduling strategy of the existing HTTP scheduling usually includes one or more of the following principles: the principle of proximity, the principle of quality, the principle of cost, etc., the scheduling granularity is generally to the region, and the region is usually divided into provinces (or municipalities) and operators. For example, Shenzhen Telecom, Shenzhen Mobile, Guangdong Telecom, etc. are all different regions. These regions plus the request domain name are used as scheduling units, that is, the same region plus the same request domain name will get the same response. However, the scheduling granularity of this CDN scheduling method is not fine enough to meet the refined scheduling requirements of users.

SUMMARY OF THE INVENTION

The purpose of the present invention is to provide a CDN scheduling method, device, system and computer-readable storage medium, so as to improve the fineness of the scheduling granularity, thereby alleviating the refined scheduling requirements of users.

The present invention provides a CDN scheduling method, including:

When receiving the access request from the client, obtain the target scheduling requirement information carried in the access request; wherein, the scheduling unit indicated by the target scheduling requirement information is smaller than the scheduling unit composed of the request domain name and the area;

Determine the target edge server corresponding to the access request according to the target scheduling requirement information and the preset matching relationship between the edge server and the scheduling requirement information;

The client is scheduled to the target edge server.

Further, the obtaining target scheduling requirement information carried in the access request includes:

If the access request is an HTTP request, the HTTP header information is parsed from the HTTP request, and the HTTP header information is used as the target scheduling requirement information corresponding to the HTTP request;

The target scheduling requirement information carries target domain name information corresponding to the requested domain name and scheduling index information, and the scheduling index information includes one or more of a uniform resource identifier URI path, a user agent, and a resource file type.

Further, the matching relationship includes the first corresponding relationship between the request domain name and the scheduling policy and the second corresponding relationship between the matching result and the scheduling group; Matching relationship, determine the target edge server corresponding to the access request, including:

Determine a target scheduling policy corresponding to the target domain name information according to the first correspondence; wherein, the target scheduling policy includes a target matching rule corresponding to the scheduling index information;

Matching the scheduling indicator information with the corresponding target matching rule to obtain a target matching result;

Determine the target scheduling group corresponding to the target matching result according to the second correspondence;

A target edge server is selected from a plurality of edge servers in the target scheduling group.

Further, the target scheduling policy further includes the priority order of multiple target matching rules; the matching of the scheduling index information with the corresponding target matching rules to obtain a target matching result, including:

According to the priority order, the target scheduling information is sequentially matched with the corresponding target matching rules;

When the matching fails, continue to match the target scheduling information with the next target matching rule;

When the matching is successful or the matching of each of the target matching rules is completed, the target matching result is determined.

Further, the scheduling indicator information includes a URI path, a user agent, and a resource file type, and the target matching rule includes a URI path matching rule corresponding to the URI path, a user agent matching rule corresponding to the user agent, and a matching rule corresponding to the user agent. The resource file type matching rule corresponding to the resource file type, the priority order includes that the priority of the URI path matching rule is higher than the priority of the user agent matching rule, and the priority of the user agent matching rule Higher priority than the resource file type matching rule.

Further, the selecting a target edge server from multiple edge servers in the target scheduling group includes:

A target edge server is selected from a plurality of edge servers in the target scheduling group in a random manner or a hash algorithm.

Further, the scheduling of the client to the target edge server includes:

constructing a uniform resource locator of the target edge server according to the IP address of the target edge server;

A response message carrying the uniform resource locator of the target edge server is returned to the client, so that the client can access the target edge server based on the uniform resource locator of the target edge server.

The present invention provides a CDN scheduling device, comprising:

an obtaining module, configured to obtain the target scheduling requirement information carried in the access request when receiving the access request from the client; wherein, the scheduling unit indicated by the target scheduling requirement information is smaller than the scheduling unit composed of the request domain name and the area ;

a determining module, configured to determine a target edge server corresponding to the access request according to the target scheduling requirement information and a preset matching relationship between the edge server and the scheduling requirement information;

A scheduling module, configured to schedule the client to the target edge server.

The present invention provides an edge scheduling server, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and the processor implements the above CDN scheduling method when executing the computer program .

The present invention provides a CDN scheduling system, comprising a central scheduling server and the above-mentioned edge scheduling server, wherein the edge scheduling server is connected with the central scheduling server;

The edge scheduling server is configured to acquire the matching relationship between the edge server and the scheduling requirement information from the central scheduling server.

The present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, it is the above-mentioned CDN scheduling method.

In the CDN scheduling method, device, system and computer-readable storage medium provided by the present invention, the method includes: when an access request from a client is received, acquiring target scheduling requirement information carried in the access request; wherein, the target scheduling requirement information The indicated scheduling unit is smaller than the scheduling unit composed of the request domain name and the area; according to the target scheduling requirement information and the matching relationship between the preset edge server and the scheduling requirement information, determine the target edge server corresponding to the access request; schedule the client to the target edge server. The method obtains the target scheduling requirement information carried in the access request of the client, determines the target edge server based on the target scheduling requirement information, and then schedules the client to the target edge server, so as to realize the scheduling according to the target scheduling requirement information. The scheduling unit indicated by the scheduling requirement information is smaller than the scheduling unit composed of the request domain name and the area, so compared with the prior art, which can only be scheduled for the area and the request domain name, the fineness of the scheduling granularity is improved, thereby alleviating the user's worries. Refinement scheduling requirements.

Description of drawings

In order to illustrate the specific embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the specific embodiments or the prior art. Obviously, the accompanying drawings in the following description The drawings are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of an application environment of a CDN scheduling method provided by an embodiment of the present invention;

FIG. 2 is a schematic flowchart of a CDN scheduling method provided by an embodiment of the present invention;

3 is a schematic flowchart of a method for implementing step S204 in FIG. 2;

FIG. 4 is a schematic flowchart of another CDN scheduling method provided by an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a CDN scheduling apparatus provided by an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of an edge scheduling server according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a CDN scheduling system according to an embodiment of the present invention.

Detailed ways

The technical solutions of the present invention will be clearly and completely described below with reference to the embodiments. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

Referring to the schematic diagram of the application environment of a CDN scheduling method shown in FIG. 1, in an embodiment of the CDN scheduling method provided by the present invention, the application environment includes: a client, a DNS system, an HTTP scheduling system, and an edge server, wherein, The HTTP scheduling system is a scheduling system that adopts HTTP scheduling (HTTP scheduling is also called HTTP302 scheduling). HTTP302 scheduling has the advantages of high accuracy, good flexibility, quick effect, and is difficult to be hijacked. It is more suitable for scheduling resources such as large files and video files.

The principle of HTTP302 scheduling is as follows: First, the client accesses the HTTP scheduling system through the DNS system, the HTTP scheduling system selects the optimal edge server, and assembles the HTTP response with the IP (Internet Protocol) address of the edge server. The URL of the header (Uniform Resource Locator, Uniform Resource Locator), the URL is responded to the client through the status code of 302, and then the client initiates a connection according to the URL. It should be noted that the servers that directly interact with the client are all edge servers, that is, the scheduling server that directly interacts with the client in the HTTP scheduling system also belongs to the edge server (herein referred to as the edge scheduling server).

Specifically, as shown in Figure 1, the process of HTTP302 scheduling is as follows: Process 1, the client sends a DNS request to the DNS system, and the DNS request includes the requested domain name; Process 2, the DNS system returns the IP address of the scheduling server based on the requested domain name; Process 3 , the client sends an HTTP request to the HTTP scheduling system based on the IP address of the scheduling server, the HTTP request includes a request URL, and the request URL points to the resource that the client requests to access; process 4, the HTTP scheduling system returns a response message with a status code of 302 (that is, 302 response), the response message includes the edge server URL pointing to the target edge server; process 5, the client sends a request message to the corresponding edge server (that is, the target edge server) based on the edge server URL, and the request message includes the request URL; process 6 , the edge server returns the content response corresponding to the request URL to the client. The embodiments of the present invention mainly relate to the interaction process between the client and the HTTP scheduling system, that is, mainly relate to the process 3 and the process 4 in the above process.

In the prior art, the scheduling granularity of the HTTP scheduling system generally depends on the area, and the area plus the request domain name is used as the scheduling unit, and the scheduling granularity is not fine enough. In the embodiment of the present invention, by analyzing the scheduling requirement information carried in the HTTP request by the edge scheduling server, the scheduling for the target scheduling requirement information can be realized, and the fineness of the scheduling granularity can be improved.

To facilitate understanding of this embodiment, a CDN scheduling method disclosed in the embodiment of the present invention is first introduced in detail.

FIG. 2 is a schematic flowchart of a CDN scheduling method according to an embodiment of the present invention. The method may be executed by an edge scheduling server in the above-mentioned HTTP scheduling system. As shown in Figure 2, the CDN scheduling method includes the following steps:

Step S202, when an access request from the client is received, obtain target scheduling requirement information carried in the access request; wherein, the scheduling unit indicated by the target scheduling requirement information is smaller than the scheduling unit composed of the request domain name and the area.

In this embodiment, the scheduling unit refers to the smallest unit capable of making different scheduling responses, that is, the scheduling responses corresponding to multiple access requests having the same scheduling unit are the same. The above areas can be divided into provinces (or municipalities directly under the Central Government) and operators.

In some possible embodiments, the above-mentioned access request is an HTTP request, and the above-mentioned step S202 includes: parsing out the HTTP header information from the HTTP request, and using the HTTP header information as the target scheduling requirement information corresponding to the HTTP request; wherein , the target scheduling demand information includes target domain name information corresponding to the request domain name and scheduling index information, that is, the scheduling unit indicated by the target scheduling demand information is composed of the request domain name and the scheduling index information. The scheduling indicator information can be selected according to actual requirements, and the scheduling indicator information can be any HTTP header information or self-defined HTTP header information.

Specifically, the HTTP header information includes request header information, the request header information includes user agent, resource file type, and request URL, etc., and the request URL includes the request domain name and URI (Uniform Resource Identifier); wherein, the user Agent is User-Agent; resource file types include pictures, video files, ordinary text, etc. Based on this, in some possible implementations, the request header information is used as the target scheduling requirement information, and the scheduling indicator information includes one or more of URI path, User-Agent, and resource file type. When the scheduling indicator information includes the User-Agent, specifically, the client type in the User-Agent may be used as the scheduling indicator information.

Step S204: Determine the target edge server corresponding to the access request according to the target scheduling requirement information and the preset matching relationship between the edge server and the scheduling requirement information.

The target edge server corresponding to the access request is determined based on the above target scheduling requirement information and the above matching relationship. For example, the corresponding target edge server is determined according to the URI path, User-Agent and resource file type, etc., which can meet the requirements of certain specific scenarios. Scheduling requirements, the same request domain name and the same area can return completely different responses, to achieve more accurate, finer-grained scheduling in special business scenarios, and make up for the shortcomings of traditional HTTP302 scheduling methods.

Step S206, the client is scheduled to the target edge server.

In a possible implementation manner, step S206 includes: constructing a uniform resource locator of the target edge server according to the IP address of the target edge server; returning a response message carrying the uniform resource locator of the target edge server to the client, so that the The client accesses the target edge server based on the uniform resource locator of the target edge server.

Optionally, the edge scheduling server may use the IP address of the target edge server to assemble the URL of the Location response field of the HTTP response header, and respond to the client in a manner of status code 302. In this way, the client can access the target edge server based on the assembled URL.

In the embodiment of the present invention, the method obtains the target scheduling requirement information carried in the access request of the client, determines the target edge server based on the target scheduling requirement information, and then schedules the client to the target edge server, thereby realizing the target scheduling requirement. The scheduling of information, because the scheduling unit indicated by the target scheduling requirement information is smaller than the scheduling unit composed of the request domain name and the area, so compared with the prior art, which can only be scheduled for the area and the request domain name, the fineness of the scheduling granularity is improved. , thereby alleviating the user's refined scheduling requirements.

The embodiment of the present invention provides an optional implementation manner of the above step S204. In this implementation manner, the target scheduling requirement information includes target domain name information corresponding to the request domain name and scheduling index information, and the matching relationship includes the request domain name and the scheduling policy. The first corresponding relationship and the matching result of , and the second corresponding relationship of the scheduling group. As shown in Figure 3, step S204 includes the following sub-steps:

Step S302 , determining a target scheduling policy corresponding to the target domain name information according to the first corresponding relationship; wherein, the target scheduling policy includes a target matching rule corresponding to the scheduling index information.

The edge scheduling server stores the configured scheduling policy. The configuration granularity of the scheduling policy can be the domain name, that is, each domain name has its own scheduling policy. If a domain name does not have a scheduling policy configured, it means that the domain name does not need to use this scheduling method. The scheduling policy includes one or more matching rules corresponding to the scheduling index information. Here, the scheduling policy corresponding to the request domain name is called the target scheduling policy, and the matching rules included in the target scheduling policy are called the target matching rule. The edge scheduling server may determine the target scheduling policy corresponding to the target domain name information by looking up the first correspondence.

Further optionally, when the target scheduling policy includes multiple target matching rules, the target scheduling policy further includes the priority order of the multiple target matching rules. It should be noted that the priority order can be set according to actual requirements.

In an optional implementation manner, the scheduling indicator information includes a URI path, a user agent, and a resource file type; the target matching rule includes a URI path matching rule corresponding to the URI path, a user agent matching rule corresponding to the user agent, and a resource matching rule corresponding to the resource The resource file type matching rule corresponding to the file type; the priority order includes that the priority of the URI path matching rule is higher than the priority of the user agent matching rule, and the priority of the user agent matching rule is higher than the priority of the resource file type matching rule.

Step S304: Match the above scheduling index information with the corresponding target matching rule to obtain a target matching result.

In an optional implementation manner, when there is only one target matching rule, the above-mentioned scheduling indicator information is directly matched with the target matching rule to obtain a target matching result, where the target matching result includes matching with the target matching rule Or the match fails.

When there are only a plurality of target matching rules, the above-mentioned target scheduling policy also includes the priority order of the plurality of target matching rules. At this time, the target scheduling information can be matched with the corresponding target matching rules in sequence according to the priority order; when the matching fails When the target scheduling information is matched, the next target matching rule is continued to be matched; when the matching is successful or the matching of each target matching rule is completed, the target matching result is determined. The target matching result includes matching with a certain target matching rule or failing to match. It should be noted that each target matching rule may be a rule or may include multiple sub-rules, and the target matching result may be refined to match a certain sub-rule.

Step S306: Determine the target scheduling group corresponding to the target matching result according to the second corresponding relationship.

When configuring a matching rule, the scheduling group corresponding to each matching rule will be specified (if multiple sub-rules are included, each sub-rule corresponds to a scheduling group), indicating that if the matching rule is matched, it will be scheduled to this scheduling group. That is, when the target matching result matches a certain target matching rule, the target scheduling group is the scheduling group corresponding to the target matching rule. In addition, each domain name has a default scheduling group. If no matching rule is matched (that is, the matching fails), the target scheduling group is determined as the default scheduling group.

A scheduling group is a collection of service nodes (edge servers) that store the content that users want to access. If the content is not available, the nodes will pull and cache the content from the customer origin site. The scheduling group can be flexibly configured, and different nodes can be configured according to different business types. For example, configure nodes with large bandwidth for video files, and configure BGP (Border Gateway Protocol) with small bandwidth but fast speed for PK (Player Killing, competition/challenge) domain names. , Border Gateway Protocol) node. The scheduling group can be represented by, but not limited to, k1, k2, k3, and so on.

For example, the scheduling policy can be configured as follows: in terms of priority, the URI path matching rule has the highest priority, followed by the user agent matching rule; the URI path matching rule includes URI sub-rule 1 and URI sub-rule 2, and URI sub-rule 1 is: if yes If it starts with /rule1, it will be scheduled to scheduling group k1; URI sub-rule 2 is: if it starts with /rule2, it will be scheduled to scheduling group k2. The user agent matching rule is that if User-Agent contains the bowser123 keyword, it will be dispatched to dispatch group k3.

Step S308, selecting a target edge server from a plurality of edge servers in the above-mentioned target scheduling group.

Once the target scheduling group is determined, the target edge server that finally responds to the content must come from this scheduling group. Since the target scheduling group includes multiple edge servers, each response can only be one edge server. If one is selected, the target edge server may be selected from multiple edge servers in the target scheduling group in a random manner or a hash algorithm, but is not limited to.

In a possible implementation manner, the target scheduling group includes the IP addresses corresponding to the edge servers, and the IP address in the final 302 response must come from this target scheduling group, because there are multiple IP addresses in the target scheduling group , each response can only be one IP address, so one needs to be selected from multiple IP addresses, and the selected method can be but not limited to random or hash algorithm.

For ease of understanding, an embodiment of the present invention also provides a specific implementation of a CDN scheduling method. In this implementation, the scheduling indicator information includes a URI path and a user agent, and the target scheduling policy includes URI path matching rules, user agent matching rules and Priority order, where the priority order is that the priority of the URI path matching rule is higher than the priority of the user agent matching rule. Referring to the schematic flowchart of another CDN scheduling method shown in FIG. 4 , the method includes the following steps:

Step S402, when an access request from the client is received, the target domain name information, the URI path and the User-Agent are parsed from the access request.

Step S404: Determine a target scheduling policy according to the target domain name information, where the target scheduling policy includes a URI path matching rule and a user agent matching rule.

Step S406, judging whether the URI path matches the URI path matching rule. If no, go to step S407; if yes, go to step S408.

Step S407, judging whether the User-Agent matches the user-agent matching rule. If yes, go to step S409; if not, go to step S410.

Step S408, determining that the target scheduling group is the scheduling group corresponding to the above-mentioned URI path matching rule.

Step S409, determining that the target scheduling group is the scheduling group corresponding to the above-mentioned user agent matching rule.

Step S410, determining the target scheduling group as the default scheduling group.

Step S412, randomly select an IP address in the target scheduling group, use the IP address to synthesize the HTTP302 response URL, and return it to the client.

In this embodiment, the scheduling based on the target domain name information, the URI path and the User-Agent in the HTTP header information can make the scheduling more accurate and targeted, and can make up for the shortcomings of the traditional HTTP302 scheduling. After verification, for some clients with poor access, after applying this method, the access effect is obviously improved.

The embodiment of the present invention also provides a specific example of applying the above CDN scheduling method. The following describes how the 302 response is returned in conjunction with a specific scheduling policy. Assuming that the requested domain name is 123.com, the scheduling policy is as follows: the priority of the URI path matching rule is higher than that of the user agent matching rule, the URI path matching rule is that the URI request is scheduled to group k1 under the /video path, and the user agent matches The rule is that User-Agent containing the kscdn keyword is scheduled to group k2, and the default scheduling group is k0. A representation of this scheduling policy is as follows:

At the same time, it is assumed that the IP addresses of the nodes under the k0 scheduling group are 1.1.1.1 and 2.2.2.2, the IP addresses of the nodes under the k1 scheduling group are 3.3.3.3 and 4.4.4.4, and the node IP addresses under the k2 scheduling group are 5.5. 5.5 and 6.6.6.6, the responses to different access requests are as follows:

In the first case, the request URI is /video/abc.mp4 (matching the URI path matching rule). Since the URI has the highest priority, regardless of whether the User-Agent matches or not, the access request will be combined with the IP addresses in the k1 scheduling group to respond with 302 .

Access request: curl http://123.com/video/abc.mp4-H"User-Agent:kscdn-client".

302 response: http://3.3.3.3/123.com/video/abc.mp4 (3.3.3.3 and 4.4.4.4 random).

Indicates that the access request is transferred to the edge server 3.3.3.3.

In the second case, the request URI is /game/xyz.jpg (does not match the URI path matching rule), User-Agent contains the keyword kscdn (matches the user agent matching rule), this access request will be synthesized by the IP addresses in the k2 scheduling group 302 response.

Access request: curl http://123.com/game/xyz.jpg-H"User-Agent:kscdn-client".

302 response: http://5.5.5.5/123.com/game/xyz.jpg (5.5.5.5 and 6.6.6.6 random).

Indicates that the access request is transferred to the edge server 5.5.5.5.

In the third case, the request URI is /game/xyz.jpg, the kscdn keyword is not included in the User-Agent, and the two rules do not match. In this case, the IP address in the default scheduling group k0 is synthesized with a 302 response.

Access request: curl http://123.com/game/xyz.jpg-H"User-Agent:xxxxyyyyzzz".

302 response: http://1.1.1.1/123.com/game/xyz.jpg (1.1.1.1 and 2.2.2.2 random).

Indicates that the access request is transferred to the edge server 1.1.1.1.

In this way, access requests for the same domain name are scheduled to different nodes (edge servers), or the same access resource (request URL) under the same domain name is scheduled to different nodes due to different clients. These rules are flexibly combined. Applications can meet the needs of special business.

To sum up, the CDN scheduling method provided in this embodiment has finer scheduling granularity. Even the same domain name in the same area can be scheduled to different nodes (edge servers) according to different factors such as clients and access resources.

An embodiment of the present invention further provides a CDN scheduling apparatus, which is mainly used to execute the CDN scheduling method provided by the above content of the embodiment of the present invention. The following will introduce the CDN scheduling apparatus provided by the embodiment of the present invention.

Referring to the schematic structural diagram of a CDN scheduling apparatus shown in FIG. 5, the apparatus includes:

The obtaining module 52 is used to obtain the target scheduling requirement information carried in the access request when receiving the access request of the client; wherein, the scheduling unit indicated by the target scheduling requirement information is smaller than the scheduling unit formed by the request domain name and the area;

The determining module 54 is configured to determine the target edge server corresponding to the access request according to the target scheduling requirement information and the preset matching relationship between the edge server and the scheduling requirement information;

The scheduling module 56 is configured to schedule the client to the target edge server.

In this embodiment, when receiving the access request from the client, the obtaining module 52 obtains the target scheduling requirement information carried in the access request; wherein, the scheduling unit indicated by the target scheduling requirement information is smaller than the scheduling unit composed of the request domain name and the area The determining module 54 determines the target edge server corresponding to the access request according to the target scheduling requirement information and the matching relationship between the preset edge server and the scheduling requirement information; the scheduling module 56 schedules the client to the target edge server. The device obtains the target scheduling requirement information carried in the client's access request, determines the target edge server based on the target scheduling requirement information, and then schedules the client to the target edge server, thereby realizing the scheduling for the target scheduling requirement information. The scheduling unit indicated by the scheduling requirement information is smaller than the scheduling unit composed of the request domain name and the area. Therefore, compared with the prior art, which can only be scheduled for the area and the request domain name, the fineness of the scheduling granularity is improved, thereby alleviating the user's worries. Refinement scheduling requirements.

Optionally, the above-mentioned obtaining module 52 is specifically configured to: if the access request is an HTTP request, then parse out the HTTP header information from the HTTP request, and use the HTTP header information as the target scheduling requirement information corresponding to the HTTP request; wherein, The target scheduling requirement information carries target domain name information corresponding to the requested domain name and scheduling index information, and the scheduling index information includes one or more of a URI path, a user agent, and a resource file type.

Optionally, the above-mentioned matching relationship includes a first corresponding relationship between the request domain name and the scheduling policy and a second corresponding relationship between the matching result and the scheduling group; the above-mentioned determining module 54 is specifically configured to: determine the target corresponding to the target domain name information according to the first corresponding relationship. scheduling strategy; wherein, the target scheduling strategy includes target matching rules corresponding to the scheduling index information; the scheduling index information is matched with the corresponding target matching rules to obtain a target matching result; the target scheduling corresponding to the target matching result is determined according to the second correspondence group; selects the target edge server from multiple edge servers in the target scheduling group.

Optionally, the above-mentioned target scheduling strategy further includes the priority order of multiple target matching rules; when the above-mentioned determining module 54 matches the scheduling index information with the corresponding target matching rules to obtain the target matching result, it is specifically used for: according to the priority. The target scheduling information is matched with the corresponding target matching rules in sequence; when the matching fails, the target scheduling information continues to be matched with the next target matching rule; when the matching is successful or the matching of each target matching rule is completed, the target matching is determined. result.

Optionally, the above-mentioned scheduling indicator information includes a URI path, a user agent, and a resource file type, and the target matching rule includes a URI path matching rule corresponding to the URI path, a user agent matching rule corresponding to the user agent, and a resource corresponding to the resource file type. File type matching rules. The priority order includes that the priority of URI path matching rules is higher than that of user agent matching rules, and the priority of user agent matching rules is higher than that of resource file type matching rules.

Optionally, when selecting the target edge server from the multiple edge servers in the target scheduling group, the above determining module 54 is specifically configured to: select the target edge server from the multiple edge servers in the target scheduling group in a random manner or a hash algorithm. .

Optionally, the above-mentioned scheduling module 56 is specifically configured to: construct a uniform resource locator of the target edge server according to the IP address of the target edge server; return a response message carrying the uniform resource locator of the target edge server to the client, so that the client The terminal accesses the target edge server based on the uniform resource locator of the target edge server.

The implementation principle and technical effects of the device provided in this embodiment are the same as those in the foregoing method embodiments. For brief description, for the parts not mentioned in the device embodiments, reference may be made to the corresponding content in the foregoing method embodiments.

6, an embodiment of the present invention further provides an edge scheduling server 600, including: a processor 60, a memory 61, a bus 62 and a communication interface 63, the processor 60, the communication interface 63 and the memory 61 are connected through the bus 62; The processor 60 is used to execute executable modules, such as computer programs, stored in the memory 61 .

The memory 61 may include a high-speed random access memory (RAM, Random Access Memory), and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory. The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 63 (which may be wired or wireless), which may use the Internet, a wide area network, a local area network, a metropolitan area network, and the like.

The bus 62 may be an ISA bus, a PCI bus, an EISA bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one bidirectional arrow is shown in FIG. 6, but it does not mean that there is only one bus or one type of bus.

The memory 61 is used to store a program, and the processor 60 executes the program after receiving the execution instruction. The method executed by the apparatus defined by the stream process disclosed in any of the foregoing embodiments of the present invention can be applied to processing in the processor 60 , or implemented by the processor 60 .

The processor 60 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method can be completed by a hardware integrated logic circuit in the processor 60 or an instruction in the form of software. The above-mentioned processor 60 may be a general-purpose processor, including a central processing unit (CPU for short), a network processor (NP for short), etc.; it may also be a digital signal processor (Digital Signal Processing, DSP for short) , Application Specific Integrated Circuit (ASIC for short), Field-Programmable Gate Array (FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components. Various methods, steps, and logical block diagrams disclosed in the embodiments of the present invention can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present invention may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory 61, and the processor 60 reads the information in the memory 61, and completes the steps of the above method in combination with its hardware.

The implementation principle and the technical effects of the edge scheduling server provided in this embodiment are the same as those in the foregoing method embodiments. For brief description, for the parts not mentioned in the edge scheduling server embodiments, reference may be made to the corresponding content in the foregoing method embodiments. .

Referring to the schematic diagram of the structure of a CDN scheduling system shown in FIG. 7, the CDN scheduling system includes a central scheduling server 70 and the above-mentioned edge scheduling server 72. The edge scheduling server 72 is connected to the central scheduling server 70; The scheduling server obtains the matching relationship between the edge server and the scheduling requirement information.

As shown in FIG. 7 , in some possible embodiments, the data transmission of the above-mentioned CDN scheduling system adopts the architecture of one central scheduling server 70 and multiple edge scheduling servers 72 (the number of edge scheduling servers 72 is not limited to those shown in FIG. 7 ). 7 is only an example), the central scheduling server 70 is responsible for the configuration and storage of scheduling policies, and provides an API (Application Programming Interface, application program interface) interface. Each edge scheduling server 72 synchronizes scheduling policies with the central scheduling server 70 and responds to the client's access request according to these scheduling policies. When the edge scheduling server 72 responds to the user's access request, it makes decisions based on the HTTP header information or URI path, etc., so that the same domain name and the same area can return completely different responses, so as to achieve more accurate, finer-grained, special Scheduling in business scenarios makes up for the shortcomings of traditional HTTP302 scheduling.

Specifically, the central scheduling server 70 is mainly responsible for the storage of the relationship between the request domain name and the scheduling group, configuration data, etc., and at the same time responds to the request of the edge scheduling server 72 , and delivers the configured policy to the edge scheduling server 72 .

The edge scheduling server 72 may periodically request information such as the configured scheduling policy from the central scheduling server 70 by, but is not limited to, the pull (PULL) method, and the obtained information is stored in the memory and the memory database of the edge scheduling server 72 . When responding to the user's access request, the edge scheduling server 72 will perform logical processing according to the scheduling policy of the requested domain name and the like.

The scheduling policy can be configured, but is not limited to: in terms of priority, the URI path matching rule has the highest priority, followed by the user agent matching rule; the URI path matching rule is that if the URI starts with /rule1, it will be scheduled to scheduling group k1, if it is Starting with /rule2, it will be scheduled to scheduling group k2; the user agent matching rule is that if User-Agent contains the bowser123 keyword, it will be scheduled to scheduling group k3. Then after an access request arrives, first determine whether the request URI matches /rule1 or /rule2. If it matches, it will synthesize the response according to the configured scheduling group k1 or k2. If there is no match, continue to determine whether the User-Agent contains the bowser123 keyword. If there is a match, the response will be synthesized according to the specified scheduling group k3, and if there is no match, it will be processed according to the default scheduling group.

The implementation principle and technical effects of the system provided in this embodiment are the same as those in the foregoing method embodiments. For brief description, for the parts not mentioned in the system embodiments, reference may be made to the corresponding content in the foregoing method embodiments.

In all examples shown and described herein, any specific value should be construed as merely exemplary and not as limiting, as other examples of exemplary embodiments may have different values.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more functions for implementing the specified logical function(s) executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented in dedicated hardware-based systems that perform the specified functions or actions , or can be implemented in a combination of dedicated hardware and computer instructions.

The computer program product for performing the CDN scheduling method provided by the embodiment of the present invention includes a computer-readable storage medium storing a computer program, and the computer program executes the method described in the foregoing method embodiments when the computer program is run by a processor. Refer to the method embodiment, which is not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. The apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some communication interfaces, indirect coupling or communication connection of devices or units, which may be in electrical, mechanical or other forms.

The functions, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a processor-executable non-volatile computer-readable storage medium. Based on such understanding, the technical solution of the present invention can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes: U disk, removable hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features thereof can be equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the embodiments of the present invention. scope.

Claims (11)

1. a CDN scheduling method, is characterized in that, comprises: When receiving the access request from the client, obtain the target scheduling requirement information carried in the access request; wherein, the scheduling unit indicated by the target scheduling requirement information is smaller than the scheduling unit composed of the request domain name and the area; Determine the target edge server corresponding to the access request according to the target scheduling requirement information and the preset matching relationship between the edge server and the scheduling requirement information; The client is scheduled to the target edge server. 2. The method according to claim 1, wherein the acquiring target scheduling requirement information carried in the access request comprises: If the access request is an HTTP request, the HTTP header information is parsed from the HTTP request, and the HTTP header information is used as the target scheduling requirement information corresponding to the HTTP request; The target scheduling requirement information carries target domain name information corresponding to the requested domain name and scheduling index information, and the scheduling index information includes one or more of a uniform resource identifier URI path, a user agent, and a resource file type. 3. The method according to claim 2, wherein the matching relationship comprises a first corresponding relationship between a request domain name and a scheduling policy and a second corresponding relationship between a matching result and a scheduling group; the said matching relationship according to the target scheduling requirement The matching relationship between the information and the preset edge server and the scheduling requirement information to determine the target edge server corresponding to the access request, including: Determine a target scheduling policy corresponding to the target domain name information according to the first correspondence; wherein, the target scheduling policy includes a target matching rule corresponding to the scheduling index information; Matching the scheduling indicator information with the corresponding target matching rule to obtain a target matching result; Determine the target scheduling group corresponding to the target matching result according to the second correspondence; A target edge server is selected from a plurality of edge servers in the target scheduling group. 4. The method according to claim 3, wherein the target scheduling policy further comprises a priority order of a plurality of target matching rules; the scheduling indicator information is matched with the corresponding target matching rules to obtain Target matching results, including: According to the priority order, the target scheduling information is sequentially matched with the corresponding target matching rules; When the matching fails, continue to match the target scheduling information with the next target matching rule; When the matching is successful or the matching of each of the target matching rules is completed, the target matching result is determined. The method according to claim 4, wherein the scheduling indicator information comprises a URI path, a user agent and a resource file type, and the target matching rule comprises a URI path matching rule corresponding to the URI path, and a URI path matching rule corresponding to the URI path. The user agent matching rule corresponding to the user agent and the resource file type matching rule corresponding to the resource file type, and the priority order includes that the priority of the URI path matching rule is higher than the priority of the user agent matching rule. level, and the priority of the user agent matching rule is higher than the priority of the resource file type matching rule. 6. The method according to claim 3, wherein the selecting a target edge server from a plurality of edge servers in the target scheduling group comprises: A target edge server is selected from a plurality of edge servers in the target scheduling group in a random manner or a hash algorithm. 7. The method according to claim 1, wherein the scheduling the client to the target edge server comprises: constructing a uniform resource locator of the target edge server according to the IP address of the target edge server; A response message carrying the uniform resource locator of the target edge server is returned to the client, so that the client can access the target edge server based on the uniform resource locator of the target edge server. 8. A CDN scheduling device, comprising: an obtaining module, configured to obtain the target scheduling requirement information carried in the access request when receiving the access request from the client; wherein, the scheduling unit indicated by the target scheduling requirement information is smaller than the scheduling unit composed of the request domain name and the area ; a determining module, configured to determine a target edge server corresponding to the access request according to the target scheduling requirement information and a preset matching relationship between the edge server and the scheduling requirement information; A scheduling module, configured to schedule the client to the target edge server. 9. An edge scheduling server, comprising a memory and a processor, wherein a computer program that can be run on the processor is stored in the memory, and claim 1 is implemented when the processor executes the computer program The method of any one of -7. 10. A CDN scheduling system, comprising a central scheduling server and an edge scheduling server as claimed in claim 9, wherein the edge scheduling server is connected to the central scheduling server; The edge scheduling server is configured to acquire the matching relationship between the edge server and the scheduling requirement information from the central scheduling server. 11. A computer-readable storage medium on which a computer program is stored, wherein the computer program executes the method according to any one of claims 1-7 when the computer program is run by a processor .

Images