Distributed adr node remote management method and device, equipment and medium

Abstract

The application discloses a distributed ADR node remote management and control method and device, equipment and medium, discloses a distributed ADR node remote management and control method, comprising: receiving an operation request from a client, the operation request is used to request to call the management and control operation of at least one ADR node in a preset ADR list;Acquire the task attribute parameter and node identification information corresponding to the operation request;Task attribute parameters and node identification information are analyzed, and the task type information and target ADR node corresponding to the operation request are obtained;According to the task attribute parameter, an execution instruction is generated, and the execution instruction is issued to the target ADR node through the ADR communication center, so that the target ADR node executes the corresponding management and control operation.Based on this, through the ADR communication center as a unified communication transfer and scheduling hub, the client only needs to establish a single communication link with the communication center to complete multi-node management and control, and the management and control efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of adaptive data rate node technology, and in particular to a method, apparatus, equipment and medium for remote management and control of distributed ADR nodes. Background Technology

[0002] In the remote operation and maintenance management technology of distributed adaptive data rate (ADR) nodes, the management efficiency is improved by unifying the command scheduling and execution result feedback of multiple nodes, and the stable operation of nodes is ensured.

[0003] When remotely managing multiple distributed ADR nodes, a point-to-point direct connection mode is typically used, where the terminal device establishes an independent communication link with each ADR node individually. Operation commands are then sent to the target node one by one based on the node's address information. Because the terminal device needs to establish an independent communication link with each ADR node individually, in distributed deployment scenarios with a large number of nodes, the more nodes there are, the higher the link maintenance cost and concurrent communication resource consumption on the client side, resulting in low management efficiency under large-scale node deployments.

[0004] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main purpose of this application is to provide a method, device, equipment and medium for remote management and control of distributed ADR nodes, which aims to solve the technical problem of low management and control efficiency under large-scale nodes.

[0006] To achieve the above objectives, this application proposes a distributed ADR node remote management method, applied to an ADR communication center, which communicates with clients and multiple ADR nodes respectively. The method includes: Receive an operation request from the client, the operation request being used to request the invocation of a control operation of at least one of the ADR nodes in a preset ADR list; Obtain the task attribute parameters and node identifier information corresponding to the operation request; The task attribute parameters and node identification information are parsed by the ADR communication center to obtain the task type information and target ADR node corresponding to the operation request; An execution instruction is generated based on the task attribute parameters and sent to the target ADR node through the ADR communication center so that the target ADR node can perform the corresponding control operation.

[0007] In one embodiment, prior to the step of receiving an operation request from the client, the distributed ADR node remote management method further includes: When the ADR communication center is in standby mode, the connection requests initiated by the clients corresponding to each ADR node are obtained; The preset ADR list is constructed based on the connection request.

[0008] In one embodiment, the step of constructing the preset ADR list based on the connection request includes: Determine the basic node information corresponding to the connection request, wherein the basic node information includes at least a node identifier and a network communication address; Determine whether an ADR list containing the node identifier exists; If so, the address information and online status of the ADR list are updated based on the network communication address to obtain the preset ADR list.

[0009] In one embodiment, the step of obtaining the task attribute parameters and node identifier information corresponding to the operation request includes: The node identification information is obtained by parsing the header of the operation request, wherein the node identification information includes a unique node identifier and node communication address information; Extract the task attribute parameters from the data payload field of the operation request.

[0010] In one embodiment, the step of parsing the task attribute parameters and the node identifier information to obtain the task type information and the target ADR node corresponding to the operation request includes: Based on the preset node routing table, the target ADR node that is online and connected is matched with the node identification information. Based on a preset task type mapping table and task attribute parameters, task type information is determined, including command execution, file operation, and system information acquisition.

[0011] In one embodiment, the step of generating an execution instruction based on the task attribute parameters and issuing the execution instruction to the target ADR node to cause the target ADR node to perform the corresponding control operation includes: When the task attribute parameter is a command execution type, an execution command instruction is generated and sent to the target ADR node so that the target ADR node executes the control command; When the task attribute parameter is a file operation type, a file operation instruction is generated and the file operation instruction is sent to the target ADR node so that the target ADR node performs a file operation action. When the task attribute parameter is of the system acquisition type, a system information acquisition instruction is generated and sent to the target ADR node so that the target ADR node performs a system information query action.

