CDN request processing method and CDN request processing system for edge node

Abstract

The invention relates to the technical field of communication, and discloses a CDN request processing method and a CDN request processing system of an edge node, the CDN request processing method of the edge node is applied to an edge cache node of a CDN, and the method comprises the following steps: obtaining a target configuration file sent by an edge management node; obtaining a CDN request, and determining a first domain name configuration in the CDN request; when the target configuration file does not comprise the first domain name configuration, requesting an edge management node to obtain the first domain name configuration; and loading the first domain name configuration, and processing the CDN request based on the first domain name configuration. According to the method and the device, the full domain name configuration can be loaded into the edge management node of the edge node, so that the edge cache node can load the required target configuration file from the edge management node, the storage cost is reduced while the memory occupation of the edge cache node is reduced, and the starting duration of the edge cache node is further reduced.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a CDN request processing method and a CDN request processing system for an edge node. Background Art

[0002] A Content Delivery Network (CDN) service accelerates content delivery and optimizes the user experience by deploying server clusters across multiple locations. In a CDN architecture, you manage the configuration files for accelerated domain names at the central node and distribute them to all edge nodes.

[0003] Configuration file management solutions typically load all configuration files into the memory of edge cache nodes, ready for use when CDN requests arrive. Over time, the number of accelerated domain names connected to CDN systems continues to grow, leading to a growing number of configuration files synchronized in edge cache nodes. Ultimately, managing this massive volume of small files can lead to numerous management and performance issues, such as slowing server startup times and occupying significant amounts of memory, increasing storage costs. Summary of the Invention

[0004] In view of this, the present disclosure provides a CDN request processing method and a CDN request processing system for edge nodes to solve the management and performance problems caused by the increasing number of configuration files in the edge cache nodes of the CDN system.

[0005] In a first aspect, the present disclosure provides a CDN request processing method for an edge node, which is applied to an edge cache node of a CDN, and the edge cache node is used to interact with an interactive object. The method includes: Obtaining a target configuration file sent by an edge management node. The edge management node and the edge cache node are located at the same edge node in the CDN. The edge management node is used to store and manage the full domain name configuration sent by the CDN central node. The target configuration file includes a partial domain name configuration in the full domain name configuration. Obtain a CDN request and determine the first domain name configuration in the CDN request; When the target configuration file does not include the first domain name configuration, requesting the edge management node to obtain the first domain name configuration; The first domain name configuration is loaded, and the CDN request is processed based on the first domain name configuration.

[0006] In a second aspect, the present disclosure provides a CDN request processing method for an edge node, which is applied to an edge management node of a CDN, wherein the edge management node is used to store and manage the full domain name configuration sent by the CDN central node, and the method includes: detecting a second acquisition request sent by an edge cache node, wherein the edge cache node and the edge management node are located at the same edge node in the CDN, and the edge cache node is used to interact with the interaction object for data; Searching the full domain name configuration for the first domain name configuration indicated by the second acquisition request; In response to the second acquisition request, the first domain name configuration is sent to the edge cache node.

[0007] In a third aspect, the present disclosure provides a CDN request processing device for an edge node, which is applied to an edge cache node of a CDN. The edge cache node is used to interact with an interactive object for data. The device includes: A first acquisition module is configured to acquire a target configuration file sent by an edge management node, wherein the edge management node and the edge cache node are located at the same edge node in the CDN, and the edge management node is configured to store and manage the full domain name configuration sent by the CDN central node, wherein the target configuration file includes a partial domain name configuration in the full domain name configuration; A determination module, configured to obtain a CDN request and determine a first domain name configuration in the CDN request; A second acquisition module is configured to request the edge management node to acquire the first domain name configuration when the target configuration file does not include the first domain name configuration; The processing module is used to load the first domain name configuration and process the CDN request based on the first domain name configuration.

[0008] In a fourth aspect, the present disclosure provides a CDN request processing device for an edge node, which is applied to an edge management node of a CDN, wherein the edge management node is used to store and manage the full domain name configuration sent by the central node of the CDN, and the device includes: a detection module, configured to detect a second acquisition request sent by the edge management node, wherein the edge cache node and the edge management server are located at the same edge node in the content distribution network and are configured to interact with the interaction object for data; A search module, configured to search the full domain name configuration for the first domain name configuration indicated by the second acquisition request; The sending module is configured to send the first domain name configuration to the edge cache node in response to the second acquisition request.

