Design method for supporting heterogeneous serial port communication of multi-terminal nodes

Abstract

This invention provides a design method for supporting heterogeneous serial communication among multiple terminal nodes. It constructs a serial command communication control infrastructure, including a main command communication structure for sending commands from the master node to the terminal, and a process monitoring structure for monitoring the command communication process. It also constructs a serial telemetry transmission processing infrastructure, including a telemetry transmission main structure for sending telemetry data from the terminal to the master node, and a process monitoring structure for monitoring the telemetry data transmission process. Based on these infrastructures, a heterogeneous serial command communication processing mechanism is executed, supporting diverse command communication needs of terminal nodes and monitoring and evaluating the command communication process. Furthermore, a heterogeneous serial telemetry transmission processing mechanism is executed, supporting different types of telemetry data transmission needs of terminal nodes and monitoring the acquisition and reception process of telemetry data. Thus, this invention can meet the differentiated serial communication needs of a large number of different types of terminal device nodes on a satellite.

Description

Technical Field

[0001] This invention relates to the field of satellite communication technology, and to a design method for supporting heterogeneous serial communication of multiple terminal nodes, which is used to meet the serial communication needs of a large number of different types of terminal device nodes in high-orbit communication satellites. Background Technology

[0002] There are heterogeneous serial communication requirements between a large number of terminal device nodes and the main control node. The main control node sends control commands through the serial port to set and control the working mode and status of the terminal device nodes. At the same time, each terminal device node periodically or on demand transmits its telemetry data to the main control node through serial communication.

[0003] During communication with the main control node, different terminal device nodes have different serial communication requirements.

[0004] For terminal device nodes with high reliability requirements: 1) Before receiving serial port commands from the main control node, the main control node needs to verify the command length, completeness, and correctness of the content. During command communication, the command response performance also needs to be assessed. Finally, the main control node needs to evaluate the command communication status. 2) When transmitting telemetry data to the main control node, the telemetry data transmission needs to be initiated through a message triggering mechanism. During the telemetry data transmission process, adaptive recognition of the data transmission length is required based on the different needs of the terminal device nodes. The telemetry data transmission process needs to be monitored to ensure that the telemetry data transmission is completed within the specified time. Finally, the main control node evaluates the status of the telemetry data transmission.

[0005] Conversely, for terminal device nodes with low requirements for serial communication reliability, taking serial command communication as an example, when receiving serial commands, the main control node only needs to control the length, integrity and correctness of the command content. There is no need to judge the command response performance, nor does the main control node need to evaluate the command communication status. Summary of the Invention

[0006] To address the problems existing in the prior art, this invention provides a design method that supports heterogeneous serial communication among multiple terminal nodes, supporting heterogeneous serial communication mechanisms, and can meet the serial communication needs of a large number of different types of terminal device nodes on a satellite.

[0007] To achieve the above technical effects, this invention provides a design method for supporting heterogeneous serial port communication among multiple terminal nodes, including the following steps: A serial port command communication control infrastructure is constructed, which includes a serial port command communication main structure for the main control node to send control commands to the terminal device node, and a serial port command communication process monitoring structure for monitoring the command communication process. A serial port telemetry transmission processing infrastructure is constructed, which includes a main serial port telemetry transmission processing structure for sending telemetry data from terminal device nodes to the main control node, and a serial port telemetry transmission monitoring structure for monitoring the telemetry data transmission process. Based on the aforementioned serial port command communication control infrastructure, a heterogeneous serial port command communication processing mechanism is executed to support different types of command communication needs of terminal device nodes, monitor the command communication process, and realize differentiated command control for different terminal device nodes. Based on the aforementioned serial port telemetry transmission processing infrastructure, a heterogeneous serial port telemetry transmission processing mechanism is implemented to support different types of telemetry data transmission needs of terminal nodes. The process of acquiring and receiving telemetry data is monitored to achieve differentiated telemetry data acquisition for different terminal device nodes.

[0008] Furthermore, the main structure of the serial port command communication includes, in sequence, a command communication synchronization header, a first serial port device address, a command length, command data, a command communication process monitoring structure, and a first checksum field; The command communication process monitoring structure includes, in sequence, a first switch control state, a command response substructure, a command communication statistics substructure, and fields for command communication monitoring information.

[0009] Furthermore, the instruction response substructure further includes an instruction response element for indicating whether a response is required and an instruction response time for specifying the response time limit; The instruction communication statistics substructure further includes an instruction communication success count for recording the number of successful communications and an instruction communication error count for recording the number of failed communications. The instruction communication monitoring information includes instruction communication status for describing the instruction communication status and instruction execution result feedback for providing feedback on instruction execution results.

[0010] Furthermore, the main structure of the serial port telemetry transmission processing includes, in sequence, a telemetry transmission synchronization header, a second serial port device address, a telemetry length, telemetry data, a telemetry transmission monitoring structure, and a field for a second checksum; The telemetry transmission monitoring structure includes, in sequence, a second switch control state, a telemetry request substructure, a length adaptive substructure, a telemetry transmission statistics substructure, and fields for telemetry transmission status.

[0011] Furthermore, the telemetry request substructure further includes a telemetry request element for indicating whether telemetry reporting needs to be triggered by a master control request and a request time for specifying the response time limit after the request. The length adaptive substructure further includes a length adaptive element for indicating whether the telemetry length is a fixed value and a telemetry transmission length for recording the actual telemetry transmission length; The telemetry transmission statistics substructure further includes a telemetry transmission success count for recording the number of successful transmissions and a telemetry transmission error count for recording the number of failed transmissions.

