Network node management method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of wireless communication, in particular to a distributed network node management method, device and system. The method comprises the following steps: sending a node information request to a network node; receiving node information fed back by the network node; wherein the node information comprises a node service state. The network control center can obtain the current node service state fed back by each network node by sending a node information request to the network nodes; for the network control center, based on different node service states, the network control center can conveniently manage the network nodes in different service states in time, so that the waste of network resources is reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a network node management method, device, electronic device and storage medium, and computer program product. Background Art

[0002] 6G (sixth-generation mobile communication technology) networks are trending toward distributed network architectures. Current mechanisms for distributed network architectures only address the design and generation of distributed network nodes. In a distributed network architecture, unused distributed nodes, distributed nodes that have not been used for a long time, or distributed nodes that have not been removed can lead to redundant and wasted network resources. Summary of the Invention

[0003] Based on this, it is necessary to provide a network node management method to address the above technical issues, which can achieve timely management of the service status and survival status of network nodes and reduce the waste of network resources.

[0004] In a first aspect, the present application provides a distributed network node management method, applied to a network control center, the method comprising:

[0005] Sending node information request to network nodes;

[0006] Receive node information fed back by the network node; wherein the node information includes node service status.

[0007] In one embodiment, the method further comprises:

[0008] When the node service state of the network node is an unservice state, a node status timing task is configured for the network node, so as to update the node status information of the network node according to the execution result of the node status timing task.

[0009] In one embodiment, updating the node status information of the node to be processed according to the execution result of the node status scheduled task includes:

[0010] When the node status timing task is not completed, the node service status of the standby network node is configured as an in-service state, and the node status timing task is deleted.

[0011] In one embodiment, updating the node status information of the node to be processed according to the execution result of the node status scheduled task includes:

[0012] When the node status timing task is completed, the node status of the node to be processed is configured as a long-term out-of-service state;

[0013] A node deletion instruction is sent to the network node to delete the network node.

[0014] In one embodiment, the method further comprises:

[0015] Obtaining first node information corresponding to a first network node, and comparing the first node information with second node information corresponding to other network nodes;

[0016] A redundant node is determined according to the node information comparison result, and a node deletion instruction is sent to the redundant node to delete the redundant node.

[0017] In one embodiment, determining the redundant node according to the node information comparison result includes:

[0018] When the first node information is the same as the second node information, determining that the first network node or the second network node is the redundant node; or

[0019] When the first node information includes the second node information, the second network node is determined to be the redundant node.

[0020] In one embodiment, the node information of the network nodes is synchronized to a central node.

[0021] In one embodiment, the central node includes the network control center.

[0022] In one embodiment, the node service status includes any one of: an in-service status, an out-of-service status, and a long-term out-of-service status.

[0023] In one embodiment, the method further comprises:

[0024] In response to a network node creation request, a service period timing task is configured for the network node, so as to configure the node state of the network node to be an unserviced state when the service period timing task ends.

[0025] In a second aspect, the present application provides a distributed network node management device, which is applied to a network control center. The device includes:

[0026] A request sending module, used for sending a node information request to a network node;

[0027] The node information receiving module is used to receive the node information fed back by the network node; wherein the node information includes the node service status.

[0028] In one embodiment, the apparatus further comprises:

[0029] a node information comparison module, configured to obtain first node information corresponding to a first network node, and compare the first node information with second node information corresponding to other network nodes;

[0030] The redundant node calculation module is used to determine the redundant node according to the node information comparison result, and send a node deletion instruction to the redundant node to delete the redundant node.

[0031] In one embodiment, the apparatus further comprises:

[0032] The node status timing task configuration module is used to configure a node status timing task for the network node when the node service status of the network node is an unserviced state, so as to update the node status information of the network node according to the execution result of the node status timing task.

[0033] In one embodiment, the apparatus further comprises:

[0034] The service period timing task configuration module is used to configure a service period timing task for the network node in response to a network node creation request, so as to configure the node state of the network node to be an unserviced state when the service period timing task ends.

[0035] In a third aspect, the present application further provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method in any embodiment of the first aspect.

[0036] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method in any one of the embodiments of the first aspect.

[0037] In a fifth aspect, the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the method in any one of the embodiments of the first aspect.

[0038] In a sixth aspect, the present application provides a distributed network node management method, applied to a distributed network node, the method comprising:

[0039] Receive node information request sent by the network control center;

[0040] Sending node information to the network control center; wherein the node information includes node service status.

[0041] In one embodiment, the method further comprises:

[0042] Get node status scheduled task;

[0043] The node service status is updated according to the execution result of the node status timing task.

