CDN back-to-source method and device, electronic equipment and storage medium

Abstract

One or more embodiments of the invention disclose a CDN (Content Delivery Network) back-to-source method and device, electronic equipment and a storage medium. The method comprises the steps that a CDN aggregation node receives an access request forwarded by an aggregated CDN edge node, a target cluster corresponding to an IP address of the CDN aggregation node is determined based on a pre-configured cluster cache, the cluster cache is a configuration file representing the corresponding relation between the IP address and the cluster, and the cluster cache is a configuration file representing the corresponding relation between the IP address and the cluster; the cluster is used for representing an operator and / or an area to which the CDN sink node belongs; according to the target cluster and an access domain name contained in the access request, determining a target source station address which is the same as an operator to which the CDN aggregation node belongs from a scheduling cache containing a plurality of operators; and initiating a source returning request for a target resource of the target source station address to a source station, caching the target resource sent by the source station according to the source returning request, and returning the cached target resource to the user side initiating the access request.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a CDN back-to-source method and device, an electronic device, and a storage medium. Background Art

[0002] Content Delivery Network (CDN) is a distributed network built on and covered by the bearer network, consisting of edge node server clusters distributed in different regions. CDN can share the pressure of the source station, avoid network congestion, ensure the acceleration of website content distribution in different regions and scenarios, and improve the speed of resource access.

[0003] CDN back-to-source means that when the resource that the user wants to request is not hit (Miss) at the CDN edge node, the user needs to go to the upper server or the source server to download the resource. Cross-operator back-to-source is a link of CDN back-to-source. In this cross-operator back-to-source link, the node that initiates the back-to-source request and the source server node connected to are not from the same operator.

[0004] A multi-line data center refers to a data center that is connected to multiple operators as export lines at the same time. In this way, the data center will have many groups of IPs, and each group of IPs belongs to the same operator. The existence of a multi-line data center may cause cross-operator back-to-source problems, and cross-operator back-to-source will cause the CDN back-to-source link to be reset, which will affect the services provided by the CDN when the end user requests to access and obtain the source station resources, and thus affect the end user experience. Summary of the invention

[0005] The embodiments of this specification provide a CDN back-to-source method and device, an electronic device, and a storage medium to provide a better CDN back-to-source solution.

[0006] In a first aspect, an embodiment of this specification provides a CDN back-to-source method, including: The CDN aggregation node receives the access request forwarded by the aggregated CDN edge node, and determines the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, wherein the cluster cache is a configuration file indicating the correspondence between the IP address and the cluster, and the cluster corresponds to the operator and / or region to which the CDN aggregation node belongs; According to the target cluster and the target access domain name included in the access request, determine, from a scheduling cache including multiple operators and / or regions, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs; A back-to-source request for the target resource at the target source station address is initiated to the source station, and after caching the target resource sent by the source station according to the back-to-source request, it is returned to the user end that initiated the access request.

[0007] Optionally, determining, according to the target cluster and the target access domain name included in the access request, from a scheduling cache including multiple operators and / or regions, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs, includes: According to the target cluster and the target access domain name included in the access request, construct a target key for querying multiple key-value pairs in the scheduling cache, wherein the key in the key-value pair at least includes the cluster and the access domain name in the historical back-to-source information, and the value in the key-value pair at least includes the back-to-source address in the historical back-to-source information; From the multiple key-value pairs, query the target key-value pair corresponding to the target key, and use the address corresponding to the target value in the target key-value pair as the target source station address.

[0008] Optionally, when there is no key-value pair corresponding to the target key in the scheduling cache, the method further includes: Initiate a scheduling request including the target cluster and the target access domain name to the scheduling interface; The target source station address is obtained from the scheduling information generated based on the scheduling request and returned by the scheduling interface.

[0009] Optionally, acquiring the target source station address from the scheduling information generated based on the scheduling request and returned from the scheduling interface includes: In the case where the scheduling information includes a back-to-source domain name, a domain name resolution is performed on the back-to-source domain name to obtain a target source station address corresponding to the back-to-source domain name.

[0010] Optionally, the method further includes: Construct the target value based on the target source station address obtained by parsing; A target key-value pair is constructed according to the constructed target key and target value, and the scheduling cache is updated using the newly constructed target key-value pair.

[0011] Optionally, before determining the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, the method further includes: When the CDN aggregation node receives the access request, the CDN aggregation node searches for a target resource corresponding to the target access domain name included in the access request in a resource cache corresponding to the CDN aggregation node; And confirm that the target resource is not found.

[0012] Optionally, before determining the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, the method further includes: If the target resource is not found, further searching whether the CDN aggregation node has a CDN aggregation node at an upper level; And confirm that the CDN aggregation node does not have a CDN aggregation node at the previous level; The method further comprises: When the target resource is not found and the CDN aggregation node has an upper-level CDN aggregation node, the access request is forwarded to the upper-level CDN aggregation node, so that the upper-level CDN aggregation node executes the CDN tracing method.