[0009] In a fifth aspect, the present disclosure provides a CDN request processing system for an edge node, the system comprising: a CDN central node, an edge management node, and an edge cache node, wherein the edge management node and the edge cache node are located in the same edge node of the CDN; The central node is used to send the full domain name configuration to the edge management node, where the full domain name configuration includes the domain name configuration of all accelerated domain names set in the CDN; The edge management node is configured to determine a first domain name configuration whose access count meets a popularity condition in the full domain name configuration, and determine a target configuration file based on the first domain name configuration; The edge cache node is configured to load the target configuration file into the memory, and when the target configuration file does not include the first domain name configuration in the received CDN request, request the edge management node to obtain the first domain name configuration, and process the CDN request based on the first domain name configuration.

[0010] In an embodiment of the present disclosure, first, a target configuration file sent by an edge management node can be obtained, wherein the edge management node and the edge cache node are located at the same edge node in the CDN, and the edge management node is used to store and manage the full domain name configuration sent by the central node of the CDN, and the target configuration file includes a partial domain name configuration in the full domain name configuration. Next, a CDN request can be obtained, and the first domain name configuration in the CDN request can be determined. Then, when the first domain name configuration is not included in the target configuration file, a request can be made to the edge management node to obtain the first domain name configuration, and the first domain name configuration can be loaded to process the CDN request based on the first domain name configuration, thereby loading the full domain name configuration into the edge management node of the edge node, so that the edge cache node can load the required target configuration file from the edge management node, and obtain the first domain name configuration from the edge management node in response to the CDN request, while reducing the memory usage of the edge cache node, reducing storage costs, and thereby reducing the startup time of the edge cache node. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0012] Figure 1 This is a flow chart of a CDN request processing method of an edge node according to an embodiment of the present disclosure; Figure 2 is a schematic diagram of a CDN network architecture according to an embodiment of the present disclosure; Figure 3 1 is a flow chart of another CDN request processing method of an edge node according to an embodiment of the present disclosure; Figure 4 This is a structural block diagram of a CDN request processing device of an edge node according to an embodiment of the present disclosure; Figure 5 is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present disclosure; Figure 6 is a structural block diagram of a CDN request processing device of another edge node according to an embodiment of the present disclosure; Figure 7 Schematic diagram of the hardware structure of the computer device according to the embodiment of the present disclosure. DETAILED DESCRIPTION

[0013] To make the purpose, technical solutions, and advantages of the embodiments of the present disclosure more clear, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of the present disclosure.

[0014] In conjunction with the application scenarios on which the execution of the configuration management method depends, the application scenarios are described here.

[0015] A Content Delivery Network (CDN) service accelerates content delivery and optimizes the user experience by deploying server clusters across multiple locations. In a CDN architecture, you manage the configuration files for accelerated domain names at the central node and distribute them to all edge nodes.

[0016] Configuration file management solutions typically load all configuration files into the memory of edge cache nodes, ready for use when CDN requests arrive. Over time, the number of accelerated domain names connected to CDN systems continues to grow, leading to a growing number of configuration files synchronized in edge cache nodes. Ultimately, managing this massive volume of small files can lead to numerous management and performance issues, such as slowing server startup times and occupying significant amounts of memory, increasing storage costs.

[0017] Specifically, with the development of CDN services, the number of accelerated domain names undertaken by CDNs has increased, resulting in the number of configuration files for a single CDN server reaching millions. The presence of massive small files poses multiple technical challenges to edge nodes in CDNs. First, when the edge cache node acceleration service software in the edge node is started or restarted, all small configuration files must be read from disk into memory and parsed. This massive configuration slows down service startup. Second, this massive configuration consumes a large amount of server memory. Assuming that each domain name only requires 10KB, 1 million configuration files will consume 10GB of memory space. In related configuration file management solutions, a grouping and platform-based approach is commonly adopted to divide CDN server clusters into multiple groups. The number of domain names that need to be managed by each server cluster is shared. However, this approach also brings additional group management burdens and is not conducive to resource reuse in CDN server clusters. Therefore, a more reasonable management method is needed to solve the problems of slow service startup and high memory usage.

[0018] Based on this, an embodiment of the present disclosure provides a CDN request processing method for an edge node. The CDN request processing method is applied to an edge cache node of a CDN, which is used to interact with interactive objects. The method first obtains a target configuration file sent by an edge management node, wherein the edge management node and the edge cache node are located at the same edge node in the CDN. The edge management node is used to store and manage the full domain name configuration sent by the CDN central node, and the target configuration file includes a partial domain name configuration in the full domain name configuration. Next, a CDN request can be obtained and a first domain name configuration in the CDN request can be determined. Then, if the first domain name configuration is not included in the target configuration file, a request can be made to the edge management node to obtain the first domain name configuration, and the first domain name configuration can be loaded to process the CDN request based on the first domain name configuration. The full domain name configuration is loaded into the edge management node of the edge node, so that the edge cache node can load the required target configuration file from the edge management node and obtain the first domain name configuration from the edge management node in response to the CDN request. This reduces the memory usage of the edge cache node and reduces storage costs, thereby reducing the startup time of the edge cache node.

