A remote node data management system based on a single port

Abstract

This invention discloses a remote node data management system based on a single port, relating to the field of data analysis. The system comprises a data center layer that generates management instructions containing instruction identifiers, operation parameters, and target node addresses, and sends these instructions to a single-port gateway layer. The single-port gateway layer then distributes the management instructions to the remote node layer. After address matching, the remote nodes execute operations based on the instruction identifiers and operation parameters, generating instruction execution results and collecting operational parameters and environmental monitoring data. The single-port gateway layer preprocesses the feedback data to obtain preprocessed data and determines the management instruction distribution time and the upload time of the preprocessed data and instruction execution results based on the instruction closed-loop process. The data center layer generates new management instructions based on the matching execution status, operation execution status, preprocessed data, and management instructions. This invention improves the real-time performance, accuracy, and closed-loop scheduling capability of remote node data management under single-port conditions.

Description

Technical Field

[0001] This invention relates to the field of data analysis, specifically a remote node data management system based on a single port. Background Technology

[0002] As the coal industry continues to develop towards intelligent, unmanned, and minimally staffed operations, a large number of remote node devices have been deployed in underground mine work areas, coal conveying systems, substations, and surface coal yards to perform tasks such as status monitoring, environmental sensing, equipment inspection, fault early warning, and remote control. To ensure the stable operation of these remote nodes, it is usually necessary to remotely manage them and synchronously collect their operating parameters, environmental parameters, and production data to support scheduling decisions, safety supervision, and operation and maintenance management.

[0003] However, existing solutions typically implement remote node management and data acquisition as relatively independent functions, often relying on multiple communication ports or transmission links to complete command interaction and data transmission. This not only leads to low port resource utilization, increased system deployment costs and operational complexity, but also easily causes problems such as insufficient communication link stability, delayed command transmission, untimely data upload, and asynchrony between management and acquisition in complex environments such as underground high interference and coal yard high dust. Furthermore, facing the application demands of a continuously increasing number of remote nodes and expanding equipment types, existing solutions also have shortcomings in terms of compatibility, scalability, and continuous adaptation capabilities, making it difficult to simultaneously meet the comprehensive requirements of communication reliability, real-time management, data integrity, and ease of operation and maintenance in complex industrial scenarios. Summary of the Invention

[0004] The purpose of this invention is to provide a remote node data management system based on a single port to solve the problems raised in the prior art.

[0005] To achieve the above objectives, the present invention provides the following technical solution: A remote node data management system based on a single port, comprising a data center layer, a single-port gateway layer, and a remote node layer; The data center layer is the decision-making and management center of this system. It is used to generate management instructions for remote nodes and send them to the corresponding remote nodes through the single-port gateway layer. Specifically, initial management instructions can be generated from preset management strategies, manual control requirements, or historical operating rules; The new management instructions are generated by combining the preprocessed data uploaded by the data center layer based on the single-port gateway layer and the instruction execution results returned by the remote node layer; The data center layer not only undertakes the functions of generating and issuing instructions, but also the functions of interpreting, comparing and adjusting feedback information. That is, when a remote node successfully matches and executes a management instruction, the data center layer can compare the pre-processed data with the operation parameters in the management instruction, and generate a new adjusted management instruction based on the preset parameter range. When a node address matching failure or an operation execution failure occurs, the data center layer can generate a new management instruction with the target node address corrected or a new management instruction resent, thereby enabling the data center layer to continuously correct the management process based on feedback results. The single-port gateway layer is the intermediate processing layer and single-port transmission core layer of this system. It is used to forward management commands, receive feedback data, and preprocess data between the data center layer and the remote node layer. The single-port gateway layer receives management commands from the data center layer on one hand, and feedback data from the remote node layer on the other hand. It also preprocesses the operating parameters and environmental monitoring data in the feedback data to obtain preprocessed data. The single-port gateway layer undertakes functions such as instruction correspondence, status connection, closed-loop scheduling, and data processing, enabling the transmission of management instructions and data feedback under single-port communication conditions to form a unified process. The remote node layer is the instruction execution layer and raw data generation layer of this system. It is used to receive management instructions forwarded by the single-port gateway layer, and complete the corresponding operations according to the management instructions. At the same time, it collects running parameters and environmental monitoring data during the execution process, and returns the relevant results as feedback data to the single-port gateway layer. The remote node layer is not only the main body for implementing management instructions, but also the direct source of raw status data and environmental data in the closed-loop feedback; In this system, every operation will record a timestamp so that the system can extract the timestamp for corresponding time difference analysis.

[0006] The data center layer is used to generate management commands and send them to the single-port gateway layer; Furthermore, the structure of the management instruction includes an instruction identifier, operation parameters, and a target node address; the instruction identifier is used to indicate the type of management instruction. Management instructions are dedicated control information used in the remote node management process. They include three parts: instruction identifier, operation parameters, and target node address. The instruction identifier indicates the management type to which the management instruction belongs, the operation parameters indicate the specific parameters to be executed under the management type, and the target node address indicates the remote node object corresponding to the management instruction. This allows the remote node to complete the matching based on the target node address and, after successful matching, execute the corresponding operation based on the instruction identifier and operation parameters. Specifically, the instruction identifier is the type identifier field in the management instruction, which is used to indicate the category of the management instruction so that the remote node can identify what kind of management operation needs to be performed. The management operation can correspond to parameter configuration, fault diagnosis, remote retransmission, node start / stop control or other remote management behaviors. The role of the instruction identifier is to define the function of the management instruction so that the remote node can first determine the nature of the instruction after receiving the management instruction and then call the corresponding execution logic. Operation parameters are the content parameter fields in management instructions, used to represent the specific execution content or control quantity corresponding to the instruction identifier, so that the remote node can perform specific operations according to the operation parameters after identifying the instruction type; The target node address is the addressing field in the management command, used to indicate the remote node to which the management command is targeted. After receiving the management command, the remote node layer first reads the target node address and matches the target node address with its own address. The purpose of the target node address is to limit the execution target of the management command and prevent the management command from being mistakenly executed by non-target nodes under single-port, single-link transmission conditions. The remote node layer reads the target node address, matches the target node address with the node address, and generates the instruction execution result; The execution result of the instruction includes the management instruction and the execution status corresponding to the management instruction. The execution status includes the operation execution status and the matching execution status.

[0007] Furthermore, the matching includes: When the target node address matches the node address, the matching execution status is considered a successful match. The remote node corresponding to the target node address executes the operation according to the instruction identifier and operation parameters, and generates the corresponding operation execution status according to preset rules. The operation execution status includes execution success and execution failure. When the target node address and the node address do not match, the matching execution status is considered a matching failure, and the operation execution status is considered an execution failure.