[0012] Furthermore, the heterogeneous serial port command communication processing mechanism specifically includes: The main control node determines whether communication is allowed based on the first switch control state of the target terminal device node, and performs a rationality check on the main structure of the serial port command communication. If the check passes, the main control node determines whether a response is required based on the instruction response elements of the target terminal device node. If a response is required, the main control node waits within the instruction response time to receive the instruction execution result feedback from the target terminal device node. Otherwise, the instruction communication process ends. The main control node evaluates the status of this instruction communication based on the rationality check results, whether the instruction execution result feedback was received on time, and the content of the instruction execution result feedback, and updates the instruction communication status and instruction communication success and failure statistics. Furthermore, the rationality check of the main structure of the serial port command communication specifically includes checking the fields of the command communication synchronization header, the first serial port device address, and the first checksum. The command communication success / failure statistics include the command communication success count and the command communication error count; If the first checksum error is detected, the current communication status is determined to be a checksum error, and the instruction communication error count is incremented by 1; If no instruction execution result feedback is received within the instruction response time, the current communication status is determined to be an instruction timeout, and the instruction communication error count is incremented by 1. If the feedback of the instruction execution result is received and the result is correct, the communication status is determined to be correct, and the instruction communication success count is incremented by 1. If the instruction execution result feedback is received but indicates an execution error, the current communication status is determined to be an execution error, and the instruction communication error count is incremented by 1.

[0013] Furthermore, the heterogeneous serial port telemetry transmission processing mechanism specifically includes: The main control node determines whether telemetry transmission is allowed based on the second switch control state of the target terminal device node, and determines whether it needs to actively send a telemetry request signal based on the telemetry request elements therein. The main control node receives telemetry data sent by the target terminal device node, determines the parsing method of the telemetry length according to the length adaptive element, and performs a rationality check on the main structure of the serial port telemetry transmission processing. The master control node evaluates the telemetry transmission status based on the rationality check results and whether data was received within the requested time, and updates the telemetry transmission status and telemetry transmission success / failure statistics.

[0014] Furthermore, if it is determined that an active request is required based on the telemetry request elements, the main control node shall send a telemetry request signal to the target terminal device node before receiving telemetry data each time. If the length adaptive element indicates that the telemetry length is a fixed value, the master control node sets the telemetry length according to the agreed fixed value; if the length adaptive element indicates that the telemetry length is adaptive, the telemetry transmission length is updated according to the actual length of the received telemetry data. A rationality check is performed on the main structure of the serial port telemetry transmission processing, specifically including checking the fields of the telemetry transmission synchronization header, the second serial port device address, and the second checksum.

[0015] Furthermore, the telemetry transmission success / failure statistics include the telemetry transmission success count and the telemetry transmission error count; If the second checksum error is detected, the current transmission status is determined to be a checksum error, and the telemetry transmission error count is incremented by 1. If the target terminal device node fails to complete the telemetry data transmission within the requested time, the current transmission status is determined to be telemetry timeout, and the telemetry transmission error count is incremented by 1. If the check is correct and reception is completed within the requested time, the current transmission status is determined to be telemetry correct, and the telemetry transmission success count is incremented by 1.

[0016] The design method for supporting heterogeneous serial communication across multiple terminal nodes, as described in this invention, aims to solve the problem of differentiated serial communication between a satellite master control node and a large number of terminal device nodes with different communication needs. It comprises four core parts: First, designing a basic serial command communication structure, including a main command communication structure and a process monitoring structure, providing a unified data foundation for differentiated command transmission and response monitoring; second, designing a basic serial telemetry data transmission structure, including a main telemetry data transmission structure and a transmission monitoring structure, providing a unified data foundation for differentiated telemetry data acquisition and reception monitoring; third, designing a heterogeneous serial command communication processing mechanism, which, by judging the response needs of terminal nodes, performs differentiated monitoring of the response process after command issuance and evaluates the communication effect; fourth, designing a heterogeneous serial telemetry data transmission processing mechanism, which, by judging the reporting needs of terminal nodes, is compatible with both on-demand request and periodic reporting modes, supports the processing of fixed-length and adaptive-length data, and evaluates the transmission results. Thus, this invention, by constructing a standardized data structure and supporting differentiated processing mechanisms, achieves unified management and refined control of the serial communication needs of various heterogeneous terminals. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating the steps of a design method for supporting heterogeneous serial communication across multiple terminal nodes, as provided in an embodiment of the present invention. Figure 2 This is a schematic diagram of the main structure of the serial port command communication of the design method supporting heterogeneous serial port communication of multiple terminal nodes provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the instruction communication process monitoring structure of the design method supporting heterogeneous serial port communication of multiple terminal nodes provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the main structure of the serial port telemetry transmission processing of the design method supporting heterogeneous serial port communication of multiple terminal nodes provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of the telemetry transmission monitoring structure of the design method supporting heterogeneous serial communication of multiple terminal nodes provided in an embodiment of the present invention. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0020] It should be noted that references to "an embodiment," "embodiment," "example embodiment," etc., in this specification refer to the described embodiment including specific features, structures, or characteristics, but not every embodiment must include these specific features, structures, or characteristics. Furthermore, such expressions do not refer to the same embodiment. Moreover, when describing specific features, structures, or characteristics in conjunction with embodiments, whether or not explicitly described, it is indicated that incorporating such features, structures, or characteristics into other embodiments is within the knowledge of those skilled in the art.

