Rocket engine integrated controller multi-node udp transmission and analysis method

Abstract

The application discloses a rocket engine integrated controller multi-node UDP transmission and analysis method, and belongs to the technical field of spaceflight measurement and control and data transmission. The method comprises the following steps: a data receiving thread listens to a UDP port, receives a complete data frame sent by each controller node in multiple UDP data packets in turn, and after verification, sends the complete data frame into a thread-safe receiving queue according to a source node number; a buffer management thread extracts data packets, identifies a segment serial number according to a command word, and classifies and stores data areas into a buffer queue; a packet assembling thread reassembles the complete data frame in sequence after all data packets are collected; and an analysis thread calls a structured template library for matching analysis, extracts servo control parameters, fault diagnosis parameters or telemetry parameters. Through optimization of the UDP transmission protocol, the multi-thread safe queue architecture and the template analysis mechanism, the application solves the problems of data packet loss, congestion and low analysis efficiency in multi-node communication, and realizes high-reliability real-time transmission and accurate analysis of multi-node data of the rocket engine.

Description

Technical Field

[0001] This application relates to the field of aerospace telemetry, tracking and control and data transmission technology, and in particular to a multi-node UDP transmission and parsing method for a rocket engine integrated controller. Background Technology

[0002] In space launch missions, the integrated controller of a rocket engine plays a crucial role. It is responsible for receiving commands from the rocket / ground control system, precisely controlling the rocket engine, and providing real-time feedback on the engine's operational status data. With the rapid development of space technology, the amount of data that the integrated controller needs to process is increasing daily, and the data update frequency is also rising, placing higher demands on data transmission and analysis technologies.

[0003] Traditional data transmission methods, such as serial communication or low-speed network protocols, can no longer meet the requirements of rocket engine integrated controllers for data transmission speed and real-time performance. UDP, as a connectionless, unreliable, message-based transport layer protocol, although it does not guarantee data integrity, order, or correctness, has significant advantages in applications with extremely high real-time requirements due to its low overhead and high transmission speed.

[0004] However, applying UDP to data transmission in rocket engine integrated controllers also faces numerous challenges. First, due to the unreliability of UDP, an efficient data retransmission and verification mechanism needs to be designed to ensure data integrity and correctness. Second, effectively managing network traffic and avoiding data congestion and loss during UDP communication with multiple controller nodes is also a pressing issue. Furthermore, the data received by the rocket engine integrated controller typically includes various types, such as temperature, pressure, and speed; quickly and accurately parsing this data and extracting useful information is crucial for achieving precise engine control. Summary of the Invention

[0005] This invention addresses the technical problems existing in the background art by proposing a multi-node UDP transmission and parsing method for rocket engine integrated controllers.

[0006] To solve the technical problem, the technical solution of the present invention is as follows:

[0007] A method for multi-node UDP transmission and parsing in a rocket engine integrated controller, the method comprising: S1: The data receiving thread listens to the UDP port, receives UDP data packets sent by each controller node, verifies the UDP data packets, and sends them to the corresponding thread-safe receive queue according to the source node number; among them, each controller node splits the complete data frame to be sent into multiple UDP data packets and sends them sequentially. S2: The cache management thread extracts UDP packets from the receiving queue, identifies the segment sequence number of the UDP packet in the complete data frame according to the command word, and stores the data area into the corresponding cache queue according to the source node and segment sequence number. S3: The packet assembly thread listens to the cache queue. When it determines that all data packets constituting a complete data frame have been collected, the data area contents are retrieved in sequence according to the segment number and reassembled into a complete data frame. S4: The parsing thread calls a pre-set structured template library to match and parse the complete data frame; the template library is classified according to the data function type and defines field offsets, data types and verification rules, and finally extracts servo control parameters, fault diagnosis parameters or telemetry parameters.

[0008] Furthermore, the UDP data packet includes: a frame type field, a frame count field, a source node number field, a destination node number field, a retransmission count field, a data area field, and a CRC16 checksum field.