[0008] Specifically, the preset rules include operation completion determination rules, target status determination rules, and abnormal status determination rules. When the target action corresponding to the instruction identifier has been completed, and the parameter configuration value, node start / stop status, or working mode corresponding to the operation parameters meets the preset requirements, and no fault status, communication connection abnormality, or power status abnormality occurs, the operation execution status corresponding to the operation is determined to be executed successfully. When the target action corresponding to the instruction identifier has not been completed, or the parameter configuration value, node start / stop status, or working mode corresponding to the operation parameters does not meet the preset requirements, or a fault status, communication connection abnormality, or power status abnormality occurs during execution, the operation execution status corresponding to the operation is determined to be executed failed. Subsequently, the operation execution status is associated with the matching execution status to generate the corresponding instruction execution result. Furthermore, the process by which the data center layer generates new management instructions based on the uploaded preprocessed data and the results of instruction execution includes: The data center layer reads the matching execution status and the corresponding operation execution status; When the matching execution status is "match successful" and the operation execution status is "execution successful", the preprocessed data is compared with the operation parameters in the management instruction, and new operation parameters in the management instruction are generated according to the preset parameter range of the preprocessed data and the corresponding operation parameters in the management instruction. When the matching execution status is "match failed", a new management instruction with the target node address corrected is generated based on the target node address; When the matching execution status is "match successful" and the operation execution status is "execution failed", a new management instruction is generated based on the instruction identifier and operation parameters in the management instruction.

[0009] Specifically, the data center layer first reads two types of status information: one is the matching execution status, and the other is the operation execution status corresponding to the matching execution status. The matching execution status reflects whether the management command was correctly delivered to the expected target node, i.e., whether the target node address matches the actual execution node; the operation execution status reflects whether the target node has completed the corresponding operation according to the management command after the address matching is completed. These two states are the direct basis for the data center layer to make subsequent decisions. After reading these two states, the data center layer will first determine which execution scenario this feedback belongs to, and then enter the corresponding processing branch; When the matching execution status is "match successful" and the operation execution status is "execution successful", it means that the management command has accurately reached the target node and the target node has completed the operation required by the command. In this case, the data center layer no longer focuses on address correction or retransmission issues, but enters the stage of fine-tuning based on the execution result. At this time, the data center layer will compare the preprocessed data uploaded by the single-port gateway layer with the original operation parameters in this round of management command. The comparison is not a general comparison of two sets of data, but an item-by-item analysis of the specific parameters corresponding to the management objectives. That is, it is to determine whether the node status, operation feedback or environmental feedback after execution has reached the expected range, and whether the current parameter settings are still suitable for subsequent operation. For each parameter that needs to be compared, the data center layer reads the corresponding preset parameter range and determines the relationship between the actual state reflected by the preprocessed data and the preset parameter range. If the actual feedback indicates that the current parameter is already in a reasonable range, the operation parameters in the new management instruction can remain at their original values ​​or be slightly modified. If the actual feedback indicates that there is still a deviation between the current parameter and the target state, the data center layer will recalculate or adjust the parameter according to the preset parameter range and write the adjusted result into the operation parameter in the new management instruction. The new management instructions generated are essentially a continuation optimization of the successful execution results of the previous round. Their purpose is to make the subsequent operating state of the node further approach the predetermined goal, rather than simply repeating the original control content. In other words, this branch reflects the dynamic correction mechanism after successful execution. That is, based on the execution already taking effect, the parameters for the next round are reset using feedback data, so that the management process has continuous adjustment capabilities. When the matching execution status is "match failed", the problem faced by the data center layer is no longer whether the parameters are appropriate, but that there is a deviation in the instruction addressing object; although the management instruction has entered the transmission process, the feedback from the remote node side indicates that the target node address in the current instruction has not been correctly matched with the actual node address, so this round of management instructions has not entered the effective execution stage. In this scenario, the data center layer shifts its focus to correcting the target node address in the instruction. The specific process can be understood as follows: the data center layer first identifies that the root cause of the instruction execution failure in this round lies in the address matching process. Then, based on the target node address in the original management instruction, and combined with the node address information, node mapping relationship, node status information, or historical feedback results stored in the system, the target node address is corrected. This operation essentially uses the original target node address as a reference, modifying its address field to generate a new, more accurately addressed management instruction. In this new instruction, the instruction identifier and operational parameters typically retain the original management purpose. The main change is the re-determination of the target node address, ensuring that subsequent instructions are received and executed by the correct remote node. This branch embodies the address correction mechanism, aiming to guarantee that management instructions are accurately delivered to the target object, establishing the subsequent management loop based on the correct node correspondence.

[0010] When the matching execution status is "match successful" and the operation execution status is "execution failed," it means that the management command has been accurately sent to the target node, and the node has also recognized that the command should be executed by itself, but the expected result was not achieved in the actual execution process. At this time, there is no problem at the address level, and the data center layer does not need to correct the target node address. At the same time, since the operation was not successfully completed, the preprocessed data is usually not suitable as a direct basis for parameter optimization, so it will not be prioritized to enter the parameter adjustment branch. At this point, the focus of the data center layer is to generate new management instructions for resending. In a more complete understanding, the resending process means that the data center layer has identified the execution failure as an intermediate state that needs to be remedied. Therefore, the new management instructions serve to supplement the execution, trigger it again, and implement it again, rather than change the management goal itself. This branch reflects the execution remediation mechanism, whose core function is to maintain the continuity of management tasks until the target node completes the predetermined operation.

[0011] The single-port gateway layer receives management commands sent by the data center layer, and also receives feedback data and command execution results sent by the remote node layer; the feedback data is preprocessed to obtain preprocessed data; Furthermore, the process by which the single-port gateway layer preprocesses the feedback data to obtain preprocessed data includes: The single-port gateway layer performs standardization processing on the received operating parameters and environmental monitoring data. This standardization processing includes: Convert analog data in environmental monitoring data into digital data, and convert non-standardized data formats in operating parameters and environmental monitoring data into JSON format; The standardized operating parameters and environmental monitoring data are deduplicated, denoised, and completed. The standardized operating parameters and environmental monitoring data are then encrypted to obtain preprocessed data.