[0021] Furthermore, certain terms are used in the specification and subsequent claims to refer to specific components or parts. Those skilled in the art will understand that manufacturers may use different names or terms to refer to the same component or part. This specification and subsequent claims do not distinguish components or parts by differences in name, but rather by differences in function.

[0022] The core concept of this invention is to solve the problem of heterogeneous serial communication among multiple terminal devices in satellite communication by combining a "unified data structure foundation" with a "differentiated processing mechanism".

[0023] To enable those skilled in the art to reproduce and implement the present invention, the following will describe in detail each step of the design method and system supporting heterogeneous serial port communication of multiple terminal nodes through specific embodiments, in conjunction with the accompanying drawings.

[0024] Figure 1 This invention illustrates a design method for supporting heterogeneous serial port communication among multiple terminal nodes, comprising the following steps: S101: Construct a basic serial port command communication control structure. This basic structure includes a main serial port command communication structure for the master control node to send control commands to the terminal device node, and a serial port command communication process monitoring structure for monitoring the command communication process. This basic structure design provides the data structure foundation for heterogeneous serial port command communication and control between the master control node and the terminal device node.

[0025] like Figure 2As shown, the main structure of the serial port command communication includes, in sequence, a command communication synchronization header, a first serial port device address, a command length, command data, a command communication process monitoring structure, and a first checksum field; it forms the basis for the main control node to control command communication with multiple terminal device nodes, and can also meet the requirements of heterogeneous serial port command communication. The functions of each field in the main structure of the serial port command communication in this embodiment are explained below: Command Communication Synchronization Header: This element defines the identification field for initiating command communication between the master control node and the terminal device node.

[0026] The first serial port device address (specifically, the terminal device node address): This element defines the underlying physical address corresponding to each terminal device node. A unique address is designed for each terminal device node to ensure that instructions issued by the master control node can be accurately transmitted to the corresponding terminal device node. This embodiment supports 40 different terminal device node addresses, meaning it supports instruction communication between the master control node and 40 different terminal device nodes.

[0027] Command Length: This element defines the length of command communication between the master control node and the current terminal device node. Both parties agree to use this length for command communication per cycle.

[0028] Command Data: This element defines the specific data for serial port command communication between the master control node and the current terminal device node. After receiving the command, the current terminal device node parses and processes it.

[0029] Command Communication Process Monitoring Structure: This structure enables the main control node to control the serial port command communication process with each terminal device node, thereby providing diversified serial port command communication capabilities and supporting the monitoring and statistics of command communication effects. This structure encompasses switch control status, command response (including response elements and response time), command communication statistics (including communication success count and communication error count), and command communication monitoring information (including communication status and command execution result feedback). Details of this structure are described below.

[0030] First checksum: This element is the checksum field for serial port commands. Before the master control node communicates with the terminal device node via serial port commands, it needs to verify the checksum field according to the agreed verification method to ensure the integrity and correctness of the serial port command content.

[0031] like Figure 3As shown, the command communication process monitoring structure sequentially includes a first switch control state, a command response substructure, a command communication statistics substructure, and fields for command communication monitoring information. Further, the command response substructure includes a command response element indicating whether a response is needed and a command response time specifying the response time limit; the command communication statistics substructure includes a command communication success count for recording the number of successful communications and a command communication error count for recording the number of failed communications; the command communication monitoring information includes a command communication status for describing the command communication status and a command execution result feedback for providing feedback on the command execution result. This command communication process monitoring structure is used to control and monitor the command transmission process between the main control node and each terminal device node. The command communication process monitoring structure consists of four substructures (a total of seven elements): switch control state, command response (including response element and response time), command communication statistics (including communication success count and communication error count), and command communication monitoring information (including communication status and command execution result feedback). The functions of each field in the command communication process monitoring structure of this embodiment are described below: 1) First switch control state: Represented by Com_enable_flag, indicating whether the terminal device node can be in the enabled state for command communication in this cycle. This sub-element has a binary value: "Yes", indicating that the serial port command communication of the terminal device node is enabled; "No", indicating that the serial port command communication of the terminal device node is disabled and needs to be enabled.

[0032] 2) Command Response Element: Represented by Com_response_flag, this element specifies whether the terminal device node needs to respond to the received serial port commands from the master control node in this communication. This sub-element has a binary value: "Yes" indicates that the terminal device node needs to respond to the received serial port commands from the master control node, and "No" indicates that the terminal device node does not need to respond to the received serial port commands from the master control node and only needs to receive them in one direction.

[0033] 3) Command response time: Represented by Tc_res, if the value of the "Command response element" field is "yes", it means that the terminal device node in this communication needs to respond to the serial port command received from the master control node. The "Command response time" specifies that after receiving the serial port communication command from the master control node, the terminal device node needs to feed back the result of the serial port command response of this cycle to the master control node within a time of less than Tc_res.

[0034] 4) Command communication success count: Represented by Com_success_num, this field is an integer type. When the master control node completes the serial port command communication process with the current terminal device node and executes it correctly, the count will be automatically incremented by 1.

[0035] 5) Command communication error count: Represented by Com_failure_num, this field is an integer type. When the master control node encounters an error during the serial port command communication process with the current terminal device node, the count is automatically incremented by 1.

[0036] 6) Command Communication Status: Represented by Com_status, this describes the status of command communication between the master control node and the terminal device node. This sub-element has four possible values: "Communication Correct," indicating that the command communication was successful; "Verification Error," indicating that the serial communication command verification for the current terminal device node failed; "Command Timeout," indicating that the current terminal device node did not complete the response to the master control node's command within the specified time Tc_res; and "Execution Error," indicating that the current terminal device node failed to execute the command correctly.