[0009] Furthermore, the frame type field includes periodic information frames, non-periodic information frames, and acknowledgment frames; wherein, the frame type value of a periodic information frame is 0x0002, and no acknowledgment frame is required from the receiver; the frame type value of a non-periodic information frame is 0x0001, and an acknowledgment frame is required from the receiver; the frame type value of an acknowledgment frame is 0x8001, and no further acknowledgment is required.

[0010] Furthermore, the generator polynomial of the CRC16 checksum field is x^16 + x^12 + x^5 + x^0, and the checksum is appended to the end of the data packet with the least significant byte first. If the receiver encounters a checksum error, it discards the data packet and considers it as if it has not been received. When the receiver determines that the data packet is incorrect or has not been received, it sends a retransmission request to the sender. The sender retransmits the corresponding data packet according to the retransmission request and increments the value of the retransmission count field.

[0011] Furthermore, each controller node splits the complete data frame into multiple UDP packets and sends all the packets corresponding to a complete data frame at a period of 10ms, with a 1ms interval between two adjacent packets.

[0012] Furthermore, in S2, the cache management thread also prioritizes storing the data area corresponding to high-priority data packets into the cache queue based on the priority identifier carried by the data packets; the priority includes high-priority servo control parameters, medium-priority fault diagnosis parameters, and low-priority telemetry parameters.

[0013] Furthermore, the structured template library is stored in categories such as servo control parameter templates, fault diagnosis parameter templates, and telemetry parameter templates. Each template is pre-set with the field offset, data length, data type, value range threshold, and field relationship of the corresponding data type. Each template is also assigned a unique type identifier code, which is used to match the type identifier carried in the complete data frame.

[0014] Furthermore, the data receiving thread, the cache management thread, the packet assembly thread, and the parsing thread run independently in the host computer, and asynchronous data transmission and decoupling between threads are achieved through the thread-safe receiving queue and the cache queue.

[0015] Furthermore, the frame count field has a value range of 0 to 4294967295. The frame count starts from 1 and increments by 1 each time a new data packet is sent, except for retransmission of frames. When the frame count reaches the maximum value, it starts counting again from 0.

[0016] This application has the following advantages: By optimizing the UDP transmission protocol, designing frame type identification, frame count tracking, CRC16 check and retransmission mechanisms, and splitting complete data frames for transmission, the high-speed transmission advantage of UDP is retained while effectively overcoming its unreliability defects, thus achieving highly reliable real-time data transmission in a multi-node environment.

[0017] By adopting a priority-based network traffic management mechanism, combined with a multi-threaded architecture and thread-safe queues, data reception, caching, packet assembly, and parsing tasks are separated and processed in parallel to avoid single-threaded blocking. At the same time, priority scheduling is used to ensure the transmission of key parameters such as servo control, thus solving the problems of data congestion and packet loss in multi-node communication.

[0018] A structured template library categorized by data function was constructed, and rapid data parsing and extraction were achieved through template matching, significantly improving parsing efficiency and meeting the real-time requirements of rocket engine integrated controller for accurate parsing of multiple types of parameters.

[0019] This application can be widely used in multi-node data interaction scenarios of rocket engine integrated controllers and other aerospace equipment, providing efficient and reliable data support for precise engine control. Attached Figure Description

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

[0021] Figure 1 A system framework diagram of the multi-node UDP transmission and parsing method for the integrated controller of a rocket engine provided in this application embodiment; Figure 2 This is a technical roadmap for the multi-node UDP transmission and parsing method of the rocket engine integrated controller provided in the embodiments of this application. Detailed Implementation

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

[0023] Example 1: This embodiment provides a multi-node UDP transmission and parsing method for a rocket engine integrated controller. This method is applied to the host computer monitoring system of the rocket engine integrated controller to achieve real-time, reliable data transmission and efficient data parsing between multiple controller nodes. The host computer adopts a multi-threaded architecture design, with each thread running independently and cooperating collaboratively. Figure 1 A schematic diagram of the multi-threaded framework in this invention is shown. Figure 2 A flowchart of the data parsing algorithm in this invention is shown.