[0013] In a second aspect, one or more embodiments of this specification provide a CDN aggregation node device, including: A cluster determination module, configured for a CDN aggregation node to receive an access request forwarded by an aggregated CDN edge node, and to determine a target cluster corresponding to the IP address of the CDN aggregation node based on a pre-configured cluster cache, wherein the cluster cache is a configuration file indicating a correspondence between an IP address and a cluster, and the cluster corresponds to an operator and / or region to which the CDN aggregation node belongs; An address determination module, configured to determine, according to the target cluster and the target access domain name included in the access request, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs from a scheduling cache including multiple operators and / or regions; The source station back-to-source module is used to initiate a back-to-source request for the target resource of the target source station address to the source station, cache the target resource sent by the source station according to the back-to-source request, and return it to the user end that initiated the access request.

[0014] Optionally, an address determination module includes: A key unit, configured to construct a target key for querying a plurality of key-value pairs in the scheduling cache according to the target cluster and the target access domain name included in the access request, wherein the key in the key-value pair at least includes the cluster and the access domain name in the historical back-to-source information, and the value in the key-value pair at least includes the back-to-source address in the historical back-to-source information; The address unit is used to query the target key-value pair corresponding to the target key from the multiple key-value pairs, and use the address corresponding to the target value in the target key-value pair as the target source station address.

[0015] Optionally, the CDN back-to-source device includes: A scheduling request module, configured to initiate a scheduling request including the target cluster and the target access domain name to the scheduling interface when there is no target key-value pair corresponding to the target key in the scheduling cache; The scheduling information module is used to obtain the target source station address from the scheduling information generated based on the scheduling request and returned by the scheduling interface.

[0016] Optional, scheduling information module, including: The domain name resolution unit is used to perform domain name resolution on the back-to-source domain name when the scheduling information includes the back-to-source domain name, and obtain the target source station address corresponding to the back-to-source domain name.

[0017] Optionally, the CDN back-to-source device further includes: The value module is used to construct the target value according to the parsed target source station address; The update module is used to construct a target key-value pair according to the constructed target key and target value, and use the newly constructed target key-value pair to update the scheduling cache.

[0018] Optionally, a cluster determination module includes: a cache search unit, configured to, before determining the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, search, when the CDN aggregation node receives the access request, for a target resource corresponding to the target access domain name included in the access request in the resource cache corresponding to the CDN aggregation node; The cluster determination unit is used to confirm that the target resource is not found.

[0019] Optionally, the CDN back-to-source device further includes: The upper node module is used for, before determining the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, if the target resource is not found, further finding out whether the CDN aggregation node has an upper-level CDN aggregation node; An upper-level node determination module is used to confirm that the CDN aggregation node does not have an upper-level CDN aggregation node; The upper-level node execution module is used to forward the access request to the upper-level CDN aggregation node when the target resource is not found and the CDN aggregation node has an upper-level CDN aggregation node, so that the upper-level CDN aggregation node executes the CDN back-to-source method.

[0020] In a fourth aspect, an embodiment of the present specification provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0021] In a fifth aspect, an embodiment of this specification provides a chip, the chip comprising a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.

[0022] In a sixth aspect, an embodiment of this specification provides a computer program product, which, when executed by a processor, implements the method described in the first aspect.

[0023] In the embodiment of this specification, after receiving the access request, the target cluster to which the CDN edge node belongs is first determined based on the cluster cache and the IP address of the CDN aggregation node, and then the target source station address that is the same as the operator and / or region of the CDN aggregation node is determined based on the target cluster and the target access domain name, and then the target resource corresponding to the target source station address is cached from the source station and returned to the user end. This process uses the IP address of the CDN aggregation node, the cluster cache and the scheduling cache in sequence, to determine the target source station address that is the same as the operator and / or region of the CDN aggregation node, solves the cross-operator problem that may occur in the return to source process, avoids the reset of the return to source link caused by cross-operators in multi-line computer rooms, improves the availability and assurance of CDN services, and thus improves the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in one or more embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0025] Figure 1 This is a flowchart of a CDN back-to-source method provided in an embodiment of this specification; Figure 2 This is a system architecture diagram of a CDN network provided in an embodiment of this specification; Figure 3 is a schematic diagram of an application example provided in the embodiments of this specification; Figure 4 This is a schematic diagram of the structure of a CDN back-to-source device provided in an embodiment of this specification; Figure 5It is a structural diagram of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0027] The terms "first", "second", etc. in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of this specification can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0028] The CDN back-to-source method and device, electronic device, and storage medium provided in the embodiments of this specification are described in detail below with reference to the accompanying drawings through specific embodiments and their application scenarios.