[0012] In one embodiment, after the step of generating an execution instruction based on the task attribute parameters and issuing the execution instruction to the target ADR node so that the target ADR node performs the corresponding management and control operation, the distributed ADR node remote management and control method further includes: Receive the control operation execution results fed back by each of the target ADR nodes; In response to the client's execution result query request, each execution result is fed back to the client.

[0013] Furthermore, to achieve the above objectives, this application also proposes a distributed ADR node remote management and control device, which includes: The receiving module is configured to receive an operation request from the client, wherein the operation request is used to request the invocation of a control operation of at least one of the ADR nodes in a preset ADR list; The acquisition module is used to acquire the task attribute parameters and node identification information corresponding to the operation request; The parsing module is used to parse the task attribute parameters and the node identification information through the ADR communication center to obtain the task type information and target ADR node corresponding to the operation request; The execution module is used to generate execution instructions based on the task attribute parameters and send the execution instructions to the target ADR node through the ADR communication center so that the target ADR node can perform the corresponding control operation.

[0014] In addition, to achieve the above objectives, this application also proposes a distributed ADR node remote management and control device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the distributed ADR node remote management and control method described above.

[0015] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the distributed ADR node remote management method described above.

[0016] One or more technical solutions proposed in this application have at least the following technical effects: Using the ADR communication center as the control hub, the system receives operation requests from clients, obtains the corresponding task attribute parameters and node identification information, parses these parameters to determine the task type and target ADR node, generates execution instructions based on the task attribute parameters, and sends them to the target ADR node to trigger the corresponding control operation. By using the ADR communication center as a unified communication relay and scheduling hub, clients only need to establish a single communication link with the center to complete multi-node control, eliminating the need for direct connections to all ADR nodes. Simultaneously, the communication center centrally handles instruction parsing, node routing matching, and targeted distribution, converging the communication pressure from multiple concurrent nodes to the center side. This significantly reduces communication resource consumption on the client side, improving overall control efficiency and ensuring the stability of multi-node remote control operations in distributed deployment scenarios with a large number of nodes. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart illustrating the first embodiment of the distributed ADR node remote management method of this application; Figure 2 This is a flowchart illustrating the second embodiment of the distributed ADR node remote management method of this application; Figure 3 A simplified flowchart illustrating the distributed ADR node remote management method provided in this application embodiment; Figure 4 This is a schematic diagram of the hardware operating environment involved in the distributed ADR node remote management and control method in this application embodiment.

[0020] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0021] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0022] When remotely managing multiple distributed ADR nodes, a point-to-point direct connection mode is used, where the terminal device establishes an independent communication link with each ADR node one by one, and operation commands are sent to the target node one by one based on the node address information. Since the terminal device needs to establish an independent communication link with each ADR node, in distributed deployment scenarios with a large number of nodes, the more nodes there are, the higher the link maintenance cost and concurrent communication resource consumption on the client side, resulting in low management efficiency under large-scale nodes.

[0023] Based on this, this application provides a solution that uses an ADR communication center as a unified communication relay and scheduling hub. Clients only need to establish a single communication link with the communication center to complete multi-node management, without needing to directly connect to all ADR nodes. Simultaneously, the communication center uniformly handles command parsing, node routing matching, and targeted distribution, converging the communication pressure of multiple concurrent nodes to the communication center side. This significantly reduces the communication resource consumption on the client side, improving overall management efficiency and ensuring the stability of multi-node remote management operations in distributed deployment scenarios with a large number of nodes.

[0024] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0025] This application provides a method for remote management and control of distributed ADR nodes, applied to an ADR communication center. The ADR communication center communicates with clients and multiple ADR nodes. The ADR nodes are independent terminal hardware deployed in a real physical environment, such as temperature sensors in factories, soil monitors in farmland, and pressure transmitters on pipelines. The ADR communication center is a software system running on a cloud server or a local industrial control computer. This software system can be deployed on electronic devices or electronic devices.

[0026] Based on this, refer to Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the distributed ADR node remote management method of this application.