[0019] According to an embodiment of the present disclosure, a configuration management method embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0020] It is understandable that before using the technical solutions disclosed in the various embodiments of this disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved in this disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0021] For example, in response to a user's active request, a prompt message is sent to the user to clearly inform the user that the operation requested will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the electronic device, application, server, storage medium, or other software or hardware that performs the operations of the disclosed technical solution based on the prompt message.

[0022] As an optional but non-limiting implementation, in response to receiving a user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. Furthermore, the pop-up window may also contain a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0023] It is understandable that the above notification and user authorization process are merely illustrative and do not limit the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0024] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0025] According to an embodiment of the present disclosure, an embodiment of a CDN request method for an edge node is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0026] In this embodiment, a CDN request processing method for an edge node is provided, which can be used for the edge cache node of the CDN. The edge cache node is used to interact with the interactive object for data. Figure 1 FIG. 1 is a flow chart of a CDN request processing method of an edge node according to an embodiment of the present disclosure. Figure 1 As shown, the process includes the following steps: Step S101: Obtain a target configuration file sent by an edge management node, wherein the edge management node and the edge cache node are located at the same edge node in the CDN. The edge management node is used to store and manage the full domain name configuration sent by the central node of the CDN. The target configuration file includes a partial domain name configuration in the full domain name configuration.

[0027] In the disclosed embodiments, CDN may be a complex network system composed of core components such as a central node, an edge node, a content management system, and a monitoring system. The central node is the core of the CDN system, responsible for receiving all user requests and routing the requests to the most appropriate edge node based on factors such as the user's geographical location. The central node is usually a centralized server cluster with powerful processing capabilities and load balancing functions. The edge node, namely the above-mentioned edge node, is the distribution carrier of the CDN system. It is distributed in geographically distant places and is responsible for storing and distributing content and directly providing services to users. The content management system is responsible for generating, updating, and managing website content. The monitoring system is responsible for real-time monitoring of the performance and availability of the CDN in order to promptly discover and resolve problems.

[0028] Here, as Figure 2 The diagram shows a CDN network architecture, wherein the CDN architecture may include a central node and several edge nodes. Figure 2 FIG3 shows edge node 1 and edge node 2, and the remaining edge nodes in the CDN architecture are not shown one by one.

[0029] Specifically, the CDN central computer room is the aforementioned central node, which includes a central server that manages the domain name configuration of all accelerated domain names set up in the CDN through this central server cluster. Specifically, the central server cluster can be used to manage the addition, deletion, and modification of domain name configurations and transmit the full domain name configuration to each edge node.

