Node management method and apparatus, storage medium, device, and program product
Patent Information
- Application Number
- PCT/CN2026/075197
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-02-28
- Filing Date
- 2026-01-27
- Publication Date
- 2026-09-03
Smart Images
Figure CN2026075197_03092026_PF_FP_ABST
Abstract
Description
Node management methods, devices, storage media, equipment and software products
[0001] This application claims priority to Chinese Patent Application No. 202510243474.7, filed on February 28, 2025, entitled “Node Management Method, Apparatus, Storage Medium, Device and Program Product”, the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of computer network technology, specifically to a node management method, apparatus, storage medium, device, and program product. Background Technology
[0003] In modern internet architecture, Content Delivery Networks (CDNs) play a crucial role. By deploying a large number of acceleration nodes globally, they effectively shorten the distance between users and data, thereby significantly improving content loading speed and user experience. The sheer number of CDN nodes is the foundation of its efficient operation; these nodes are widely distributed across various countries and regions, ensuring that users can enjoy fast and stable content access services no matter where they are.
[0004] However, as the scale of CDN networks continues to expand, their complexity also increases. The ability of CDN nodes to process tasks is affected by a variety of factors, including but not limited to current access traffic, the number of requests, network status, and available network bandwidth. These factors work together to cause inconsistent speeds at which CDN nodes consume and refresh tasks, making cache inconsistencies easily occur in the CDN system. Summary of the Invention
[0005] This application provides a node management method, apparatus, storage medium, device, and program product that can monitor the task processing latency of CDN nodes in real time, promptly detect CDN nodes with abnormal progress, and take CDN nodes with abnormal progress offline to ensure cache consistency of all nodes in the CDN system.
[0006] On one hand, embodiments of this application provide a node management method, the method comprising:
[0007] The task processing latency of a CDN node is calculated based on the task processing monitoring cycle. The task processing latency is the current task processing latency of the cache refresh task being processed by the CDN node.
[0008] The working state of the CDN node is controlled according to the task processing delay time, wherein the working state of the CDN node includes online state and offline state, and when it is offline, the task processing delay time of the CDN node exceeds the task processing delay threshold.
[0009] On the other hand, embodiments of this application provide a node management device, the device comprising:
[0010] The calculation unit is used to calculate the task processing latency of the CDN node based on the task processing monitoring cycle, wherein the task processing latency is the task processing latency of the cache refresh task currently being processed by the CDN node.
[0011] A control unit is configured to control the working state of the CDN node based on the task processing delay time, wherein the working state of the CDN node includes an online state and an offline state, and when the CDN node is in an offline state, the task processing delay time exceeds a task processing delay threshold.
[0012] On the other hand, an embodiment of this application provides a computer-readable storage medium storing a computer program adapted for loading by a processor to execute the node management method as described in any of the above embodiments.
[0013] On the other hand, an embodiment of this application provides a computer device, which includes a processor and a memory. The memory stores a computer program, and the processor executes the node management method as described in any of the above embodiments by calling the computer program stored in the memory.
[0014] On the other hand, an embodiment of this application provides a computer program product, including computer instructions, which, when executed by a processor, implement the node management method as described in any of the above embodiments.
[0015] This application embodiment calculates the task processing latency of CDN nodes based on the task processing monitoring cycle. The task processing latency is the latency of the cache refresh task currently being processed by the CDN node. The working state of the CDN node is controlled according to the task processing latency. The working state of the CDN node includes online state and offline state. When the CDN node is offline, the task processing latency exceeds the task processing latency threshold. By monitoring the task processing latency of the CDN node in real time, it is determined whether the CDN node is in an abnormal state. The CDN node with the abnormal task processing latency exceeding the task processing latency threshold is temporarily taken offline (i.e., the working state of the CDN node is controlled to be offline) to avoid accessing old cached content and improve the cache consistency of each node in the CDN system. Attached Figure Description
[0016] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0017] Figure 1 is a system architecture diagram of the node management system provided in an embodiment of this application.
[0018] Figure 2 is a schematic diagram of the first process of the node management method provided in the embodiment of this application.
[0019] Figure 3 is a schematic diagram of the application scenario of the node management method provided in the embodiments of this application.
[0020] Figure 4 is a schematic diagram of the second process of the node management method provided in the embodiment of this application.
[0021] Figure 5 is a schematic diagram of the node management device provided in the embodiment of this application.
[0022] Figure 6 is a schematic diagram of the structure of the computer device provided in an embodiment of this application. Embodiments of the present invention
[0023] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0024] This application provides a node management method, apparatus, storage medium, device, and program product. Exemplarily, the node management method of this application can be executed by a computer device, which can be a terminal or a server. The terminal can be a smartphone, tablet, laptop, desktop computer, smart TV, smart speaker, wearable smart device, personal computer (PC), smart vehicle terminal, etc. The terminal may also include a client, which can be a video client, shopping application client, reading application client, browser client, or instant messaging client, etc. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.
[0025] The embodiments of this application can be applied to scenarios such as cloud technology and Internet content distribution.
[0026] First, some of the nouns or terms that appear in the description of the embodiments of this application are explained as follows:
[0027] CDN: The basic idea of CDN is to bypass bottlenecks and points of failure on the internet that could affect data transmission speed and stability, making content delivery faster and more stable. By placing node servers throughout the network, forming an intelligent virtual network on top of the existing internet infrastructure, the CDN system can redirect user requests to the nearest service node in real time based on comprehensive information such as network traffic, the connectivity and load of each node, and the distance and response time to the user. Its purpose is to allow users to obtain the content they need from the nearest location, alleviating internet congestion and improving website response speed.
[0028] Caching: The process of storing content on CDN nodes to ensure a fast response and delivery of content when requested by a user. CDN nodes store frequently accessed content (such as web pages, images, videos, and files) in their cache. This content can be static, consisting of files that don't change frequently. When a user requests content, the CDN node first checks its cache for the requested content. If it is, the CDN node immediately returns the content to the user, reducing transmission latency. This is called a cache hit. If the requested content is not in the cache, the CDN node sends a request to the origin server and caches the content on the node.
[0029] Cache expiration time: Cache expiration time refers to the duration for which resources from the origin server are cached on CDN nodes. After a preset time, the resource will be marked as expired by the CDN nodes. If the resource requested by the client from the CDN node has expired, the CDN will retrieve the latest resource from the origin server and cache it on the CDN nodes.
[0030] Cache refresh: Cache refresh refers to the process of forcibly updating the content in the CDN cache to the latest version. When the content on the origin server changes, the CDN refresh operation ensures that users receive the latest version when requesting content, rather than retrieving older content from the CDN cache.
[0031] Cache consistency: Cache consistency is a crucial guarantee for CDN performance and reliability. In a distributed CDN system, ensuring that cached content remains consistent across all edge CDN nodes is paramount. This means that regardless of the user's geographical location when accessing the same resource, they should receive the same version of the content. To achieve this, CDN systems typically employ complex synchronization and update mechanisms to maintain cached content consistency.
[0032] Heartbeat Mechanism: A heartbeat mechanism is a communication protocol used to maintain active connections between devices. By periodically sending heartbeat signals to a managing device (such as a server), a managed device (such as a client) can indicate that it is still active. This mechanism helps to promptly detect and handle connection interruptions or failures, thereby ensuring service continuity and stability.
[0033] The solutions provided in this application relate to technologies such as node management in CDN systems, and are specifically illustrated through the following embodiments. Detailed descriptions are provided below. It should be noted that the order of description in the following embodiments is not intended to limit the priority of the embodiments.
[0034] Please refer to Figure 1, which is a system architecture diagram of the node management system provided in this embodiment of the application. This system can implement a node management method. The node management system includes a terminal 10, a CDN control server 20, CDN nodes 30, and a source content server 40, etc. It should be noted that the node management system includes multiple CDN nodes 30. Figure 1 only shows one of the multiple CDN nodes as an example.
[0035] Terminal 10 serves as the entry point for object operations and is controlled by objects with corresponding permissions, such as content management objects and operation and maintenance objects. When the content management object updates the file content in the source content server 40, the content management object will also submit a cache refresh task through the CDN console deployed in terminal 10. The CDN console in terminal 10 will send the cache refresh task to the CDN control server 20.
[0036] On one hand, CDN control server 20 receives cache refresh tasks from terminal 10 and distributes them to each CDN node 30 for processing. Refresh clients on each CDN node 30 receive cache refresh tasks from CDN control server 20 and send them to CDN servers on CDN nodes 30. CDN servers on CDN nodes 30 parse the cache refresh tasks, first perform cache cleanup, then pull the latest file content from source content server 40 and write it into the cache of CDN node 30, thereby updating their own cache content. After receiving an access request from a content consumer, CDN node 30 sends the latest cached content in CDN node 30 to the content consumer, ensuring that the content consumer can quickly obtain the required content.
[0037] On the other hand, the CDN control server 20 also calculates the task processing delay time of each CDN node 30 based on the task processing monitoring cycle. The task processing delay time of the CDN node 30 is the task processing delay time of the cache refresh task currently being processed by the CDN node 30, and controls the working status of each CDN node 30 according to the task processing delay time of each CDN node 30.
[0038] In some embodiments, if it is determined that the task processing delay time of CDN node 30 exceeds a preset task processing delay threshold, then CDN node 30 is designated as an abnormal node. CDN control server 20 can send an offline instruction to the abnormal node to mark the working status of the CDN node 30 as offline, so that the content consumption object does not obtain potentially expired content from the abnormal CDN node 30, thereby improving cache consistency. For CDN nodes 30 that are in the normal operating range, that is, CDN nodes 30 whose task processing delay time does not exceed the task processing delay threshold, CDN control server 20 controls these CDN nodes 30 to be online and continuously sends various cache refresh tasks to them.
[0039] This application provides a node management method, which is illustrated by taking the execution of the node management method by the CDN control server 20 in Figure 1 as an example.
[0040] Please refer to Figures 2 and 3. Figure 2 is a flowchart illustrating the node management method provided in this embodiment, and Figure 3 is an application scenario illustration of the node management method provided in this embodiment. The method may include the following steps 110 to 120:
[0041] Step 110: Calculate the task processing latency of the CDN node based on the task processing monitoring cycle. The task processing latency is the current task processing latency of the cache refresh task being processed by the CDN node.
[0042] The CDN control server calculates the task processing latency of the corresponding CDN node every task processing monitoring period. This CDN node can be any node in the CDN system.
[0043] In some embodiments, calculating the task processing latency of a CDN node based on a task processing monitoring period includes:
[0044] Based on the task processing monitoring cycle, obtain the task submission time when the currently processed cache refresh task is submitted to the CDN control server;
[0045] Calculate the time difference between the current time and the task submission time, and determine the time difference as the task processing delay time.
[0046] In this embodiment, the task processing delay time of a CDN node is the time difference between the task submission time when the cache refresh task currently being processed by the CDN node is submitted to the CDN control server and the current time.
[0047] In CDN systems of related technologies, there is usually an existing control server for routine management and control of CDN nodes, such as node online / offline operation and task distribution. As the scale of the CDN system expands, the task processing capacity of nodes may be affected by various factors, leading to task processing delays or anomalies on some nodes. To address this issue, this application proposes a novel control server specifically designed to monitor and remove CDN nodes with task processing anomalies, ensuring cache consistency within the CDN system.
[0048] It should be noted that the control server in this application can be the same server as the original control server, that is, the original control server adds the function of abnormal node monitoring and removal on the basis of the original functions; or it can be a different server, that is, an independent server specifically used for abnormal node management. The technical solution of this application does not limit the specific implementation of the control server, as long as it can realize the node management function based on task processing delay time.
[0049] In some embodiments, as shown in Figure 3, the CDN control server is equipped with a heartbeat module based on a heartbeat mechanism, which can calculate the task processing latency of CDN nodes based on the task processing monitoring cycle.
[0050] Specifically, the heartbeat module in the CDN control server can send a request to the CDN node according to a preset task processing monitoring cycle to obtain relevant information about the cache refresh task that the CDN node is currently processing. After receiving the request, the CDN node feeds back the task identifier of the cache refresh task that is currently processing to the heartbeat module in the CDN control server so that the heartbeat module can calculate the task processing latency of the CDN node.
[0051] In some embodiments, the CDN controller server stores a correspondence table between the task identifier of each cache refresh task and the task submission time when the cache refresh task is submitted to the CDN controller server. After the CDN controller server obtains the task identifier of the cache refresh task currently being processed by the CDN node, it can determine the task submission time corresponding to the task identifier from the correspondence table, and then calculate the difference between the time and the current time to obtain the task processing delay time of the CDN node.
[0052] In some embodiments, a refresh task queue is set in the CDN controller server. The refresh task queue includes a preset number of newly received cache refresh tasks. When the relevant content management object submits a cache refresh task, different cache refresh tasks are continuously written to the refresh task queue through the access layer. The task identifier of the cache refresh task can be set by the access layer when writing the cache refresh task to the refresh task queue, and is used to uniquely indicate the cache refresh task. For example, the task identifier of the cache refresh task can be an auto-incrementing ID.
[0053] In some embodiments, the time when the cache refresh task is written to the refresh task queue is taken as the task submission time when the cache refresh task is submitted to the CDN control server.
[0054] Step 120: Control the working status of CDN nodes based on task processing delay time. The working status of CDN nodes includes online status and offline status. When the CDN node is in offline status, the task processing delay time exceeds the task processing delay threshold.
[0055] The CDN control server controls the working status of CDN nodes based on the task processing delay time of the CDN nodes.
[0056] Specifically, the task processing latency of a CDN node reflects the lag in task processing. If the task processing latency of a CDN node exceeds the task processing latency threshold, it can be assumed that the refresh task following the currently processing cache refresh task in the CDN node has not been executed. This means that the file cache cleanup operation of this CDN node is ineffective across the entire network. In order to ensure the cache consistency of the CDN system, it may be necessary to temporarily take the task processing latency exceeding the task processing latency threshold offline to prevent users from requesting the CDN node and accessing the old file cache.
[0057] In some embodiments, the task processing latency threshold is determined based on at least one of the following: the service type of the CDN node service, the file directory to which the CDN node's cache refresh task belongs, and the URL type corresponding to the CDN node's cache refresh task.
[0058] Specifically, different businesses have different requirements for real-time performance and data consistency. Therefore, task processing latency thresholds can be set according to the business type served by the CDN node. For example, in e-commerce, data such as product details pages, pricing information, and inventory status must be updated in real time. Therefore, the task processing latency threshold for CDN nodes serving e-commerce needs to be set relatively low, perhaps only a few seconds to tens of seconds, to ensure that users can obtain the latest product information as soon as possible. On the other hand, for news and information businesses, although news also pursues timeliness, a slight delay is acceptable compared to real-time transaction data in e-commerce. The task processing latency threshold can be set higher, such as tens of seconds to several minutes.
[0059] In some embodiments, the method further includes:
[0060] If the file directory to which the cache refresh task of the CDN node belongs is the first file directory, set the task processing delay threshold to the first threshold.
[0061] If the file directory to which the cache refresh task of the CDN node belongs is the second file directory, the task processing delay threshold is set to the second threshold, wherein the update frequency of the first file directory is higher than that of the second file directory, and the first threshold is less than the second threshold.
[0062] Specifically, for the file directories to which cache refresh tasks belong, the importance and update frequency of files in different directories may vary. Therefore, the task processing latency threshold can be set based on the file directories to which the CDN node's cache refresh tasks belong. For example, the core file directory of a website's homepage (the first file directory) usually contains key files that guide user browsing paths and showcase the brand image, such as homepage images and popular recommendation content. These files are updated frequently, and once updated, they need to be quickly pushed to users. The corresponding CDN node's task processing latency threshold, i.e., the first threshold, needs to be set relatively low to ensure fast synchronization across the entire network. On the other hand, some file directories that store historical documents and supplementary materials (the second file directory) have a low update frequency. That is, the update frequency of the first file directory is higher than that of the second file directory, which has less impact on the user's immediate experience. Therefore, the corresponding CDN node's task processing latency threshold, i.e., the second threshold, can be set relatively high to reduce frequent system monitoring and excessive resource investment.
[0063] In some embodiments, the method further includes:
[0064] If the URL type corresponding to the cache refresh task of the CDN node is a dynamic URL, set the task processing delay threshold to the third threshold.
[0065] If the URL type corresponding to the cache refresh task of the CDN node is a static URL, the task processing delay threshold is set to the fourth threshold, where the third threshold is less than the fourth threshold.
[0066] Specifically, for the URL type corresponding to the cache refresh task, different types of URLs may have different importance and update frequencies. Therefore, a task processing delay threshold can be set for the URL type corresponding to the cache refresh task. For example, if the URL type corresponding to the cache refresh task of the CDN node is a dynamic URL, these dynamic URLs are often associated with real-time data driven by the database, such as e-commerce order query pages and social media dynamic push pages. The content of these pages changes frequently with user operations and backend data updates. In this case, the task processing delay threshold can be set to the third threshold. The third threshold needs to be set relatively small to respond quickly to changes. If the URL type corresponding to the cache refresh task of the CDN node is a static URL, these static URLs point to relatively fixed resources, such as website-wide style sheets and fixed brand promotional videos, with long update cycles. In this case, the task processing delay threshold can be set to the fourth threshold. This fourth threshold is set relatively leniently (i.e., with a larger value) to avoid excessively strict checks consuming unnecessary system resources, while maintaining the overall efficient operation of the CDN system. Therefore, in this embodiment, the third threshold is smaller than the fourth threshold.
[0067] In some embodiments, controlling the working state of CDN nodes based on task processing delay time may include the following steps 1201 to 1202:
[0068] Step 1201: If the task processing delay time exceeds the task processing delay threshold, obtain the number of offline nodes in the CDN system. The number of offline nodes is the number of CDN nodes that are currently offline in the CDN system.
[0069] If it is determined that the task processing delay time of a CDN node exceeds the task processing delay threshold, the CDN control server obtains the number of CDN nodes in the CDN system that are offline, and uses this number as the offline node count of the CDN system.
[0070] Step 1202: If the number of offline nodes is not greater than the node removal threshold, control the working status of the CDN nodes to be offline.
[0071] If it is determined that the number of CDN nodes currently in an offline state is not greater than the node removal threshold, then the working state of the CDN nodes is controlled to be offline to prevent users from making requests to that CDN node and thus accessing the old file cache.
[0072] In some embodiments, the node management method may further include step 1203:
[0073] Step 1203: If the number of offline nodes is greater than the node removal threshold, keep the CDN nodes in the online state.
[0074] Specifically, considering that special scenarios such as data center cutovers and carrier link anomalies can lead to significant delays in CDN node task processing, simply putting all lagging CDN nodes offline could easily result in an insufficient number of normally functioning CDN nodes in the system, causing CDN service disruptions. Therefore, a node removal threshold can be set; once the number of offline nodes exceeds this threshold, further removal of that CDN node is prohibited.
[0075] The specific value of the node removal threshold should be reasonably set according to the actual application scenario, and this application does not impose any restrictions on it.
[0076] In some embodiments, the node management method may further include the following step 1204:
[0077] Step 1204: If the number of offline nodes is greater than the node removal threshold, issue an alarm message to indicate that the number of offline nodes exceeds the node removal threshold.
[0078] If the number of offline nodes in the CDN system is determined to be greater than the node removal threshold, the CDN control server will issue an alarm message to indicate that the number of offline nodes exceeds the node removal threshold, thus reminding relevant operations and maintenance personnel to intervene.
[0079] In some embodiments, after controlling the working state of the CDN node to be offline, the node management method may further include the following steps 1205 to 1206:
[0080] Step 1205: Continuously calculate the task processing latency of CDN nodes based on the task processing monitoring cycle;
[0081] Step 1206: If the task processing delay time does not exceed the task processing delay threshold, control the working status of the CDN node to change from offline to online.
[0082] Specifically, CDN nodes in offline mode are still fetching cache refresh tasks and processing them. The CDN control server will continuously monitor the task processing status of CDN nodes in offline mode. If it finds that the task processing delay time of the CDN node does not exceed the task processing delay threshold, it means that the CDN node has recovered to the normal task processing status. Therefore, the CDN control server can re-add the CDN node to the service, that is, control the working status of the CDN node from offline to online.
[0083] In some embodiments, as shown in FIG3, the CDN control server further includes a health center. After the heartbeat module determines the task processing status of the CDN node by calculating the task processing delay time of the CDN node, it sends the working status adjustment information of the CDN node to the health center, so that the CDN control server can control the working status of the CDN node through the health center according to the working status adjustment information of the CDN node.
[0084] In this embodiment, the health center is a core component of the CDN system used for unified management of node online / offline status. The health center is responsible for maintaining the status information of all CDN nodes and provides standardized interfaces for other system components to call. Specifically, the health center can dynamically adjust the online / offline status of nodes based on their task processing latency, ensuring the stability and cache consistency of the CDN system. The control server interacts with the health center through its interface to manage nodes with abnormal task processing.
[0085] For example, when the control server detects that the task processing latency of a CDN node exceeds a preset threshold, it will call the health center's interface to mark the node as abnormal and trigger a shutdown operation. By centrally managing node online and offline status through the health center, cache inconsistency issues caused by node abnormalities can be effectively avoided, while ensuring the overall stability of the CDN system.
[0086] In some embodiments, controlling the working state of a CDN node to change from offline to online includes:
[0087] If the task processing delay exceeds the task retention time threshold of the CDN control server, the working status of the CDN node will be changed from offline to online after the cached content of the CDN node is cleared. The task retention time threshold is the time range of all cache refresh tasks that the CDN control server can accommodate.
[0088] In some embodiments, the step of determining the task retention time threshold includes:
[0089] The task retention time threshold is determined based on the storage capacity of the refresh task queue and the generation speed of cache refresh tasks.
[0090] Specifically, the task retention time threshold can be set based on the storage capacity of the refresh task queue on the control server and the generation rate of refresh tasks. For example, if the refresh task queue on the control server can store refresh tasks within a maximum of one hour, then the task retention time threshold is one hour.
[0091] If the task processing delay of a CDN node exceeds the task retention time threshold, it means that the CDN node may have missed some cache refresh tasks, resulting in incomplete or expired cached content. Therefore, the CDN control server will first clean up the cached content of the CDN node to ensure that its cache is consistent with the content of the origin server. After the cleanup is completed, the CDN control server will change the working status of the CDN node from offline to online, so that it can rejoin the CDN system to provide services.
[0092] Specifically, in a CDN system, the task processing latency of a CDN node reflects its speed in processing cache refresh tasks. When the task processing latency of a node exceeds a preset threshold, the node is marked as abnormal and taken offline to prevent users from accessing expired cached content. However, when the node's task processing latency returns to normal, the node needs to come back online. Before going back online, it is essential to ensure that the node's cached content is up-to-date to avoid cache inconsistency issues. Since the number of cache refresh tasks that a CDN control server can store is limited—only tasks within a certain time range (i.e., the task retention time threshold)—some cache refresh tasks will be discarded due to disk rolling. If a node's task processing latency exceeds this time range, it means that the node may have missed some cache refresh tasks, resulting in incomplete or expired cached content, thus providing incorrect or outdated content and failing to guarantee cache consistency within the CDN system. Therefore, when bringing the CDN node back online, it is not allowed to add it directly to the production network. The cached content of the CDN node needs to be cleared before it can be added back to the production environment. In other words, the working status of the CDN node should be controlled to be online to ensure that its cache is consistent with the content of the origin server.
[0093] This embodiment can ensure the stable and reliable operation of the CDN system.
[0094] In some embodiments, the node management method may further include the following steps 130 to 150:
[0095] Step 130: In response to the cache refresh request sent by the CDN node, obtain the cache refresh progress information corresponding to the CDN node. The cache refresh progress information includes the latest successfully executed cache refresh task. The cache refresh request is triggered by the CDN node based on the cache refresh request period.
[0096] The cache refresh agent in the CDN node sends a cache refresh request to the CDN control server according to the cache refresh request period. The cache refresh request includes the node IP address of the CDN node and the execution status of the cache refresh task currently being processed. The cache refresh request is used to request new cache refresh tasks. In response to the cache refresh request sent by the CDN node, the CDN control server will first obtain the cache refresh progress information corresponding to the CDN node. The cache refresh progress information includes the latest successfully executed cache refresh task.
[0097] Step 140: If it is determined that the cache refresh task currently being processed by the CDN node has been successfully executed, update the latest successfully executed cache refresh task of the CDN node to the cache refresh task currently being processed.
[0098] If it is determined that the cache refresh task currently being processed by the CDN node has been successfully executed, the CDN control server will update the latest successfully executed cache refresh task of the CDN node to the cache refresh task currently being processed.
[0099] In some embodiments, the cache refresh request includes an acknowledgment bit identifier, which is used to indicate the execution status of the cache refresh task currently being processed by the CDN node. The steps by which the CDN control server determines whether the cache refresh task currently being processed by the CDN node has been successfully executed include:
[0100] The CDN control server determines whether the cache refresh task currently being processed by the CDN node has been successfully executed based on the response bit flag in the cache refresh request.
[0101] In some embodiments, the CDN control server maintains task processing progress information for each CDN node in the CDN system. The task processing progress information specifically includes the latest successfully executed cache refresh task for each CDN node. As cache refresh tasks are successfully executed continuously, the latest successfully executed cache refresh task for each CDN node is continuously updated.
[0102] Step 150: Send the cache refresh task that has not yet been sent to the CDN node from the CDN control server to the CDN node.
[0103] In some embodiments, the step of obtaining cache refresh tasks that have not yet been sent to CDN nodes locally on the CDN control server includes: obtaining cache refresh tasks that have not yet been sent to CDN nodes from the refresh task queue.
[0104] In this embodiment, by recording the task processing progress of CDN nodes and distributing different cache refresh tasks to CDN nodes according to their different task processing progress, CDN nodes can process and update cached content as quickly as possible, thereby improving the response speed and user experience of the CDN system. It can also ensure the complete execution of the corresponding cache refresh tasks of CDN nodes and avoid inconsistencies in cached content caused by task failures.
[0105] In some embodiments, the node management method may further include the following step 160:
[0106] Step 160: If it is determined that the cache refresh task currently being processed by the CDN node has not yet been successfully executed, the cache refresh task currently being processed is resent to the CDN node.
[0107] By querying the task processing progress information of the CDN nodes maintained locally by the CDN control server, if it is determined that the cache refresh task currently being processed by the CDN node has not yet been successfully executed, the CDN control server will resend the cache refresh task currently being processed by the CDN node to the CDN node for processing.
[0108] In this embodiment, by resending the unsuccessful cache refresh task to the CDN node, the reliability of task execution can be improved, ensuring that the cached content in the CDN system is always up-to-date and accurate.
[0109] In some embodiments, if it is determined that the cache refresh task currently being processed by the CDN node has not yet been successfully executed, the node management method may further include the following step 170:
[0110] Step 170: Send all cache refresh tasks following the currently processed cache refresh task of the CDN node stored locally on the CDN control server to the CDN node.
[0111] If it is determined that the cache refresh task currently being processed by the CDN node has not yet been successfully executed, the CDN control server will send all cache refresh tasks after the currently processed cache refresh task stored in the local refresh task queue to the CDN node.
[0112] To better illustrate the node management method provided in this application embodiment, please refer to Figure 4. The flow of the node management method provided in this application embodiment can be summarized as follows:
[0113] Step 401: In response to the cache refresh request sent by the CDN node, obtain the cache refresh progress information corresponding to the CDN node based on the cache refresh request period;
[0114] Step 402: Determine whether the cache refresh task currently being processed by the CDN node has been successfully executed based on the cache refresh progress information corresponding to the CDN node. If yes, proceed to step 403; otherwise, proceed to step 404.
[0115] Step 403: Update the latest successfully executed cache refresh task on the CDN node with the currently processed cache refresh task, and send the cache refresh tasks that have not yet been sent to the CDN node from the CDN control server to the CDN node.
[0116] Step 404: Resend the currently processing cache refresh task and all cache refresh tasks following the currently processing cache refresh task to the CDN node.
[0117] Step 405: Calculate the task processing latency of the CDN node based on the task processing monitoring cycle;
[0118] Step 406: Determine whether the task processing delay time of the CDN node exceeds the task processing delay threshold, and determine whether the CDN node is offline. If the task processing delay time of the CDN node exceeds the task processing delay threshold, and the CDN node is not offline, proceed to step 407. If the task processing delay time of the CDN node does not exceed the task processing delay threshold, and the CDN node is offline, proceed to step 4010.
[0119] Step 407: Determine whether the number of offline nodes in the CDN system is not greater than the node removal threshold. If yes, proceed to step 408; otherwise, proceed to step 409.
[0120] Step 408: Change the working status of the CDN node from online to offline.
[0121] Step 409: Keep the CDN node in an online state and issue an alarm message indicating that the number of offline nodes in the CDN system exceeds the node removal threshold.
[0122] Step 4010: If the task processing delay of the CDN node exceeds the task retention time threshold of the CDN control server, after clearing the cached content of the CDN node, control the working status of the CDN node to change from offline to online; if the task processing delay of the CDN node does not exceed the task retention time threshold of the CDN control server, directly control the working status of the CDN node to change from offline to online.
[0123] All of the above technical solutions can be combined in any way to form optional embodiments of this application, and will not be described in detail here.
[0124] This application embodiment calculates the task processing latency of CDN nodes based on the task processing monitoring cycle. The task processing latency is the latency of the cache refresh task currently being processed by the CDN node. The working state of the CDN node is controlled according to the task processing latency. The working state of the CDN node includes online state and offline state. When the CDN node is offline, the task processing latency exceeds the task processing latency threshold. By monitoring the task processing latency of the CDN node in real time, it is determined whether the CDN node is in an abnormal state. The CDN node with the abnormal task processing latency exceeding the task processing latency threshold is temporarily taken offline (i.e., the working state of the CDN node is controlled to be offline) to avoid accessing old cached content and improve the cache consistency of each node in the CDN system.
[0125] To facilitate better implementation of the node management method of this application embodiment, this application embodiment also provides a node management device. Please refer to FIG5, which is a schematic diagram of the structure of the node management device provided in this application embodiment. The node management device 500 may include:
[0126] The calculation unit 510 is used to calculate the task processing delay time of the CDN node based on the task processing monitoring cycle. The task processing delay time is the task processing delay time of the cache refresh task currently being processed by the CDN node.
[0127] The control unit 520 is used to control the working state of the CDN node based on the task processing delay time. The working state of the CDN node includes online state and offline state. When the CDN node is in offline state, the task processing delay time exceeds the task processing delay threshold.
[0128] In some embodiments, when the control unit 520 controls the working state of the CDN node based on the task processing delay time, it is specifically used for:
[0129] If the task processing delay time exceeds the task processing delay threshold, obtain the number of offline nodes in the CDN system. The number of offline nodes is the number of CDN nodes that are currently offline in the CDN system.
[0130] If the number of offline nodes is not greater than the node removal threshold, the working status of the CDN nodes is controlled to be offline.
[0131] In some embodiments, the control unit 520 is further configured to:
[0132] If the number of offline nodes exceeds the node removal threshold, keep the CDN nodes in an online state.
[0133] In some embodiments, the control unit 520 is further configured to:
[0134] If the number of offline nodes exceeds the node removal threshold, an alarm message is issued to indicate that the number of offline nodes exceeds the node removal threshold.
[0135] In some embodiments, after controlling the CDN node to operate in an offline state, the control unit 520 is further configured to:
[0136] Calculate the task processing latency of CDN nodes based on the task processing monitoring cycle;
[0137] If the task processing delay time does not exceed the task processing delay threshold, the working status of the CDN node will be changed from offline to online.
[0138] In some embodiments, when the control unit 520 controls the working state of the CDN node to change from offline to online, it is specifically used for:
[0139] If the task processing delay exceeds the task retention time threshold of the CDN control server, the working status of the CDN node will be changed from offline to online after the cached content of the CDN node is cleared. The task retention time threshold is the time range of all cache refresh tasks that the CDN control server can accommodate.
[0140] In some embodiments, the apparatus is further configured to determine a task retention time threshold, specifically for:
[0141] The task retention time threshold is determined based on the storage capacity of the refresh task queue and the generation speed of cache refresh tasks.
[0142] In some embodiments, the apparatus is further configured to:
[0143] In response to a cache refresh request sent by a CDN node, obtain the cache refresh progress information corresponding to the CDN node. The cache refresh progress information includes the cache refresh task currently being processed and the latest successfully executed cache refresh task. The cache refresh request is triggered by the CDN node based on the cache refresh request period.
[0144] If it is determined that the cache refresh task currently being processed by the CDN node has been successfully executed, the latest successfully executed cache refresh task of the CDN node will be updated to the cache refresh task currently being processed.
[0145] Send cache refresh tasks that have not yet been sent to CDN nodes from the CDN control server to the CDN nodes.
[0146] In some embodiments, the device is further configured to:
[0147] If it is determined that the cache refresh task currently being processed by the CDN node has not yet been successfully executed, the cache refresh task currently being processed will be resent to the CDN node.
[0148] In some embodiments, if it is determined that the cache refresh task currently being processed by the CDN node has not yet been successfully executed, the apparatus is further configured to:
[0149] Send all cache refresh tasks after the currently processing cache refresh task of the CDN node stored locally on the CDN control server to the CDN node.
[0150] In some embodiments, the task processing latency threshold is determined based on at least one of the following: the service type of the CDN node service, the file directory to which the CDN node's cache refresh task belongs, and the URL type corresponding to the CDN node's cache refresh task.
[0151] In some embodiments, the device is further configured to:
[0152] If the file directory to which the cache refresh task of the CDN node belongs is the first file directory, set the task processing delay threshold to the first threshold.
[0153] If the file directory to which the cache refresh task of the CDN node belongs is the second file directory, the task processing delay threshold is set to the second threshold, wherein the update frequency of the first file directory is higher than that of the second file directory, and the first threshold is less than the second threshold.
[0154] In some embodiments, the device is further configured to:
[0155] If the URL type corresponding to the cache refresh task of the CDN node is a dynamic URL, set the task processing delay threshold to the third threshold.
[0156] If the URL type corresponding to the cache refresh task of the CDN node is a static URL, the task processing delay threshold is set to the fourth threshold, where the third threshold is less than the fourth threshold.
[0157] In some embodiments, the cache refresh request includes an acknowledgment bit identifier, which is used to indicate the execution status of the cache refresh task currently being processed by the CDN node. When determining whether the cache refresh task currently being processed by the CDN node has been successfully executed, the device is specifically used for:
[0158] The response bit flag in the cache refresh request determines whether the cache refresh task currently being processed by the CDN node has been successfully executed.
[0159] In some embodiments, the CDN control server is provided with a refresh task queue, which includes a preset number of recently received cache refresh tasks. When the device is used to obtain cache refresh tasks that have not yet been sent to the CDN nodes locally by the CDN control server, it is specifically used for:
[0160] Retrieve cache refresh tasks from the refresh task queue that have not yet been sent to CDN nodes.
[0161] In some embodiments, when the device is used to calculate the task processing latency of a CDN node based on a task processing monitoring period, it is specifically used for:
[0162] Based on the task processing monitoring cycle, obtain the task submission time when the currently processed cache refresh task is submitted to the CDN control server;
[0163] Calculate the time difference between the current time and the task submission time, and determine the time difference as the task processing delay time.
[0164] It should be noted that the functions of each module in the node management device 500 in this application embodiment can be referred to the specific implementation of any embodiment in the above method embodiments, and will not be repeated here.
[0165] Each unit in the above-described device can be implemented entirely or partially through software, hardware, or a combination thereof. Each unit can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each unit.
[0166] For example, the node management device 500 can be integrated into a terminal or server that has storage and a processor and thus computing power, or the node management device 500 can be the terminal or server.
[0167] In some embodiments, this application also provides a computer device including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.
[0168] Figure 6 is a schematic structural diagram of a computer device provided in an embodiment of this application. As shown in Figure 6, the computer device 600 may include: a communication interface 601, a memory 602, a processor 603, and a communication bus 604. The communication interface 601, the memory 602, and the processor 603 communicate with each other through the communication bus 604. The communication interface 601 is used for data communication between the device 600 and external devices. The memory 602 can be used to store software programs and modules, and the processor 603 runs the software programs and modules stored in the memory 602, such as the software programs for the corresponding operations in the aforementioned method embodiments.
[0169] In some embodiments, the processor 603 may invoke software programs and modules stored in the memory 602 to perform the following operations: calculate the task processing latency of the CDN node based on the task processing monitoring cycle, wherein the task processing latency is the task processing latency of the cache refresh task currently being processed by the CDN node; control the working state of the CDN node according to the task processing latency, wherein the working state of the CDN node includes online state and offline state, and when it is in offline state, the task processing latency of the CDN node exceeds the task processing latency threshold.
[0170] In some embodiments, the computer device 600 may be integrated into a terminal or server that has storage and a processor, thus possessing computing capabilities; or the computer device 600 may be the terminal or server. The terminal may be a smartphone, tablet, laptop, smart TV, smart speaker, wearable smart device, personal computer, or other similar device. The server may be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.
[0171] This application also provides a computer-readable storage medium for storing a computer program. This computer-readable storage medium can be applied to a computer device, and the computer program causes the computer device to execute the corresponding processes in the methods described above in the embodiments of this application; for brevity, further details are omitted here.
[0172] This application also provides a computer program product including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the corresponding processes in the methods described above in the embodiments of this application. For brevity, these details will not be elaborated further here.
[0173] This application also provides a computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the corresponding processes in the methods described above in the embodiments of this application. For brevity, these details will not be elaborated further here.
[0174] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.
[0175] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0176] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0177] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0178] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0179] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.
[0180] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0181] In addition, the functional units in the embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0182] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer or a server) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.
[0183] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A node management method, characterized in that, A CDN control server applied in a content delivery network (CDN) system, the method comprising: The task processing latency of a CDN node is calculated based on the task processing monitoring cycle. The task processing latency is the current task processing latency of the cache refresh task being processed by the CDN node. The working state of the CDN node is controlled according to the task processing delay time, wherein the working state of the CDN node includes online state and offline state, and when it is offline, the task processing delay time of the CDN node exceeds the task processing delay threshold.
2. The node management method as described in claim 1, characterized in that, Controlling the working status of the CDN node based on the task processing delay time includes: If the task processing delay time exceeds the task processing delay threshold, obtain the number of offline nodes in the CDN system, where the number of offline nodes is the number of CDN nodes currently offline in the CDN system. If the number of offline nodes is not greater than the node removal threshold, the working state of the CDN node is controlled to be offline.
3. The node management method as described in claim 2, characterized in that, The method further includes: If the number of offline nodes is greater than the node removal threshold, the CDN node is kept in an online state.
4. The node management method as described in claim 2, characterized in that, The method further includes: If the number of offline nodes is greater than the node removal threshold, an alarm message is issued to indicate that the number of offline nodes exceeds the node removal threshold.
5. The node management method as described in claim 2, characterized in that, After controlling the CDN node to operate in an offline state, the method further includes: The task processing delay time of the CDN node is calculated based on the task processing monitoring cycle. If the task processing delay time does not exceed the task processing delay threshold, the working status of the CDN node is controlled to change from offline to online.
6. The node management method as described in claim 5, characterized in that, Controlling the working state of the CDN node from offline to online includes: If the task processing delay exceeds the task retention time threshold of the CDN control server, after clearing the cached content of the CDN node, the working status of the CDN node is controlled to change from offline to online. The task retention time threshold is the time range of all cache refresh tasks accommodated by the CDN control server.
7. The node management method as described in claim 6, characterized in that, The steps for determining the task retention time threshold include: The task retention time threshold is determined based on the storage capacity of the refresh task queue and the generation speed of the cache refresh task.
8. The node management method as described in claim 1, characterized in that, The method further includes: In response to a cache refresh request sent by the CDN node, cache refresh progress information corresponding to the CDN node is obtained. The cache refresh progress information includes the latest successfully executed cache refresh task. The cache refresh request is triggered by the CDN node based on a cache refresh request cycle. If it is determined that the cache refresh task currently being processed by the CDN node has been successfully executed, the latest successfully executed cache refresh task of the CDN node is updated to the cache refresh task currently being processed; Send cache refresh tasks that have not yet been sent locally to the CDN node from the CDN control server to the CDN node.
9. The node management method as described in claim 8, characterized in that, The method further includes: If it is determined that the cache refresh task currently being processed by the CDN node has not yet been successfully executed, the cache refresh task currently being processed will be resent to the CDN node.
10. The node management method as described in claim 9, characterized in that, If it is determined that the cache refresh task currently being processed by the CDN node has not yet been successfully executed, the method further includes: The CDN control server sends all cache refresh tasks, after the currently processing cache refresh task of the CDN node, stored locally on the CDN node, to the CDN node.
11. The node management method as described in claim 1, characterized in that, The task processing latency threshold is determined based on at least one of the following: the service type of the CDN node service, the file directory to which the cache refresh task of the CDN node belongs, and the URL type corresponding to the cache refresh task of the CDN node.
12. The node management method as described in claim 11, characterized in that, The method further includes: If the file directory to which the cache refresh task of the CDN node belongs is the first file directory, the task processing delay threshold is set to the first threshold. If the file directory to which the cache refresh task of the CDN node belongs is the second file directory, the task processing delay threshold is set to the second threshold, wherein the update frequency of the first file directory is higher than the update frequency of the second file directory, and the first threshold is less than the second threshold.
13. The node management method as described in claim 11, characterized in that, The method further includes: If the URL type corresponding to the cache refresh task of the CDN node is a dynamic URL, the task processing delay threshold is set to the third threshold. If the URL type corresponding to the cache refresh task of the CDN node is a static URL, the task processing delay threshold is set to the fourth threshold, wherein the third threshold is less than the fourth threshold.
14. The node management method as described in claim 8, characterized in that, The cache refresh request includes a response bit identifier, which is used to indicate the execution status of the cache refresh task currently being processed by the CDN node. The step of determining whether the cache refresh task currently being processed by the CDN node has been successfully executed includes: The response bit identifier in the cache refresh request determines whether the cache refresh task currently being processed by the CDN node has been successfully executed.
15. The node management method as described in claim 8, characterized in that, The CDN control server is equipped with a refresh task queue, which includes a preset number of recently received cache refresh tasks. The step of obtaining cache refresh tasks that the CDN control server has not yet sent to the CDN node includes: Retrieve cache refresh tasks that have not yet been sent to the CDN node from the refresh task queue.
16. The node management method as described in claim 1, characterized in that, The calculation of CDN node task processing latency based on task processing monitoring cycle includes: Based on the task processing monitoring cycle, the task submission time when the currently processed cache refresh task is submitted to the CDN control server is obtained; Calculate the time difference between the current time and the task submission time, and determine the time difference as the task processing delay time.
17. A node management device, characterized in that, The device includes: The calculation unit is used to calculate the task processing latency of the CDN node based on the task processing monitoring cycle, wherein the task processing latency is the task processing latency of the cache refresh task currently being processed by the CDN node. A control unit is configured to control the working state of the CDN node based on the task processing delay time, wherein the working state of the CDN node includes an online state and an offline state, and when the CDN node is in an offline state, the task processing delay time exceeds a task processing delay threshold.
18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted for loading by a processor to perform the node management method as described in any one of claims 1-16.
19. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing a computer program, and the processor executing the node management method as described in any one of claims 1-16 by calling the computer program stored in the memory.
20. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the node management method according to any one of claims 1-16.