[0037] 7) Command Execution Result Feedback: Represented by Com_result, this element is used by the terminal device node to report the command execution result to the master control node. This sub-element has two values: "Result Correct," indicating that the terminal device node successfully executed the serial port command; and "Execution Error," indicating that there was an error in the serial port command communication between the master control node and the current terminal device node.

[0038] S102: Construct a serial port telemetry transmission processing infrastructure, which includes a main serial port telemetry transmission processing structure for sending telemetry data from terminal device nodes to the main control node, and a serial port telemetry transmission monitoring structure for monitoring the telemetry data transmission process.

[0039] like Figure 4 As shown, the main structure of the serial port telemetry transmission processing includes, in sequence, a telemetry transmission synchronization header, a second serial port device address, telemetry length, telemetry data, a telemetry transmission monitoring structure, and a second checksum field. This main structure forms the data structure basis for communication between multiple terminal device nodes and the main control node for transmitting telemetry data, enabling the main control node to collect and transmit telemetry data from different terminal device nodes on demand. This structure consists of six elements: a telemetry transmission synchronization header, a serial port device address, a telemetry length, telemetry data, a telemetry transmission control structure, and a checksum field. The functions of each field in the main structure of the serial port telemetry transmission processing in this embodiment are explained below: Telemetry Transmission Synchronization Header: This element defines the identifier field for the terminal device node to transmit telemetry data to the master control node, denoted as TM_HEAD.

[0040] The second serial port device address (specifically, the terminal device node address) is the same as the serial port device address defined in the aforementioned "Serial Port Command Communication Main Structure". Each terminal device node is associated with a unique serial port address, ensuring that the master control node can accurately receive the unique telemetry data transmitted by a specific terminal device node. This system supports a total of 40 different terminal device node addresses, meaning it supports receiving telemetry data from 40 different terminal device nodes.

[0041] Telemetry Length: This element defines the length of telemetry data transmitted between the terminal device node and the master control node. Both parties agree to transmit telemetry data for each cycle according to this length.

[0042] Telemetry data: This element defines the specific telemetry data content transmitted between the current terminal device node and the main control node. After the telemetry data is transmitted to the main control node, it is received and processed by the latter.

[0043] Telemetry Transmission Monitoring Structure: This structure enables control over the process of transmitting telemetry data from terminal device nodes to the main control node, providing diverse telemetry data transmission capabilities for different terminal device nodes, and monitoring and statistically analyzing the status of telemetry transmission. This structure includes switch control status, telemetry requests (containing request elements and request time), length structure (containing length adaptive elements and telemetry transmission length), telemetry transmission statistics (containing telemetry transmission success count and error count), and telemetry transmission status. Details of this structure are described below.

[0044] like Figure 5 As shown, the telemetry transmission monitoring structure sequentially includes fields for a second switch control state, a telemetry request substructure, a length adaptive substructure, a telemetry transmission statistics substructure, and telemetry transmission status. The telemetry request substructure further includes a telemetry request element indicating whether telemetry reporting needs to be triggered by a master control request and a request time specifying the response time limit after the request. The length adaptive substructure further includes a length adaptive element indicating whether the telemetry length is a fixed value and a telemetry transmission length recording the actual telemetry transmission length. The telemetry transmission statistics substructure further includes a telemetry transmission success count recording the number of successful transmissions and a telemetry transmission error count recording the number of failed transmissions. The telemetry transmission monitoring structure is used to control and monitor the status of telemetry data transmission from terminal device nodes to the master control node. This structure consists of 5 substructures (8 elements in total): switch control state, telemetry request (including request element and request time), length structure (including length adaptive element and telemetry transmission length), telemetry transmission statistics (including telemetry transmission success count and error count), and telemetry transmission status.

[0045] The functions of each field in the telemetry transmission monitoring structure of this embodiment are explained below: 1) Second switch control state: Represented by Para_enable_flag, it indicates whether the terminal device node can perform telemetry transmission in this cycle. This sub-element has a binary value: "Yes", indicating that the telemetry transmission of the terminal device node is enabled; "No", indicating that the serial port is in a telemetry transmission disabled state and an enable setting operation is required.

[0046] 2) Telemetry Request Element: Represented by Para_request_flag, this element specifies whether the master control node actively sends a telemetry request signal to the terminal device node to initiate the telemetry transmission process. This element has a binary value: "Yes" indicates that the master control node needs to actively send a telemetry request signal to the current terminal device node to start the telemetry transmission process; "No" indicates that the master control node does not need to actively send a telemetry request signal to the current terminal device node to start the telemetry transmission process, and telemetry transmission can be carried out periodically.

[0047] 3) Request time: Represented by Para_request_time, when the telemetry request element (Para_request_flag) is "yes", the terminal device node currently transmitting telemetry data is required to send all its telemetry data for this period to the master control node within the Para_request_time time after receiving the telemetry request signal actively sent by the master control node.

[0048] 4) Length Adaptive Element: Represented by Para_adjust_flag, this describes whether the telemetry data transmitted from the terminal device node to the master control node is of a fixed length. This sub-element has a binary value: "Yes", in which case the master control node receives and processes telemetry data according to the fixed agreed telemetry length field each cycle; "No", in which case the master control node receives and processes the telemetry data of the current terminal device node according to dynamic telemetry data each cycle and automatically updates the length field.

