CN109660578B

CN109660578B - CDN back-to-source processing method, device and system

Info

Publication number: CN109660578B
Application number: CN201710942745.3A
Authority: CN
Inventors: 杨复勇; 姚伟斌; 韩瑞
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2017-10-11
Filing date: 2017-10-11
Publication date: 2022-01-21
Anticipated expiration: 2037-10-11
Also published as: CN109660578A

Abstract

A CDN back-to-source processing method, device and system includes: acquiring a request of a target resource and source returning path information, wherein the source returning path information at least comprises a virtual IP address on a source returning path of a target source station, and the virtual IP address is configured to execute source returning processing of a CDN node; and forwarding the request according to the source return path information so that the request is sent to the target source station. The method and the device can at least effectively improve the acceleration effect of the CDN on the website content.

Description

CDN back-to-source processing method, device and system

Technical Field

The present invention relates to the field of internet technologies, and in particular, to a method, an apparatus, and a system for processing a back source of a CDN.

Background

In the related art, a Content Delivery Network (CDN) system needs to specially designate a part of CDN nodes as transit nodes, and when returning to the source, the CDN nodes can only forward the Content through the transit nodes. The related art has at least the following defects: only part of nodes can be used as transit nodes, the number of usable nodes during forwarding is limited, all CDN node resources cannot be fully utilized to execute back-to-source processing, the acceleration effect of the CDN on website content is reduced, and resource waste can be caused.

Disclosure of Invention

In view of the above drawbacks in the related art, the present application provides a method, an apparatus, and a system for processing a back source of a CDN, which can at least effectively improve an acceleration effect of the CDN on website content.

The technical scheme is as follows:

a back source processing method of a CDN comprises the following steps:

acquiring a request of a target resource and source returning path information, wherein the source returning path information at least comprises a virtual IP address on a source returning path of a target source station, and the virtual IP address is configured to execute source returning processing of a CDN node;

and forwarding the request according to the source return path information so that the request is sent to the target source station.

The acquiring the request of the target resource and the information of the source return path includes: receiving the request from a terminal; and determining a back-source path of the target source station by using the virtual IP address of the CDN node according to the IP address of the terminal and the domain name information carried in the request so as to obtain the back-source path information.

The acquiring the request of the target resource and the information of the source return path includes: and receiving a data packet from the CDN node of the previous hop, and analyzing the data packet to obtain the back-to-source path information and the request.

Wherein, the forwarding the request according to the back source path information includes: and encapsulating the back-source path information and the request into a data packet, and sending the data packet to a CDN node of a next hop according to a virtual IP address of the next hop in the back-source path information.

Wherein the method further comprises: acquiring the target resource; and forwarding the target resource according to the source return path information so that the target resource is sent to the terminal sending the request.

Wherein the obtaining of the target resource includes one of:

receiving the target resource from the target source station;

and receiving a data packet from the CDN node of the next hop, and analyzing the data packet to obtain the target resource and the back source path information.

Wherein, the forwarding the target resource according to the back source path information includes: and encapsulating the back-source path information and the target resource into a data packet, and returning the data packet to the CDN node of the previous hop according to the virtual IP address of the previous hop in the back-source path information.

An back-source processing device of a CDN (content delivery network), comprising:

the system comprises an acquisition module, a source returning module and a source returning module, wherein the acquisition module is used for acquiring a request of a target resource and source returning path information, the source returning path information at least comprises a virtual IP address on a source returning path of a target source station, and the virtual IP address is configured to execute source returning processing of a CDN node;

and the forwarding module is used for forwarding the request according to the source return path information so that the request is sent to the target source station.

The acquisition module is further configured to acquire the target resource; and the forwarding module is further configured to forward the target resource according to the source return path information, so that the target resource is sent to the terminal that sent the request.

a memory storing a source return processing program;

a processor configured to read the back source handler to perform the following operations:

Wherein the processor is further configured to read the back source handler to perform the following operations: acquiring the target resource; and forwarding the target resource according to the source return path information so that the target resource is sent to the terminal sending the request.

A CDN system comprising a plurality of CDN nodes, the CDN nodes comprising:

a memory storing a source return processing program;

The application includes the following advantages:

on one hand, the virtual IP address configured on the CDN node for executing the back source processing is used for completing the back source processing, so that each CDN node in the CDN system can be used as a forwarding node in the back source processing, the CDN node resources can be fully utilized, the back source speed can be effectively improved, the acceleration effect of the CDN is further improved, and particularly, the CDN can obtain a better acceleration effect in the application of dynamic website content.

Of course, it is not necessary for any product to achieve all of the above-described advantages at the same time for the practice of the present application.

Drawings

FIG. 1 is a schematic diagram of an exemplary application scenario of the present application;

fig. 2 is a schematic flowchart illustrating a back-source processing method of a CDN according to an embodiment;

FIG. 3 is a schematic diagram of an exemplary logical processing of the CDN system after various VIPs of a CDN node have been bound to different services;

FIG. 4 is a flowchart illustrating an exemplary implementation of a method according to one embodiment;

fig. 5 is a schematic diagram of CDN system transit corresponding to the process shown in fig. 4;

fig. 6 is a schematic structural diagram of a back source processing device of the second CDN;

fig. 7 is a schematic structural diagram of an exemplary back-source processing device of the third CDN;

fig. 8 is an exemplary structural diagram of a four-CDN system according to the embodiment.

Detailed Description

The technical solutions of the present application will be described in more detail below with reference to the accompanying drawings and embodiments.

It should be noted that, if not conflicted, the embodiments and the features of the embodiments can be combined with each other and are within the scope of protection of the present application. Additionally, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.

In a typical configuration, a computing device of a client or server may include one or more processors (CPUs), input/output interfaces, network interfaces, and memory (memory).

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium. The memory may include module 1, module 2, … …, and module N (N is an integer greater than 2).

Computer readable media include both permanent and non-permanent, removable and non-removable storage media. A storage medium may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.

Fig. 1 is a schematic diagram of an exemplary application scenario of the technical solution of the present application. In the application scenario, the terminal can obtain resources from the source station through the CDN system, the CDN system is a distributed network formed by a group of proxy servers deployed in a plurality of data centers, and rapid and highly available access experience can be provided for terminal users.

Example one

A back source processing method of a CDN, as shown in fig. 2, may include:

step 201, obtaining a request of a target resource and source returning path information, where the source returning path information at least includes a virtual IP address on a source returning path of a target source station, and the virtual IP address is configured to execute source returning processing of a CDN node;

step 202, forwarding the request according to the source return path information, so that the request is sent to the target source station.

In this embodiment, the virtual IP address configured on the CDN node to execute the back source is used to complete forwarding when the back source is returned, so that each CDN node in the CDN system can serve as a forwarding node, which not only can make full use of node resources of the CDN, but also can effectively improve the back source speed, and further effectively improve the acceleration effect of the CDN.

In this embodiment, the back-to-source path refers to a path through which a request of a target resource is forwarded from a CDN access node to a source station, and the back-to-source path information includes VIPs of one or more CDN nodes that forward the request to the source station and an IP address of the source station. For example, after receiving the request, the CDN node 1 responsible for access forwards the request to the source station 4 through the VIP2 of the CDN node 2 and the VIP2 of the CDN node 3, assuming that the identity of the CDN node 2 is CDN _2, the identity of the CDN node 3 is CDN _3, and the identity of the source station 4 is Origin Server _4, then the back-to-source path may be represented as: VIP2_ CDN _2 → VIP2_ CDN _3 → Origin Server _4, and the corresponding back-to-source path information may include: VIP2 for CDN node 2, VIP2 for CDN node 3, and the IP address of source station 4.

In this embodiment, a part of Virtual IP addresses (VIPs) on the CDN nodes may be configured in advance to be dedicated to performing the back-to-source processing, and a back-to-source path may be formed directly by using the Virtual IP addresses of each CDN node when the back-to-source processing is performed, so that forwarding may be completed by using each CDN node in the CDN system when the back-to-source processing is performed.