[0030] An edge node can contain several edge cache nodes (i.e. Figure 2 Edge caching nodes in the central node can be used to store and distribute content to accelerate user access. An edge node can include one or two edge management nodes, which are used to manage edge caching nodes. For example, they manage the full domain name configuration data distributed by the central node, load balancing, content caching and distribution, and network traffic management.

[0031] In the same edge node, after receiving the full domain name configuration sent by the central node, the edge management node can respond to the acquisition request of the edge cache node, determine the domain name configuration required by the edge cache node based on the full domain name configuration, and determine the target configuration file based on the determined domain name configuration.

[0032] After the edge cache node obtains the target configuration file, it can load it into memory. It should be understood that because the edge cache node and the edge management node are located in the same edge node, the configuration file request and loading process occurs in the same data center, taking less than 10ms, far less than the time it takes for the edge server cluster to request the configuration file from the central node.

[0033] Step S102: Obtain a CDN request and determine a first domain name configuration in the CDN request.

[0034] In the embodiment of the present disclosure, users can access the accelerated domain name through a CDN request, and the CDN request can include multiple aspects of information such as the content requested by the user, geographic location information, network status, and the configuration of the requested first domain name.

[0035] Step S103: When the target configuration file does not include the first domain name configuration, request the edge management node to obtain the first domain name configuration.

[0036] Step S104: load the first domain name configuration, and process the CDN request based on the first domain name configuration.

[0037] In the disclosed embodiment, the edge cache node can match the domain name configuration in the target configuration file to determine whether the target configuration file contains the first domain name configuration. If so, it can respond to the CDN request and interact with the user. If not, it can generate a request to the edge management node to obtain the first domain name configuration and load it into memory. It should be understood that because the edge cache node and the edge management node are located in the same computer room, the acceleration effect of the CDN is relatively small.

[0038] In summary, in the embodiment of the present disclosure, first, the target configuration file sent by the edge management node can be obtained, wherein the edge management node and the edge cache node are located at the same edge node in the CDN, and the edge management node is used to store and manage the full domain name configuration sent by the central node of the CDN, and the target configuration file includes part of the domain name configuration in the full domain name configuration. Next, the CDN request can be obtained, and the first domain name configuration in the CDN request can be determined. Then, when the first domain name configuration is not included in the target configuration file, the first domain name configuration can be requested from the edge management node, and the first domain name configuration can be loaded to process the CDN request based on the first domain name configuration, thereby loading the full domain name configuration into the edge management node of the edge node, so that the edge cache node can load the required target configuration file from the edge management node, and obtain the first domain name configuration from the edge management node in response to the CDN request, while reducing the memory usage of the edge cache node, reducing storage costs, and thereby reducing the startup time of the edge cache node.

[0039] In some optional implementations, the above step S101, obtaining the target configuration file sent by the edge management node, includes: Step S1011: When the edge cache node is started, a first acquisition request is generated, wherein the first acquisition request is used to acquire a target configuration file in the edge management node that includes a partial domain name configuration whose access times meet a popularity condition.

[0040] Step S1012: Obtain the target configuration file fed back by the edge management node in response to the first acquisition request.

[0041] In the disclosed embodiments, when an edge cache node is started or restarted, the acceleration software in the edge cache node that performs domain name acceleration in response to a user's CDN request will also restart. At this time, the target configuration file needs to be loaded. Furthermore, if the edge cache node is not started or restarted, the target configuration file also needs to be reloaded if the acceleration software restarts.

[0042] At this time, a first acquisition request can be generated, wherein the first acquisition request can include a heat condition, and the heat condition is used to instruct the edge management node to filter out some domain name configurations in the full domain name configuration whose number of visits within a preset time period meets the heat condition, so as to determine the target configuration file based on the partial domain name configuration.

[0043] For example, the popularity condition can be used to filter out domain name configurations that are ranked in the top 100 in terms of the number of recent visits, or domain name configurations that have been visited more than 100,000 times in the total number of domain name configurations.

[0044] In the embodiment of the present disclosure, the hottest domain name configuration that meets the heat condition can be pre-loaded in the edge cache node, thereby greatly reducing the number of configurations that need to be maintained in the memory of the acceleration software, thereby solving the problem of long service restart time and large memory usage.

[0045] In some optional embodiments, the above Figure 1 The corresponding embodiments also include: Step S11: determining, in the target configuration file, a second domain name configuration that has not been accessed within a preset historical period.

[0046] Step S12: clear the second domain name configuration in the target configuration file.

[0047] In an embodiment of the present disclosure, the edge cache node may, in response to an analysis request for the target configuration file, analyze the target configuration file, determine the second domain name configurations in the target configuration file that have not been accessed by CDN requests within a preset historical period, and clear the second domain name configurations in the target configuration file. For example, if the preset historical period can be set to one hour, the second domain name configurations in the target configuration file that have not been accessed for more than one hour may be cleared.

[0048] For example, when the target configuration file is loaded, the acceleration software can maintain a timestamp for each domain name configuration in memory and sort them by timestamp. When a CDN request arrives, the timestamp of the domain name configuration accessed by the CDN request can be refreshed to the current time. Then, a cleanup operation can be performed every hour to delete from memory any domain name configuration that has not been accessed by any CDN request within the hour.

[0049] In the embodiment of the present disclosure, the second domain name configuration that has not been requested to be accessed in the target configuration file can be deleted according to a certain cleaning cycle to reduce the memory usage in the edge cache node and improve the utilization of memory resources.

[0050] In this embodiment, another CDN request processing method for an edge node is provided, which can be used for the edge management node of the CDN described above, wherein the edge management node is used to store and manage the full domain name configuration sent by the CDN central node. Figure 3 FIG. 1 is a flow chart of another CDN request processing method of an edge node according to an embodiment of the present disclosure. Figure 1 As shown, the process includes the following steps: Step S301: Detect a second acquisition request sent by an edge cache node, wherein the edge cache node and the edge management node are located at the same edge node in the CDN, and the edge cache node is used to interact with the interaction object for data.

[0051] In an embodiment of the present disclosure, when an edge cache node receives a CDN request, it can determine the first domain name configuration in the CDN request, and when the first domain name configuration is not included in the target configuration file, request the edge management node to obtain the first domain name configuration through a second acquisition request.

[0052] Step S302: Search the full domain name configuration for the first domain name configuration indicated by the second acquisition request.

[0053] Step S303: In response to the second acquisition request, the first domain name configuration is sent to the edge cache node.

[0054] In the embodiment of the present disclosure, the above Figure 2It can be seen that the edge management node can be used to receive the full domain name configuration sent by the CDN and store it in the memory, and store part of the domain name configuration in the full domain name configuration in the target configuration file and distribute it to each edge cache node in the edge node.

[0055] Based on this, when the edge cache node processes the CDN request, there may be a situation where the target configuration file does not include the first domain name configuration in the CDN request. At this time, the edge cache node can generate a second acquisition request based on the first domain name configuration, so that the edge management node can search for the first domain name configuration indicated by the second acquisition request in the full domain name configuration based on the second acquisition request, and send the first domain name configuration to the edge cache node.

[0056] In summary, in the embodiment of the present disclosure, the second acquisition request sent by the edge cache node can be detected first, wherein the edge cache node and the edge management node are in the same edge node in the CDN, and the edge cache node is used to interact with the interactive object for data. Then, the first domain name configuration indicated by the second acquisition request can be searched in the full domain name configuration, and in response to the second acquisition request, the first domain name configuration is sent to the edge cache node, thereby loading the full domain name configuration into the edge management node of the edge node, so that the edge cache node can load the required target configuration file from the edge management node, and obtain the first domain name configuration from the edge management node in response to the CDN request, thereby reducing the memory usage of the edge cache node and reducing the storage cost, thereby reducing the startup time of the edge cache node.

[0057] In some optional embodiments, the above Figure 3 The corresponding embodiments also include: Step S21: Obtain a first acquisition request sent by an edge cache node, and determine a summary period in the first acquisition request.

[0058] Step S22: Aggregate the monitored CDN requests based on the summary period to obtain a first domain name configuration whose number of visits meets the popularity condition in the full domain name configuration.

[0059] Step S23: determining a target configuration file according to the first domain name configuration, and sending the target configuration file to the edge cache node in response to the first acquisition request.

[0060] In the disclosed embodiments, when an edge cache node is started or restarted, the acceleration software in the edge cache node that performs domain name acceleration in response to a user's CDN request will also restart. At this time, the target configuration file needs to be loaded. Furthermore, if the edge cache node is not started or restarted, the target configuration file also needs to be reloaded if the acceleration software restarts.

[0061] At this time, a first acquisition request can be generated, wherein the first acquisition request can include a heat condition, which is used to instruct the edge management node to filter out some domain name configurations in the full domain name configuration whose number of visits within the summary period meets the heat condition, so as to determine the target configuration file based on the partial domain name configuration.

[0062] For example, the popularity condition can be used to filter out domain name configurations that are ranked in the top 100 in terms of the number of recent visits, or domain name configurations that have been visited more than 100,000 times in the total number of domain name configurations.

[0063] In the embodiment of the present disclosure, the hottest domain name configuration that meets the heat condition can be pre-loaded in the edge cache node, thereby greatly reducing the number of configurations that need to be maintained in the memory of the acceleration software, thereby solving the problem of long service restart time and large memory usage.

[0064] In some optional embodiments, the above Figure 3 The corresponding embodiments also include: Step S31: Based on the first data interface, obtain the full domain name configuration fed back by the central node of the CDN.

[0065] Step S32: Load the second configuration file into the local memory.

[0066] In an embodiment of the present disclosure, the edge management node can be an API server cluster, and an https interface for data interaction with the central node of the CDN can be set in the edge management node. The https interface may include a first data interface, wherein the first data interface is an https interface that provides full domain name configuration download.

[0067] Specifically, when the edge management node is powered on or restarted, the full domain name configuration can be obtained from the central node of the CDN through the first data interface and loaded into the local memory.

[0068] In some optional embodiments, the above Figure 3 The corresponding embodiments also include: Step S41: Detect an update event for the full domain name configuration in the central node based on the second data interface to obtain incremental data.

[0069] Step S42: Acquire incremental data based on the third data interface, and update the full domain name configuration in the memory according to the incremental data.

[0070] In the embodiment of the present disclosure, it can be seen from the above that an https interface for data interaction with the central node of the CDN can be set in the edge management node, and the https interface can also include a second data interface and a third data interface.

[0071] Specifically, the second data interface can be a configuration change event monitoring interface, which can be used to monitor update events for the full domain name configuration in the data center, and determine incremental data based on the update time, wherein the incremental data can be used to indicate the update, modification or deletion of the full domain name configuration.

[0072] Then, incremental data can be obtained based on the third data interface, which can be a single domain name configuration download interface. When the above update time is a new domain name configuration, the new domain name configuration can be obtained through the third data interface and updated to the local memory.

[0073] In an embodiment of the present disclosure, an https interface for data interaction with the central node of the CDN can be set in the edge management node, so as to obtain the full data or incremental data of the domain name configuration according to the https interface, and maintain the consistency of the domain name configuration in the edge management node and the domain name configuration in the central node.

[0074] In summary, in the embodiment of the present disclosure, first, the target configuration file sent by the edge management node can be obtained, wherein the edge management node and the edge cache node are located at the same edge node in the CDN, and the edge management node is used to store and manage the full domain name configuration sent by the central node of the CDN, and the target configuration file includes part of the domain name configuration in the full domain name configuration. Next, the CDN request can be obtained, and the first domain name configuration in the CDN request can be determined. Then, when the first domain name configuration is not included in the target configuration file, the first domain name configuration can be requested from the edge management node, and the first domain name configuration can be loaded to process the CDN request based on the first domain name configuration, thereby loading the full domain name configuration into the edge management node of the edge node, so that the edge cache node can load the required target configuration file from the edge management node, and obtain the first domain name configuration from the edge management node in response to the CDN request, while reducing the memory usage of the edge cache node, reducing storage costs, and thereby reducing the startup time of the edge cache node.

[0075] This embodiment also provides a CDN request processing device for an edge node, which is used to implement the above Figure 1 The corresponding embodiments and preferred implementations have been described and will not be repeated here. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

[0076] This embodiment provides a CDN request processing device for an edge node, such as Figure 4 As shown, including: A first acquisition module 401 is configured to acquire a target configuration file sent by an edge management node, wherein the edge management node and the edge cache node are located at the same edge node in the CDN. The edge management node is configured to store and manage the full domain name configuration sent by the CDN central node. The target configuration file includes a partial domain name configuration in the full domain name configuration. Determination module 402, configured to obtain a CDN request and determine a first domain name configuration in the CDN request; The second acquisition module 403 is configured to request the edge management node to acquire the first domain name configuration when the target configuration file does not include the first domain name configuration; The processing module 404 is configured to load the first domain name configuration and process the CDN request based on the first domain name configuration.

[0077] In some optional implementations, the first acquisition module 401 is further configured to: When the edge cache node is started, a first acquisition request is generated, wherein the first acquisition request is used to obtain a target configuration file in the edge management node that includes a configuration of a portion of domain names whose access times meet a popularity condition; The target configuration file fed back by the edge management node in response to the first acquisition request is obtained.

[0078] In some optional embodiments, the device is further used to: Determining, in the target configuration file, a second domain name configuration that has not been accessed within a preset historical period; Clear the second domain name configuration in the target configuration file.

[0079] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0080] The CDN request processing device of the edge node in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0081] The present disclosure also provides a computer device having the above Figure 4 The CDN request processing device of the edge node shown.