[0024] I. UDP packet structure design; In this embodiment, each controller node splits the complete data frame to be sent into multiple UDP packets and sends them sequentially. The specific format of the UDP packets is shown in Table 1. Each UDP packet includes the following fields: frame type field, frame count field, source node number field, destination node number field, retransmission count field, data area field, and CRC16 checksum field. The byte length and description of each field are detailed in Table 1.

[0025] Table 1 UDP Packet Format Table

[0026] For each controller node, since a complete data frame requires a large amount of data to be transmitted, the complete data frame is split into multiple UDP packets according to the above format for transmission. Each controller node sends all the UDP packets corresponding to a complete data frame at a period of 10ms, with a 1ms interval between the transmission of two adjacent UDP packets. Through the above packet-segmentation transmission method, while retaining the advantages of UDP protocol in terms of high transmission speed and low overhead, its unreliability defects are effectively overcome, ensuring the integrity and correctness of data during high-speed transmission.

[0027] Regarding data transmission reliability, the generator polynomial for the CRC16 checksum field is x^16 + x^12 + x^5 + x^0, and the checksum is appended to the end of the data packet with the least significant byte first. If the checksum fails, the receiver discards the data packet, treating it as if it was not received. When the receiver determines that a data packet is incorrect or has not been received, it sends a retransmission request to the sender. The sender retransmits the corresponding data packet according to the retransmission request and increments the value of the retransmission count field. This synergistic effect of retransmission and checksum mechanisms ensures reliable data delivery over the unreliable UDP transport protocol.

[0028] II. Multithreaded architecture and queue mechanism; To ensure the real-time nature of data reception, the orderly nature of caching, and the efficiency of packet assembly, the data reception and caching process of the host computer adopts a multi-threaded and queue mechanism in collaboration. By dividing the work among threads and using queue buffering, the bottleneck of single-threaded processing is broken, ensuring the stability of data processing under complex working conditions.

[0029] like Figure 1 As shown, the host computer adopts a multi-threaded architecture design, with separate deployments for data receiving, cache management, packet assembly, and parsing threads. Each thread runs independently in the host computer, and asynchronous data transmission and decoupling between threads are achieved through thread-safe receive queues and cache queues, avoiding processing delays caused by task stacking in a single thread.

[0030] Specifically, the data receiving thread is dedicated to listening to the UDP port and capturing UDP packets from each controller node in real time. This thread only handles data reception and initial verification tasks and does not participate in subsequent complex processing, maximizing packet capture efficiency and avoiding packet loss due to processing time. Once the data receiving thread captures a UDP packet, it first performs a CRC16 check on the packet's integrity. If the check passes, the UDP packet is immediately sent to the corresponding controller's thread-safe receive queue according to the source node number, completing the closed loop of the receiving task.

[0031] The cache management thread continuously monitors the thread-safe receive queues of each thread. Once a data packet is detected in the queue, it retrieves the UDP data packet for further processing. This queue mechanism enables asynchronous communication between the data receiving thread and the cache management thread, preventing the receiving thread from being blocked while waiting for cache processing and ensuring the continuity of data reception. Furthermore, the thread-safe receive queue has a locking mechanism, which effectively avoids data races and errors during concurrent access by multiple threads, ensuring that UDP data packets are stored and retrieved in the queue in the order they were received.

[0032] After retrieving UDP packets from the receive queue, the cache management thread first identifies the source controller of the data based on the source node number field in the UDP packet. This step ensures that the source of the data is clear and traceable, providing a foundation for subsequent classification and processing by controller and fault location. Simultaneously, it parses the command word in the UDP packet's data area, which indicates the segment sequence number of the UDP packet within the complete data frame.