In practice, a CDN node may have one or more VIPs. In this embodiment, the configuration of the VIP for performing the back-to-source processing on the CDN node may be implemented by binding the virtual IP address on the CDN node with the back-to-source service, so that the CDN node may be used as a forwarding node when returning to the source.

In one implementation, each VIP of a CDN node may be bound to a different service in a configured manner, so that one CDN node may support the different service through each VIP thereof, where the service includes the above-mentioned back-to-source service.

For example, the services may include: common business services (i.e., services that require static resources to be obtained from the CDN cache server), and back-to-source services (i.e., services that require static resources and/or dynamic resources to be obtained from the source station).

Assuming CDN node 1 has 5 VIPs, the configuration shown in table 1 below may be employed: the VIP1 is used for general business services (for example, obtaining static resources from a CDN cache server), the VIP2 is used for back-to-source processing, and the VIP3 is used for other services, … …, so that multiple VIPs of the same CDN node can be bound based on different services, and further, resources of the same CDN node are multiplexed to support multiple services.

TABLE 1

For another example, the back-to-source service can be further subdivided into: and source returning processing of dynamic resources and source returning processing of static resources. At this time, the service may include: the service system comprises common service (namely service for acquiring static resources from a CDN cache server), back-to-source service of static resources (namely service for acquiring static resources from a source station), and back-to-source service of dynamic resources (namely service for acquiring dynamic resources from a source station).

Assuming CDN node 1 has 5 VIPs, the configuration shown in table 2 below may be employed: CDN node 1 has 5 VIPs, and may set: VIP1 is used for general traffic services (i.e., services that obtain static resources from CDN cache servers), VIP2 is used for back-to-source processing of static resources, VIP3 is used for back-to-source processing of dynamic resources, VIP4 is used for other services, … …. Therefore, resources of the same CDN node can be reused to support multiple services, dynamic and static separation can be achieved, dynamic resources and static resources walk different links, two different back-source logics are clearly divided, the coupling of the whole process of the CDN is reduced, and rapid configuration issuing and accurate positioning of path problems are facilitated.

CDN node 1
	VIP 1: common service occupation;
VIP 2: back source processing occupation of static resources;
	VIP 3: back source processing occupation of dynamic resources;
VIP 4: other service occupancies;
	VIP5：……

TABLE 2

As another example, the back-source service may only include: and (5) returning the dynamic resources to the source. At this time, the service may include: the service system comprises common service (namely service for acquiring static resources from a CDN cache server or a source station) and back-to-source service of dynamic resources (namely service for acquiring dynamic resources from the source station). The corresponding configuration mode can refer to table 1, and is not described again.

For a CDN node, one group of VIPs may be configured to be dedicated to general traffic services, and another group of VIPs may be dedicated to back-to-source processing. Here, a group may contain at least two VIPs. Thus, by dedicating multiple VIPs to back-source processing, it is more helpful to increase the speed of back-source.

In addition, all VIPs on one CDN node may be designated for forwarding or general traffic services. In practical applications, the binding relationship between the VIP and the service may be set according to the needs of a specific application. In other embodiments, other configurations may also be used. Of course, the services may also include other types of services than the various types of services described above. This is not a limitation herein.

Through the above manner, any CDN node (including an edge node, a transit node, an outbound node, and the like) in the CDN system can be configured to multiplex resources of the CDN node to execute the back-source processing, so that the back-source speed is increased.

In an implementation manner, the request may carry domain name information of the target resource, and the method may further include: confirming whether the corresponding domain name supports dynamic acceleration service or not according to the domain name information carried in the request; and when confirming that the corresponding domain name supports the dynamic acceleration service, acquiring the information of the back source path.

In this embodiment, for a CDN node near a terminal, the request for obtaining a target resource and the information of a back-to-source path may include: receiving the request from a terminal; and determining a back-source path of the target source station by using the virtual IP address of the CDN node according to the IP address of the terminal and the domain name information carried in the request so as to obtain the back-source path information.

In an implementation manner, after receiving the request sent by the terminal, the CDN node of the near terminal may report the request or domain name information carried by the request to a master control node of the CDN system, where the master control node of the CDN system determines the back-to-source path and provides the obtained back-to-source path information to the CDN node of the near terminal. Here, the main control node stores VIP configurations of each CDN node in the CDN system (that is, binding relationships between VIPs of each CDN node and different services), and determines the back-to-source path by querying the VIP configurations and performing path computation.