[0027] In this embodiment, the distributed ADR node remote management and control method includes steps S10 to S40: Step S10: Receive an operation request from the client.

[0028] An operation request is used to invoke control operations on at least one of the ADR nodes in a pre-defined ADR list. The format of this operation request can be a data message or natural language. It is understood that this operation request is an interactive request instruction (also known as a message) initiated by the client to the ADR communication center to trigger the remote ADR node to execute a specified maintenance or business action. This instruction contains key fields such as the request initiator identifier, the target object, and the operation intent. The ADR list is a node resource pre-stored in the ADR communication center, used to record basic information about all ADR nodes included in the control scope. Control operations are a collection of various remote operations applied to remote ADR nodes, including command execution, file management, status acquisition, and other node maintenance and business operations across different dimensions.

[0029] In this embodiment, when a user needs to call the ADR node through a client, the client issues an operation request. This request enters the ADR communication center through a service acquisition port pre-deployed in the ADR communication center. That is, the ADR communication center receives the request message sent by the client through the acquisition port.

[0030] For example, operations and maintenance personnel initiate a batch system information query request for ADR nodes through a client. The client encapsulates the request content into an HTTPS POST message, which carries a pre-assigned interface key and is sent to the 443 service port of the ADR communication center. After successful authentication, the communication center verifies the integrity of the format of the message, such as the number of target nodes and the query fields. Once confirmed to be correct, the request is stored in the request processing queue, completing the receipt of the operation request.

[0031] Step S20: Obtain the task attribute parameters and node identifier information corresponding to the operation request.

[0032] In this embodiment, the task attribute parameters carry the specific business attributes of the control operation, and are used to define the operation category, execution rules, input parameters, etc. Node identification information is a set of feature information used to uniquely identify remote ADR nodes, serving as a core index field for locating target nodes and matching communication links.

[0033] In this embodiment, the header of the operation request can be directly parsed to obtain node identification information, which includes a unique node identifier and node communication address information. Simultaneously, task attribute information is extracted from the payload field of the operation request. The extracted information is typically field values, and the node identification information and task attribute parameters corresponding to the extracted fields can be determined based on a preset field mapping table. Alternatively, semantic recognition can be performed on the extracted content to obtain the node identification information and task attribute parameters.

[0034] Therefore, as an optional implementation, task attribute parameters and node identification information can be obtained through a preset mapping relationship. That is, by pre-defining the mapping relationship between message fields and target parameters, the corresponding parameters can be directly extracted from the request message. Specifically, the ADR communication center pre-stores a parameter field mapping configuration file. The configuration file contains the message field names corresponding to node identification information such as the node's unique identifier and communication address, as well as the message field names corresponding to task attribute parameters such as operation category and execution input parameters. During the extraction process, the ADR communication center retrieves the structured message data of the operation request from the queue, reads the corresponding field values ​​one by one according to the field mapping relationship table, and performs format verification on the extracted node identification information. After confirming that the node's unique identifier conforms to the preset encoding rules, the extracted task attribute parameters are type-converted, converting the string-format input parameters to the corresponding data type, and outputting standardized task attribute parameters and node identification information.

[0035] For example, for a file upload request from an ADR node, after loading the mapping table, the communication center confirms that the "node_id" field in the message corresponds to the unique identifier of the node, the "op_type" field corresponds to the operation category, and the "file_path" field corresponds to the file path parameter. Then, it extracts the parameter values ​​from the request message: node_id = "ADR-0012", op_type = "file_upload", and file_path = " / local / config.ini". After verifying the validity of the node identifier format, it outputs standardized node identifier information and task attribute parameters.

[0036] As another optional implementation, parameters can also be extracted based on message semantic parsing. That is, by parsing the semantic content of the request message, task attribute parameters and node identification information can be extracted. This allows for the automatic differentiation of target object information and operation content information in the request through semantic recognition, improving the adaptability to non-standardized requests. Specifically, the ADR communication center uses its built-in semantic parsing module to perform word segmentation and semantic classification on the natural language or semi-structured descriptions in the request message. Content related to node name, node number, deployment location, etc., used for locating nodes, is classified as node identification-related content; content related to operation actions, execution parameters, target objects, etc., used for defining operations, is classified as task attribute-related content. Then, the classified content undergoes information normalization and standardization transformation to generate node identification information and task attribute parameters in a unified format. Specifically, for the categorized node identifier-related content, a preset node information ledger is matched to convert the node name, deployment location, and other descriptive information into the corresponding unique node identifier and communication address information. For the categorized task attribute-related content, a preset operation instruction dictionary is matched to convert the operation actions described in natural language into standardized operation category identifiers and extract the corresponding execution input parameter information, ultimately generating two types of parameters with a unified format.