[0049] 5) Telemetry transmission length: Represented by Para_length. When the length adaptive element is "yes", the telemetry transmission length is equal to the fixed telemetry length field. When the length adaptive element is "no", the master control node dynamically counts the actual telemetry data received in each cycle and assigns a value to the telemetry transmission length.

[0050] 6) Telemetry transmission success count: Represented by Para_success_num, this field is an integer type. When the master control node completes the instruction communication process with each terminal device node and executes it correctly, the count is automatically incremented by 1.

[0051] 7) Telemetry transmission error count: Represented by Para_failure_num, this field is an integer type. When an error occurs during the telemetry data transmission process from the current terminal device node to the master control node, this count is automatically incremented by 1.

[0052] 8) Telemetry Transmission Status: Represented by Para_status, this describes the status of the current telemetry transmission from the terminal device node to the master control node. This sub-element has three possible values: "Telemetry Correct," indicating that the telemetry data transmission was successful; "Checksum Error," indicating that the checksum of the telemetry transmission from the terminal device node to the master control node failed; and "Telemetry Timeout," indicating that the terminal device node did not complete the telemetry data transmission to the master control node within the specified request time Para_request_time.

[0053] S103: Based on the aforementioned serial port command communication control infrastructure, a heterogeneous serial port command communication processing mechanism is executed to support different types of command communication needs of terminal device nodes. The command communication process is monitored to achieve differentiated command control for different terminal device nodes. This heterogeneous serial port command communication processing mechanism can provide diverse command communication capabilities to heterogeneous terminal device nodes on demand, supports real-time control of the serial communication process, provides analysis and evaluation of communication effects, and provides data support for fault diagnosis.

[0054] The heterogeneous serial port command communication processing mechanism specifically includes: the main control node determines whether communication is allowed based on the first switch control state of the target terminal device node, and performs a rationality check on the main structure of the serial port command communication; if the check passes, the main control node determines whether a response is required based on the command response elements of the target terminal device node; if a response is required, the main control node waits to receive the command execution result feedback from the target terminal device node within the command response time; otherwise, the current command communication process ends; the main control node evaluates the current command communication status based on the rationality check result, whether the command execution result feedback is received on time, and the content of the command execution result feedback, and updates the command communication status and command communication success / failure statistics.

[0055] Furthermore, a rationality check is performed on the main structure of the serial port command communication, specifically including checking the fields of the command communication synchronization header, the first serial port device address, and the first checksum; the command communication success / failure statistics include the command communication success count and the command communication error count; if a first checksum error is detected, the current communication status is determined to be a checksum error, and the command communication error count is incremented by 1; if no command execution result feedback is received within the command response time, the current communication status is determined to be a command timeout, and the command communication error count is incremented by 1; if command execution result feedback is received and the result is correct, the current communication status is determined to be a successful communication, and the command communication success count is incremented by 1; if command execution result feedback is received but an execution error is indicated, the current communication status is determined to be an execution error, and the command communication error count is incremented by 1.

[0056] In practical implementation, within the current clock control cycle T, when the master control node detects that serial communication with a certain terminal device node is required, the serial communication processing mechanism between the two parties can be decomposed into the following three sub-steps: Step 3-1: The master control node sends serial port commands to the terminal device nodes.

[0057] The main control node first determines the first switch control status (Com_enable_flag) of the current terminal device node. If Com_enable_flag is "yes", it performs a validity check on the instruction communication synchronization header, first serial port device address, instruction length, and first checksum field in the serial port instruction communication main structure corresponding to the terminal device node. If the check is correct, it proceeds to step 3-2 and subsequent steps. If the check fails, it proceeds to step 3-3 to evaluate the serial port instruction communication effect.

[0058] If Com_enable_flag is set to "No", the main control node first enables serial communication for the corresponding terminal device node. Then, it checks the validity of the command communication synchronization header, first serial port device address, command length, and first checksum field in the main structure of the serial command communication for the current terminal device node. If the check is correct, it proceeds to step 3-2 and subsequent steps. If the check fails, it proceeds to step 3-3 to evaluate the serial command communication effect.

[0059] Different terminal device nodes exhibit differences in their responses to serial port commands and the feedback of command execution results during serial port command communication with the main control node.

[0060] For terminal device nodes that do not require command response elements, the completion of this step indicates that the serial communication process is finished, and the process proceeds to step 3-3 to evaluate the serial command communication effect.

[0061] For terminal device nodes that require instruction response elements, after this step is completed, proceed to step 3-2 and the subsequent process.

[0062] Step 3-2: Heterogeneous serial port command communication control process.

[0063] The heterogeneous serial port command communication control process is completed collaboratively by the master control node and the terminal device node. Specifically, it includes: Step 3-2-1: Terminal device node serial port command communication response process.

[0064] For terminal device nodes that require command responses, the timer starts after receiving the serial port command in step 3-1. Within the corresponding command response time Tc_res, the node must return the command execution result feedback Com_result to the main control node: if the serial port command execution result is correct, the command execution result feedback Com_result is set to "Result Correct", otherwise it is set to "Execution Error".

[0065] Step 3-2-2: Serial port command communication control process of the main control node.

[0066] After the master control node completes the serial communication command to the terminal device node, it determines the command response element Com_response_flag of the terminal device node in the current communication.

[0067] If Com_response_flag is "Yes", it means that the master control node needs to monitor the entire command communication process of the current slave node. The master control node takes the time when the serial port command is issued in step 3-1 as the starting point of time T0. Within the command response time Tc_res corresponding to the current terminal device node, it obtains the command execution result feedback Com_result of the terminal device node in step 3-2-1, and according to its specific information, proceeds to step 3-3 to perform the corresponding serial port command communication result evaluation operation.