In another implementation manner, the CDN node near the terminal may determine the back-to-source path and obtain the back-to-source path information. Here, the determining of the back-source path may include: and inquiring the VIPs configured to execute the back-to-source processing on all CDN nodes in the CDN system, and performing path calculation by using the VIPs and the IP addresses of the source stations to obtain an optimal path for forwarding the request to a target source station, wherein the optimal path is the back-to-source path.

In this embodiment, for a CDN node of an intermediate hop on a back-to-source path, the request for obtaining a target resource and back-to-source path information may include: and receiving a data packet from the CDN node of the previous hop, and analyzing the data packet to obtain the back-to-source path information and the request.

In this embodiment, for any CDN node, the forwarding the request according to the back-to-source path information may include: and encapsulating the back-source path information and the request into a data packet, and sending the data packet to a CDN node of a next hop according to a virtual IP address of the next hop in the back-source path information. In practical application, all CDN nodes on the back-to-source path execute this procedure according to the back-to-source path information, and the request may be sent to the target source station.

In this embodiment, the method may further include: acquiring the target resource; and forwarding the target resource according to the source return path information so that the target resource is sent to the terminal sending the request. In this way, the target resources (static or dynamic) required by the user can be forwarded from the source station all the way to the terminal.

In this embodiment, the obtaining of the target resource may include one of: 1) receiving the target resource from the target source station; 2) and receiving a data packet from the CDN node of the next hop, and analyzing the data packet to obtain the target resource and the back source path information. For a CDN node close to a target source station, the target resource may be obtained in the manner of 1) and, for a CDN node in a middle hop of a back-to-source path, the target resource may be obtained in the manner of 2).

In this embodiment, the forwarding the target resource according to the back-source path information may include: and encapsulating the back-source path information and the target resource into a data packet, and returning the data packet to the CDN node of the previous hop according to the virtual IP address of the previous hop in the back-source path information. In practical application, all CDN nodes on the back-to-source path are executed according to the back-to-source path information in this way, and the target resource can be sent to the terminal.

It should be noted that the target resource in this embodiment refers to a resource indicated in the request, and the resource may be a dynamic resource or a static resource. Here, the dynamic resource refers to content related to a dynamic page on a website. In one implementation, the dynamic resource may be content associated with a presentation layer, a data access layer, and a business logic layer of the dynamic page.

In particular, the method of the embodiment is particularly suitable for scenes with large dynamic resource traffic. For example, when the user accesses a website with many dynamic pages, the method of the embodiment can achieve a better acceleration effect of the user accessing the website.

One implementation of the present embodiment is described in detail below with a specific example. It should be noted that the method described in this embodiment may also be implemented in other ways. In addition, the execution sequence and the execution steps in the flow of the following example can be adjusted according to actual needs, and are not limited to the following implementation forms.

Example 1

As shown in fig. 3, an exemplary logical processing diagram of a CDN system after binding VIPs of CDN nodes with different services. As shown in fig. 3, in each CDN node (CDN node A, CDN node B, CDN node C, CDN node D) configured in the CDN system, VIP2 is bound to a back-to-source service, and VIP1 is bound to a normal traffic service, that is, VIP2 is set to be dedicated to performing back-to-source processing and VIP1 is set to perform normal traffic processing. Therefore, the same CDN node can support the service logic processing of common service and the forwarding logic processing of the back-to-source service, the common service logic processing and the forwarding logic processing of the back-to-source service can be separated, different links are arranged between the service logic processing of the common service and the forwarding logic processing of the back-to-source service, the back-to-source speed can be increased while CDN node resources are fully utilized, and a better acceleration effect is achieved.

As shown in fig. 3, terminal a may access the CDN system through VIP1 of CDN node a nearby, and use VIP2 transit of CDN node C, CDN node B to achieve its back-sourcing. The terminal B can access the CDN system through the VIP1 of the nearby CDN node C, and use the VIP2 transit of the CDN node D, CDN and the node B to realize its back-sourcing.