[0033] After determining the source and segment sequence number of the UDP packets, the cache management thread categorizes the data area fields of the UDP packets according to the source node and segment sequence number and stores them into the corresponding controller's cache queue. Each controller has an independent cache queue, further ensuring the isolation and ordering of data from different sources. This caching process relies on the first-in, first-out (FIFO) characteristic of queues to ensure that before all UDP packets are received, each frame of data is cached in sequence according to its segment sequence number, preventing loss, omission, or out-of-order issues, while also facilitating the orderly retrieval of data by the subsequent packet assembly thread.

[0034] III. Priority Traffic Management Mechanism; This embodiment also designs a priority-based network traffic management mechanism. Different priority levels are assigned to different types of data based on their urgency and importance. Specifically, the data is divided into high-priority servo control parameters, medium-priority fault diagnosis parameters, and low-priority telemetry parameters.

[0035] During the cache management thread's processing, data areas corresponding to high-priority data packets are preferentially stored in the cache queue based on the priority identifier carried by the UDP packets. Through this priority scheduling mechanism, the transmission and processing of critical data such as servo control parameters are prioritized when the network load is high, effectively avoiding data congestion and packet loss problems in multi-node communication.

[0036] IV. Packaging and Reassembly; The packet assembly thread continuously monitors the buffer queues corresponding to each controller. By recognizing and counting command words, it determines whether all the data packets buffered in the current buffer queue have been collected to form a complete data frame. Once it is determined that all data packets have been collected, the packet assembly thread retrieves the contents of all data area fields from the corresponding buffer queue according to the segment sequence number, and concatenates the contents of each data area in order to reassemble them into a complete data frame.

[0037] This packet assembly process utilizes the first-in-first-out characteristic of the buffer queue and the structure of storing data according to segment sequence numbers to ensure that the data area content of each UDP packet can be accurately restored in the original sending order, avoiding data corruption caused by out-of-order arrival.

[0038] V. Data parsing based on a structured template library; The completed data frame, once assembled, contains all the necessary engine operating status information. The parsing thread calls a pre-installed structured template library on the host computer to match and parse the complete data frame.

[0039] The construction process of the structured template library is as follows: First, it is categorized according to data function type, into servo control parameter templates, fault diagnosis parameter templates, and telemetry parameter templates. Each template clearly defines core elements, including field offsets, data length (e.g., 16-bit, 32-bit), data type (e.g., float, double, uint16, int16, etc.), value range thresholds, checksum rules, and relationships between fields. Simultaneously, a unique type identifier code is assigned to each template type for matching with the type identifier carried in the complete data frame. The template library is stored in the host computer's local cache to reduce call time and improve parsing efficiency.

[0040] like Figure 2 As shown, after receiving a complete data frame, the parsing thread first extracts the type identifier from the data frame and matches it with the unique type identifier code of each template in the template library. If a match is successful, based on the predefined field offsets, data lengths, and data types in the corresponding template, it sequentially extracts servo control parameters, fault diagnosis parameters, or telemetry parameters from the data frame. The final parsing result can be displayed to the user or used for system closed-loop control, providing real-time and accurate data support for the precise control of the rocket engine.

[0041] The method provided in this embodiment optimizes the UDP transmission protocol, designs frame type identification, frame count tracking, CRC16 check and retransmission mechanisms, and splits complete data frames for transmission. While retaining the advantages of UDP high-speed transmission, it effectively overcomes its unreliability defects and achieves highly reliable real-time data transmission in a multi-node environment.

[0042] By adopting a priority-based network traffic management mechanism, combined with a multi-threaded architecture and thread-safe queues, data reception, caching, packet assembly, and parsing tasks are separated and processed in parallel to avoid single-threaded blocking. At the same time, priority scheduling is used to ensure the transmission of key parameters such as servo control, thus solving the problems of data congestion and packet loss in multi-node communication.

[0043] By constructing a structured template library categorized by data function and employing template matching, rapid data parsing and extraction are achieved, significantly improving parsing efficiency and meeting the real-time requirements of rocket engine integrated controllers for accurate parsing of multiple types of parameters.