[0068] If the master control node does not receive the instruction execution result feedback Com_result from the terminal device node within the instruction response time Tc_res corresponding to the terminal device node, then proceed to step 3-3 to perform the corresponding instruction communication result evaluation operation.

[0069] Step 3-3: Evaluation of serial port command communication results.

[0070] After completing the serial port command communication with the current terminal device node, the master control node evaluates the serial port command communication result based on the judgment result of the main structure of the serial port command communication in step 3-1 and the command execution result feedback Com_result received in step 3-2, and forms an evaluation result. The serial port command communication result evaluation includes: When the master control node determines in step 3-1 that the serial port command checksum of the current terminal device node is incorrect, it stops sending serial port commands to the current terminal device node in this cycle, sets the command communication status Com_status to "checksum error", and increments the command communication error count Com_failure_num corresponding to the terminal device node by 1.

[0071] In step 3-2, if the master control node does not obtain the instruction execution result feedback Com_result from the current terminal device node within the instruction response time Tc_res, it indicates that the serial port instruction communication with the current terminal device node in this cycle has timed out and has not been fully successful. The instruction communication status Com_status is set to "instruction timeout", and the instruction communication error count Com_failure_num corresponding to the terminal device node is incremented by 1.

[0072] In step 3-2, if the master control node receives the instruction execution result feedback Com_result from the terminal device node within the instruction response time Tc_res, it evaluates the serial port instruction communication result based on the Com_result information. If the Com_result indicates that the slave node's instruction execution in this cycle was correct, the master control node sets the instruction communication status Com_status to "Communication Correct" and increments the instruction communication success count Com_success_num corresponding to the terminal device node by 1. If the Com_result indicates that the slave node's instruction execution in this cycle was incorrect, the master control node sets the instruction communication status Com_status to "Execution Error" and increments the instruction communication error count Com_failure_num corresponding to the terminal device node by 1.

[0073] S104: Based on the aforementioned serial port telemetry transmission processing infrastructure, a heterogeneous serial port telemetry transmission processing mechanism is executed to support different types of telemetry data transmission needs of terminal nodes. The acquisition and reception process of telemetry data is monitored to achieve differentiated telemetry data acquisition for different terminal device nodes. This heterogeneous serial port telemetry transmission processing mechanism can achieve compatibility with different types of serial port telemetry transmission systems, monitor the process of terminal device nodes transmitting telemetry data to the main control node, provide analysis and evaluation of serial port telemetry data transmission results, and provide data support for troubleshooting.

[0074] The heterogeneous serial port telemetry transmission processing mechanism specifically includes: the main control node determines whether telemetry transmission is allowed based on the second switch control state of the target terminal device node, and determines whether a telemetry request signal needs to be actively sent based on the telemetry request elements; the main control node receives the telemetry data sent by the target terminal device node, determines the parsing method of the telemetry length based on the length adaptive elements, and performs a rationality check on the main structure of the serial port telemetry transmission processing; the main control node evaluates the current telemetry transmission status based on the rationality check results and whether data is received within the requested time, and updates the telemetry transmission status and telemetry transmission success / failure statistics.

[0075] If it is determined that an active request is required based on the telemetry request elements, the master control node sends a telemetry request signal to the target terminal device node before receiving telemetry data each time. If the length adaptive element indicates that the telemetry length is a fixed value, the master control node sets the telemetry length according to the agreed fixed value. If the length adaptive element indicates that the telemetry length is adaptive, the telemetry transmission length is updated according to the actual length of the received telemetry data. A rationality check is performed on the main structure of the serial port telemetry transmission processing, specifically including checking the fields of the telemetry transmission synchronization header, the second serial port device address, and the second checksum.

[0076] Furthermore, the telemetry transmission success / failure statistics include the telemetry transmission success count and the telemetry transmission error count; if a second checksum error is detected, the current transmission status is determined to be a checksum error, and the telemetry transmission error count is incremented by 1; if the target terminal device node fails to complete the telemetry data transmission within the requested time, the current transmission status is determined to be a telemetry timeout, and the telemetry transmission error count is incremented by 1; if the check is correct and reception is completed within the requested time, the current transmission status is determined to be telemetry correct, and the telemetry transmission success count is incremented by 1.

[0077] In practical implementation, within the current clock control cycle T, when the master control node receives telemetry data from a certain terminal device node, the serial port telemetry transmission processing mechanism between the two parties can be decomposed into the following three sub-steps: Step 4-1: Preprocessing design for serial port telemetry transmission.

[0078] First, the master control node determines the on / off control status (Para_enable_flag) of the current communication terminal device node. If Para_enable_flag is "No", the master control node first enables the serial port telemetry transmission of the corresponding terminal device node, and then proceeds to the next step. If Para_enable_flag is "Yes", then proceeds to the next step.

[0079] Next, the master control node determines the telemetry request element Para_request_flag of the current communicating terminal device node. If Para_request_flag is "No", proceed to step 4-2, where the terminal device node and the master control node perform serial port telemetry transmission and reception according to the agreed period. If Para_request_flag is "Yes", then each time serial port telemetry transmission begins, the master control node needs to first send a telemetry request signal to the current terminal device node before proceeding to step 4-2 to trigger the current terminal device node's telemetry collection and transmission.

[0080] Step 4-2: Design of Heterogeneous Serial Port Telemetry Data Transmission Processing Mechanism. This step is executed according to the following two sub-steps.