[0082] See also Figure 5 , Figure 5 is a structural diagram of a computer device provided by an optional embodiment of the present disclosure, such as Figure 5As shown, the computer device includes: one or more processors 10, memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components utilize different buses to communicate with each other and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in the memory or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Equally, multiple computer devices can be connected, and each device provides part of the necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 5 A processor 10 is taken as an example.

[0083] The processor 10 may be a central processing unit, a network processor, or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic, or any combination thereof.

[0084] The memory 20 stores instructions that can be executed by at least one processor 10, so as to enable at least one processor 10 to execute the method shown in the above embodiment.

[0085] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store data created based on the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0086] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0087] The computer device further includes a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0088] This embodiment provides another CDN request processing device for edge nodes, such as Figure 6 As shown, including: A detection module 601 is configured to detect a second acquisition request sent by an edge management node, wherein the edge cache node and the edge management server are located at the same edge node in the content distribution network and are configured to interact with the interaction object for data exchange; A search module 602 is configured to search the full domain name configuration for the first domain name configuration indicated by the second acquisition request; The sending module 603 is configured to send the first domain name configuration to the edge cache node in response to the second acquisition request.

[0089] In some optional embodiments, the device is further used to: Obtaining a first acquisition request sent by the edge cache node, and determining a summary period in the first acquisition request; Aggregate the monitored CDN requests based on the summary period to obtain the first domain name configuration whose access count meets the popularity condition among the full domain name configurations; A target configuration file is determined according to the first domain name configuration, and the target configuration file is sent to the edge cache node in response to the first acquisition request.