[0029] Figure 1 A CDN back-to-source method provided by an embodiment of the present invention is shown, and the method can be applied to a CDN aggregation node. Figure 1 As shown, the CDN back-to-source method includes the following steps: Step S102: The CDN aggregation node receives the access request forwarded by the aggregated CDN edge node, and determines the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache.

[0030] Among them, CDN includes multiple important parts such as the source station, cache server, Domain Name System (DNS), and user end. Specifically, the source station refers to the original site that publishes the content, and the objects captured by the cache server are all from the source station; the cache server is used to cache data and provide the cached data directly to the user. The cache server is composed of multiple servers. When the user initiates access to resources such as pictures, the access request is located by DNS to the cache server closer to the user; DNS is used to point the access request to the cache server closer to the user based on the user's source; the user end is used for the terminal user to initiate the access request, and the user's access method at the user end is generally through a browser, etc.

[0031] CDN is a distributed network architecture, in which the cache servers can be divided into CDN edge nodes and CDN aggregation nodes. Specifically, CDN edge nodes are cache servers that are directly facing users and responsible for providing content services to users. They are deployed at the edge of the CDN network; CDN aggregation nodes are used to manage CDN edge nodes in the managed area and are responsible for content distribution and load balancing in the area. In Internet applications, CDN caches the static and dynamic content of the website to the CDN edge node closest to the user through distributed deployment of servers, which can achieve faster content access speed, better user experience and lower network latency. CDN aggregation nodes can be divided into multiple levels according to actual needs. In this way, CDN aggregation nodes can include CDN secondary nodes, CDN tertiary nodes, etc., among which CDN secondary nodes can be subordinate to at least one CDN edge node.

[0032] Figure 2 A system architecture diagram of a CDN network is shown. Figure 2 As shown in the figure, the CDN aggregation nodes in the CDN network are all CDN secondary nodes. Figure 2 In the case of a nationwide CDN network, CDN edge nodes can be distributed in provinces and cities across the country, dividing the country into several regions, and CDN aggregation nodes can be distributed in several of these regions. Each CDN aggregation node can aggregate CDN edge nodes in several regions. Figure 2 As shown, the CDN back-to-source method can be integrated into the back-to-source scheduling module of each CDN aggregation node as a user-readable configuration file. This method is a functional expansion of the CDN aggregation node, which is easy to expand and maintain and has a small amount of code.

[0033] The terminal is used to determine the CDN edge node corresponding to the access request through DNS when the user initiates an access request through the user end using the access domain name. Usually, the user end and the determined CDN edge node have the same operator (China Telecom, China Mobile, China Unicom, etc.) and / or region. When the CDN edge node has the cached resources required for the access request, it will hit the resource. At this time, the resource data can be directly returned to the user end. When the CDN edge node does not have the cached resources required for the access request (the cached resources are expired or not stored), it will forward the access request to the CDN aggregation node to which the CDN edge node belongs, so that the CDN aggregation node can process the access request.

[0034] When the CDN aggregation node receives the access request, it can first search for the target resource corresponding to the access domain name included in the access request in the resource cache corresponding to the CDN aggregation node (indicating the data cached by the cache server) to improve the efficiency of CDN back-to-source. In one implementation, before determining the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, the method also includes: When the CDN aggregation node receives the access request, the CDN aggregation node searches for a target resource corresponding to the target access domain name included in the access request in a resource cache corresponding to the CDN aggregation node; And confirm that the target resource is not found.

[0035] After receiving the aforementioned access request, the CDN aggregation node will determine the cluster (i.e., the target cluster) corresponding to the IP address of the CDN aggregation node through the pre-configured cluster cache, so as to obtain the target resource from the source station according to the target cluster. The resource cache corresponding to the CDN aggregation node has the cached resource (i.e., the target resource) required for the access request. Before executing the aforementioned steps, it is necessary to first determine that the CDN aggregation node does not have the target resource (the cached resource is expired or not stored). If the CDN aggregation node has the target resource, it will synchronize the target resource to the CDN edge node that forwards the access request, and return the target resource to the user end through the CDN edge node without executing the aforementioned steps.

[0036] The cluster cache is a pre-configured configuration file that indicates the correspondence between IP addresses and clusters. The cluster is used to indicate the operator and / or region to which the CDN aggregation node belongs (generally, the region is divided by province). The CDN aggregation nodes in the same cluster have the same operator and / or region. For example, when the IP address is A, the cluster corresponding to the IP address is cmcc.hebei (Hebei Mobile); when the IP address is B, the cluster corresponding to the IP address is ctc.hebei (Hebei Telecom); when the IP address is C, the cluster corresponding to the IP address is cnc.hebei (Hebei Unicom).

[0037] In the case where the CDN aggregation node can be divided into multiple levels according to actual needs, in one implementation, before determining the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, the method further includes: If the target resource is not found, further searching whether the CDN aggregation node has a CDN aggregation node at an upper level; And confirm that the CDN aggregation node does not have a CDN aggregation node at the previous level; The method further comprises: When the target resource is not found and the CDN aggregation node has an upper-level CDN aggregation node, the access request is forwarded to the upper-level CDN aggregation node, so that the upper-level CDN aggregation node executes the CDN tracing method.