[0081] Step 4-2-1: Design of serial port telemetry data transmission processing for terminal device nodes.

[0082] First, after receiving the telemetry request signal from the master control node for this cycle according to a pre-agreed agreement, the terminal device node needs to send the corresponding telemetry data for this cycle to the master control node within its corresponding request time, Para_request_time. Following the serial port telemetry transmission processing main structure defined in step S102, the terminal device node completes the acquisition and framing of its own telemetry data for this cycle. Additionally, based on the characteristics of its own telemetry transmission, it needs to assign a value to the length adaptive element, Para_adjust_flag. If the telemetry length of the terminal device node is fixed, its length adaptation element Para_adjust_flag is set to "Yes", and the telemetry transmission length Para_length is set to the agreed fixed length every cycle; if the telemetry length is adaptively variable, the length adaptation element Para_adjust_flag is set to "No", and telemetry data is transmitted to the master control node as needed every cycle, and the telemetry transmission length Para_length is updated to the actual length.

[0083] Step 4-2-2: Design of serial port telemetry data processing for the main control node.

[0084] The main control node handles heterogeneous serial telemetry data from different terminal device nodes in two ways: 1. Handling of terminal device nodes that do not require telemetry requests.

[0085] Based on the main structure of serial telemetry transmission processing, the main control node first checks the serial telemetry data received from the terminal device nodes in this cycle, and performs a reasonableness check on the telemetry transmission synchronization header, serial device address, and checksum field of the telemetry data.

[0086] The master control node uses the length adaptive element Para_adjust_flag. If the value is "yes", the "telemetry length" is set to a pre-agreed fixed value; if the value is "no", the length is calculated based on the actual telemetry data received in this cycle.

[0087] After the main control node completes the inspection of the telemetry data of the terminal equipment node, it proceeds to step 4-3 to reflect the rationality inspection judgment results in the telemetry data transmission result evaluation.

[0088] 2. Handling of terminal device nodes that require telemetry requests.

[0089] The master control node takes the time when it sends the telemetry request signal to the current terminal device node in step 4-1 as the starting point of time T0. Within the request time Para_request_time corresponding to the current terminal device node, it obtains the serial port telemetry data of the terminal device node in step 4-2-1, and checks the serial port telemetry data of the terminal device node received in this cycle according to the main structure of serial port telemetry transmission processing. It performs a reasonableness check and judgment on the telemetry transmission synchronization header, serial port device address, and checksum field of the telemetry data.

[0090] The master control node uses the length adaptive element Para_adjust_flag. If the value is "yes", the "telemetry length" is set to a pre-agreed fixed value; if the value is "no", the length is calculated based on the actual telemetry data received in this cycle.

[0091] After the main control node completes the inspection, it proceeds to step 4-3 to reflect the rationality inspection results in the telemetry data transmission result evaluation.

[0092] Step 4-3: Evaluation of the results of the serial port telemetry transmission process.

[0093] After the main control node completes the serial port telemetry transmission and reception process with the current terminal device node, it evaluates the results of the serial port telemetry transmission process based on the judgment results of the main structure of the serial port telemetry transmission processing in step 4-2 and the serial port telemetry data request status of the current terminal device node in step 3-2, and outputs the evaluation results.

[0094] When the master control node detects a checksum error in the serial port telemetry data in step 4-2-2, it sets the telemetry transmission status Para_status to "Checksum Error" and increments the telemetry transmission error count Para_failure_num corresponding to the terminal device node by 1.

[0095] If the master control node determines in step 4-2-2 that the terminal device node has not transmitted serial port telemetry data within the telemetry request time Para_request_time, it means that the serial port telemetry request to the current terminal device node in this cycle has timed out and has not been fully successful. The telemetry transmission status Para_status is set to "telemetry timeout", and the telemetry transmission error count Para_failure_num corresponding to the terminal device node is incremented by 1.

[0096] In summary, this invention addresses the heterogeneous serial communication requirements of multiple terminal nodes in high-orbit communication satellites. By constructing a standardized command communication and telemetry transmission infrastructure and supporting differentiated processing mechanisms, it achieves refined control and monitoring of diverse terminal devices. This method embeds configurable control fields into the data structure, enabling the master control node to flexibly adjust communication strategies according to the needs of each terminal. This satisfies the closed-loop response requirements of highly reliable devices while also being compatible with low-complexity open-loop communication modes. Furthermore, it supports both on-demand request and periodic reporting telemetry transmission systems. Thus, this invention effectively solves the problems of limited communication methods and difficulty in adapting to multiple terminals in existing technologies, improving the reliability and maintainability of satellite communication systems, providing strong support for fault diagnosis and data analysis, and possessing significant engineering application value.

[0097] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0098] It should be noted that the scope of the methods and apparatus in the embodiments of the present invention is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

[0099] Of course, the present invention may have other various embodiments. Without departing from the spirit and essence of the present invention, those skilled in the art can make various corresponding changes and modifications according to the present invention, but these corresponding changes and modifications should all fall within the protection scope of the appended claims.

Claims