[0012] Specifically, standardization is the starting point of the entire preprocessing process, and its purpose is to unify the raw feedback data into a data format that can be directly recognized and processed by the system. The conversion of analog data to digital data in environmental monitoring data refers to the process of converting continuous electrical signals, analog signals, or other raw analog outputs collected by sensors into digital quantities with clear numerical meanings after analog-to-digital conversion. For example, temperature, humidity, dust concentration, harmful gas concentration, and vibration status may initially appear as analog signals such as voltage, current, frequency, or amplitude. These signals are not suitable for direct comparison and analysis at the data center layer, so they need to be converted into corresponding numerical results first. After digitizing the simulated data, it is also necessary to convert the non-standardized data formats in the operating parameters and environmental monitoring data into JSON format. Non-standardized data formats can be understood as the original data expression forms generated by different nodes, modules, and sensors in their own ways. For example, some data may be simple key-value pairs, some may be string concatenation results, some may use manufacturer-defined message structures, and some may just be a set of field values ​​arranged in sequence. This lack of uniformity in format will complicate subsequent data parsing, field extraction, parameter comparison, and system integration. Converting them to JSON format is essentially about establishing a structured expression for each type of data, so that each operating parameter and environmental monitoring data can be organized according to the correspondence between field names and field values. After JSON formatting, the hierarchical relationship of the data, the ownership of fields, the meaning of parameters, and the content boundaries are clearer, which facilitates uploading at the single-port gateway layer and also facilitates parsing, comparison, and calling at the data center layer; The purpose of deduplication is to eliminate duplicate data items, preventing redundant records caused by repeated reporting, collection, or caching within the same time period from affecting subsequent judgments. In actual operation, the same remote node may upload the same or highly similar data due to communication retransmission, overlapping sampling periods, or repeated cache readings. If this duplicate data is not processed, the data center layer's judgment of the node status will deviate from the actual situation. After deduplication, what remains are data records that are effectively distinguishable in terms of time, content, and source, thereby improving the validity of the data. The purpose of noise reduction is to weaken or eliminate abnormal data components introduced by acquisition errors, environmental interference, instantaneous fluctuations, communication disturbances, or equipment jitter. During the acquisition process, operating parameters and environmental monitoring data are usually affected by various factors, causing some values ​​to jump, drift, have discrete deviations, or experience short-term abnormal fluctuations. If these abnormal components are directly used for subsequent comparisons, it is easy for the data center layer to misjudge the current node status or incorrectly adjust the operating parameters. Therefore, noise reduction plays a role in smoothing data, filtering interference, and retaining effective trends, so that the processed data can better reflect the true status of remote nodes and the field environment. Data completion processing addresses issues such as missing, incomplete, or incomplete data. During remote node feedback, data uploads may contain missing parameters, discontinuous time data, or incomplete structures due to reasons such as acquisition failures, temporary sensor malfunctions, lost communication packets, or unsuccessful field writing. The purpose of completion processing is to restore the complete structure of these data based on existing data relationships and system rules. Its focus is on completing necessary fields, adding key status items, and standardizing record formats, thereby ensuring sufficient readability and comparability of each data entry during subsequent processing. After completion, the data center layer no longer needs to perform additional checks on missing fields when reading preprocessed data, allowing it to be used more directly for status analysis and instruction generation. After deduplication, noise reduction, and completion, the single-port gateway layer further encrypts the standardized operating parameters and environmental monitoring data. The encryption process does not alter the data content itself, but rather protects the security of the data during transmission and storage, preventing unauthorized reading, tampering, or exploitation of node operating status, environmental monitoring results, and related parameter information in the transmission link. Since this system operates within a multi-stage transmission environment between remote nodes, the single-port gateway layer, and the data center layer, feedback data not only serves as status feedback but may also directly influence the generation of subsequent management commands; therefore, its integrity and confidentiality are of paramount importance. Through encryption, the single-port gateway layer encapsulates the cleaned and organized data into securely uploadable data results, ensuring both structural consistency and security for subsequent data transmission. The single-port gateway layer also includes an instruction closed-loop process. The single-port gateway layer determines the issuance time and upload time based on the instruction closed-loop process. Based on the issuance time, the management instruction is issued to the remote node layer, and based on the upload time, the preprocessed data and instruction execution results are uploaded to the data center layer. Furthermore, the instruction closed-loop process includes: Using the same instruction identifier and target node address as the corresponding condition, management instructions, instruction execution results, operating parameters, environmental monitoring data, and preprocessed data are matched according to the aforementioned corresponding condition; The single-port gateway layer obtains the number of instruction execution results and the number of preprocessed data corresponding to the management instruction, and uses the sum of the number of instruction execution results and the number of preprocessed data as the closed-loop feedback quantity; Acquire instruction waiting time difference, result waiting time difference, and data waiting time difference; The maximum value between the result waiting time difference and the data waiting time difference is taken as the feedback waiting time difference; the ratio of the feedback waiting time difference to the instruction waiting time difference is taken as the closed-loop scheduling value. The preset feedback quantity and preset scheduling threshold are set, and the instruction closed-loop process includes the preset feedback quantity, preset scheduling threshold, closed-loop feedback quantity, and closed-loop scheduling value.

[0013] Furthermore, the process of issuing management instructions to the remote node layer according to the issuance time, and uploading the preprocessed data and instruction execution results to the data center layer according to the upload time includes: The system acquires the current time in real time. When the number of closed-loop feedbacks is less than the preset number of feedbacks and the closed-loop scheduling value is greater than or equal to the preset scheduling threshold, it sends the preprocessed data and instruction execution result corresponding to the management instruction to the data center layer using the current time as the upload time; and it sends the management instruction to the remote node layer using the time after the preset waiting time as the distribution time. When the number of closed-loop feedbacks is greater than or equal to the preset number of feedbacks, and the closed-loop scheduling value is less than the preset scheduling threshold, the management instruction is sent to the remote node layer using the current time as the sending time; and the preprocessed data and instruction execution result corresponding to the management instruction are sent to the data center layer using the time after the preset waiting time as the upload time; in other cases, the sending time and upload time are determined according to the preset method. Furthermore, the process of obtaining the instruction waiting time difference, result waiting time difference, and data waiting time difference includes: The time difference between the generation time of the management instruction and the current time is used as the instruction waiting time difference; the time difference between the generation time of the execution result of the management instruction and the current time is used as the result waiting time difference. The latest time between the acquisition time of the operating parameters corresponding to the management command and the acquisition time of the corresponding environmental monitoring data is used as the feedback reference time. The time difference between the preprocessed data generation time corresponding to the management instruction and the feedback reference time is taken as the preprocessing time difference; When the preprocessing time difference is less than or equal to the preset time threshold, the time difference between the preprocessed data generation time corresponding to the management instruction and the current time is taken as the data waiting time difference. When the preprocessing time difference is greater than the preset time threshold, the time difference between the preprocessed data generation time corresponding to the management instruction and the current time is taken as the intermediate time difference, and the sum of the intermediate time difference and the preprocessing time difference is taken as the data waiting time difference.