[0037] For example, when a user inputs a management request through the client to "update the configuration file for the ADR node in workshop 3 of the factory area", the semantic parsing module identifies that "workshop 3 of the factory area" belongs to the node location description and "update configuration file" belongs to the operation attribute description. Then, it matches the node ledger to convert "workshop 3 of the factory area" into the node's unique identifier "ADR-WS-03" and the corresponding communication address. It matches the operation dictionary to convert "update configuration file" into the operation category "file_update" and extracts the relevant input parameters of the configuration file. Finally, it outputs standardized node identification information and task attribute parameters.

[0038] This embodiment breaks down the original request message into node location and operation attributes, ensuring that only the content after parameter extraction and standardization is processed is used for subsequent data parsing.

[0039] Step S30: Parse the task attribute parameters and node identifier information to obtain the task type information and target ADR node corresponding to the operation request.

[0040] In this embodiment, the task type information is the classification result after classifying the control operations, used to match the corresponding instruction generation logic and realize differentiated processing of different categories of control operations. The target ADR node is a remote ADR node selected from the preset ADR list that meets the node identification information and is in an executable state; this node serves as the subject of instruction execution.

[0041] As an optional implementation, node identification information and task type information can be obtained based on the parsing method of node routing table and task type mapping table. That is, based on the preset node routing table, target ADR nodes that are online and connected and correspond to the node identification information are matched, and based on the preset task type mapping table and task attribute parameters, task type information is determined. The task type information includes command execution type, file operation type, and system information acquisition type.

[0042] Specifically, the ADR communication center maintains a real-time updated node routing table, which stores information such as the unique identifier, communication address, connection status, and environment of each ADR node. The extracted node identifier information is used as a query index to match the nodes in the routing table, thereby obtaining the complete information of the corresponding node. Next, the node's connection status field is verified. If the node is online and connected, it is identified as the target ADR node; if the node is offline, an "unreachable" message is generated. Simultaneously, a pre-defined task type mapping table can be queried based on task attribute parameters to obtain the corresponding task type information. The ADR communication center pre-configures the task type mapping table, mapping different operation category identifiers to three main task types: command execution, file operation, and system information retrieval. Using the operation category identifier from the task attribute parameters as input, the mapping table is queried to obtain the corresponding task type information.

[0043] For example, if a node is identified as "ADR-0012" and the operation category is "file_upload", the ADR communication center queries the node routing table and finds that the node identified as ADR-0012 is online, thus identifying it as the target ADR node. Next, it queries the task type mapping table to confirm that the "file_upload" operation category corresponds to a file operation task type.

[0044] As another optional implementation, target nodes can be screened by combining the real-time running status of nodes, and task types can be determined through semantic classification. That is, based on node identification information and the real-time running status of nodes, target ADR nodes that meet the execution conditions are selected from the ADR list to avoid issuing instructions to nodes with excessive load or abnormal states. Specifically, the ADR communication center collects data such as load, memory usage, and abnormal running status of each ADR node in real time. Then, after locating the candidate node set based on the node identification information, the real-time running status of the candidate nodes is verified, and nodes with load within a preset threshold range and no abnormal running alarms are selected as the final target ADR nodes. If there are multiple matching nodes, the optimal node can be selected according to the load balancing strategy. For task type information, semantic feature extraction and classification are performed directly on the task attribute parameters to determine the corresponding task type information. That is, semantic features such as operation actions and operation objects are extracted from the task attribute parameters, and the feature vectors are input into a pre-trained task classification model. The classification model infers based on the classification samples of historical control operations and outputs the task type confidence score corresponding to the task. Finally, the task type with the highest confidence score is selected as the final task type information.

