Access request processing method and device and electronic equipment

Abstract

The invention provides an access request processing method and device and electronic equipment, and relates to the technical field of the Internet. The method comprises: receiving an access request ofa client for a target domain name; judging whether data of the target domain name is locally stored in node equipment or not; and if the data of the target domain name is not stored, determining an upper-layer node for processing the access request according to the target domain name, and processing the access request according to the determined upper-layer node. According to the embodiment of the invention, an association relationship between the domain name and a back-to-source node is preset, when the content data of the target domain name requested to be accessed is not stored in the nodeequipment, and the corresponding associated back-to-source node can be determined according to the target domain name for back-to-source, therefore, only resources of the target domain name need to be cached to the associated upper-layer node, the redundant storage problem caused by caching the same resources in multiple upper-layer nodes in a preferred back-to-source mode is effectively relieved, and the overall caching capacity of a CDN is enhanced.

Description

technical field [0001] The present invention relates to the technical field of the Internet, in particular to an access request processing method, device and electronic equipment. Background technique [0002] Normally, content delivery network (Content Delivery Network, CDN) nodes are divided into two levels: edge nodes and upper-level nodes, and nodes at different levels play different roles. Among them, the edge node is used to serve the user's access to the domain name and cache the content of the domain name. When there is no content cache for the corresponding domain name in the edge node, the edge node will access its corresponding upper node. If the upper node has the cache content of the domain name, it will directly respond to the edge node. If there is no cache content of the domain name, the upper The node will go back to the source site of the domain name to pull the corresponding cache content, then cache it on the node, and then respond to the edge node. [...

AI Technical Summary

Problems solved by technology

[0003] At present, the existing CDN node back-to-source methods, such as selecting the best source, because edge nodes do not distinguish domain names when returning to the upper-level nodes, but detect the connectivity of the upper-level nodes and use round-robin training to select the best back-to-source. This method will cause multiple upper-level nodes to cache the same resource at the same time, and if the required resources are not in the caches of these multiple upper-level nodes, they will all pull resources from the origin site, resulting in a higher return-to-origin rate for domain name access , and cause redundant storage of upper nodes, reducing the overall caching capacity of the content distribution network

[0004] Overall, the existing CDN node back-to-origin methods still have the problems of high back-to-origin rate of domain name access, serious redundant storage of upper-layer nodes, and weak overall caching capacity of the content distribution network

Images