[0038] When there are multiple levels of CDN aggregation nodes, the resource cache of the CDN aggregation nodes can be retrieved level by level, and when the target resource does not exist in the CDN aggregation nodes of each level, CDN back-to-source is performed in the aggregation node of the last level through steps S104-S106.

[0039] Specifically, when receiving an access request, the CDN aggregation node at each level can search for the target resource in the resource cache corresponding to the CDN aggregation node, and if the target resource is not found in the resource cache corresponding to the CDN aggregation node, the access request can be forwarded to the CDN aggregation node at the previous level of the CDN aggregation node, so that the CDN aggregation node at the previous level executes the CDN back-to-source method in this specification.

[0040] Step S104: According to the target cluster and the target access domain name included in the access request, determine the target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs from a scheduling cache including multiple operators and / or regions.

[0041] Among them, the scheduling cache is a configuration file that represents the correspondence between the source station address and the cluster under a specific cluster. In order to ensure the access speed of terminal users, in the scheduling cache corresponding to the source station, for each IP address, multiple source station addresses corresponding to the IP address can be set, and each source station address corresponds to a cluster, that is, the multiple source station addresses corresponding to each IP address have different operators and / or regions. Therefore, the target source station address corresponding to the CDN aggregation node can be determined from the scheduling cache based on the target cluster and the target access domain name, and the target source station address is the same as the operator and / or region corresponding to the CDN aggregation node. For example, the IP of the CDN aggregation node is A, and the target access domain name is aa.com. The target source station address can be searched in the scheduling cache based on the target cluster and the target access domain name.

[0042] Step S106: Initiate a back-to-source request for the target resource at the target source station address to the source station, cache the target resource sent by the source station according to the back-to-source request, and return it to the user terminal that initiated the access request.

[0043] After obtaining the target source station address, the target resource can be directly obtained by returning to the source station node according to the target source station address. Specifically, a return request containing the target source station address can be sent to the source station node. After receiving the return request, the source station node finds the target resource from the stored data according to the target source station address, and sends the target resource to the CDN cache node. Then, the CDN aggregation node can cache the target resource based on the preset cache strategy and send it to the user end. In addition, the cache strategy of the CDN aggregation node can also be to cache the target resource first and then send it to the CDN edge node. After the CDN edge node caches the target resource, it sends the target resource to the user end for the user to use.

[0044] In the embodiment of this specification, after receiving the access request, the target cluster to which the CDN edge node belongs is first determined based on the cluster cache and the IP address of the CDN aggregation node, and then the target source station address that is the same as the operator and / or region of the CDN aggregation node is determined based on the target cluster and the target access domain name, and then the target resource corresponding to the target source station address is cached from the source station and returned to the user end. This process uses the IP address of the CDN aggregation node, the cluster cache and the scheduling cache in sequence, to determine the target source station address that is the same as the operator and / or region of the CDN aggregation node, solves the cross-operator problem that may occur in the return to source process, avoids the reset of the return to source link caused by cross-operators in multi-line computer rooms, improves the availability and assurance of CDN services, and thus improves the user experience.

[0045] In one implementation, determining, according to the target cluster and the target access domain name included in the access request, from a scheduling cache including multiple operators and / or regions, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs, includes: According to the target cluster and the target access domain name included in the access request, construct a target key for querying multiple key-value pairs in the scheduling cache, wherein the key in the key-value pair at least includes the cluster and the access domain name in the historical back-to-source information, and the value in the key-value pair at least includes the back-to-source address in the historical back-to-source information; From the multiple key-value pairs, query the target key-value pair corresponding to the target key, and use the address corresponding to the target value in the target key-value pair as the target source station address.

[0046] The storage method of the clusters, access domain names, and source station addresses of various operators and / or regions in the scheduling cache can be stored in various forms such as tables, key-value pairs, documents, and graphs. Since distributed storage in the form of key-value pairs has the characteristics of fast query speed, large data storage volume, and support for high concurrency, it is easy to implement high-speed query. Therefore, the relationship between the clusters, access domain names, and source station addresses of various operators and / or regions can be stored in the form of key-value pairs. In one example, a key-value pair can be constructed based on the saved historical back-to-source information. Specifically, the key in the key-value pair can be constructed based on the cluster and access domain name in the historical back-to-source information, and the value in the key-value pair can be constructed based on the source station address in the historical back-to-source information.

[0047] Furthermore, when the target access domain name of the access request and the target cluster corresponding to the CDN aggregation node are determined, a target key for query can be constructed for the target access domain name and the target cluster, and the target key can be used to query multiple key-value pairs in the scheduling cache to determine the target key-value pair corresponding to the target key, and then the address corresponding to the value in the target key-value pair can be used as the target source station address.