1. A design method for supporting multi-terminal node heterogeneous serial port communication, characterized in that, Including the following steps: A serial port command communication control infrastructure is constructed, which includes a serial port command communication main structure for the main control node to send control commands to the terminal device node, and a serial port command communication process monitoring structure for monitoring the command communication process. A serial port telemetry transmission processing infrastructure is constructed, which includes a main serial port telemetry transmission processing structure for sending telemetry data from terminal device nodes to the main control node, and a serial port telemetry transmission monitoring structure for monitoring the telemetry data transmission process. Based on the aforementioned serial port command communication control infrastructure, a heterogeneous serial port command communication processing mechanism is executed to support different types of command communication needs of terminal device nodes, monitor the command communication process, and realize differentiated command control for different terminal device nodes. Based on the aforementioned serial port telemetry transmission processing infrastructure, a heterogeneous serial port telemetry transmission processing mechanism is implemented to support different types of telemetry data transmission needs of terminal nodes. The process of acquiring and receiving telemetry data is monitored to achieve differentiated telemetry data acquisition for different terminal device nodes.

2. The method according to claim 1, characterized in that, The main structure of the serial port command communication includes, in sequence, a command communication synchronization header, a first serial port device address, a command length, command data, a command communication process monitoring structure, and a first checksum field; The command communication process monitoring structure includes, in sequence, a first switch control state, a command response substructure, a command communication statistics substructure, and fields for command communication monitoring information.

3. The method according to claim 2, characterized in that, The instruction response substructure further includes an instruction response element for indicating whether a response is required and an instruction response time for specifying the response time limit; The instruction communication statistics substructure further includes an instruction communication success count for recording the number of successful communications and an instruction communication error count for recording the number of failed communications. The instruction communication monitoring information includes instruction communication status for describing the instruction communication status and instruction execution result feedback for providing feedback on instruction execution results.

4. The method according to claim 1, characterized in that, The main structure of the serial port telemetry transmission processing includes, in sequence, a telemetry transmission synchronization header, a second serial port device address, a telemetry length, telemetry data, the telemetry transmission monitoring structure, and a second checksum field; The telemetry transmission monitoring structure includes, in sequence, a second switch control state, a telemetry request substructure, a length adaptive substructure, a telemetry transmission statistics substructure, and fields for telemetry transmission status.

5. The method according to claim 4, characterized in that, The telemetry request substructure further includes a telemetry request element for indicating whether telemetry reporting needs to be triggered by a master control request and a request time for specifying the response time limit after the request. The length adaptive substructure further includes a length adaptive element for indicating whether the telemetry length is a fixed value and a telemetry transmission length for recording the actual telemetry transmission length; The telemetry transmission statistics substructure further includes a telemetry transmission success count for recording the number of successful transmissions and a telemetry transmission error count for recording the number of failed transmissions.

6. The method according to claim 3, characterized in that, The heterogeneous serial port command communication processing mechanism specifically includes: The main control node determines whether communication is allowed based on the first switch control state of the target terminal device node, and performs a rationality check on the main structure of the serial port command communication. If the check passes, the main control node determines whether a response is required based on the instruction response elements of the target terminal device node. If a response is required, the main control node waits within the instruction response time to receive the instruction execution result feedback from the target terminal device node. Otherwise, the instruction communication process ends. The main control node evaluates the status of this instruction communication based on the rationality check results, whether the instruction execution result feedback was received on time, and the content of the instruction execution result feedback, and updates the instruction communication status and instruction communication success / failure statistics.

7. The method according to claim 6, characterized in that, The rationality check of the main structure of the serial port command communication specifically includes checking the fields of the command communication synchronization header, the first serial port device address, and the first checksum. The command communication success / failure statistics include the command communication success count and the command communication error count; If the first checksum error is detected, the current communication status is determined to be a checksum error, and the instruction communication error count is incremented by 1; If no instruction execution result feedback is received within the instruction response time, the current communication status is determined to be an instruction timeout, and the instruction communication error count is incremented by 1. If the feedback of the instruction execution result is received and the result is correct, the communication status is determined to be correct, and the instruction communication success count is incremented by 1. If the instruction execution result feedback is received but indicates an execution error, the current communication status is determined to be an execution error, and the instruction communication error count is incremented by 1.

8. The method according to claim 5, characterized in that, The heterogeneous serial port telemetry transmission processing mechanism specifically includes: The main control node determines whether telemetry transmission is allowed based on the second switch control state of the target terminal device node, and determines whether it needs to actively send a telemetry request signal based on the telemetry request elements therein. The main control node receives telemetry data sent by the target terminal device node, determines the parsing method of the telemetry length according to the length adaptive element, and performs a rationality check on the main structure of the serial port telemetry transmission processing. The master control node evaluates the telemetry transmission status based on the rationality check results and whether data was received within the requested time, and updates the telemetry transmission status and telemetry transmission success / failure statistics.

9. The method according to claim 8, characterized in that, If it is determined that an active request is required based on the telemetry request elements, the main control node shall send a telemetry request signal to the target terminal device node before receiving telemetry data each time. If the length adaptive element indicates that the telemetry length is a fixed value, the master control node sets the telemetry length according to the agreed fixed value; if the length adaptive element indicates that the telemetry length is adaptive, the telemetry transmission length is updated according to the actual length of the received telemetry data. A rationality check is performed on the main structure of the serial port telemetry transmission processing, specifically including checking the fields of the telemetry transmission synchronization header, the second serial port device address, and the second checksum.

10. The method according to claim 8, characterized in that, The telemetry transmission success / failure statistics include the telemetry transmission success count and the telemetry transmission error count; If the second checksum error is detected, the current transmission status is determined to be a checksum error, and the telemetry transmission error count is incremented by 1. If the target terminal device node fails to complete the telemetry data transmission within the requested time, the current transmission status is determined to be telemetry timeout, and the telemetry transmission error count is incremented by 1. If the check is correct and reception is completed within the requested time, the current transmission status is determined to be telemetry correct, and the telemetry transmission success count is incremented by 1.

Images