[0090] In some optional embodiments, the device is further used to: Based on the first data interface, obtain the full domain name configuration fed back by the CDN central node; Load the second configuration file into local memory.

[0091] In some optional embodiments, the device is further used to: Detecting an update event for the full domain name configuration in the central node based on the second data interface to obtain incremental data; Obtain incremental data based on the third data interface, and update the full domain name configuration in the memory according to the incremental data.

[0092] When the edge cache node is started, a first acquisition request is generated, wherein the first acquisition request is used to obtain a target configuration file in the edge management node that includes a configuration of a portion of domain names whose access times meet a popularity condition; The target configuration file fed back by the edge management node in response to the first acquisition request is obtained.

[0093] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0094] The CDN request processing device of the edge node in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0095] The present disclosure also provides another computer device having the above Figure 6 The CDN request processing device of the edge node shown.

[0096] See also Figure 7 , Figure 7 is a structural diagram of another computer device provided by an optional embodiment of the present disclosure, such as Figure 7 As shown, the computer device includes: one or more processors 10, memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components utilize different buses to communicate with each other and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in the memory or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Equally, multiple computer devices can be connected, and each device provides part of the necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 7 A processor 40 is taken as an example.

[0097] The processor 40 may be a central processing unit (CPU), a network processor (NPU), or a combination thereof. The processor 40 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device (PLD) may be a complex programmable logic device (CPLD), a field programmable gate array (FPGA), a general purpose array logic (GAL), or any combination thereof.