[0048] The cluster cache is generated based on the source station address, cluster and access domain name related to the historical back-to-source request in the back-to-source data. If the back-to-source corresponding to the target cluster and the target access domain name has not been performed in the CDN aggregation node, the target source station address needs to be determined separately. In one implementation, if there is no key-value pair corresponding to the target key in the scheduling cache, the method further includes: Initiate a scheduling request including the target cluster and the target access domain name to the scheduling interface; The target source station address is obtained from the scheduling information generated based on the scheduling request and returned by the scheduling interface.

[0049] Among them, the scheduling interface is an interface for determining the source station address from a preset database according to a scheduling request. The preset database can be a database containing address information of multiple operators and / or regions. Specifically, the CDN aggregation node can first generate a scheduling request based on the target cluster and the target access domain name, and send the scheduling request to the scheduling interface. The scheduling interface uses the preset database to generate scheduling information containing address-related content according to the scheduling request. The scheduling information usually contains thousands of addresses corresponding to the scheduling request, and relevant tools can be used to filter out the target source station address corresponding to the access request from these addresses.

[0050] Since the scheduling information returned by the scheduling interface does not always directly include the address information, in one implementation, obtaining the target source station address from the scheduling information generated based on the scheduling request and received from the scheduling interface includes: In the case where the scheduling information includes a back-to-source domain name, a domain name resolution is performed on the back-to-source domain name to obtain a target source station address corresponding to the back-to-source domain name.

[0051] The back-to-source domain name is the domain name corresponding to the target source station address. Specifically, if the scheduling information returned by the scheduling interface contains the back-to-source domain name corresponding to the target source station address, the target source station address can be determined based on the back-to-source domain name. For example, a domain information query tool (DIG, Domain Information Groper) can be used to perform domain name resolution on the back-to-source domain name to obtain the target source station address.

[0052] After obtaining the target source station address, the target source station address can be used to update the scheduling cache to improve the efficiency of CDN back-to-source. In one implementation, the method further includes: Construct the target value based on the target source station address obtained by parsing; A target key-value pair is constructed according to the constructed target key and target value, and the scheduling cache is updated using the newly constructed target key-value pair.

[0053] The target value is the value corresponding to the target source station address in the target key-value pair. As mentioned above, the target key for query can be constructed based on the target cluster and the target access domain name, and the target key and target value can be combined to obtain the target key-value pair.

[0054] Furthermore, after obtaining the target key-value pair, the target key-value pair can be used to update the scheduling cache. For example, in the back-to-source information, the subnet of Hebei Mobile is A1 (subnet is the IP of the cluster, which is a pre-configured file). Through edig (enhanced dig) of the domain name in the back-to-source information, the back-to-source address A2 of the same operator can be obtained. In this way, A2 can be used as the value, the cluster name Hebei Mobile and the domain name to be accessed can be used as the key, and the link cache (i.e., key-value pair) as the mobile operator back-to-source can be constructed based on the key and value to update the scheduling cache. Similarly, the link caches of China Unicom and China Telecom operators can also be combined.

[0055] Figure 3 A schematic diagram showing an application example according to this specification is shown as follows: Figure 3 As shown, the embodiment of this specification proposes a CDN back-to-source method. As shown in the figure, the image processing process can be roughly divided into five steps: Step 1: The user initiates a request to access resources, and the request reaches nginx at the CDN edge; Step 2: If the CDN edge node has a cache corresponding to the access request, it will directly return it to the user. If not, it needs to return to the source. Step 3: nginx uses the IP address of the local machine (i.e., CDN aggregation node) to find the corresponding cluster in the cluster cache, and then searches the dispatch cache using the cluster and the domain name in the request; Step 4: If there is a cache corresponding to the cluster and the requested domain name, obtain the source address and directly return to the source; Step 5: If there is no cache corresponding to the cluster and the requested domain name, call the scheduling interface to obtain the source address for back-to-source.

[0056] It can be understood that the above-mentioned various method embodiments mentioned in this specification can be combined with each other to form a combined embodiment without violating the principle logic. Due to space limitations, they will not be repeated in this specification. Those skilled in the art can understand that in the above-mentioned method of the specific implementation method, the specific execution order of each step should be determined according to its function and possible internal logic.

[0057] It should be noted that the CDN retrieval method provided in the embodiments of this specification can be executed by a CDN retrieval device, or a control module in the CDN retrieval device for executing the CDN retrieval method. In the embodiments of this specification, the CDN retrieval device executing the CDN retrieval method is taken as an example to illustrate the CDN retrieval device provided in the embodiments of this specification.