[0045] For example, for a node identified as "Workshop 3 Cluster in the Factory Area" and an operation description of "running an inspection script and returning results", the communication center first selects three nodes with CPU load below 50% from the five ADR nodes in that workshop as target ADR nodes. Then, it extracts the semantic features of "running script" and "returning results", inputs them into the classification model, and determines that the task belongs to the command execution type.

[0046] This embodiment parses the task attribute parameters and node identification information to clarify the target ADR node and task type, so as to generate the corresponding execution instruction and accurately send the instruction to the target ADR node.

[0047] Step S40: Generate an execution instruction based on the task attribute parameters and send the execution instruction to the target ADR node so that the target ADR node performs the corresponding control operation.

[0048] An execution command is a standardized command message containing specific execution rules sent from the ADR communication center to the target ADR node.

[0049] In this embodiment, standardized execution instructions can be generated using predefined instruction templates and sent to a single target node via a point-to-point link. Specifically, the corresponding instruction template is matched based on the task type information, and then combined with the execution input parameters in the task attribute parameters to generate standardized execution instructions. Each task type has a pre-configured corresponding instruction template, which defines a fixed structure including an instruction header, instruction number, opcode, parameter fields, and checksum. The corresponding template can be retrieved based on the task type information, and the execution input parameters from the task attribute parameters are filled into the corresponding parameter fields of the template. The instruction number is automatically generated, and the checksum is calculated, ultimately generating a fully formatted standardized execution instruction. Specifically, when the task attribute parameter is command execution, an execution command instruction is generated using a template and sent to the target ADR node to enable the target ADR node to execute control commands; when the task attribute parameter is file operation, a file operation instruction is generated based on a template and sent to the target ADR node to enable the target ADR node to execute file operation actions; when the task attribute parameter is system retrieval, a system information retrieval instruction is generated and sent to the target ADR node to enable the target ADR node to execute system information query actions.

[0050] Alternatively, instructions can be generated through dynamic encapsulation. This involves determining the core operation logic of the instruction based on the task type, combining the common execution parameters in the task attribute parameters with the differentiated parameters of each node, dynamically assembling the common part of the instruction with the node-specific parameter part, adding a batch execution identifier in the instruction header, and configuring node adaptation rules so that each node only executes the exclusive parameter part that matches its own identifier.

[0051] Furthermore, in addition to issuing commands one by one, commands can also be issued in batches, such as by issuing commands to multiple target ADR nodes in batches via broadcast or multicast channels.

[0052] This embodiment provides a method for remote management and control of distributed ADR nodes. The ADR communication center serves as the management and control center, and requests are received, parameters are extracted, parsed and decided, and instructions are issued based on the ADR communication center. This replaces the traditional point-to-point direct connection mode with a centralized star topology. The client only needs to establish a single link with the communication center to realize remote management and control of multiple ADR nodes, reducing the link maintenance cost and concurrent communication resource consumption on the client side. At the same time, in distributed deployment scenarios with a large number of nodes, it can stably improve the overall management and control efficiency and ensure the reliability and flexibility of remote management and control operations.

[0053] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2Before step S10, the distributed ADR node remote management and control method further includes steps S01~S02: Step S01: Obtain the connection requests initiated by the clients corresponding to each ADR node when the ADR communication center is in standby mode.

[0054] The standby state is the low-load running state of the basic management thread obtained through the port after the ADR communication center completes system initialization, used to respond to access requests from remote ADR nodes. A connection request, on the other hand, is an access request message initiated by the client corresponding to the remote ADR node to the communication center.

[0055] In this embodiment, after the ADR communication center completes system initialization, it opens the connection acquisition port and enters standby mode. In this state, it continuously acquires connection access events for the port. Upon acquiring a connection handshake message initiated by a client, the connection request is stored in the pending connection queue.

[0056] For example, after 15 distributed ADR node devices in a certain park are powered on and started, their built-in clients automatically initiate TCP connection requests to port 8600 of the pre-configured ADR communication center address. Each request carries the device number of the corresponding node and a uniformly assigned access key. The communication center, which is in standby mode, captures all 15 connection requests through an acquisition thread. After verifying that the access keys are valid one by one, it stores all connection requests in the pending connection queue in the order of arrival, thus completing the acquisition of connection requests.