[0098] The memory 50 stores instructions that can be executed by at least one processor 40, so as to enable at least one processor 40 to execute the method shown in the above embodiment.

[0099] The memory 50 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store data created based on the use of the computer device, etc. In addition, the memory 50 may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 50 may optionally include a memory remotely located relative to the processor 40, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0100] The memory 50 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid-state drive; the memory 50 may also include a combination of the above types of memory.

[0101] The computer device further includes a communication interface 60 for the computer device to communicate with other devices or a communication network.

[0102] In this embodiment, a CDN request processing system for an edge node is provided. The system includes: a CDN central node, an edge management node, and an edge cache node. The edge management node and the edge cache node are located in the same CDN edge node. The central node is used to send the full domain name configuration to the edge management node, where the full domain name configuration includes the domain name configuration of all accelerated domain names set in the CDN.

[0103] The edge management node is used to determine a first domain name configuration whose number of visits meets a popularity condition in the full domain name configuration, and determine a target configuration file based on the first domain name configuration.

[0104] The edge cache node is configured to load the target configuration file into the memory, and when the target configuration file does not include the first domain name configuration in the received CDN request, request the edge management node to obtain the first domain name configuration, and process the CDN request based on the first domain name configuration.

[0105] In the embodiment of the present disclosure, the method of performing CDN request processing based on the central node, edge management node and edge cache node is as described above. Figure 1 as well as Figure 3 The corresponding embodiments have been described and will not be repeated here.

[0106] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or implemented as a computer code that can be recorded in a storage medium, or implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and downloaded through a network and will be stored in a local storage medium, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor or hardware, the method shown in the above embodiment is implemented.

[0107] It is understandable that before using the technical solutions disclosed in the various embodiments of this disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved in this disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0108] For example, in response to a user's active request, a prompt message is sent to the user to clearly inform the user that the operation requested will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the electronic device, application, server, storage medium, or other software or hardware that performs the operations of the disclosed technical solution based on the prompt message.

[0109] As an optional but non-limiting implementation, in response to receiving a user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. Furthermore, the pop-up window may also contain a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0110] It is understandable that the above notification and user authorization process are merely illustrative and do not limit the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0111] A portion of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the form in which the computer program instruction exists in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc. Accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium that can be accessed by the computer.

[0112] Although the embodiments of the present disclosure have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the accompanying description.

Claims

1. A CDN request processing method for an edge node, characterized in that: An edge cache node applied to a CDN, the edge cache node being used to perform data interaction with an interactive object, the method comprising: Obtaining a target configuration file sent by an edge management node, wherein the edge management node and the edge cache node are located at the same edge node in the CDN, the edge management node is used to store and manage the full domain name configuration sent by the central node of the CDN, and the target configuration file includes a partial domain name configuration in the full domain name configuration; Obtaining a CDN request, and determining a first domain name configuration in the CDN request; When the target configuration file does not include the first domain name configuration, requesting the edge management node to obtain the first domain name configuration; The first domain name configuration is loaded, and the CDN request is processed based on the first domain name configuration.