[0014] Specifically, the essence of this process is that the single-port gateway layer establishes a closed-loop scheduling link around the same management command, from the issuance of the command to the execution of the node and then to the uploading of the results and data feedback. By uniformly calculating the various objects, quantitative relationships and time relationships in the link, it determines whether to prioritize issuing the management command to the remote node or uploading the preprocessed data and command execution results to the data center layer at the current moment. Since the single-port gateway layer is in the middle and the transmission resources have single-port characteristics, it is necessary to coordinate and arrange the downlink command transmission and uplink feedback transmission within the same time period. The first step is to establish the corresponding relationship: After receiving management instructions from the data center layer and receiving instruction execution results, operating parameters, and environmental monitoring data from the remote node layer, the single-port gateway layer first merges them according to unified corresponding conditions. The second step is to count the number of closed-loop feedbacks after completing the corresponding steps: For a given management command, the single-port gateway layer will count two quantities: the number of command execution results corresponding to the management command and the number of preprocessed data corresponding to the management command. The number of command execution results reflects how many execution status feedbacks have been generated around the management command. The number of preprocessed data reflects how many data results have been generated around the management command and are available for uploading; the single-port gateway layer adds these two numbers together to get the number of closed-loop feedbacks; the significance of this number is to reflect how much effective feedback content has been accumulated in the feedback chain for the current management command; the smaller the number of closed-loop feedbacks, the less sufficient the feedback accumulation related to the management command is; the larger the number of closed-loop feedbacks, the more sufficient the feedback content related to the management command is. The third step is to calculate the three waiting time differences: instruction waiting time difference, result waiting time difference, and data waiting time difference. These three time differences reflect the waiting level of various objects in the current closed-loop process from different perspectives. The instruction waiting time difference is calculated by comparing the generation time of a management instruction with the current time, and using the time difference between the two as the instruction waiting time difference. This means how long the management instruction has been waiting since its generation, and how long the accumulated time before further processing is completed. The result waiting time difference is calculated by comparing the generation time of the instruction execution result with the current time, and using the time difference between the two as the result waiting time difference. This means how long the execution result has been stuck since its generation, and how long the accumulated time before it has been uploaded or utilized is. The specific process for calculating the data waiting time difference is as follows: First, select the latest time from the collection time of the operating parameters and the collection time of the environmental monitoring data corresponding to the management instruction as the feedback reference time; The latest time is taken because the operating parameters and environmental monitoring data together constitute the feedback data. Only when the last part of the data is also available can the feedback source data be considered to have a basis for preprocessing. The preprocessed data generation time corresponding to the management instruction is compared with the feedback baseline time to obtain the preprocessing time difference. This time difference reflects how long it takes from the arrival of the last piece of raw feedback data to the actual formation of the preprocessed data. This time difference essentially reflects the processing time of the preprocessing stage itself. After obtaining the preprocessing time difference, the single-port gateway layer further determines the data waiting time difference based on the relationship between the time difference and the preset time threshold. If the preprocessing time difference is less than or equal to the preset time threshold, it indicates that the preprocessing process is within a reasonable range and there is no significant delay. In this case, the time difference between the preprocessed data generation time and the current time is directly used as the data waiting time difference. The data waiting time difference at this time only reflects the time it takes to upload the data after it is generated. If the preprocessing time difference is greater than the preset time threshold, it indicates that the preprocessing stage itself has already consumed a significant amount of time. In this case, when the single-port gateway layer calculates the data waiting time difference, it will take this additional time into account, that is, add the preprocessing time difference on top of the original data waiting time difference. The result of this processing is that once the preprocessing stage itself is too slow, the corresponding data waiting degree will be amplified and reflected, so that the scheduling mechanism can perceive this delay and avoid long-term backlog of preprocessed data. The fourth step is to form a closed-loop scheduling value based on the three waiting time differences: The single-port gateway layer first compares the result waiting time difference with the data waiting time difference, taking the larger value as the feedback waiting time difference. The logic is that the waiting pressure on the feedback link mainly comes from two types of objects: instruction execution results and preprocessed data. The object that waits longer better represents the urgency of the current feedback direction; therefore, the larger value is used to summarize the waiting state on the feedback side. Then, the feedback waiting time difference is divided by the instruction waiting time difference to obtain the closed-loop scheduling value. The closed-loop scheduling value essentially reflects the relative relationship between the waiting pressure on the feedback side and the waiting pressure on the instruction side. If this ratio is large, it indicates that the waiting level on the feedback side is higher than that on the instruction side, and feedback upload has higher priority; if this ratio is small, it indicates that the waiting level on the instruction side is higher, and issuing management instructions has higher priority. The fifth step is to compare the calculation result with the preset threshold and determine whether the current time should be used as the upload time or the download time. Threshold parameters are the preset feedback quantity and the preset scheduling threshold. The preset feedback quantity is used to determine whether the feedback content in the current closed loop has accumulated sufficiently, and the preset scheduling threshold is used to determine whether the feedback priority has reached the level of switching to upload priority. The single-port gateway layer does not only look at one indicator, but combines the closed loop feedback quantity and the closed loop scheduling value to make a joint judgment. When the number of closed-loop feedbacks is less than the preset number of feedbacks, and the closed-loop scheduling value is greater than or equal to the preset scheduling threshold, it indicates that the total amount of feedback content related to the current management command is not large, but the waiting level of the already formed feedback content is high, and the pressure on the feedback side has reached the level that needs to be prioritized; the single-port gateway layer determines the current time as the upload time and prioritizes uploading the preprocessed data and command execution results corresponding to the management command to the data center layer; To avoid a single port simultaneously handling both upload and download tasks, the gateway does not immediately issue management commands. Instead, it determines the time after a preset waiting period as the download time and then sends the management commands to the remote node layer at that download time. In this branch, the scheduling strategy is to upload first and then download. The reason is that although the number of feedbacks has not yet reached a large scale, the feedback waiting level is already high, and uploading has a more immediate requirement. When the number of closed-loop feedbacks is greater than or equal to the preset number of feedbacks, and the closed-loop scheduling value is less than the preset scheduling threshold, it indicates that the feedback content related to the current management command has accumulated to a certain extent. At the same time, the waiting advantage of the feedback side relative to the command side is not obvious, and it can even be understood that the waiting demand of the command side is stronger. The single-port gateway layer determines the current time as the distribution time and prioritizes the distribution of the management command to the remote node layer so that the node can enter the next round of execution process as soon as possible. The time after the preset waiting time is determined as the upload time, and the preprocessed data and command execution results corresponding to the management command are sent to the data center layer at the upload time. That is, in this branch, the scheduling strategy is to send down first and then upload. The reason is that although there is a lot of feedback content at this time, the relative urgency of the feedback side is not enough to meet the demand for sending down the command. Therefore, priority should be given to ensuring the start of the next round of command execution.

[0015] The remote node layer is used to receive and execute management commands, obtain command execution results, and simultaneously collect operating parameters and environmental monitoring data, and use the operating parameters and environmental monitoring data as feedback data; at the same time, the feedback data and command execution results are sent to the single-port gateway layer. In this invention, a remote node refers to a field device or terminal deployed in areas such as underground mining areas, coal conveying systems, substations, and surface coal yards, capable of receiving and executing management commands, and simultaneously collecting its own operating status and the environmental status of its surrounding area. Remote nodes possess three basic capabilities: First, it has the capability to receive and execute commands, that is, to receive management commands forwarded by a single-port gateway layer, and to perform parameter configuration, fault diagnosis, remote restart or state switching according to the command identifier, operation parameters and target node address; Second, it has the ability to sense state, which means collecting the operating parameters of this node during the execution of management instructions; Thirdly, it has environmental perception capabilities, which means synchronously collecting the temperature, humidity, dust concentration, harmful gas concentration, and vibration status of the area where the node is located, and sending this information, along with the command execution results, as feedback data.

[0016] Specifically, when a remote node performs an operation based on the instruction identifier and operation parameters, the node's internal controller calls the local status interface and external sensor interface to synchronously read the operating parameters and environmental monitoring data in a preset sampling period or event-triggered manner. A collection timestamp is added to each collection result, and then the collection result is associated with the instruction execution result corresponding to the management instruction to form feedback data and sent to the single-port gateway layer. Real-time data acquisition refers to continuously acquiring the current status according to the time granularity set by the system during the execution of management instructions, or triggering data acquisition immediately when events such as parameter changes, status switching, fault occurrence, or communication anomalies occur. More specifically, the acquisition of operating parameters mainly comes from the internal status reading of the remote node itself; the remote node reads the current configuration parameters, start / stop status, working mode, fault flag, network connection status and power supply status in real time through its local control board, embedded processor, driver module, power management module, communication module or device register; This part of the data does not necessarily rely on external environmental sensors, but rather on readings of the device's own control status, execution status, and health status; The environmental monitoring data is mainly collected from environmental sensors installed on or around the remote node, such as temperature and humidity sensors, dust sensors, gas sensors, and vibration sensors. While executing management commands, the remote node periodically reads the detection values ​​from these sensors, encapsulates the detection values ​​together with its own operating parameters, and uploads them.

[0017] Furthermore, when a remote node executes an operation based on the instruction identifier and operation parameters, it also includes: The remote node collects the operating parameters and environmental monitoring data in real time. The operating parameters include the parameter configuration values ​​of the remote node when executing management commands, the node start / stop status, working mode, fault status, communication connection status, and power status. The environmental monitoring data includes temperature, humidity, dust concentration, harmful gas concentration, and vibration status in the area where the remote node is located.