[0057] This embodiment eliminates the need for the communication center to actively detect the network addresses of all nodes, reducing the configuration cost of node deployment.

[0058] Step S02: Construct a preset ADR list based on the connection request.

[0059] Understandably, after an ADR client successfully goes online, an ADR command list needs to be built, and the ADR communication center sends the corresponding operation commands to the ADR client. When building this list, the basic information of the node corresponding to the connection request can be determined first. This basic information includes at least the node identifier and network communication address. Then, it is checked whether an ADR list containing the node identifier exists. If so, the address information and online status of the ADR list are updated based on the network communication address to obtain the preset ADR list.

[0060] Specifically, the ADR communication center parses the node identifier and network communication address from fixed fields in the message, while simultaneously extracting extended attributes such as the node's environment group and supported control types. Then, using the node identifier as a search index, it performs a precise match in the currently stored ledger data to determine if an ADR list record containing that node identifier exists. This distinguishes between newly added nodes accessing the network for the first time and existing nodes re-entering the network, avoiding data redundancy and conflicts caused by duplicate entries of the same node. Therefore, if a corresponding node record is found, it is determined to be an existing node re-accessing the network, and the information is updated. If no corresponding record is found, it is determined to be a newly added node accessing the network for the first time, and a new list is created. That is, if it is determined to be an existing node, the communication center overwrites the original address information of that node in the list based on the network communication address corresponding to the connection request, updates the node's online status to "online," and refreshes the most recent access time. If a node is identified as a new node, the verified basic information and extended attributes of the node are encapsulated according to the preset field structure of the ADR list to generate a complete node record, which is then inserted into the ADR list and the online status is initialized to "online". After all connection requests are processed, the updated preset ADR list is synchronously written to the memory cache and persistent database and pushed to business modules such as instruction distribution and status monitoring to ensure the consistency of node data across the entire system.

[0061] This embodiment uses an incremental construction logic based on node identifier matching, eliminating the need to rebuild the complete list every time a node comes online. It can automatically manage newly added ADR nodes to adapt to the dynamic expansion needs of distributed systems. Simultaneously, it can update the communication addresses and online status of existing nodes in real time, avoiding command delivery failures caused by dynamic address changes or offline reconnection.

[0062] Based on any of the above embodiments, in the third embodiment of this application, the content that is the same as or similar to the above embodiments can be referred to the above description, and will not be repeated hereafter. In addition, after step S40, steps S50-S60 are also included: Step S50: Receive the control operation execution results from each target ADR node.

[0063] In this embodiment, the execution result of the control operation is feedback information generated after the target ADR node completes the instruction execution. This feedback information may include an execution status identifier, execution output content, error messages, and execution time. The target ADR node can automatically return the execution result after executing the corresponding operation, or it can return the execution result after receiving the instruction from the ADR communication center.

[0064] In step S60, in response to the client's execution result query request, each execution result is fed back to the client.

[0065] In this embodiment, after the client initiates a control operation, and the communication center receives the query request and confirms that it has the query permission for the corresponding node control result, it can first extract the associated operation identifier from the request to retrieve the target execution result. Specifically, the ADR communication center retrieves the corresponding execution result data in the instruction execution ledger and result cache based on the extracted associated operation identifier; if the result has been successfully returned, it extracts information such as execution status, core output, and execution time. If the result has not yet been returned, it returns a "running" status message and the estimated remaining time; finally, through the communication link with the client, it returns the rectified result data to the client that initiated the query.

[0066] For example, after the operations and maintenance personnel initiate a batch system information collection operation for 10 nodes through the client, they send a result query request carrying the original request number every 10 seconds. After the communication center verifies the identity, it matches the request number to find that 8 nodes have returned execution results and 2 nodes are still in execution. The system information of the completed nodes and the execution status of the 2 nodes are uniformly encapsulated into structured data and returned to the client. The client interface synchronously displays the execution status and result details of each node.