[0044] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0045] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for multi-node UDP transmission and parsing in a rocket engine integrated controller, characterized in that, The method includes: S1: The data receiving thread listens to the UDP port, receives UDP data packets sent by each controller node, verifies the UDP data packets, and sends them to the corresponding thread-safe receive queue according to the source node number; among them, each controller node splits the complete data frame to be sent into multiple UDP data packets and sends them sequentially. S2: The cache management thread extracts UDP packets from the receiving queue, identifies the segment sequence number of the UDP packet in the complete data frame according to the command word, and stores the data area into the corresponding cache queue according to the source node and segment sequence number. S3: The packet assembly thread listens to the cache queue. When it determines that all data packets constituting a complete data frame have been collected, the data area contents are retrieved in sequence according to the segment number and reassembled into a complete data frame. S4: The parsing thread calls a pre-set structured template library to match and parse the complete data frame; the template library is classified according to the data function type and defines field offsets, data types and verification rules, and finally extracts servo control parameters, fault diagnosis parameters or telemetry parameters.

2. The method for multi-node UDP transmission and parsing of a rocket engine integrated controller according to claim 1, characterized in that, The UDP data packet includes: frame type field, frame count field, source node number field, destination node number field, retransmission count field, data area field, and CRC16 checksum field.

3. The method for multi-node UDP transmission and parsing of a rocket engine integrated controller according to claim 2, characterized in that, The frame type field includes periodic information frames, non-periodic information frames, and acknowledgment frames; wherein, the frame type value of periodic information frames is 0x0002, and no acknowledgment frame is required from the receiver; the frame type value of non-periodic information frames is 0x0001, and an acknowledgment frame is required from the receiver; the frame type value of acknowledgment frames is 0x8001, and no further acknowledgment is required.

4. The method for multi-node UDP transmission and parsing of a rocket engine integrated controller according to claim 2, characterized in that, The generator polynomial of the CRC16 checksum field is x^16 + x^12 + x^5 + x^0. The checksum is appended to the end of the data packet with the least significant byte first. If the receiver encounters a checksum error, it discards the data packet and considers it not received. When the receiver determines that the data packet is incorrect or has not been received, it sends a retransmission request to the sender. The sender retransmits the corresponding data packet according to the retransmission request and increments the value of the retransmission count field.

5. The method for multi-node UDP transmission and parsing of a rocket engine integrated controller according to claim 1, characterized in that, Each controller node splits the complete data frame into multiple UDP packets and sends all the packets corresponding to a complete data frame at a period of 10ms, with a 1ms interval between the transmission of two adjacent packets.

6. The method for multi-node UDP transmission and parsing of a rocket engine integrated controller according to claim 1, characterized in that, In step S2, the cache management thread also prioritizes storing the data area corresponding to high-priority data packets into the cache queue based on the priority identifier carried by the data packets; the priority includes high-priority servo control parameters, medium-priority fault diagnosis parameters, and low-priority telemetry parameters.

7. The method for multi-node UDP transmission and parsing of a rocket engine integrated controller according to claim 1, characterized in that, The structured template library is stored in categories such as servo control parameter templates, fault diagnosis parameter templates, and telemetry parameter templates. Each template has pre-set field offsets, data lengths, data types, value range thresholds, and inter-field relationships for the corresponding data type. Each template is also assigned a unique type identifier code, which is used to match the type identifier carried in the complete data frame.

8. The method for multi-node UDP transmission and parsing of a rocket engine integrated controller according to claim 1, characterized in that, The data receiving thread, the cache management thread, the packet assembly thread, and the parsing thread run independently in the host computer, and asynchronous data transmission and decoupling between threads are achieved through the thread-safe receiving queue and the cache queue.

9. A method for multi-node UDP transmission and parsing of a rocket engine integrated controller according to claim 2, characterized in that, The frame count field has a value range of 0 to 4294967295. The frame count starts from 1 and increments by 1 each time a new data packet is sent, except for retransmission of frames. When the frame count reaches the maximum value, it starts counting again from 0.

Images