[0018] Specifically, the parameter configuration value refers to the current value of various control parameters that are set, invoked, or adjusted by the remote node according to the management instructions, which is used to characterize the configuration status of the node under the current task; for example, the sampling period, alarm threshold, upload frequency, sensitivity level, working level, or action parameters of the execution component of a monitoring node can all be considered parameter configuration values. The node start / stop status refers to information about whether the remote node is currently in a state such as starting, stopping, standby, restarting, or shutting down. It is used to characterize whether the node has responded to management commands and is in an effective working state; for example, one of the four states of starting, stopping, standby, and restarting; this data is usually given directly by the node's operating system status, device master control status, or power enable status. The working mode refers to the current business operation mode or task execution mode of the remote node, which reflects what type of function the node is currently performing. The operating modes include monitoring mode, inspection mode, alarm mode, low power mode, maintenance mode, and remote control mode. The fault status is information about whether there are any abnormalities and the types of abnormalities during the execution of management commands or normal operation of remote nodes, which is used to characterize the current health status of the nodes; The fault status can be formed by the node's internal self-test results, fault codes, module abnormality flags, port abnormality flags, sensor failure flags, or execution failure results; the fault status can include no fault, communication failure, sensor failure, execution component failure, power supply abnormality failure, etc. The communication connection status is information on whether the current communication link between the remote node and the single-port gateway layer is connected and its connection quality. It is used to characterize whether the node has the ability to upload feedback data and receive new management commands normally. The communication connection status is reflected in the online, offline, connection interruption, weak connection, and connection recovery status, and link quality parameters can also be attached. Power status is the current working status information of the power supply system of the remote node, which is used to characterize whether the device has the ability to operate continuously; it can include power on, power off, battery powered, mains powered, backup power powered, insufficient power, abnormal voltage, etc.; if the remote node is a mobile device or a device with a backup power supply, this parameter can further include data such as remaining power and charging status, which can be used to support remote start-up and maintenance management. For environmental monitoring data, specifically, temperature refers to the thermal state detection value of the air environment or the environment around the equipment in the area where the remote node is located. It is used to characterize the degree of hotness or coldness on site and is usually expressed in degrees Celsius. Humidity refers to the measured value of moisture content in the air in the area where a remote node is located. It is used to characterize the humidity of the environment and is usually expressed as relative humidity. Dust concentration is the content of suspended dust particles in a unit volume of air in the area where the node is located, and is used to reflect the degree of dust pollution in coal yards, coal conveying systems or underground work areas. The concentration of hazardous gases is the content of target hazardous gases in the air in the area where the node is located, which is used to reflect the enrichment degree of hazardous gases such as methane and carbon monoxide. Vibration status refers to the intensity, frequency, or abnormal vibration of mechanical vibration in the area where the node is located or the foundation on which the node is installed, and is used to reflect the stability of equipment operation or the state of on-site disturbance.

[0019] Compared with the prior art, the beneficial effects of the present invention are: 1. This invention constructs a unified data management architecture by collaboratively building the data center layer, single-port gateway layer and remote node layer, so that the issuance of management instructions, node execution, feedback collection, data preprocessing and the generation of new management instructions form a continuous closed loop, which improves the integration of remote node management and data collection, reduces the time sequence disconnection problem caused by the dispersion of management links, and thus improves the real-time management and operational reliability in complex industrial scenarios.

[0020] 2. This invention sets up a closed-loop instruction process in the single-port gateway layer and performs dynamic scheduling by combining the number of closed-loop feedbacks, the closed-loop scheduling value, the issuance time, and the upload time. This enables instruction transmission and feedback upload under single-port conditions to be coordinated and allocated according to the actual waiting state, thereby improving the utilization efficiency of single-port communication resources, reducing the probability of instruction congestion, feedback lag, and link conflicts, and thus enhancing the communication stability of the system in complex environments.

[0021] 3. This invention standardizes, deduplicates, reduces noise, completes, and encrypts operating parameters and environmental monitoring data. It also generates new management instructions for parameter adjustment, address correction, or retransmission by matching the execution status with the operation execution status. This makes the uploaded data more available and secure, and enables subsequent management processes to adaptively correct for different execution results. As a result, it improves the accuracy, continuous adaptability, and ease of operation and maintenance of remote node data management. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of the structure of a remote node data management system based on a single port according to the present invention. Detailed Implementation

[0023] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0024] Example: Figure 1 As shown, the present invention provides a remote node data management system based on a single port, the system comprising a data center layer, a single-port gateway layer, and a remote node layer; In this embodiment, the data center layer is deployed on the management-side cluster, the single-port gateway layer is deployed on the control node in the controlled-side cluster, and the remote node layer includes multiple controlled nodes in the controlled-side cluster. The management-side cluster and the controlled-side cluster are network isolated based on security management policies. The management-side cluster cannot directly access the controlled nodes in the controlled-side cluster. The controlled-side cluster opens a single control port to the outside world through the control node. The data center layer establishes a communication connection with the control node through the single control port, and the control node forwards management commands to the corresponding controlled nodes to achieve unified management of multiple remote nodes in the controlled-side cluster. The data center layer is used to generate management commands and send them to the single-port gateway layer; The structure of a management instruction includes an instruction identifier, operation parameters, and a target node address; the instruction identifier indicates the type of management instruction. The remote node layer reads the target node address, matches the target node address with the node address, and generates the instruction execution result; In this embodiment, after receiving management instructions from the data center layer, the control node first parses the target node address and distributes the management instructions to one or more corresponding controlled nodes according to the node mapping relationship maintained within the controlled cluster. Each controlled node then matches the received target node address with its own node address and executes the corresponding operation based on the instruction identifier and operation parameters; the instruction execution results generated by each controlled node are returned to the control node, which summarizes them and sends them to the data center layer; The execution result of the instruction includes the management instruction and the execution status corresponding to the management instruction. The execution status includes the operation execution status and the matching execution status.

[0025] Furthermore, the matching includes: When the target node address matches the node address, the matching execution status is considered a successful match. The remote node corresponding to the target node address executes the operation according to the instruction identifier and operation parameters, and generates the corresponding operation execution status according to preset rules. The operation execution status includes execution success and execution failure. In this embodiment, the operations include node start / stop control, service restart control, working mode switching, parameter configuration distribution, task loading, and fault reset; When the control node parses the target node address and determines the corresponding multiple controlled nodes, the control node distributes the same management instruction to the corresponding multiple controlled nodes so that the multiple controlled nodes execute the corresponding operation and generate the operation execution status respectively; When the target node address and the node address do not match, the matching execution status is considered a matching failure, and the operation execution status is considered an execution failure.

[0026] Furthermore, the process by which the data center layer generates new management instructions based on the uploaded preprocessed data and the results of instruction execution includes: The data center layer reads the matching execution status and the corresponding operation execution status; When the matching execution status is "match successful" and the operation execution status is "execution successful", the preprocessed data is compared with the operation parameters in the management instruction, and new operation parameters in the management instruction are generated according to the preset parameter range of the preprocessed data and the corresponding operation parameters in the management instruction. When the matching execution status is "match failed", a new management instruction with the target node address corrected is generated based on the target node address; When the matching execution status is "match successful" and the operation execution status is "execution failed", a new management instruction is generated based on the instruction identifier and operation parameters in the management instruction.