[0044] In one embodiment, updating the node service status according to the execution result of the node status scheduled task includes:

[0045] When the node status timer task is not completed, configuring the node service status to be in service and deleting the node status timer task; or,

[0046] When the node status timing task is completed, the node service status is configured as a long-term unserviced state.

[0047] In one embodiment, the method further comprises:

[0048] Receive node deletion instructions sent by the central node or network control center;

[0049] The node deletion instruction is executed to delete the network node.

[0050] In one embodiment, the method further comprises:

[0051] According to the long-term non-service status of the network node, a node deletion request is sent to the network management center or the central node to obtain the receiving node deletion instruction.

[0052] In one embodiment, the method further comprises:

[0053] A service period timing task is obtained, so as to configure the service state of the node to be an unserviced state when the service period timing task ends.

[0054] In one embodiment, the method further comprises:

[0055] According to the initialization status, configure the current node service status to be in service;

[0056] Acquire current business information, and update the node service status according to the current business information.

[0057] In one embodiment, obtaining current service information includes:

[0058] The currently accessed service and / or currently executed service is obtained to determine the current business information.

[0059] In one embodiment, updating the node service status according to the current service information includes:

[0060] When the current service information is empty, configure the node service state to be unserviced; or

[0061] When the current service information is not empty, the node service state is configured to be in service.

[0062] In one embodiment, the current service information includes any one of: node service and node collaboration service.

[0063] In an eighth aspect, the present application provides a distributed network node management device, applied to a distributed network node, the device comprising:

[0064] A request receiving module is used to receive a node information request sent by a network control center;

[0065] The node information sending module is used to send node information to the network control center; wherein the node information includes the node service status.

[0066] In one embodiment, the apparatus further comprises:

[0067] The node status timed task execution module is used to obtain the node status timed task; and update the node service status according to the execution result of the node status timed task.

[0068] In one embodiment, the apparatus further comprises:

[0069] The node deletion execution module is used to receive a node deletion instruction sent by a central node or a network manager; and execute the node deletion instruction to delete a network node.

[0070] In one embodiment, the apparatus further comprises:

[0071] The node deletion request initiating module is used to send a node deletion request to the network management center or the central node according to the long-term non-service status of the network node; receive the node deletion instruction, and execute the node deletion instruction.

[0072] In one embodiment, the apparatus further comprises:

[0073] The service cycle timed task processing module is used to obtain a service cycle timed task, so as to configure the node service state to an unserviced state when the service cycle timed task ends.

[0074] In one embodiment, the apparatus further comprises:

[0075] The initialization module is used to configure the current node service status to the in-service state according to the initialization status;

[0076] The node status update module is used to obtain current business information and update the node service status according to the current business information.

[0077] In an eighth aspect, the present application further provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method in any one of the embodiments of the sixth aspect when executing the computer program.

[0078] In a ninth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method in any one of the embodiments of the sixth aspect.

[0079] In the tenth aspect, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the method in any one of the embodiments of the sixth aspect.

[0080] In an eleventh aspect, the present application further provides a distributed network node management system, the system comprising:

[0081] Distributed network nodes, used to update node service status based on current business information;

[0082] The network control center is configured to obtain node information of the distributed network nodes; wherein the node information includes node service status.

[0083] In one embodiment, the system further includes: a central node, configured to synchronize node information with the network control center.

[0084] In the above-mentioned distributed network node management method, the network control center can obtain the current node service status fed back by each network node by sending a node information request to the network node; for the network control center, based on different node service states, it can facilitate the network control center to timely manage network nodes in different service states, thereby reducing the waste of network resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] Figure 1 A schematic flow chart of a distributed network node management method applied to a network control center in one embodiment;

[0086] Figure 2 A schematic flow chart of a method for processing redundant nodes in one embodiment;

[0087] Figure 3 A flowchart of a method for processing a node status timing task in one embodiment;

[0088] Figure 4 A schematic diagram of an interactive process for processing a node status timing task in one embodiment;

[0089] Figure 5 1 is a flow chart of a distributed network node management method applied to a distributed network node in one embodiment;

[0090] Figure 6 A schematic diagram of a method for a distributed network node to process a node status timing task in one embodiment is provided;

[0091] Figure 7 is a schematic diagram of a method for deleting a distributed network node in one embodiment;

[0092] Figure 8 A schematic diagram of a method for updating a node service status in a distributed network node according to an embodiment;

[0093] Figure 9 is a schematic diagram of a distributed network node management device in one embodiment;

[0094] Figure 10 is a schematic diagram of another distributed network node management device according to an embodiment;

[0095] Figure 11 is a schematic diagram of a distributed network node management system in one embodiment;