Example 2

Fig. 4 is a flowchart illustrating an exemplary execution flow of the source return processing method according to this embodiment. As shown in fig. 4, an exemplary execution flow of the source return processing method of the present embodiment may include:

step 401, a CDN node receives a request from a terminal, where the request carries domain name information of dynamic data to be acquired, where the dynamic data is a target resource of the present example;

step 402, judging whether the domain name is a dynamic acceleration domain name or not according to the domain name information carried in the request; if the domain name is dynamically accelerated, continue to step 404; otherwise, continuing to step 403;

here, it may be determined whether the domain name corresponding to the requested domain name information starts dynamic acceleration service by querying domain name configuration information issued by a master control node in the CDN system, and if the dynamic acceleration service is started, the domain name is regarded as a dynamic acceleration domain name, and according to the fact that if the dynamic acceleration service is not started, the domain name is regarded as a normal domain name, and a non-dynamic acceleration domain name is logically processed according to a normal service.

In one implementation, each CDN service domain name in the domain name configuration information is provided with a plurality of associated configuration items, for example, a dynamic acceleration service item. Assuming that the name of the dynamic acceleration service item is dsa, after the domain name starts the service item, the CDN master node issues corresponding domain name configuration information to each CDN node that provides service to the outside. When the request related to the domain name reaches the CDN node, the CDN node parses and identifies the domain name, matches the related configuration item, and if the domain name is found to be dsa-that is, the dynamic acceleration domain name configuration item, the domain name is regarded as a dynamic acceleration domain name. If the domain name is found not to be opened by the dsa, namely the dynamic acceleration domain name configuration item, the domain name is regarded as a common domain name, and the domain name is not dynamically accelerated.

Step 403, processing according to the common service logic, and jumping to step 407 after the common service logic processing is executed;

step 404, obtaining source returning path information from the current CDN node to the source station under the corresponding domain name, where the source returning path information includes a VIP forwarding the request to each hop in a source returning path of the source station;

it should be noted that each VIP in the back-source path information is set as a VIP for performing back-source processing. That is, the information of the selected intermediate hop on the back-to-source path corresponds to the VIP dedicated to performing the back-to-source processing.

Step 405, forwarding the request to a corresponding source station according to the source return path information;

specifically, the current CDN node encapsulates the back-source path information and the request into a data packet and forwards the data packet to a next-hop CDN node according to the back-source path information, and the next-hop CDN node continues to forward the request according to the back-source path information until the request is sent to a corresponding source station according to a back-source path indicated by the back-source path information;

step 406, after receiving the request, the source station returns dynamic data corresponding to the request to the terminal through a corresponding CDN node according to the back-to-source path information;

specifically, after receiving the request, the source station encapsulates the back-source path information and corresponding dynamic data into a data packet, and forwards the data packet to a CDN node of a previous hop according to the back-source path information; and the CDN node of the previous hop continuously forwards the dynamic data according to the back-to-source path information until the dynamic data is sent to a corresponding terminal according to the back-to-source path indicated by the back-to-source path information.

In step 407, the current process ends.

Fig. 5 is a diagram illustrating a transfer process in the exemplary flow shown in fig. 4. In the process shown in fig. 4, a CDN node 0 near the terminal in the CDN system receives the request, and obtains corresponding source return path information when it is determined that the domain name corresponding to the request is the dynamic acceleration domain name, where the source return path information includes the following: vip _ fwd1 → vip _ fwd2, the corresponding back-to-source path is: CDN node 1 with address vip _ fwd1 → CDN node 2 with address vip _ fwd2 → the source station. And sending the request to the source station through the source returning path, and returning the dynamic data of the source station to the terminal through the source returning path. The VIP resources of CDN node 1 include: VIP0, VIP1, VIP2, … …, wherein VIP1 is set to be dedicated to back-to-source processing. If the domain name is a normal domain name, that is, the domain name without the dynamic acceleration service being started, according to normal service processing, the normal service processing may include: first, an attempt is made to obtain cache resources to the L2 node of the CDN, and if not, the acquisition of resources to the source station is continued.