[0027] In this embodiment, the retransmitted new management instructions are still sent to the corresponding controlled nodes via the control node; after receiving the instruction execution results returned by each controlled node, the control node summarizes the matching execution status, operation execution status and node running status of each controlled node to support the data center layer in performing unified retransmission control, unified status confirmation and unified fault handling for one or more remote nodes in the controlled cluster. Taking the coal yard as the remote monitoring scenario, a data center layer, a single-port gateway layer, and a remote node layer are set up; the remote node layer includes three remote nodes, with addresses A101, A102, and A103 respectively. At 08:30:00, the data center layer generates an initial management command. The command identifier is set to parameter configuration type, the target node address is set to A102, and the operation parameters are set to a sampling period of 2 seconds, an upload period of 10 seconds, and a dust alarm threshold of 8.0 mg / m³. 3 The alarm threshold for harmful gases is 35 ppm. The initial management command is first sent from the management side cluster to the control node G101 in the controlled side cluster, and then forwarded by the control node G101 to the controlled node corresponding to the target node address A102 via the control port P1001. In other management tasks, the target node address in the management command generated by the data center layer can also correspond to multiple controlled nodes after being resolved by the control node G101. The control node G101 then forwards the same management command to the corresponding multiple controlled nodes, so as to achieve unified control of multiple remote nodes through a single control port. The single-port gateway layer receives management commands sent by the data center layer, and also receives feedback data and command execution results sent by the remote node layer; the feedback data is preprocessed to obtain preprocessed data; Furthermore, the process by which the single-port gateway layer preprocesses the feedback data to obtain preprocessed data includes: The single-port gateway layer performs standardization processing on the received operating parameters and environmental monitoring data. This standardization processing includes: Convert analog data in environmental monitoring data into digital data, and convert non-standardized data formats in operating parameters and environmental monitoring data into JSON format; The standardized operating parameters and environmental monitoring data are deduplicated, denoised, and completed. The standardized operating parameters and environmental monitoring data are then encrypted to obtain preprocessed data.

[0028] The single-port gateway layer also includes an instruction closed-loop process. The single-port gateway layer determines the issuance time and upload time based on the instruction closed-loop process. Based on the issuance time, the management instruction is issued to the remote node layer, and based on the upload time, the preprocessed data and instruction execution results are uploaded to the data center layer. In this embodiment, after receiving the management instruction at 08:30:01, the single-port gateway layer establishes a correspondence between the instruction identifier and the target node address, and temporarily stores the management instruction. The control node G101 determines the controlled node corresponding to the target node address A102 based on the node mapping relationship within the controlled cluster, and verifies the target node address when necessary. When the target node address corresponds to multiple controlled nodes after resolution, the control node G101 establishes a correspondence between the same management command and multiple controlled nodes respectively, so as to forward and summarize the execution results returned by each controlled node in a unified manner. Since there is only one management instruction corresponding to A102 in this round, the initial value of the number of instruction execution results of this management instruction is 0, the initial value of the number of preprocessed data is 0, and the number of closed-loop feedback is 0. In this embodiment, the preset feedback quantity is set to 2, which can be set to 2 to 4 depending on the expected number of data categories returned in each round; The preset scheduling threshold is set to 1.20, which can be adjusted to 1.00 to 1.50 depending on the busyness of different links; The preset waiting time is set to 3 seconds. When the port speed is high, it can be set to 1 to 2 seconds. When the link jitter is large, it can be set to 3 to 5 seconds. The preset time threshold is set to 3 seconds to identify whether there is a significant delay in the preprocessing stage. When the amount of data is larger, it can be increased to 4 to 5 seconds. Furthermore, the instruction closed-loop process includes: Using the same instruction identifier and target node address as the corresponding condition, management instructions, instruction execution results, operating parameters, environmental monitoring data, and preprocessed data are matched according to the aforementioned corresponding condition; The single-port gateway layer obtains the number of instruction execution results and the number of preprocessed data corresponding to the management instruction, and uses the sum of the number of instruction execution results and the number of preprocessed data as the closed-loop feedback quantity; Acquire instruction waiting time difference, result waiting time difference, and data waiting time difference; The maximum value between the result waiting time difference and the data waiting time difference is taken as the feedback waiting time difference; the ratio of the feedback waiting time difference to the instruction waiting time difference is taken as the closed-loop scheduling value. The preset feedback quantity and preset scheduling threshold are set, and the instruction closed-loop process includes the preset feedback quantity, preset scheduling threshold, closed-loop feedback quantity, and closed-loop scheduling value.

[0029] Furthermore, the process of issuing management instructions to the remote node layer according to the issuance time, and uploading the preprocessed data and instruction execution results to the data center layer according to the upload time includes: The system acquires the current time in real time. When the number of closed-loop feedbacks is less than the preset number of feedbacks and the closed-loop scheduling value is greater than or equal to the preset scheduling threshold, it sends the preprocessed data and instruction execution result corresponding to the management instruction to the data center layer using the current time as the upload time; and it sends the management instruction to the remote node layer using the time after the preset waiting time as the distribution time. When the number of closed-loop feedbacks is greater than or equal to the preset number of feedbacks, and the closed-loop scheduling value is less than the preset scheduling threshold, the management instruction is sent to the remote node layer using the current time as the sending time; and the preprocessed data and instruction execution result corresponding to the management instruction are sent to the data center layer using the time after the preset waiting time as the upload time.

[0030] Furthermore, the process of obtaining the instruction waiting time difference, result waiting time difference, and data waiting time difference includes: The time difference between the generation time of the management instruction and the current time is used as the instruction waiting time difference; the time difference between the generation time of the execution result of the management instruction and the current time is used as the result waiting time difference. The latest time between the acquisition time of the operating parameters corresponding to the management command and the acquisition time of the corresponding environmental monitoring data is used as the feedback reference time. The time difference between the preprocessed data generation time corresponding to the management instruction and the feedback reference time is taken as the preprocessing time difference; When the preprocessing time difference is less than or equal to the preset time threshold, the time difference between the preprocessed data generation time corresponding to the management instruction and the current time is taken as the data waiting time difference. When the preprocessing time difference is greater than the preset time threshold, the time difference between the preprocessed data generation time corresponding to the management instruction and the current time is taken as the intermediate time difference, and the sum of the intermediate time difference and the preprocessing time difference is taken as the data waiting time difference.