[0058] Figure 4Schematic diagram of the structure of a CDN back-to-source device according to an embodiment of the present invention. Figure 4 As shown, the CDN back-to-source device 400 includes: A cluster determination module 410 is configured for a CDN aggregation node to receive an access request forwarded by an aggregated CDN edge node, and to determine a target cluster corresponding to the IP address of the CDN aggregation node based on a pre-configured cluster cache, wherein the cluster cache is a configuration file indicating a correspondence between an IP address and a cluster, and the cluster corresponds to an operator and / or region to which the CDN aggregation node belongs; An address determination module 420 is configured to determine, according to the target cluster and the target access domain name included in the access request, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs from a scheduling cache including multiple operators and / or regions; The source station back-to-source module 430 is used to initiate a back-to-source request for the target resource of the target source station address to the source station, cache the target resource sent by the source station according to the back-to-source request, and return it to the user end that initiated the access request.

[0059] In one embodiment, the address determination module 420 includes: A key unit, configured to construct a target key for querying a plurality of key-value pairs in the scheduling cache according to the target cluster and the target access domain name included in the access request, wherein the key in the key-value pair at least includes the cluster and the access domain name in the historical back-to-source information, and the value in the key-value pair at least includes the back-to-source address in the historical back-to-source information; The address unit is used to query the target key-value pair corresponding to the target key from the multiple key-value pairs, and use the address corresponding to the target value in the target key-value pair as the target source station address.

[0060] In one embodiment, the CDN back-to-origin device 400 further includes: A scheduling request module, configured to initiate a scheduling request including the target cluster and the target access domain name to the scheduling interface when there is no target key-value pair corresponding to the target key in the scheduling cache; The scheduling information module is used to obtain the target source station address from the scheduling information generated based on the scheduling request and returned by the scheduling interface.

[0061] In one embodiment, the scheduling information module includes: The domain name resolution unit is used to perform domain name resolution on the back-to-source domain name when the scheduling information includes the back-to-source domain name, and obtain the target source station address corresponding to the back-to-source domain name.

[0062] In one embodiment, the CDN back-to-origin device 400 further includes: The value module is used to construct the target value according to the parsed target source station address; The update module is used to construct a target key-value pair according to the constructed target key and target value, and use the newly constructed target key-value pair to update the scheduling cache.

[0063] In one embodiment, the cluster determination module 410 includes: a cache search unit, configured to, before determining the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, search, when the CDN aggregation node receives the access request, for a target resource corresponding to the target access domain name included in the access request in the resource cache corresponding to the CDN aggregation node; The cluster determination unit is used to confirm that the target resource is not found.

[0064] In one embodiment, the CDN back-to-origin device 400 further includes: The upper node module is used for, before determining the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, if the target resource is not found, further finding out whether the CDN aggregation node has an upper-level CDN aggregation node; An upper-level node determination module is used to confirm that the CDN aggregation node does not have an upper-level CDN aggregation node; The upper-level node execution module is used to forward the access request to the upper-level CDN aggregation node when the target resource is not found and the CDN aggregation node has an upper-level CDN aggregation node, so that the upper-level CDN aggregation node executes the CDN back-to-source method.

[0065] In the embodiment of this specification, after receiving the access request, the target cluster to which the CDN edge node belongs is first determined based on the cluster cache and the IP address of the CDN aggregation node, and then the target source station address that is the same as the operator and / or region of the CDN aggregation node is determined based on the target cluster and the target access domain name, and then the target resource corresponding to the target source station address is cached from the source station and returned to the user end. This process uses the IP address of the CDN aggregation node, the cluster cache and the scheduling cache in sequence, to determine the target source station address that is the same as the operator and / or region of the CDN aggregation node, solves the cross-operator problem that may occur in the return to source process, avoids the reset of the return to source link caused by cross-operators in multi-line computer rooms, improves the availability and assurance of CDN services, and thus improves the user experience.

[0066] Each module in the above CDN back-to-source device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in the terminal device or the server in the form of hardware, or can be stored in the memory in the terminal device or the server in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0067] Furthermore, corresponding to the CDN back-to-source method described above, based on the same technical concept, one or more embodiments of the present application further provide an electronic device, such as Figure 5 As shown. The electronic device may have relatively large differences due to different configurations or performances, and may include one or more processors 501 and memory 502, and the memory 502 may store one or more storage applications or data. Among them, the memory 502 may be a short-term storage or a persistent storage. The application stored in the memory 502 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the electronic device. Furthermore, the processor 501 can be configured to communicate with the memory 502 to execute a series of computer executable instructions in the memory 502 on the electronic device. The electronic device may also include one or more power supplies 503, one or more wired or wireless network interfaces 504, one or more input and output interfaces 505, and one or more keyboards 506.