It should be noted that fig. 4 and fig. 5 are exemplary implementations, and are not used to limit the present embodiment. In other application scenarios, the method of the embodiment may also be implemented in other manners.

Example two

A back source processing apparatus of CDN, as shown in fig. 6, may include:

an obtaining module 61, configured to obtain a request of a target resource and source return path information, where the source return path information at least includes a virtual IP address on a source return path of a target source station, and the virtual IP address is configured to perform source return processing of a CDN node;

a forwarding module 62, configured to forward the request according to the source return path information, so that the request is sent to the target source station.

In one implementation, the obtaining module 61 is specifically configured to determine whether the corresponding domain name supports the dynamic acceleration service according to the domain name information carried in the request; and acquiring the back source path information when confirming that the corresponding domain name supports the dynamic acceleration service.

In one implementation, the obtaining module 61 is configured to obtain the request of the target resource and the source return path information, and may include: receiving the request from a terminal; and determining a back-source path of the target source station by using the virtual IP address of the CDN node according to the IP address of the terminal and the domain name information carried in the request so as to obtain the back-source path information.

In another implementation manner, the obtaining module 61 is configured to obtain the request of the target resource and the source return path information, and may include: and receiving a data packet from the CDN node of the previous hop, and analyzing the data packet to obtain the back-to-source path information and the request.

In this embodiment, the forwarding module 62 is configured to forward the request according to the back-source path information, and may include: and encapsulating the back-source path information and the request into a data packet, and sending the data packet to a CDN node of a next hop according to a virtual IP address of the next hop in the back-source path information.

In this embodiment, the obtaining module 61 may be further configured to obtain the target resource; the forwarding module 62 may be further configured to forward the target resource according to the source return path information, so that the target resource is sent to the terminal that sent the request.

In this embodiment, the obtaining module 61 may be configured to obtain the target resource, where the obtaining module includes one of the following: receiving the target resource from the target source station; and receiving a data packet from the CDN node of the next hop, and analyzing the data packet to obtain the target resource and the back source path information.

In this embodiment, the forwarding module 62 may be configured to forward the target resource according to the back-source path information, and includes: and encapsulating the back-source path information and the target resource into a data packet, and returning the data packet to the CDN node of the previous hop according to the virtual IP address of the previous hop in the back-source path information.

In practical application, the obtaining module 61 in the back-to-source processing device of the CDN is responsible for obtaining back-to-source paths and back-to-source path information on CDN nodes, and may be software, hardware, or a combination of the software and the hardware;

in practical applications, the forwarding module 62 in the back-source processing device of the CDN is responsible for completing forwarding processing between the CDN node and other CDN nodes, and may be software, hardware, or a combination of the software and the hardware;

in this embodiment, the back-to-source processing device of the CDN may be disposed at any CDN node or implemented by any CDN node.

Other technical details of the present embodiment may refer to the first embodiment.

EXAMPLE III

A back source processing apparatus of CDN, as shown in fig. 7, may include:

a memory 71 storing a return source processing program;

a processor 72 configured to read the back source handler to perform the following operations:

In this embodiment, the processor 72 may be further configured to read the source return handler to perform the following operations: acquiring the target resource; and forwarding the target resource according to the source return path information so that the target resource is sent to the terminal sending the request.

In one implementation, the processor 73 may be further configured to read the dynamic resource acquisition program to perform the following operations: receiving a data packet returned by the CDN node of the next hop, wherein the data packet is filled with dynamic resources from a source station and the information of the source returning path; and returning the dynamic resources to the terminal according to the source return path information.

In practical applications, the back-source processing apparatus of the CDN may be embodied as any computing device capable of implementing the above functions. The computing device may be any CDN node in a CDN system, or may be part of any such CDN node.

It should be noted that fig. 7 is only an exemplary structure of the back source processing device of the CDN. In practical applications, the back-source processing device of the CDN may further include a communication circuit, a bus, and the like, where the bus is used to connect various components such as a processor, a memory, and a communication circuit in the back-source processing device of the CDN, and the communication circuit is used to implement a communication function of the back-source processing device of the CDN. For example, the processor 72 may obtain the request and the source return path information via the communication circuit. Of course, the back source processing device of the CDN may also include other components or adopt other forms of architectures, which are not limited herein.