[0096] Figure 12 FIG. 4 is a structural diagram of an electronic device in one embodiment. DETAILED DESCRIPTION

[0097] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0098] In related technologies, in 6G network architectures, distributed network units are micro-cloud units deployed at the network edge, or edge networks. In distributed network scenarios, NAR (Node Automatic Registration) network elements are used to implement node-level plug-and-play and registration discovery for distributed network nodes. However, handling distributed nodes that are removed after creation or that have been unused for an extended period requires a specific and detailed management solution.

[0099] In order to solve the technical defects in the related art, in one embodiment, a distributed network node management method is provided. The method can be applied to the network control center side. Figure 1 As shown, the management methods may specifically include:

[0100] Step S11, sending a node information request to a network node;

[0101] Step S12: receiving node information fed back by the network node; wherein the node information includes the node service status.

[0102] Specifically, an independent network control center can be provided to collect information and manage distributed network nodes. For example, the network control center can send command messages to distributed network nodes. Upon receiving the command message from the network control center, each network node can execute the corresponding specific command, generate the corresponding command execution result or response message, and provide feedback to the network control center. After receiving the feedback message from the network node, the network control center can perform status management and node management for the network node based on the message content.

[0103] For example, the network control center can be deployed on the server side and interact with the central node and network nodes. Alternatively, in a distributed network architecture, the network control center can also be an independent functional network element in the control plane. The network control center can synchronize data with the central network element or NAR network element to obtain initial data such as the identity, interface information, address information, and registration information of each network node.

[0104] For example, the network control center can send node information requests to all or some network nodes based on parameters such as the network node's address information or identity information. This node information request can include only a request for node service status information. Upon receiving the request information from the network control center, the network node can generate node information and send it to the network control center along with the current node service status information. The network control center can then receive and receive node information fed back by the network nodes to obtain the current node service status of each network node.

[0105] Exemplarily, the node service status includes any one of: an in-service status, an out-of-service status, and a long-term out-of-service status.

[0106] The in-service state (DN-ACTIVE) indicates that the network node is currently in service. The out-of-service state (DN-INACTIVE) indicates that the network node is currently out of service. For example, this could be in power-saving or standby mode. In this state, upon receiving a service request, the node can be activated and switched to the in-service state. The long-term out-of-service state (DN-IDLE) indicates that the network node has been out of service for a predetermined period of time and has been in the out-of-service state. For example, from the central node's perspective, a distributed network node can have only the in-service state and the long-term out-of-service state. The out-of-service state is transparent to the central node. From the user's perspective, a distributed network node only has the in-service state. Even if a distributed node is in the out-of-service state, a user triggering a service request will still select the distributed network node for service, and the node's actual state will be activated from the out-of-service state to the in-service state.

[0107] In an exemplary embodiment, the method further comprises: synchronizing the node information of the network node to a central node.

[0108] Specifically, after receiving node information from network nodes, the network control center can synchronize this information with the central node. This synchronization ensures consistency between the node information stored in the network control center and the central node. This also facilitates the central node's management of network nodes.

[0109] In an exemplary embodiment, the method further includes: when the node service status of the network node is an unserviced state, configuring a node status timing task for the network node to update the node status information of the network node according to the execution result of the node status timing task.

[0110] For example, after obtaining the current node service status of a network node, the network control center can manage the network node based on the current status. Specifically, upon detecting that a network node is currently out of service, the network control center can configure a scheduled node status task for the network node. This scheduled node status task can be sent by the network control center to the network node and executed by the node. Alternatively, the network control center can configure the scheduled node status task for the network node and execute it there. In this case, the network control center determines the execution status of the scheduled task based on the node service status reported by the network node. The network control center and the network node can update the corresponding node service status based on the execution results of the scheduled task. The node information reported by each network node to the network management center can also include node energy consumption information. For example, node energy consumption information can include: node creation time, resource consumption information corresponding to node creation, and resource utilization information of the network node. When configuring a scheduled node status task for a network node, the network control center can configure the specific duration of the scheduled task based on the node energy consumption information. For example, for network nodes with high energy consumption, you can configure a longer node status scheduled task; for network nodes with low energy consumption and less network resource usage, you can configure a shorter node status scheduled task. Alternatively, you can configure the same node status scheduled task duration for different network nodes.

[0111] In an exemplary embodiment, updating the node status information of the node to be processed based on the execution result of the node status timing task includes: when the node status timing task is not completed, configuring the node service status of the node to be processed to an in-service state, and deleting the node status timing task.