[0068] In a specific embodiment, the electronic device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions for the electronic device, and the one or more programs configured to be executed by one or more processors include the following computer executable instructions: The CDN aggregation node receives the access request forwarded by the aggregated CDN edge node, and determines the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, wherein the cluster cache is a configuration file indicating the correspondence between the IP address and the cluster, and the cluster corresponds to the operator and / or region to which the CDN aggregation node belongs; According to the target cluster and the target access domain name included in the access request, determine, from a scheduling cache including multiple operators and / or regions, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs; A back-to-source request for the target resource at the target source station address is initiated to the source station, and after caching the target resource sent by the source station according to the back-to-source request, it is returned to the user end that initiated the access request.

[0069] In the embodiment of this specification, after receiving the access request, the target cluster to which the CDN edge node belongs is first determined based on the cluster cache and the IP address of the CDN aggregation node, and then the target source station address that is the same as the operator and / or region of the CDN aggregation node is determined based on the target cluster and the target access domain name, and then the target resource corresponding to the target source station address is cached from the source station and returned to the user end. This process uses the IP address of the CDN aggregation node, the cluster cache and the scheduling cache in sequence, to determine the target source station address that is the same as the operator and / or region of the CDN aggregation node, solves the cross-operator problem that may occur in the return to source process, avoids the reset of the return to source link caused by cross-operators in multi-line computer rooms, improves the availability and assurance of CDN services, and thus improves the user experience.

[0070] It should be noted that the embodiment of the electronic device in the present application and the embodiment of the CDN back-to-source method in the present application are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding CDN back-to-source method mentioned above, and the repeated parts will not be repeated.

[0071] Furthermore, corresponding to the CDN back-to-source method described above, based on the same technical concept, one or more embodiments of the present application further provide a storage medium for storing computer executable instructions. In a specific embodiment, the storage medium may be a USB flash drive, an optical disk, a hard disk, etc. When the computer executable instructions stored in the storage medium are executed by a processor, the following process can be implemented: The CDN aggregation node receives the access request forwarded by the aggregated CDN edge node, and determines the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, wherein the cluster cache is a configuration file indicating the correspondence between the IP address and the cluster, and the cluster corresponds to the operator and / or region to which the CDN aggregation node belongs; According to the target cluster and the target access domain name included in the access request, determine, from a scheduling cache including multiple operators and / or regions, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs; A back-to-source request for the target resource at the target source station address is initiated to the source station, and after caching the target resource sent by the source station according to the back-to-source request, it is returned to the user end that initiated the access request.

[0072] In the embodiment of this specification, after receiving the access request, the target cluster to which the CDN edge node belongs is first determined based on the cluster cache and the IP address of the CDN aggregation node, and then the target source station address that is the same as the operator and / or region of the CDN aggregation node is determined based on the target cluster and the target access domain name, and then the target resource corresponding to the target source station address is cached from the source station and returned to the user end. This process uses the IP address of the CDN aggregation node, the cluster cache and the scheduling cache in sequence, to determine the target source station address that is the same as the operator and / or region of the CDN aggregation node, solves the cross-operator problem that may occur in the return to source process, avoids the reset of the return to source link caused by cross-operators in multi-line computer rooms, improves the availability and assurance of CDN services, and thus improves the user experience.

[0073] It should be noted that the embodiment of the storage medium in the present application and the CDN back-to-source method in the present application are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding CDN back-to-source method mentioned above, and the repeated parts will not be repeated.

[0074] Furthermore, corresponding to the CDN back-to-origin method described above, based on the same technical concept, one or more embodiments of the present application further provide a computer program product, the computer program product including a computer program, which can implement the following process when executed by a processor: The CDN aggregation node receives the access request forwarded by the aggregated CDN edge node, and determines the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, wherein the cluster cache is a configuration file indicating the correspondence between the IP address and the cluster, and the cluster corresponds to the operator and / or region to which the CDN aggregation node belongs; According to the target cluster and the target access domain name included in the access request, determine, from a scheduling cache including multiple operators and / or regions, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs; A back-to-source request for the target resource at the target source station address is initiated to the source station, and after caching the target resource sent by the source station according to the back-to-source request, it is returned to the user end that initiated the access request.

[0075] In the embodiment of this specification, after receiving the access request, the target cluster to which the CDN edge node belongs is first determined based on the cluster cache and the IP address of the CDN aggregation node, and then the target source station address that is the same as the operator and / or region of the CDN aggregation node is determined based on the target cluster and the target access domain name, and then the target resource corresponding to the target source station address is cached from the source station and returned to the user end. This process uses the IP address of the CDN aggregation node, the cluster cache and the scheduling cache in sequence, to determine the target source station address that is the same as the operator and / or region of the CDN aggregation node, solves the cross-operator problem that may occur in the return to source process, avoids the reset of the return to source link caused by cross-operators in multi-line computer rooms, improves the availability and assurance of CDN services, and thus improves the user experience.

[0076] It should be noted that the embodiment of the computer program product in the present application and the embodiment of the CDN back-to-source method in the present application are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding CDN back-to-source method mentioned above, and the repeated parts will not be repeated.