[0067] For example, to help understand the implementation process of the distributed ADR node remote management method obtained by combining the above embodiments, please refer to... Figure 3 . Figure 3 A simplified flowchart of a distributed ADR node remote management method is provided. Specifically: The user first initiates a management operation input, and the corresponding operation request is transmitted to the ADR client. The ADR client performs structured processing of the user's operation intent, generates standardized task instructions, and outputs them to the ADR communication center. Upon receiving the task, the ADR communication center uniformly performs instruction parsing and task distribution processing. Based on the task's business attributes, it classifies it into three categories: command tasks, file operation tasks, and system information requests, and then directs the corresponding tasks to the corresponding execution units of the target ADR nodes. ADR nodes receiving command tasks invoke their local command execution capabilities to execute the specified instructions, output the command results after execution, and send them back upwards. ADR nodes receiving file operation tasks invoke their local file processing capabilities to perform operations on the corresponding file or directory, output the file operation results after execution, and send them back upwards. ADR nodes receiving system information requests invoke their local information acquisition capabilities to retrieve node system data, output the system information after acquisition, and send it back upwards. After the result data generated by the three types of execution are returned and transmitted separately, they are uniformly gathered to the ADR communication center. The communication center summarizes, integrates and unifies the execution results of multiple nodes and multiple types, and finally forms a complete execution result for output, thus completing a complete remote management process.

[0068] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the distributed ADR node remote management method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0069] This application also provides a distributed ADR node remote management and control device, the distributed ADR node remote management and control device comprising: The receiving module is configured to receive an operation request from the client, wherein the operation request is used to request the invocation of a control operation of at least one of the ADR nodes in a preset ADR list; The acquisition module is used to acquire the task attribute parameters and node identification information corresponding to the operation request; The parsing module is used to parse the task attribute parameters and the node identification information through the ADR communication center to obtain the task type information and target ADR node corresponding to the operation request; The execution module is used to generate execution instructions based on the task attribute parameters and send the execution instructions to the target ADR node through the ADR communication center so that the target ADR node can perform the corresponding control operation.

[0070] The distributed ADR node remote management device provided in this application, employing the distributed ADR node remote management method in the above embodiments, can solve the technical problem of low management efficiency under large-scale nodes. Compared with the prior art, the beneficial effects of the distributed ADR node remote management device provided in this application are the same as those of the distributed ADR node remote management method provided in the above embodiments, and other technical features in the distributed ADR node remote management device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0071] This application provides a distributed ADR node remote management and control device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the distributed ADR node remote management and control method in the first embodiment described above. The distributed ADR node remote management and control device is equipped with an ADR communication center.

[0072] The following is for reference. Figure 4 It shows a schematic diagram of a structure suitable for implementing the distributed ADR node remote management device in the embodiments of this application. Figure 4 The distributed ADR node remote management device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0073] like Figure 4 As shown, the distributed ADR node remote control device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 1002 or a program loaded from storage device 1003 into random access memory (RAM) 1004. The random access memory 1004 also stores various programs and data required for the operation of the distributed ADR node remote control device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the distributed ADR node remote control device to communicate wirelessly or wiredly with other devices to exchange data. Although a distributed ADR node remote control device with various systems is shown in the figure, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented alternatively.

[0074] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0075] The distributed ADR node remote management and control device provided in this application, employing the distributed ADR node remote management and control method in the above embodiments, can solve the technical problem of low management and control efficiency under large-scale nodes. Compared with the prior art, the beneficial effects of the distributed ADR node remote management and control device provided in this application are the same as those of the distributed ADR node remote management and control method provided in the above embodiments, and other technical features in this distributed ADR node remote management and control device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0076] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0077] 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.

[0078] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the distributed ADR node remote management method in the above embodiments.

[0079] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory (EPROM, or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, radio frequency (RF), etc., or any suitable combination thereof.

[0080] The aforementioned computer-readable storage medium may be included in the distributed ADR node remote management device; or it may exist independently and not be assembled into the distributed ADR node remote management device.

[0081] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the distributed ADR node remote management device, enable the distributed ADR node remote management device to: Receive an operation request from the client, the operation request being used to request the invocation of a control operation of at least one of the ADR nodes in a preset ADR list; Obtain the task attribute parameters and node identifier information corresponding to the operation request; By parsing the task attribute parameters and the node identifier information, the task type information and the target ADR node corresponding to the operation request are obtained; An execution instruction is generated based on the task attribute parameters and sent to the target ADR node so that the target ADR node performs the corresponding control operation.

[0082] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0083] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0084] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0085] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described distributed ADR node remote management and control method, which can solve the technical problem of low management and control efficiency under large-scale nodes. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the distributed ADR node remote management and control method provided in the above embodiments, and will not be repeated here.

