A method and system for solving multi-type telemetry data with cross-frame variable length
By checking the continuity of frame sequence numbers and the type-length mapping in telemetry data frames, the problems of low efficiency and cross-frame anomalies in telemetry data processing are solved, and efficient and accurate data processing is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- NO 63921 UNIT OF PLA
- Filing Date
- 2026-04-15
- Publication Date
- 2026-07-10
AI Technical Summary
Existing telemetry data processing methods suffer from low processing efficiency, lack of false search identification, and missing cross-frame anomaly handling, which can easily lead to processing errors, especially under unreliable UDP transmission.
By searching for preset identifiers starting from the frame header of the original telemetry data frame, checking the continuity of frame sequence numbers, determining the data length using the type-length mapping relationship, and splicing incomplete data across frames, mismatch of data areas and errors across frames are avoided.
It improves the efficiency and stability of telemetry data processing, prevents erroneous searches and cross-frame data splicing errors, and enhances overall performance.
Smart Images
Figure CN122372664A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of telemetry data processing technology, specifically a method and system for processing multi-type telemetry data with varying frame lengths. Background Technology
[0002] Telemetry parameters are transmitted using the raw telemetry data frame format. Various common telemetry parameters are combined into specific types of telemetry data blocks according to preset rules. The byte length of telemetry data blocks of the same type is a fixed value, while the byte length of telemetry data blocks of different types varies. A single frame of raw telemetry data typically encapsulates multiple heterogeneous telemetry data blocks and involves cross-frame transmission. Therefore, the processing of multi-type telemetry data with variable lengths across frames is a crucial aspect of telemetry data processing.
[0003] The commonly used solution method is as follows: First, search all identifiers globally in the original telemetry data frame, then cut out telemetry data blocks according to the identifiers. The last data block needs to be concatenated with the first data block of the next original data frame to form a complete telemetry data block. Finally, solve the data area parameters according to the data type. However, this solution method has the following problems: 1) Low solution efficiency: For each new frame of raw telemetry data received, all content except the frame header data needs to be searched; 2) Possibility of incorrect identifier search: Fields with the same identifier but not actually the identifier may appear in the data area. For example, if the identifier is 0XAABBCC, in common solution algorithms, all positions matching 0XAABBCC (including the data area) will be marked as the starting point of the new telemetry data; if 0XAABBCC appears in the data area, it will directly lead to a solution error; 3) Failure to consider cross-frame anomaly issues: Raw telemetry data frames are usually sent in UDP (User Datagram Protocol) format, and UDP is an unreliable transmission method, where data frames are sent first and arrive later. When the transmission is unreliable, the last frame splicing of cross-frame data will be incorrect. Summary of the Invention The purpose of this invention is to provide a method for solving multi-type telemetry data with varying frame lengths to solve the problems mentioned in the background art.
[0004] To achieve the above objectives, one aspect of the present invention provides the following technical solution: A method for processing multi-type telemetry data across frame-variable lengths includes the following steps: S1: Receive raw telemetry data frames; S2: Start searching from after the frame header of the original telemetry data frame until the first preset identifier is found; S3: Check whether the frame number of the current telemetry raw data frame is consecutive to the frame number of the previous telemetry raw data frame. S4: If the frame sequence numbers are consecutive, the telemetry data block corresponding to the first preset identifier in the current telemetry raw data frame is concatenated with the last telemetry data block of the previous telemetry raw data frame, and then the data area parameter value is calculated according to the type information of the telemetry data block. S5: Read the type value of the telemetry data block after the first preset identifier of the current telemetry raw data frame, and query the standard data length corresponding to the type value according to the preset type-length mapping relationship; S6: Determine whether the length of the standard data is greater than the length of the remaining unprocessed data in the current telemetry raw data frame; S7: If the corresponding telemetry data in the current telemetry data frame is determined to be incomplete data across frames, the incomplete data across frames is concatenated with the first telemetry data block of the next frame's original telemetry data frame. S8: Publish all solved parameter values.
[0005] Preferably, step S4 further includes: If the frame sequence numbers are not consecutive, the telemetry data blocks preceding the first preset identifier in the current telemetry raw data frame are discarded.
[0006] Preferably, step S7 specifically includes: S71: If the standard data length is less than or equal to the remaining unprocessed data length, the parameter value of the corresponding data area is calculated according to the type value, and then the next preset identifier is searched from the data area. If the next preset identifier is found, the process returns to step S5. If the next preset identifier is not found, it is determined that there is an identifier spanning frames, and the process proceeds to step S72. S72: If the standard data length is greater than the remaining unprocessed data length, or if the transition condition for identifying cross-frame in step S71 is met, then the corresponding telemetry data in the current telemetry data frame is determined to be incomplete cross-frame data, and the incomplete cross-frame data is spliced with the first telemetry data block of the next frame of original telemetry data.
[0007] Another aspect of the present invention provides a multi-type telemetry data processing system spanning frame-variable lengths, used to implement the multi-type telemetry data processing method spanning frame-variable lengths as described above, including: The data receiving module is used to receive raw telemetry data frames; The identifier search module is used to search from the frame header of the original telemetry data frame until the first preset identifier is found. The frame sequence number continuity judgment module is used to check whether the frame sequence number of the current telemetry raw data frame is continuous with the frame sequence number of the previous telemetry raw data frame. The data length reading module is used to read the type value of the telemetry data block from the first preset identifier of the current telemetry raw data frame, and query the standard data length corresponding to the type value according to the preset type-length mapping relationship; The cross-frame data judgment module determines whether the corresponding telemetry data in the current telemetry data frame is incomplete cross-frame data. The data block splicing module is used to splice telemetry data blocks. The publish module is used to publish all the calculated values of each parameter that have been solved.
[0008] Compared with the prior art, the beneficial effects of the present invention are: 1. In the process of identifier search, the present invention makes full use of the length characteristics of various telemetry data. By skipping the search data area, it can not only speed up the search, but also eliminate the risk of mismatching normal data in the data area as identifiers. 2. The step of checking the continuity of the original telemetry data frames by frame sequence number in this invention can solve the problem of cross-frame calculation errors caused by unreliable UDP transmission, thereby preventing deviations in parameter calculation values. Attached Figure Description
[0009] Figure 1 This is an overall flowchart of a multi-type telemetry data processing method with varying frame lengths in an embodiment of the present invention; Figure 2 This is a structural block diagram of a multi-type telemetry data processing system with varying lengths across frames, according to an embodiment of the present invention. Detailed Implementation
[0010] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0011] Figure 1 This is an overall flowchart of a method for solving multi-type telemetry data with varying lengths across frames, as described in an embodiment of the present invention. Figure 1 As shown, the embodiments of the present invention provide a method for solving multi-type telemetry data with varying frame lengths, including the following steps: S1: Receive raw telemetry data frames; S2: Start searching from after the frame header of the original telemetry data frame until the first preset identifier is found; S3: Check whether the frame number of the current telemetry raw data frame is consecutive to the frame number of the previous telemetry raw data frame. S4: If the frame sequence numbers are consecutive, the telemetry data block corresponding to the first preset identifier in the current telemetry raw data frame is concatenated with the last telemetry data block of the previous telemetry raw data frame, and then the data area parameter value is calculated according to the type information of the telemetry data block. S5: Read the type value of the telemetry data block after the first preset identifier of the current telemetry raw data frame, and query the standard data length corresponding to the type value according to the preset type-length mapping relationship; S6: Determine whether the length of the standard data is greater than the length of the remaining unprocessed data in the current telemetry raw data frame; S7: If the corresponding telemetry data in the current telemetry data frame is determined to be incomplete data across frames, the incomplete data across frames is concatenated with the first telemetry data block of the next frame's original telemetry data frame. S8: Publish all solved parameter values.
[0012] This invention addresses the shortcomings of existing methods for processing multi-type telemetry data with varying lengths across frames, such as low processing efficiency, mismatched identifiers, and lack of cross-frame anomaly handling. It provides a high-efficiency, accurate, and transmission-adaptable telemetry data processing scheme to solve the time-consuming problem caused by traversing all content except the frame header for each new data frame received in existing methods. It also avoids erroneous search errors caused by fields in the data area being identical to identifiers, and overcomes the cross-frame data splicing failure problem caused by unreliable UDP transmission, thereby improving the overall performance and stability of telemetry data processing.
[0013] In one embodiment of the present invention, step S4 further includes: If the frame sequence numbers are not consecutive, the telemetry data blocks preceding the first preset identifier in the current telemetry raw data frame are discarded.
[0014] The present invention solves the problem of cross-frame calculation errors caused by unreliable UDP transmission by checking the continuity of the original telemetry data frames through the frame sequence number, thereby preventing deviations in parameter calculation values.
[0015] In one embodiment of the present invention, step S7 specifically includes: S71: If the standard data length is less than or equal to the remaining unprocessed data length, the parameter value of the corresponding data area is calculated according to the type value, and then the next preset identifier is searched from the data area. If the next preset identifier is found, the process returns to step S5. If the next preset identifier is not found, it is determined that there is an identifier spanning frames, and the process proceeds to step S72. S72: If the standard data length is greater than the remaining unprocessed data length, or if the transition condition for identifying cross-frame in step S71 is met, then the corresponding telemetry data in the current telemetry data frame is determined to be incomplete cross-frame data, and the incomplete cross-frame data is spliced with the first telemetry data block of the next frame of original telemetry data.
[0016] In the process of identifier search, this invention makes full use of the length characteristics of various telemetry data to determine whether there is incomplete data across frames. By skipping the search data area, it can not only speed up the search, but also eliminate the risk of mismatching normal data in the data area as identifiers.
[0017] Figure 2 This is a structural block diagram of a multi-type telemetry data processing system with varying frame lengths according to an embodiment of the present invention. The present invention also provides a multi-type telemetry data processing system with varying frame lengths, used to implement the multi-type telemetry data processing method with varying frame lengths as described above, such as... Figure 2 As shown, it includes: The data receiving module is used to receive raw telemetry data frames; The identifier search module is used to search from the frame header of the original telemetry data frame until the first preset identifier is found. The frame sequence number continuity judgment module is used to check whether the frame sequence number of the current telemetry raw data frame is continuous with the frame sequence number of the previous telemetry raw data frame. The data length reading module is used to read the type value of the telemetry data block from the first preset identifier of the current telemetry raw data frame, and query the standard data length corresponding to the type value according to the preset type-length mapping relationship; The cross-frame data judgment module determines whether the corresponding telemetry data in the current telemetry data frame is incomplete cross-frame data. The data block splicing module is used to splice telemetry data blocks. The publish module is used to publish all the calculated values of each parameter that have been solved.
[0018] The present invention provides a multi-type telemetry data processing system with variable length across frames, which can solve the problem of time consumption caused by the need to traverse all contents except the frame header for each new data frame received by the existing method, avoid the false search error caused by the presence of the same field as the identifier in the data area, and overcome the problem of cross-frame data splicing failure caused by unreliable UDP transmission, thereby improving the overall performance and stability of telemetry data processing.
[0019] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.
Claims
1. A method for solving multi-type telemetry data with varying frame lengths, characterized in that, Includes the following steps: S1: Receive raw telemetry data frames; S2: Start searching from after the frame header of the original telemetry data frame until the first preset identifier is found; S3: Check whether the frame number of the current telemetry raw data frame is consecutive to the frame number of the previous telemetry raw data frame. S4: If the frame sequence numbers are consecutive, the telemetry data block corresponding to the first preset identifier in the current telemetry raw data frame is concatenated with the last telemetry data block of the previous telemetry raw data frame, and then the data area parameter value is calculated according to the type information of the telemetry data block. S5: Read the type value of the telemetry data block after the first preset identifier of the current telemetry raw data frame, and query the standard data length corresponding to the type value according to the preset type-length mapping relationship; S6: Determine whether the length of the standard data is greater than the length of the remaining unprocessed data in the current telemetry raw data frame; S7: If the corresponding telemetry data in the current telemetry data frame is determined to be incomplete data across frames, the incomplete data across frames is concatenated with the first telemetry data block of the next frame's original telemetry data frame. S8: Publish all solved parameter values.
2. The method for solving multi-type telemetry data with varying lengths across frames according to claim 1, characterized in that, Step S4 also includes: If the frame sequence numbers are not consecutive, the telemetry data blocks preceding the first preset identifier in the current telemetry raw data frame are discarded.
3. The method for solving multi-type telemetry data across frame-varying lengths according to claim 2, characterized in that, Step S7 specifically includes: S71: If the standard data length is less than or equal to the remaining unprocessed data length, the parameter value of the corresponding data area is calculated according to the type value, and then the next preset identifier is searched from the data area. If the next preset identifier is found, the process returns to step S5. If the next preset identifier is not found, it is determined that there is an identifier spanning frames, and the process proceeds to step S72. S72: If the standard data length is greater than the remaining unprocessed data length, or if the transition condition for identifying cross-frame in step S71 is met, then the corresponding telemetry data in the current telemetry data frame is determined to be incomplete cross-frame data, and the incomplete cross-frame data is spliced with the first telemetry data block of the next frame of original telemetry data.
4. A system for processing multi-type telemetry data across frame lengths, used to implement the method for processing multi-type telemetry data across frame lengths as described in any one of claims 1-3, characterized in that, include: The data receiving module is used to receive raw telemetry data frames; The identifier search module is used to search from the frame header of the original telemetry data frame until the first preset identifier is found. The frame sequence number continuity judgment module is used to check whether the frame sequence number of the current telemetry raw data frame is continuous with the frame sequence number of the previous telemetry raw data frame. The data length reading module is used to read the type value of the telemetry data block from the first preset identifier of the current telemetry raw data frame, and query the standard data length corresponding to the type value according to the preset type-length mapping relationship; The cross-frame data judgment module determines whether the corresponding telemetry data in the current telemetry data frame is incomplete cross-frame data. The data block splicing module is used to splice telemetry data blocks. The publish module is used to publish all the calculated values of each parameter that have been solved.