[0112] Exemplary, reference Figure 3 As shown, when a network node fails to complete a node status timer task, it indicates that during the execution of the task, the network node receives a new user service request, and the network node switches from an unserved state to an in-service state. After switching to an in-service state, the network node reports the switched in-service state to the network control center and can automatically delete the local node status timer task. Alternatively, after obtaining the in-service state of the network node after the switch, the network control center sends a timer task deletion instruction to the network node, allowing the network node to delete the node status timer task.

[0113] In an exemplary embodiment, updating the node status information of the node to be processed based on the execution result of the node status timing task includes: when the node status timing task is completed, configuring the node status of the node to be processed to a long-term unserviced state; and sending a node deletion instruction to the network node to delete the network node.

[0114] Specifically, when a network node completes a node status timing task, it means that during the execution of the timing task, the network node remains in an unserviced state. After executing the timing task, the network node can automatically update the node service status to a long-term unserviced state locally, and feed back the task execution results to the network control center. The network control center can update the status of the network node to a long-term unserviced state based on the task execution results, so as to trigger subsequent tasks based on the status information. Alternatively, after the network control center updates the status of the network node to a long-term unserviced state, a service status switching instruction can be sent to the network node, so that the network node updates its status and switches to a long-term unserviced state. In addition, based on the long-term unserviced state updated by the network node, the network control center can send a node deletion instruction to the network node, and the network node executes the deletion instruction, thereby deleting the network node that is in a long-term unserviced state.

[0115] In addition, after the network control center or central node sends a node deletion instruction to a distributed network node, it can, after a preset period of time, use the original interface address or physical address of the network node to send a message requesting a response. If no response message is received from the network node, it proves that the network node has been deleted. Alternatively, if a response message is received, it indicates that the network node deletion failed. After confirming that the network node has been successfully deleted, the network control center can synchronize information with the central node.

[0116] In an exemplary embodiment, the network control center may also be configured in a central node, that is, the central node implements the functions implemented by the network control center.

[0117] Exemplary, reference Figure 4 As shown, for the network control center, central node, and distributed network nodes, the interaction process may include the following steps:

[0118] Step 41: Create a distributed network node and configure the initial node service state to be in service;

[0119] Step 42: The network control center sends a node information request to the distributed network node;

[0120] Step 43: The distributed network node processes the node information request and feeds back the node information to the network control center as a response to the node information request;

[0121] Step 44: The distributed network nodes synchronize node information with the central node, and the central node replies with a response message to the distributed network nodes.

[0122] Step 45: If the distributed network node does not provide user services for a period of time, the node service state is updated to an unserviced state;

[0123] Step 46: When the network control center detects that the current state of the distributed network node is out of service, it configures a node state timer task for the distributed network node and starts the timer.

[0124] Step 47a: before the node status timer task ends, if a user service selects a distributed network node for service, the current node service status of the distributed network node is updated to the in-service state;

[0125] Step 47b: The network control center deletes the node status scheduled task;

[0126] Step 48a: When the node status timer task ends, the distributed network node updates the current node service status and switches to a long-term non-service state;

[0127] Step 48b: The distributed network node synchronizes the long-term out-of-service status to the central node.

[0128] In one exemplary embodiment, reference Figure 2 As shown, the method further includes:

[0129] Step S21, obtaining first node information corresponding to a first network node, and comparing the first node information with second node information corresponding to other network nodes;

[0130] Step S22: Determine a redundant node according to the node information comparison result, and send a node deletion instruction to the redundant node to delete the redundant node.

[0131] For example, for the network control center, the node information obtained from the network node may also include node service information, and redundancy judgment of the network node is performed based on the node service information. For example, the node service information can be any combination of the specific service content, service scenario, network function, coverage, stored data content, supported network slices, and connected network resources of the network node.

[0132] Specifically, the network control center compares the node business information of each network node to determine whether there are multiple network nodes with exactly the same business information or a similarity greater than a preset threshold, thereby determining whether there are redundant nodes and deleting the redundant nodes.

[0133] Exemplarily, determining the redundant node according to the node information comparison result includes: when the first node information is identical to the second node information, determining the first network node or the second network node as the redundant node.

[0134] Specifically, when determining redundant nodes, the network control node may select a network node as the first network node, select a second network node from other network nodes, and then compare node information between the first and second network nodes to determine whether the node information is identical. If the node information is identical, either the first or second network node may be marked as a redundant node, and a node deletion instruction may be sent to the redundant node. For example, for the first network node, the other network nodes may include one or more. If multiple other network nodes are included, the first network node may be compared with each network node in sequence. If a redundant node is determined to exist, the current redundant node determination process may be terminated. For example, the network control center may determine redundant nodes for a certain type of service based on a service request, obtain all network nodes that perform that type of service, select a network node as the first network node, select a second network node from the remaining network nodes, and then compare the first network node with the second network node. This allows each other network node to be compared to determine whether a redundant node exists.