[0086] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for remote management and control of distributed ADR nodes, characterized in that, The method is applied to an ADR communication center, which communicates with clients and multiple ADR nodes respectively. Receive an operation request from the client, the operation request being used to request the invocation of a control operation of at least one of the ADR nodes in a preset ADR list; Obtaining the task attribute parameters and node identification information corresponding to the operation request includes parsing the message header of the operation request to obtain the node identification information, wherein the node identification information includes a unique node identifier and node communication address information; and extracting the task attribute parameters from the data payload field of the operation request. By parsing the task attribute parameters and the node identifier information, the task type information and the target ADR node corresponding to the operation request are obtained; An execution instruction is generated based on the task attribute parameters and sent to the target ADR node so that the target ADR node performs the corresponding control operation.

2. The distributed ADR node remote management and control method as described in claim 1, characterized in that, Before the step of receiving the operation request from the client, the distributed ADR node remote management method further includes: When the ADR communication center is in standby mode, the connection requests initiated by the clients corresponding to each ADR node are obtained; The preset ADR list is constructed based on the connection request.

3. The distributed ADR node remote management and control method as described in claim 2, characterized in that, The step of constructing the preset ADR list based on the connection request includes: Determine the basic node information corresponding to the connection request, wherein the basic node information includes at least a node identifier and a network communication address; Determine whether an ADR list containing the node identifier exists; If so, the address information and online status of the ADR list are updated based on the network communication address to obtain the preset ADR list.

4. The distributed ADR node remote management and control method as described in claim 1, characterized in that, The step of parsing the task attribute parameters and the node identifier information to obtain the task type information and target ADR node corresponding to the operation request includes: Based on the preset node routing table, the target ADR node that is online and connected is matched with the node identification information. Based on a preset task type mapping table and task attribute parameters, task type information is determined, including command execution, file operation, and system information acquisition.

5. The distributed ADR node remote management and control method as described in claim 4, characterized in that, The step of generating an execution instruction based on the task attribute parameters and issuing the execution instruction to the target ADR node so that the target ADR node performs the corresponding control operation includes: When the task attribute parameter is a command execution type, an execution command instruction is generated and sent to the target ADR node so that the target ADR node executes the control command; When the task attribute parameter is a file operation type, a file operation instruction is generated and the file operation instruction is sent to the target ADR node so that the target ADR node performs a file operation action. When the task attribute parameter is of the system acquisition type, a system information acquisition instruction is generated and sent to the target ADR node so that the target ADR node performs a system information query action.

6. The distributed ADR node remote management and control method as described in claim 1, characterized in that, After the step of generating an execution instruction based on the task attribute parameters and issuing the execution instruction to the target ADR node so that the target ADR node performs the corresponding control operation, the distributed ADR node remote control method further includes: Receive the control operation execution results fed back by each of the target ADR nodes; In response to the client's execution result query request, each execution result is fed back to the client.

7. A distributed ADR node remote control device, characterized in that, The device includes: The receiving module is used to receive operation requests from clients, the operation requests being used to request the invocation of control operations of at least one of the ADR nodes in a preset ADR list; The acquisition module is used to acquire the task attribute parameters and node identification information corresponding to the operation request, including parsing the message header of the operation request to obtain the node identification information, wherein the node identification information includes a unique node identifier and node communication address information; and extracting the task attribute parameters from the data payload field of the operation request. The parsing module is used to parse the task attribute parameters and the node identification information through the ADR communication center to obtain the task type information and target ADR node corresponding to the operation request; The execution module is used to generate execution instructions based on the task attribute parameters and send the execution instructions to the target ADR node through the ADR communication center so that the target ADR node can perform the corresponding control operation.

8. A distributed ADR node remote control device, characterized in that, The distributed ADR node remote management device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the distributed ADR node remote management method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the distributed ADR node remote management method as described in any one of claims 1 to 6.

Images