[0031] In this embodiment, at 08:30:02, the single-port gateway layer obtains the current time in real time and calculates the time parameters in the instruction closed-loop process; The management command was generated at 08:30:00, therefore the command waiting time difference is 2 seconds. Since the execution result and feedback data have not yet been received and no feedback content has been generated that can be uploaded, the single-port gateway layer will prioritize the execution of the distribution during the initial scheduling phase, using 08:30:02 as the distribution time, and send the management command to the remote node corresponding to address A102. After generating the instruction execution results and preprocessed data, the upload time and the distribution time are determined based on the number of closed-loop feedbacks and the closed-loop scheduling value. At 08:30:02, control node G101 forwards the management command to the controlled node corresponding to address A102 via control port P1001. If the target node address corresponds to multiple controlled nodes after being resolved by control node G101, control node G101 forwards the management command to the corresponding multiple controlled nodes sequentially or in parallel under the same control port according to a predetermined order or scheduling strategy, so as to achieve unified scheduling and management of multiple remote nodes under limited network conditions. Remote node A102 completed address matching at 08:30:03, and the matching execution status was "match successful". Subsequently, it executed parameter loading according to parameter configuration instructions, and generated the instruction execution result at 08:30:05. The operation execution status was "execution successful". The execution completion time is set to 08:30:05 because parameter writing, state switching and local verification usually take 1 to 3 seconds. The 2-second range can reflect the common processing rhythm of industrial nodes executing configuration commands. When the hardware performance is low or multiple modules need to be linked, it can be extended to 4 to 6 seconds. Remote node A102 synchronously collects operating parameters and environmental monitoring data while executing management commands; At 08:30:04, operating parameters were collected, including a sampling period of 2 seconds, an upload period of 10 seconds, and a dust alarm threshold of 8.0 mg / m³. 3 The alarm threshold for harmful gases is 35ppm, the node start / stop status is "start", the working mode is "monitoring mode", the fault status is "no fault", the communication connection status is "online", and the power supply status is "mains power supply". Environmental monitoring data was collected at 08:30:04, including a temperature of 31.2℃, humidity of 68%RH, and a dust concentration calculated from the simulated concentration to be 7.4 mg / m³. 3 The simulated concentration of harmful gases was converted to 18 ppm, and the effective value of vibration velocity was 1.6 mm / s. The temperature of 31.2℃ and humidity of 68%RH are within the common range for summer operation conditions in open-pit coal yards. Dust concentration 7.4 mg / m³ 3 Below the alarm threshold of 8.0 mg / m³ 3 However, approaching the upper limit helps to highlight the necessity of subsequent parameter fine-tuning; 18ppm is in the normal high range below the alarm threshold, indicating that the gas monitoring function is normal; 1.6mm / s corresponds to a slight mechanical disturbance state, which is suitable as a vibration sample under normal operating conditions. After receiving the operating parameters and environmental monitoring data at 08:30:05.2, the single-port gateway layer first performs standardization processing; The 0.5V to 2.7V analog signal output from the dust sensor is converted to 7.4mg / m³. 3 The 0.9V analog signal output from the gas sensor is converted to 18ppm; then the operating parameters and environmental monitoring data are uniformly converted into JSON format. The process involved deduplication, noise reduction, completion, and encryption. One duplicate temperature record was removed, and the instantaneous dust peak value of 8.6 mg / m³ was corrected. 3 7.5 mg / m 3 The missing timestamp field was filled in, and the data was encrypted using AES128. The preprocessed data was finally generated at 08:30:06. AES128 was used in this embodiment because it is maturely deployed in industrial gateways, has moderate computational overhead, and balances security and real-time performance. AES256 can also be used in gateways with more abundant resources. 08:30:04 is the feedback reference time, and 08:30:06 is the preprocessed data generation time; therefore, the preprocessing time difference is 1.5 seconds. This value is less than the preset time threshold of 3 seconds, indicating that the preprocessing time is within an acceptable range. The single-port gateway layer retrieves the current time again at 08:30:07 and completes the closed-loop calculation; the management instruction is generated at 08:30:00, so the instruction waiting time difference is 7 seconds; the instruction execution result is generated at 08:30:05, so the result waiting time difference is 2 seconds; the preprocessed data is generated at 08:30:06, so the data waiting time difference is 1 second; the maximum value between the result waiting time difference of 2 seconds and the data waiting time difference of 1 second is taken as the feedback waiting time difference, so the feedback waiting time difference is 2 seconds; the closed-loop scheduling value is calculated using the following formula: Closed-loop scheduling value = feedback waiting time difference ÷ instruction waiting time difference; In this embodiment, the closed-loop scheduling value is 0.29. At this time, the number of instruction execution results is 1, the number of preprocessed data is 1, and the number of closed-loop feedbacks is 2. Since the number of closed-loop feedbacks is greater than or equal to the preset feedback number 2, and the closed-loop scheduling value of 0.29 is less than the preset scheduling threshold of 1.20, the gateway layer uses 08:30:07 as the sending time, prioritizes sending the new management instructions to the remote node layer, and uses 08:30:10 as the upload time, then uploads the preprocessed data and instruction execution results to the data center layer. The reason for prioritizing this is that a closed-loop feedback has already been formed, and the waiting pressure on the feedback side is significantly lower than that on the command side, making it suitable to start the next round of control as soon as possible. After receiving the preprocessed data and instruction execution results at 08:30:10, the data center layer reads the matching execution status and the operation execution status. Since the matching execution status is "match successful" and the operation execution status is "execution successful", it enters the parameter adjustment branch. The data center layer will preprocess the data to detect a dust concentration of 7.5 mg / m³. 3 The dust alarm threshold of 8.0 mg / m³ in the original operating parameters is different. 3 The parameters are compared and combined with the preset parameter range to generate new operating parameters; In this embodiment, the preset parameter range for the dust alarm threshold is set to 6.5 mg / m³. 3 Up to 9.5 mg / m 3 In other scenarios, the range width can be adjusted according to historical peak values, environmental background, and fault tolerance requirements; Since the actual dust concentration is already close to the upper limit of the original threshold, the data center layer has revised the new dust alarm threshold to 7.6 mg / m³. 3 Meanwhile, the sampling period of 2s, the upload period of 10s, and the hazardous gas alarm threshold of 35ppm remain unchanged. 7.6 mg / m 3 Higher than the current dust concentration of 7.5 mg / m³ 3 It can maintain the necessary safety margin, while reducing the original threshold of 8.0 mg / m³. 3More sensitive, suitable for subsequent rounds of dynamic adjustment; This generates a new management instruction. The instruction identifier remains a parameter configuration type, the target node address remains A102, and the new operating parameters are a sampling period of 2 seconds, an upload period of 10 seconds, and a dust alarm threshold of 7.6 mg / m³. 3 The alarm threshold for harmful gases is 35 ppm.

[0032] In this embodiment, if the data center layer generates a management command for A103 in a subsequent management task, but the actual online address of the remote node is updated to A203, the remote node returns a matching execution status of "matching failed" and an operation execution status of "execution failed". Based on this, the data center layer modifies the target node address from A103 to A203, while keeping the instruction identifier and operation parameters unchanged, thus forming a new management instruction with the target node address modified. The address correction here uses last-level address replacement because such changes usually come from node migration or address reprogramming. Directly correcting the addressing field can restore the communication loop the fastest. When the address system is more complex, the first-level or multi-level address fields can also be corrected according to the node mapping table. If the target node address matches successfully, but the node fails to respond when executing start / stop commands, resulting in an execution failure status, the data center layer generates a new, resent management command based on the original command identifier and operation parameters. For example, a node start / stop control command is generated at 09:10:00, with the target node address being A103 and operation parameters of a 1-second restart delay and a 3-second status confirmation period. After the node returns an execution failure at 09:10:04, the data center layer generates a new, resent management command at 09:10:06, still using the same command identifier and operation parameters. The 1-second restart delay is to allow a state switching buffer for the local control unit; the 3-second status confirmation period can be set to 2 to 5 seconds in similar devices, depending on the start / stop time and confirmation requirements. The remote node layer is used to receive and execute management commands, obtain command execution results, and simultaneously collect operating parameters and environmental monitoring data, and use the operating parameters and environmental monitoring data as feedback data; at the same time, the feedback data and command execution results are sent to the single-port gateway layer. Furthermore, when a remote node executes an operation based on the instruction identifier and operation parameters, it also includes: The remote node collects the operating parameters and environmental monitoring data in real time. The operating parameters include the parameter configuration values ​​of the remote node when executing management commands, the node start / stop status, working mode, fault status, communication connection status, and power status. The environmental monitoring data includes temperature, humidity, dust concentration, harmful gas concentration, and vibration status in the area where the remote node is located.