[0135] For example, when determining the presence of redundant nodes, the network control center may also determine the current network resource usage and service status of the first and second network nodes. For example, if users / services on the first and second network nodes in the distributed network do not require a large amount of the same resources, node resource redundancy may be determined, and the first or second network node may be designated as a redundant node.

[0136] Illustratively, after a redundant node is selected, the node service status of the redundant node may be obtained, and when the redundant node is in an unserviced state, a node deletion instruction may be sent to the redundant node.

[0137] Alternatively, if the network control center configures the first network node as a redundant node, but the first network node always processes user services within a certain monitoring period, the user services can be migrated to the second network node and the redundant node can be deleted.

[0138] For example, after determining the redundant node to be deleted, the network control center can synchronize the redundant node information with the central node and delete the redundant node after receiving a response from the central node. Alternatively, after receiving the redundant node information, the central node can send a node deletion instruction to the redundant node.

[0139] In an exemplary embodiment, determining the redundant node according to the node information comparison result includes: when the first node information includes the second node information, determining the second network node as the redundant node.

[0140] Specifically, for the network control center, when creating a network node, it can collect the node information of the newly created node, and then compare the node information of the newly created node with the node information of other network nodes. For example, a distributed network creates a first network node based on the user's service request, and the network control center collects the node information of the first network node. A network node is selected from other network nodes as the second network node, and the corresponding second node information is collected; the first node information is compared with the second node information. If the parameters such as the node function, service type and applicable scenario of the first network node can cover the second network node, the second network node can be configured as a redundant node, and the information of the redundant node can be synchronized to the central node, so that the network control center or the central node sends a node deletion instruction to the redundant node.

[0141] In an exemplary embodiment, the method further includes: in response to a network node creation request, configuring a service period timing task for the network node, so as to configure the node state of the network node to an out-of-service state when the service period timing task ends.

[0142] Specifically, when a new distributed network node is created based on a user service request, a corresponding service cycle timer task can be configured for the newly added node and sent to the newly added node. This service cycle timer task allows the node's service cycle to be configured; when the node reaches the preset service cycle duration, the node's service status is switched to an unserviced state. By configuring service cycle timer tasks for network nodes, the service duration of distributed network nodes can be accurately managed.

[0143] In one exemplary embodiment, reference Figure 5 As shown, a distributed network node management method is provided, which is applied to distributed network nodes, and the method includes:

[0144] Step S51, receiving a node information request sent by a network control center;

[0145] Step S52: Send node information to the network control center; wherein the node information includes node service status.

[0146] Specifically, a distributed network node may receive a node information request from a network control center, wherein the node information request may be a request for the node's service status. The distributed network node may respond to the request by reading the current node service type of the network node, generating node information, and sending the node information to the network control center, thereby enabling the network control center to obtain the current node service status of the network node.

[0147] Exemplarily, after sending node information to the network control center, the distributed network node can also synchronize the node information to the central node, so that the central node can obtain the current node service status of the network node, thereby facilitating the central node to initiate management messages to the network node.

[0148] In one exemplary embodiment, reference Figure 6 As shown, the method further includes:

[0149] Step S61, obtaining node status timing task;

[0150] Step S62: Update the node service status according to the execution result of the node status timing task.

[0151] Specifically, after a network node reports its node service status to the network control center, if the reported node service status indicates an unavailable state, the node can receive a node status timer task assigned by the network control center. The network node can execute the node status timer task and update its node service status based on the results of the timer task. The node information reported by the network node to the network control center can also include node energy consumption information, such as node creation time, resource consumption information corresponding to node creation, and resource occupancy information of the network node. The network control center can configure the duration of the node status timer task for the network node based on the node energy consumption information of the network node.

[0152] In an exemplary embodiment, updating the node service status according to the execution result of the node status timer task includes: when the node status timer task is not completed, configuring the node service status to be in-service state and deleting the node status timer task; or

[0153] When the node status timing task is completed, the node service status is configured as a long-term unserviced state.

[0154] For example, for a distributed network node, if a user service request is received during the execution of a node status timer task, the node can be updated from an unserviced state to a serviced state, and the node status timer task can be deleted. Alternatively, if a distributed network node completes a node status timer task, indicating that no user service request has been received during that time period, the node can be updated from an unserviced state to a long-term unserviced state.

[0155] In addition, the distributed network nodes can also feed back the updated node service status to the network control center. In addition, the updated node service status can also be synchronized to the central node.

[0156] In one exemplary embodiment, reference Figure 7 As shown, the method further includes:

[0157] Step S71, receiving a node deletion instruction sent by a central node or a network control center;

[0158] Step S72: Execute the node deletion instruction to delete the network node.

[0159] Specifically, a distributed network node may receive a node deletion instruction from a network control center or central node. These node deletion instructions may be triggered by the network control center or central node based on a network node's long-term out-of-service status. Upon receiving the node deletion instruction, the network node may execute the instruction and delete the node.

[0160] In an exemplary embodiment, the method further includes: sending a node deletion request to a network management center or a central node according to the long-term out-of-service status of the network node, so as to obtain the receiving node deletion instruction.

[0161] Specifically, for distributed network nodes, if the current node service status is long-term out-of-service, a node deletion request can be proactively triggered and sent to the network management center or central node. After receiving a confirmation response message from the network management center or central node, the proactive deletion can be executed. After the node is deleted, the network management center can send a response request to the network node. If no response message is received from the network node, it can confirm that the node deletion was successful and synchronize information with the central node. After completing the information synchronization, the central node can send a response message back to the network management center.

[0162] In one exemplary embodiment, reference Figure 8 As shown, the method further includes:

[0163] Step S81, according to the initialization state, configure the current node service state to be in service state;

[0164] Step S82: Acquire current business information, and update the node service status according to the current business information.

[0165] Specifically, when a new distributed network node is created, the initial node service state can be configured for the network node as an in-service state. The network node can update the node service state based on the business information processed by the node.

[0166] Exemplarily, the obtaining of the current service information includes: obtaining a currently accessed service and / or a currently executed service to determine the current service information.

[0167] Exemplarily, the current service information includes any one of: node service and node collaboration service.

[0168] Exemplarily, updating the node service status according to the current business information includes:

[0169] When the current service information is empty, configure the node service state to be unserviced; or

[0170] When the current service information is not empty, the node service state is configured to be in service.

[0171] Specifically, the user services processed by the distributed network node may include services that access the distributed node, services that access services through the distributed node, and services that require the coordination of the distributed node. The status of a distributed network node changes not only based on whether the node has user access / services, but also whether the node needs to provide services. This includes both the node's own user access / services and the access / services that other nodes need to coordinate with it. Only when it has no services at all will it undergo a state transition, from the in-service state to the out-of-service state. If the out-of-service state persists for a certain period of time, it can be converted to a long-term out-of-service state. In the out-of-service state or the long-term out-of-service state, if a user service request is received, it can be converted to the in-service state.

[0172] In an exemplary embodiment, the method further includes: acquiring a service period timing task, so as to configure the node service state to an unserviced state when the service period timing task ends.

[0173] Specifically, a distributed network node, in its initial state, can receive and execute a scheduled service cycle task assigned by the network control center. When the scheduled task completes, the node's service cycle ends, and the node's service state is switched to an unserviced state. Status information is then synchronized with the network control center and the central node.

[0174] The distributed network node management method provided by the present disclosure sets a service status identifier for a distributed network node to identify the current node service status of the distributed network node. The network management center sets and monitors the service status transitions of the distributed network nodes, facilitating the management of the network nodes by the network control center and central node. Furthermore, by configuring scheduled tasks, the node service status can be updated promptly and accurately. Node deletion can be initiated by the network management center, the central node, or the distributed network node itself. Furthermore, a network control center is introduced to collect node information from distributed network nodes, monitor the energy-saving time of distributed network nodes, and monitor network conditions. This allows the deletion of distributed network nodes that have been unused for a long time or are redundant, saving network resources.

[0175] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0176] Based on the same inventive concept, embodiments of the present application also provide a distributed network node management device and system for implementing the above-mentioned distributed network node management method. The implementation solutions provided by the device and system are similar to those described in the above-mentioned method. Therefore, the specific limitations in one or more device embodiments provided below can be found in the above-mentioned method limitations and will not be repeated here.

[0177] In one embodiment, Figure 9 As shown, a distributed network node management device 90 is provided, which is applied to a network control center. The device includes:

[0178] Request sending module 901, used to send a node information request to a network node;

[0179] The node information receiving module 902 is configured to receive node information fed back by the network node; wherein the node information includes the node service status.

[0180] In one embodiment, the apparatus further comprises:

[0181] a node information comparison module, configured to obtain first node information corresponding to a first network node, and compare the first node information with second node information corresponding to other network nodes;

[0182] The redundant node calculation module is used to determine the redundant node according to the node information comparison result, and send a node deletion instruction to the redundant node to delete the redundant node.

[0183] In one embodiment, the apparatus further comprises:

[0184] The node status timing task configuration module is used to configure a node status timing task for the network node when the node service status of the network node is an unserviced state, so as to update the node status information of the network node according to the execution result of the node status timing task.

[0185] In one embodiment, the apparatus further comprises:

[0186] The service period timing task configuration module is used to configure a service period timing task for the network node in response to a network node creation request, so as to configure the node state of the network node to be an unserviced state when the service period timing task ends.

[0187] In one embodiment, Figure 10 As shown, a distributed network node management device 10 is provided, which is applied to a distributed network node, and the device includes:

[0188] The request receiving module 1001 is used to receive a node information request sent by the network control center;

[0189] The node information sending module 1002 is used to send node information to the network control center; wherein the node information includes the node service status.

[0190] In one embodiment, the apparatus further comprises:

[0191] The node status timed task execution module is used to obtain the node status timed task; and update the node service status according to the execution result of the node status timed task.

[0192] In one embodiment, the apparatus further comprises:

[0193] The node deletion execution module is used to receive a node deletion instruction sent by a central node or a network manager; and execute the node deletion instruction to delete a network node.

[0194] In one embodiment, the apparatus further comprises:

[0195] The node deletion request initiating module is used to send a node deletion request to the network management center or the central node according to the long-term non-service status of the network node; receive the node deletion instruction, and execute the node deletion instruction.

[0196] In one embodiment, the apparatus further comprises:

[0197] The service cycle timed task processing module is used to obtain a service cycle timed task, so as to configure the node service state to an unserviced state when the service cycle timed task ends.

[0198] In one embodiment, the apparatus further comprises:

[0199] The initialization module is used to configure the current node service status to the in-service state according to the initialization status;

[0200] The node status update module is used to obtain current business information and update the node service status according to the current business information.

[0201] In one embodiment, Figure 11 As shown, a distributed network node management system is provided, the system comprising:

[0202] Distributed network node 1101, used to update the node service status according to current business information;

[0203] The network control center 1102 is configured to obtain node information of the distributed network nodes; wherein the node information includes node service status.

[0204] There may be multiple distributed network nodes 1101.

[0205] In one embodiment, the system further comprises:

[0206] The central node 1103 is used to synchronize node information with the network control center.

[0207] The distributed network node management method described in the above embodiment can be applied to the distributed network node management system.

[0208] Each module in the above-mentioned distributed network node management device and system can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0209] In one embodiment, a communication device is provided, whose structure diagram can be as follows: Figure 12As shown. The device includes a processor, memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals via wired or wireless means. The wireless means can be implemented via Wi-Fi, mobile cellular networks, NFC (near field communication), or other technologies. When executed by the processor, the computer program implements a proximity service communication method. The display unit of the computer device is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse.

[0210] Those skilled in the art will understand that Figure 12 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0211] In one embodiment, a communication device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0212] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0213] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0214] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions.

[0215] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), data processing logic devices based on quantum computing, and the like.

[0216] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0217] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A distributed network node management method, characterized in that: Applied to a network control center, the method includes: Sending node information request to network nodes; Receive node information fed back by the network node; wherein the node information includes node service status.

2. The method according to claim 1, characterized in that The method further comprises: When the node service state of the network node is an unservice state, a node status timing task is configured for the network node, so as to update the node status information of the network node according to the execution result of the node status timing task.

3. The method according to claim 2, characterized in that The updating of the node status information of the node to be processed according to the execution result of the node status timing task includes: When the node status timing task is not completed, the node service status of the standby network node is configured as an in-service state, and the node status timing task is deleted.

4. The method according to claim 2, characterized in that The updating of the node status information of the node to be processed according to the execution result of the node status timing task includes: When the node status timing task is completed, the node status of the node to be processed is configured as a long-term out-of-service state; A node deletion instruction is sent to the network node to delete the network node.

5. The method according to claim 1, wherein The method further comprises: Obtaining first node information corresponding to a first network node, and comparing the first node information with second node information corresponding to other network nodes; A redundant node is determined according to the node information comparison result, and a node deletion instruction is sent to the redundant node to delete the redundant node.

6. The method according to claim 5, characterized in that The determining of the redundant node according to the node information comparison result includes: When the first node information is the same as the second node information, determining that the first network node or the second network node is the redundant node; or When the first node information includes the second node information, the second network node is determined to be the redundant node.

7. The method according to any one of claims 1 to 6, characterized in that The method further includes: synchronizing the node information of the network nodes to a central node.

8. The method according to claim 7, characterized in that The central node includes the network control center.

9. The method according to claim 1, characterized in that The method further comprises: In response to a network node creation request, a service period timing task is configured for the network node, so as to configure the node state of the network node to be an unserviced state when the service period timing task ends.