2. The method according to claim 1, characterized in that The step of obtaining the target configuration file sent by the edge management node includes: When the edge cache node is started, a first acquisition request is generated, wherein the first acquisition request is used to acquire a target configuration file in the edge management node that contains a partial domain name configuration whose access times meet a heat condition; Obtain a target configuration file fed back by the edge management node in response to the first acquisition request.

3. The method according to claim 1, characterized in that The method further comprises: Determining, in the target configuration file, a second domain name configuration that has not been accessed within a preset historical period; The second domain name configuration in the target configuration file is cleared.

4. A CDN request processing method for an edge node, characterized in that: An edge management node applied to a CDN, wherein the edge management node is used to store and manage the full domain name configuration sent by the central node of the CDN, and the method includes: Detecting a second acquisition request sent by an edge cache node, wherein the edge cache node and the edge management node are located at the same edge node in the CDN, and the edge cache node is used to interact with the interactive object for data; Searching the full domain name configuration for the first domain name configuration indicated by the second acquisition request; In response to the second acquisition request, the first domain name configuration is sent to the edge cache node.

5. The method according to claim 4, characterized in that The method further comprises: Obtaining a first acquisition request sent by the edge cache node, and determining a summary period in the first acquisition request; Aggregating the monitored CDN requests based on the summary period to obtain a first domain name configuration whose access times meet a popularity condition in the full domain name configuration; A target configuration file is determined according to the first domain name configuration, and the target configuration file is sent to the edge cache node in response to the first acquisition request.

6. The method according to claim 4, characterized in that The method further comprises: Based on the first data interface, obtaining the full domain name configuration fed back by the central node of the CDN; Load the full domain name configuration into local memory.

7. The method according to claim 4, characterized in that The method further comprises: Detecting an update event for the full domain name configuration in the central node based on the second data interface to obtain incremental data; The incremental data is obtained based on the third data interface, and the full domain name configuration in the memory is updated according to the incremental data.

8. A CDN request processing device for an edge node, characterized in that: An edge management node applied to a CDN, wherein the edge management node is used to store and manage the full domain name configuration sent by the central node of the CDN, and the device includes: A detection module, configured to detect a second acquisition request sent by an edge cache node, wherein the edge cache node and the edge management node are located at the same edge node in the CDN and are configured to perform data interaction with an interactive object; A search module, configured to search the full domain name configuration for the first domain name configuration indicated by the second acquisition request; A sending module is used to send the first domain name configuration to the edge cache node in response to the second acquisition request.

9. A CDN request processing device for an edge node, characterized in that: An edge cache node applied to a CDN, the edge cache node being used to perform data interaction with an interactive object, the device comprising: A first acquisition module is configured to acquire a target configuration file sent by an edge management node, wherein the edge management node and the edge cache node are located at the same edge node in the CDN, the edge management node is configured to store and manage the full domain name configuration sent by the central node of the CDN, and the target configuration file includes a partial domain name configuration in the full domain name configuration; A determination module, used to obtain a CDN request and determine a first domain name configuration in the CDN request; A second acquisition module, configured to request the edge management node to acquire the first domain name configuration when the target configuration file does not include the first domain name configuration; A processing module is used to load the first domain name configuration and process the CDN request based on the first domain name configuration.

10. A CDN request processing system for an edge node, characterized in that: The system comprises: a central node, an edge management node and an edge cache node of a CDN, wherein the edge management node and the edge cache node are located in the same edge node of the CDN; The central node is used to send the full domain name configuration to the edge management node, wherein the full domain name configuration includes the domain name configuration of all acceleration domain names set in the CDN; The edge management node is used to determine a first domain name configuration whose access times meet a popularity condition in the full domain name configuration, and determine a target configuration file according to the first domain name configuration; The edge cache node is used to load the target configuration file into the memory, and when the target configuration file does not include the first domain name configuration in the received CDN request, request the edge management node to obtain the first domain name configuration, and process the CDN request based on the first domain name configuration.

11. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the CDN request processing method for the edge node according to any one of claims 1 to 7 by executing the computer instructions.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the CDN request processing method for an edge node according to any one of claims 1 to 7.

13. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to enable a computer to execute the CDN request processing method of the edge node according to any one of claims 1 to 7.

Images