[0033] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the invention can be implemented in other specific forms without departing from its spirit or essential characteristics. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be included within the present invention. No reference numerals in the claims should be construed as limiting the scope of the claims.

Claims

1. A remote node data management system based on a single port, characterized in that: The system includes a data center layer, a single-port gateway layer, and a remote node layer; The data center layer is used to generate management commands and send them to the single-port gateway layer; The single-port gateway layer receives management commands sent by the data center layer, and also receives feedback data and command execution results sent by the remote node layer; the feedback data is preprocessed to obtain preprocessed data; The single-port gateway layer also includes an instruction closed-loop process, which determines the sending time and uploading time based on the instruction closed-loop process. The management instructions are sent to the remote node layer according to the issuance time, and the preprocessed data and instruction execution results are uploaded to the data center layer according to the upload time. The remote node layer is used to receive and execute management commands, obtain command execution results, and simultaneously collect operating parameters and environmental monitoring data, and use the operating parameters and environmental monitoring data as feedback data; at the same time, the feedback data and command execution results are sent to the single-port gateway layer. The data center layer generates new management instructions based on the uploaded preprocessed data and the instruction execution results, and sends the new management instructions to the single-port gateway layer.

2. The remote node data management system based on a single port according to claim 1, characterized in that: The structure of a management instruction includes an instruction identifier, operation parameters, and a target node address; the instruction identifier indicates the type of management instruction. The remote node layer reads the target node address, matches the target node address with the node address, and generates the instruction execution result; The execution result of the instruction includes the management instruction and the execution status corresponding to the management instruction. The execution status includes the operation execution status and the matching execution status.

3. The remote node data management system based on a single port according to claim 2, characterized in that, The matching includes: When the target node address matches the node address, the matching execution status is considered a successful match. The remote node corresponding to the target node address executes the operation according to the instruction identifier and operation parameters, and generates the corresponding operation execution status according to preset rules. The operation execution status includes execution success and execution failure. When the target node address and the node address do not match, the matching execution status is considered a matching failure, and the operation execution status is considered an execution failure.

4. The remote node data management system based on a single port according to claim 1, characterized in that, The process by which the single-port gateway layer preprocesses the feedback data to obtain preprocessed data includes: The single-port gateway layer performs standardization processing on the received operating parameters and environmental monitoring data. This standardization processing includes: Convert analog data in environmental monitoring data into digital data, and convert non-standardized data formats in operating parameters and environmental monitoring data into JSON format; The standardized operating parameters and environmental monitoring data are deduplicated, denoised, and completed. The standardized operating parameters and environmental monitoring data are then encrypted to obtain preprocessed data.

5. A remote node data management system based on a single port according to claim 1, characterized in that, The instruction closed-loop process includes: Using the same instruction identifier and target node address as the corresponding condition, management instructions, instruction execution results, operating parameters, environmental monitoring data, and preprocessed data are matched according to the aforementioned corresponding condition; The single-port gateway layer obtains the number of instruction execution results and the number of preprocessed data corresponding to the management instruction, and uses the sum of the number of instruction execution results and the number of preprocessed data as the closed-loop feedback quantity; Acquire instruction waiting time difference, result waiting time difference, and data waiting time difference; The maximum value between the result waiting time difference and the data waiting time difference is taken as the feedback waiting time difference; the ratio of the feedback waiting time difference to the instruction waiting time difference is taken as the closed-loop scheduling value. The preset feedback quantity and preset scheduling threshold are set, and the instruction closed-loop process includes the preset feedback quantity, preset scheduling threshold, closed-loop feedback quantity, and closed-loop scheduling value.

6. A remote node data management system based on a single port according to claim 5, characterized in that, The process of issuing management instructions to the remote node layer according to the issuance time, and uploading preprocessed data and instruction execution results to the data center layer according to the upload time includes: The system acquires the current time in real time. When the number of closed-loop feedbacks is less than the preset number of feedbacks and the closed-loop scheduling value is greater than or equal to the preset scheduling threshold, it sends the preprocessed data and instruction execution result corresponding to the management instruction to the data center layer using the current time as the upload time; and it sends the management instruction to the remote node layer using the time after the preset waiting time as the distribution time. When the number of closed-loop feedbacks is greater than or equal to the preset number of feedbacks, and the closed-loop scheduling value is less than the preset scheduling threshold, the management instruction is sent to the remote node layer using the current time as the sending time; and the preprocessed data and instruction execution result corresponding to the management instruction are sent to the data center layer using the time after the preset waiting time as the upload time.

7. A remote node data management system based on a single port according to claim 6, characterized in that, The process of obtaining the instruction waiting time difference, result waiting time difference, and data waiting time difference includes: The time difference between the generation time of the management instruction and the current time is used as the instruction waiting time difference; the time difference between the generation time of the execution result of the management instruction and the current time is used as the result waiting time difference. The latest time between the acquisition time of the operating parameters corresponding to the management command and the acquisition time of the corresponding environmental monitoring data is used as the feedback reference time. The time difference between the preprocessed data generation time corresponding to the management instruction and the feedback reference time is taken as the preprocessing time difference; When the preprocessing time difference is less than or equal to the preset time threshold, the time difference between the preprocessed data generation time corresponding to the management instruction and the current time is taken as the data waiting time difference. When the preprocessing time difference is greater than the preset time threshold, the time difference between the preprocessed data generation time corresponding to the management instruction and the current time is taken as the intermediate time difference, and the sum of the intermediate time difference and the preprocessing time difference is taken as the data waiting time difference.

8. A remote node data management system based on a single port according to claim 4, characterized in that, The process by which the data center layer generates new management instructions based on the uploaded preprocessed data and the results of instruction execution includes: The data center layer reads the matching execution status and the corresponding operation execution status; When the matching execution status is "match successful" and the operation execution status is "execution successful", the preprocessed data is compared with the operation parameters in the management instruction, and new operation parameters in the management instruction are generated according to the preset parameter range of the preprocessed data and the corresponding operation parameters in the management instruction. When the matching execution status is "match failed", a new management instruction with the target node address corrected is generated based on the target node address; When the matching execution status is "match successful" and the operation execution status is "execution failed", a new management instruction is generated based on the instruction identifier and operation parameters in the management instruction.

9. A remote node data management system based on a single port according to claim 3, characterized in that, When a remote node executes an operation based on the instruction identifier and operation parameters, it also includes: The remote node collects the operating parameters and environmental monitoring data in real time. The operating parameters include the parameter configuration values ​​of the remote node when executing management commands, the node start / stop status, working mode, fault status, communication connection status, and power status. The environmental monitoring data includes temperature, humidity, dust concentration, harmful gas concentration, and vibration status in the area where the remote node is located.

Images