10. The method according to claim 1, characterized in that The node service status includes any one of: in-service status, out-of-service status, and long-term out-of-service status.

11. A distributed network node management method, characterized in that: Applied to a distributed network node, the method includes: Receive node information request sent by the network control center; Sending node information to the network control center; wherein the node information includes node service status.

12. The method according to claim 11, characterized in that The method further comprises: Get node status scheduled task; The node service status is updated according to the execution result of the node status timing task.

13. The method according to claim 12, characterized in that The updating of the node service status according to the execution result of the node status timing task includes: When the node status timer task is not completed, configuring the node service status to be in service and deleting the node status timer task; or, When the node status timing task is completed, the node service status is configured as a long-term unserviced state.

14. The method according to claim 11, characterized in that The method further comprises: Receive node deletion instructions sent by the central node or network control center; The node deletion instruction is executed to delete the network node.

15. The method according to claim 11 or 14, characterized in that The method further comprises: According to the long-term non-service status of the network node, a node deletion request is sent to the network management center or the central node to obtain the receiving node deletion instruction.

16. The method according to claim 11, characterized in that The method further comprises: A service period timing task is obtained, so as to configure the service state of the node to be an unserviced state when the service period timing task ends.

17. The method according to claim 11, characterized in that The method further comprises: According to the initialization status, configure the current node service status to be in service; Acquire current business information, and update the node service status according to the current business information.

18. The method according to claim 17, characterized in that The obtaining of current business information includes: The currently accessed service and / or currently executed service is obtained to determine the current business information.

19. The method according to claim 17, wherein The updating of the node service status according to the current business information includes: When the current service information is empty, configure the node service state to be unserviced; or When the current service information is not empty, the node service state is configured to be in service.

20. The method according to claim 11, characterized in that The current service information includes: any one of: node service and node collaboration service.

21. A distributed network node management device, characterized in that: Applied to a network control center, the device comprises: A request sending module, used for sending a node information request to a network node; The node information receiving module is used to receive the node information fed back by the network node; wherein the node information includes the node service status.

22. The device according to claim 21, characterized in that The device further comprises: a node information comparison module, configured to obtain first node information corresponding to a first network node, and compare the first node information with second node information corresponding to other network nodes; The redundant node calculation module is used to determine the redundant node according to the node information comparison result, and send a node deletion instruction to the redundant node to delete the redundant node.

23. The device according to claim 21, characterized in that The device further comprises: The node status timing task configuration module is used to configure a node status timing task for the network node when the node service status of the network node is an unserviced state, so as to update the node status information of the network node according to the execution result of the node status timing task.

24. The device according to claim 21, characterized in that The device further comprises: The service period timing task configuration module is used to configure a service period timing task for the network node in response to a network node creation request, so as to configure the node state of the network node to be an unserviced state when the service period timing task ends.

25. A distributed network node management device, characterized in that: Applied to a distributed network node, the device comprises: A request receiving module is used to receive a node information request sent by a network control center; The node information sending module is used to send node information to the network control center; wherein the node information includes the node service status.

26. The device according to claim 25, characterized in that The device further comprises: The node status timed task execution module is used to obtain the node status timed task; and update the node service status according to the execution result of the node status timed task.

27. The device according to claim 25, characterized in that The device further comprises: The node deletion execution module is used to receive a node deletion instruction sent by a central node or a network manager; and execute the node deletion instruction to delete a network node.

28. The device according to claim 26, characterized in that The device further comprises: The node deletion request initiating module is used to send a node deletion request to the network management center or the central node according to the long-term non-service status of the network node; receive the node deletion instruction, and execute the node deletion instruction.

29. The device according to claim 25, characterized in that The device further comprises: The service cycle timed task processing module is used to obtain a service cycle timed task, so as to configure the node service state to an unserviced state when the service cycle timed task ends.

30. The device according to claim 25, wherein The device further comprises: The initialization module is used to configure the current node service status to the in-service state according to the initialization status; The node status update module is used to obtain current business information and update the node service status according to the current business information.

31. A distributed network node management system, characterized in that: The system comprises: Distributed network nodes, used to update node service status based on current business information; The network control center is configured to obtain node information of the distributed network nodes; wherein the node information includes node service status.

32. The system according to claim 31, wherein: The system further comprises: The central node is used to synchronize node information with the network control center.

33. A communication device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 10 or claims 11 to 20 are implemented.

34. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 10 or claims 11 to 20 are implemented.

35. A computer program product, characterized in that The computer program product comprises a computer program, which implements the steps of the method of any one of claims 1 to 10 or claims 11 to 20 when executed by a processor.

Images