[0077] The above describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0078] In the 1990s, it was very clear whether the improvement of a technology was hardware improvement (for example, improvement of the circuit structure of diodes, transistors, switches, etc.) or software improvement (improvement of the method flow). However, with the development of technology, many improvements of the method flow today can be regarded as direct improvements of the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented with a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming themselves, without having to ask chip manufacturers to design and make dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0079] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0080] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0081] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing the embodiments of the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0082] Those skilled in the art will appreciate that one or more embodiments of the present application may be provided as a method, system or computer program product. Therefore, one or more embodiments of the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0083] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0084] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0085] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0086] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0087] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0088] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules 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 disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0089] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0090] One or more embodiments of the present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present application may also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0091] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0092] The above are only embodiments of this document and are not intended to limit this document. For those skilled in the art, this document may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this document should be included in the scope of the claims of this document.

Claims

1. A CDN back-to-source method, characterized in that: include: The CDN aggregation node receives the access request forwarded by the aggregated CDN edge node, and determines the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, wherein the cluster cache is a configuration file indicating the correspondence between the IP address and the cluster, and the cluster corresponds to the operator and / or region to which the CDN aggregation node belongs; According to the target cluster and the target access domain name included in the access request, determine, from a scheduling cache including multiple operators and / or regions, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs; A back-to-source request for the target resource at the target source station address is initiated to the source station, and after caching the target resource sent by the source station according to the back-to-source request, it is returned to the user end that initiated the access request.

2. The method according to claim 1, characterized in that The determining, according to the target cluster and the target access domain name included in the access request, from a scheduling cache including multiple operators and / or regions, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs, includes: According to the target cluster and the target access domain name included in the access request, construct a target key for querying multiple key-value pairs in the scheduling cache, wherein the key in the key-value pair at least includes the cluster and the access domain name in the historical back-to-source information, and the value in the key-value pair at least includes the back-to-source address in the historical back-to-source information; From the multiple key-value pairs, query the target key-value pair corresponding to the target key, and use the address corresponding to the target value in the target key-value pair as the target source station address.

3. The method according to claim 2, characterized in that In the case where there is no key-value pair corresponding to the target key in the scheduling cache, the method further includes: Initiate a scheduling request including the target cluster and the target access domain name to the scheduling interface; The target source station address is obtained from the scheduling information generated based on the scheduling request and returned by the scheduling interface.

4. The method according to claim 3, characterized in that The acquiring the target source station address from the scheduling information generated based on the scheduling request and returned from the scheduling interface includes: In the case where the scheduling information includes a back-to-source domain name, a domain name resolution is performed on the back-to-source domain name to obtain a target source station address corresponding to the back-to-source domain name.

5. The method according to claim 4, characterized in that The method further comprises: Construct the target value based on the target source station address obtained by parsing; A target key-value pair is constructed according to the constructed target key and target value, and the scheduling cache is updated using the newly constructed target key-value pair.

6. The method according to claim 1, characterized in that Before determining the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, the method further includes: When the CDN aggregation node receives the access request, the CDN aggregation node searches for a target resource corresponding to the target access domain name included in the access request in a resource cache corresponding to the CDN aggregation node; And confirm that the target resource is not found.

7. The method according to claim 6, characterized in that Before determining the target cluster corresponding to the IP address of the CDN aggregation node based on the pre-configured cluster cache, the method further includes: If the target resource is not found, further searching whether the CDN aggregation node has a CDN aggregation node at an upper level; And confirm that the CDN aggregation node does not have a CDN aggregation node at the previous level; The method further comprises: When the target resource is not found and the CDN aggregation node has an upper-level CDN aggregation node, the access request is forwarded to the upper-level CDN aggregation node, so that the upper-level CDN aggregation node executes the CDN tracing method.

8. A CDN back-to-source device, characterized in that: include: A cluster determination module, configured for a CDN aggregation node to receive an access request forwarded by an aggregated CDN edge node, and to determine a target cluster corresponding to the IP address of the CDN aggregation node based on a pre-configured cluster cache, wherein the cluster cache is a configuration file indicating a correspondence between an IP address and a cluster, and the cluster corresponds to an operator and / or region to which the CDN aggregation node belongs; An address determination module, configured to determine, according to the target cluster and the target access domain name included in the access request, a target source station address that is the same as the operator and / or region to which the CDN aggregation node belongs from a scheduling cache including multiple operators and / or regions; The source station back-to-source module is used to initiate a back-to-source request for the target resource of the target source station address to the source station, cache the target resource sent by the source station according to the back-to-source request, and return it to the user end that initiated the access request.

9. An electronic device, characterized in that: include: processor; as well as A memory arranged to store computer executable instructions, the executable instructions being configured to be executed by the processor, the executable instructions comprising instructions for performing the steps in the method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is used to store computer-executable instructions, and the executable instructions enable a computer to execute the method according to any one of claims 1 to 7.

Images