Other technical details of the present embodiment refer to the first embodiment.

Example four

A CDN system, as shown in fig. 8, includes a plurality of CDN nodes (CDN node 1, … …, CDN node n, n is an integer no less than 2).

Wherein, the CDN node includes: a memory storing a source return processing program; a processor configured to read the back source handler to perform the following operations: acquiring a request of a target resource and source returning path information, wherein the source returning path information at least comprises a virtual IP address on a source returning path of a target source station, and the virtual IP address is configured to execute source returning processing of a CDN node; and forwarding the request according to the source return path information so that the request is sent to the target source station.

In this embodiment, the processor may be further configured to read the source return handler to perform the following operations: acquiring the target resource; and forwarding the target resource according to the source return path information so that the target resource is sent to the terminal sending the request.

As shown in fig. 8, the CDN system in this embodiment may further include a master node, where the master node stores VIP configurations of each CDN node in the CDN system (that is, binding relationships between VIPs of each CDN node and different services), and is responsible for determining the back-to-source path by querying the VIP configuration and performing path calculation, and providing corresponding back-to-source path information to each CDN node.

EXAMPLE five

A computer-readable storage medium, wherein a back-source processing program is stored on the computer-readable storage medium, and when executed by a processor, the back-source processing program implements the steps of the back-source processing method of the CDN of embodiment one.

It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing the relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module/unit in the above embodiments may be implemented in the form of hardware, and may also be implemented in the form of a software functional module. The present application is not limited to any specific form of hardware or software combination.

There are, of course, many other embodiments of the invention that can be devised without departing from the spirit and scope thereof, and it will be apparent to those skilled in the art that various changes and modifications can be made herein without departing from the spirit and scope of the invention.

Claims

1. A back-to-source processing method for a Content Delivery Network (CDN) comprises the following steps:

2. The method of claim 1, wherein the acquiring the request for the target resource and the source return path information comprises:

receiving the request from a terminal;

and determining a back-source path of the target source station by using the virtual IP address of the CDN node according to the IP address of the terminal and the domain name information carried in the request so as to obtain the back-source path information.

3. The method of claim 1, wherein the acquiring the request for the target resource and the source return path information comprises:

and receiving a data packet from the CDN node of the previous hop, and analyzing the data packet to obtain the back-to-source path information and the request.

4. The back-source processing method according to claim 1, 2 or 3, wherein the forwarding the request according to the back-source path information includes:

and encapsulating the back-source path information and the request into a data packet, and sending the data packet to a CDN node of a next hop according to a virtual IP address of the next hop in the back-source path information.

5. The back-source processing method of claim 1, wherein the method further comprises:

acquiring the target resource;

and forwarding the target resource according to the source return path information so that the target resource is sent to the terminal sending the request.

6. The back source processing method according to claim 5,

the acquiring the target resource includes one of:

receiving the target resource from the target source station;

7. The back-source processing method according to claim 5 or 6, wherein the forwarding the target resource according to the back-source path information includes:

and encapsulating the back-source path information and the target resource into a data packet, and returning the data packet to the CDN node of the previous hop according to the virtual IP address of the previous hop in the back-source path information.

8. A back-source processing device of a Content Delivery Network (CDN), comprising:

9. The back source processing apparatus according to claim 8,

the acquisition module is further used for acquiring the target resource;

and the forwarding module is further configured to forward the target resource according to the source return path information, so that the target resource is sent to the terminal that sent the request.

10. A back-source processing device of a Content Delivery Network (CDN), comprising:

a memory storing a source return processing program;

11. The source-return processing apparatus of claim 10, wherein the processor is further configured to read the source-return handler to perform the following operations:

acquiring the target resource;

12. A CDN system for a content delivery network, comprising a plurality of CDN nodes, the CDN nodes comprising:

a memory storing a source return processing program;

13. The CDN system of claim 12 wherein the processor is further configured to read the back-source handler to:

acquiring the target resource;