Telemetry data analysis method and system

Abstract

The application provides a telemetry data analysis method and system, comprising: repeatedly using a structured telemetry configuration file homologous to a ground test system; adjusting the structured telemetry configuration file homologous to the ground test system; maintaining original core code of an on-orbit fault diagnosis load; and establishing a telemetry analysis capability model multiple times based on the structured telemetry configuration file homologous to the ground test system.

Description

Technical Field

[0001] This invention relates to the field of aerospace technology, and in particular to a method and system for telemetry data analysis. Background Technology

[0002] Traditional on-orbit fault diagnosis payloads typically use hardware decoding to process satellite platform telemetry data. This means that APIDs, telemetry parameter locations, data types, engineering value calculation relationships, and output formats are pre-defined within the diagnostic payload software. When the satellite computer code is refactored, a single platform unit is replaced, an external payload is added, the mission combination mode changes, or the telemetry structure is adjusted, the original hardware decoding logic cannot automatically adapt to the new telemetry data structure, which can easily lead to the diagnostic payload being unable to correctly parse the platform's telemetry data. Summary of the Invention

[0003] The purpose of this invention is to provide a telemetry data parsing method and system to solve the problem that existing decoding methods cannot automatically adapt to the new telemetry data structure of modified spacecraft.

[0004] To solve the above-mentioned technical problems, the present invention provides a telemetry data parsing method, comprising: Use a structured telemetry configuration file that is the same as the one used in the ground testing system; Adjust the structured telemetry configuration file; and Based on the structured telemetry configuration file, a telemetry resolution capability model is established.

[0005] Optionally, the telemetry data parsing method further includes: The modified spacecraft and / or satellite platform fully receives telemetry data, on-orbit fault diagnosis payloads, and on-board intelligent payload data, performs data processing, ground testing, and on-orbit homogeneous configuration reuse; The data supply for building and reconstructing diagnostic models is built within the on-orbit fault diagnosis payload; Modified spacecraft include reconfiguration of spacecraft software, replacement of individual platform components, access to external payloads, changes in mission combination modes, and adjustments to telemetry APID or parameter structure. The core code of the fault diagnosis payload is fixed, and the recovery or update of the diagnostic payload affects the parsing, quality labeling and standardized distribution of platform telemetry.

[0006] Optionally, in the telemetry data parsing method, the parameters of the telemetry parsing capability model include an APID set, a telemetry packet set, a parameter set, parameter locations, input types, engineering value calculation rules, parameter dependencies, quality rules, and / or standardized output mappings.

[0007] Optionally, in the telemetry data parsing method, the use of a structured telemetry configuration file of the same origin as the ground test system includes: The updated configuration file is loaded via betting configuration, preset configuration switching, or application restart; and After the new configuration takes effect, newly added APIDs or telemetry data will be included in the parsing and output scope, while deleted APIDs or telemetry data will stop being parsed and output, in order to modify the parameters of the telemetry parsing capability model; and The establishment of the telemetry resolution capability model based on the structured telemetry configuration file includes: The parameters of the modified telemetry resolution capability model are analyzed according to the new location, new type, or new formula rules to reconstruct the telemetry resolution capability model that is effective for the current diagnostic payload.

[0008] Optionally, the telemetry data parsing method further includes: By extracting the original bytes and interpretation types from the structured telemetry configuration file, and separating the formula chain solution, the parameter type interpretation logic of the main parsing process for specific models or single machines is adjusted to adapt to various configurations, single machines, and telemetry layouts. Through parameter-level anomaly isolation and quality labeling mechanisms, when a single telemetry measurement experiences out-of-bounds errors, bad values, dependency anomalies, or solution anomalies, its quality status and error information are recorded. Simultaneously, other available telemetry measurements within the same package continue to be output, providing continuous on-orbit fault diagnosis data. By unifying and standardizing telemetry data objects and local inter-process distribution interfaces, a unified input is provided for multiple upper-layer diagnostic applications, diagnostic models, or scripted diagnostic engines, thereby decoupling the on-orbit fault diagnosis model from the underlying telemetry format.

[0009] Optionally, the telemetry data parsing method further includes: The telemetry receiving and frame synchronization preprocessing unit receives the full telemetry data sent by the satellite platform through an external communication interface, and performs synchronization header lookup, length verification, frame type verification and complete frame extraction. The same-source configuration loading module loads a structured telemetry configuration file that is the same as the ground test system. The structured telemetry configuration file describes APID, telemetry packets, parameter encoding, parameter bytes or bits (byte position and bit position), input type, byte order, formula chain, conditional expression, parameter dependency relationship, output unit and quality rules. The telemetry parsing capability model construction module parses the structured telemetry configuration file into a currently executable telemetry parsing capability model. The telemetry parsing capability model includes an APID mapping table, a telemetry package definition table, a parameter extraction table, an input type table, a formula chain execution table, a parameter dependency context, and a standardized output description. The APID and parameter mapping module matches the corresponding telemetry packet with the APID in the complete telemetry frame and determines the set of telemetry parameters to be parsed. The raw byte extraction module extracts the raw bytes or bit segments related to the target parameters from the telemetry payload data based on the bytes or bits described in the structured telemetry configuration file. The type interpretation and formula chain solving module converts raw bytes or intermediate values ​​into engineering values ​​based on input type, byte order, formula chain, conditional expression, and parameter dependency context. When a single telemetry measurement experiences an out-of-bounds error, bad value, missing dependency, formula anomaly, or local parsing failure, the parameter-level anomaly isolation and quality labeling module writes a quality field and error message to that telemetry measurement and allows other telemetry measurements to continue parsing. The standardized output module organizes the parsing results into a unified data object, which includes packet-level metadata, parameter encoding, parameter name, raw bytes, engineering value, unit, quality field, and error information. The diagnostic application distribution interface module distributes standardized telemetry data objects to multiple upper-layer diagnostic applications, diagnostic models, or scripted diagnostic engines through a local inter-process communication interface.

[0010] Optionally, the telemetry data parsing method further includes: When a spacecraft undergoes a single-unit replacement, external payload access, combination mode change, or satellite service software reconfiguration, the ground test system updates and verifies the same-source configuration file, and uploads the new configuration to the on-orbit fault diagnosis payload via the uplink remote control link, or the on-orbit side selects the preset configuration according to the command. Based on engineering constraints, pause the current real-time service flow and restart the telemetry adaptation and parsing application without interrupting the power supply to the load, or reload the target configuration. After the configuration takes effect, the APID mapping table, parameter extraction table, formula chain execution table, parameter dependency context, and output description are rebuilt based on the new configuration to rebuild the current telemetry parsing capability.

[0011] Optionally, the telemetry data parsing method further includes: For newly added APIDs or telemetry data, after the new configuration takes effect, the corresponding parsing and output relationships will be established. When an APID or telemetry measurement is deleted, the generation of parsing results is stopped and the corresponding data is no longer distributed to upper-layer diagnostic applications. For telemetry measurements where parameter location, input type, formula chain, or dependencies have changed, perform parsing according to the new configuration.

[0012] Optionally, the telemetry data parsing method further includes: The system compares the currently effective configuration with the configuration to be effective, identifies newly added items, deleted items, and changed items, and generates a configuration change record; the configuration change record identification assists in ground backtracking.

[0013] Optionally, the telemetry data parsing method further includes: Retain the stable configuration of the previous version; If the configuration file to be used does not exist, structured parsing fails, or it is incompatible with the current software capabilities, the configuration will be rejected, and the previous stable configuration will be retained to support the continued operation of the fault diagnosis load.

[0014] The present invention also includes a telemetry data parsing system, comprising: The parameter configuration and adjustment unit is configured to reuse the structured telemetry configuration file of the same origin as the ground test system; and Adjust the structured telemetry configuration file that is identical to the ground test system; The telemetry resolution capability building block is configured to maintain the original core code for on-orbit fault diagnosis payloads; and Based on the structured telemetry configuration file that is the same as the ground test system, a telemetry analysis capability model was established multiple times.

[0015] In the telemetry data parsing method and system provided by this invention, the parameter configuration and adjustment unit reuses the structured telemetry configuration file that is the same as the ground test system and adjusts the structured telemetry configuration file that is the same as the ground test system. While maintaining the original core code of the on-orbit fault diagnosis payload, the telemetry parsing capability construction unit establishes the telemetry parsing capability model multiple times based on the structured telemetry configuration file that is the same as the ground test system. This realizes that by reusing the structured telemetry configuration file that is the same as the ground test system, the on-orbit fault diagnosis payload can build and reconstruct the telemetry parsing capability model based on the configuration file without modifying the core code.

[0016] The inventors of this invention discovered through research that existing decoding methods cannot automatically adapt to the new telemetry data structure of modified spacecraft, specifically in the following ways: Existing configuration-driven parsing solutions are mostly geared towards ground testing, offline telemetry software, general display software, or single business applications, typically focusing on configuration file loading, field extraction, parsing, and display. While these solutions can reduce the amount of modification required for ground software, they do not model the current parsing capability status of the on-orbit fault diagnosis payload—"which APIDs can be parsed, which parameters, how to calculate them, how to label the quality, and how to output them to the diagnostic model"—as an effective, switchable, and reversible parsing capability.

[0017] Some integrated space-ground telemetry configuration management solutions focus on satellite frame configuration, ground-based frame table resolution, on-orbit programming annotations, and satellite-ground closed-loop comparison, primarily addressing the consistency issue between on-board frame configuration and ground-based resolution configuration. These solutions do not prioritize the internal resolution capability model, parameter-level quality annotation, and diagnostic data object distribution within the fault diagnosis payload.

[0018] Some multi-source telemetry processing or downlink data fusion solutions focus on converting data from different sources such as geodetic surveying, telemetry, and data transmission into a common format or forwarding it to the ground server, addressing the issue of ground systems being compatible with different channels and formats. However, these solutions do not address how to rebuild the analytical capabilities of on-orbit diagnostic payloads after configuration changes and how to continuously provide reliable data to multiple diagnostic models.

[0019] Some payload status discrimination schemes focus on telemetry feature selection, machine learning model training, or status classification output, with the core being the diagnostic discrimination algorithm itself. The core of this scheme is not training or limiting a particular diagnostic model, but rather providing standardized telemetry data objects that are consistent, labelable in quality, and sustainably available for different diagnostic models.

[0020] Existing solutions typically lack effective control and rollback mechanisms for on-orbit operational constraints during configuration updates. If the configuration file to be updated does not exist, structured parsing fails, or it is incompatible with the current software capabilities, it can easily lead to parsing program startup failure, incorrect configuration taking effect, or interruption of diagnostic data supply.

[0021] Existing solutions often fail as a whole packet, interrupt the process, or only issue error alarms in cases of abnormalities such as bad values, out-of-bounds bytes, formula anomalies, and missing dependencies. It is difficult to isolate a single abnormal parameter within the same telemetry packet and keep other normal parameters output to the upper-level diagnostic model.

[0022] Existing diagnostic models often adapt to different underlying telemetry frame formats, APID layouts, and parameter fields, resulting in high coupling between the diagnostic models and the underlying telemetry structure. When the spacecraft's telemetry structure changes, each diagnostic model needs to repeatedly modify its data access logic, leading to high expansion and maintenance costs.

[0023] The purpose of this invention is to provide a method and system for constructing and reconstructing telemetry analytical capability models for on-orbit fault diagnosis payloads for spacecraft with variable configurations, thereby solving the problem that traditional hard-decoding fault diagnosis payloads cannot adapt to on-orbit changes in spacecraft configurations, single-unit replacements, external payload access, satellite software reconstruction, and dynamic changes in telemetry structures.

[0024] This invention reuses a structured telemetry configuration file that is the same as that of the ground test system, enabling on-orbit fault diagnosis payloads to build a currently effective telemetry resolution capability model based on the configuration file without modifying the core code, and to rebuild the capability model after configuration updates, preset configuration switching, or application restarts.

[0025] This invention defines "telemetry resolution capability" as a set of capabilities comprised of APID sets, telemetry packet sets, parameter sets, parameter locations, input types, engineering value calculation rules, parameter dependencies, quality rules, and standardized output mappings. Furthermore, by supporting configuration annotation, preset configuration switching, or application restart to load updated configuration files, newly added APIDs or telemetry measurements are included in the resolution and output scope after the new configuration takes effect; deleted APIDs or telemetry measurements cease resolution and output. Modified parameters are resolved according to their new locations, types, or formula rules. Therefore, the configuration changes provided by this invention do not simply modify the parameter table, but rather reconstruct the telemetry resolution capability of the currently effective diagnostic payload.

[0026] This invention adopts a method that separates raw byte extraction from type interpretation and formula chain calculation, so that the main parsing process does not fix the parameter type interpretation logic of specific models or single machines, thereby enhancing the adaptability to different configurations, different single machines, and different telemetry layouts.

[0027] This invention uses a parameter-level anomaly isolation and quality labeling mechanism to record the quality status and error information of a single telemetry measurement when it experiences out-of-bounds errors, bad values, dependency anomalies, or solution anomalies. At the same time, it continues to output other available telemetry measurements in the same package, thereby improving the continuity of on-orbit fault diagnosis data supply.

[0028] This invention provides a unified input for multiple upper-layer diagnostic applications, diagnostic models, or scripted diagnostic engines by unifying and standardizing telemetry data objects and local inter-process distribution interfaces, thereby reducing the coupling of diagnostic models to the underlying telemetry formats.

[0029] This invention is applicable to on-orbit fault diagnosis payloads for variable-structure spacecraft. It enables fault diagnosis payloads to restore or rebuild telemetry resolution capabilities without modifying the core code after spacecraft undergoes reconfiguration of satellite software, replacement of individual units, access of external payloads, changes in mission combination mode, or changes in telemetry structure, and to continuously provide usable data to the diagnostic model.

[0030] The configuration file in this invention is not a typical protocol configuration table, display configuration table, or satellite service frame table generation basis, but rather used to construct the currently effective telemetry resolution capability model. The telemetry resolution capability model includes at least an APID mapping table, a telemetry packet definition table, a parameter extraction table, an input type table, a formula chain execution table, a parameter dependency context, quality rules, and a standardized output description. In other words, this invention provides the diagnostic payload's capability status—"what it can currently resolve, how to resolve it, how to label its quality, and how to output it to the diagnostic model"—rather than simply reading the configuration and completing field parsing or interface display.

[0031] The core processing chain of the telemetry data parsing method proposed in this invention is as follows: loading of homogeneous structured configuration, configuration validity verification, construction of parsing capability model, APID and parameter mapping, extraction of raw bytes or bit fields, type interpretation, parameter dependency parsing and formula chain calculation, parameter-level anomaly isolation, quality labeling, output of standardized telemetry data objects, and local diagnostic distribution. This chain differs from existing technologies that commonly use integrated generation of satellite / ground frame tables, on-orbit programming to modify satellite frame tables, parsing of large ground-level hierarchical tables, satellite-ground closed-loop comparison, unification of multi-source telemetry formats throughout the entire lifecycle, VCDU / BPDU / MPDU data reassembly, and B / S server relay or machine learning status determination.

[0032] Existing technologies typically employ general parsing methods to output parsing results, display interfaces, result files, or data in a common telemetry format; satellite-ground configuration management methods output satellite crew configuration, ground parsing configuration, on-orbit data entry, or closed-loop verification results; and state discrimination methods output payload state classification results. This invention outputs a standardized telemetry data object for multiple fault diagnosis applications or diagnostic models. This object carries packet-level metadata, parameter encoding, raw values, engineered values, units, quality fields, and error information, providing a unified input for rule-based diagnosis, trend analysis, scripted diagnosis, or AI-based diagnosis.

[0033] Furthermore, the technical advantage of the telemetry data parsing method of this invention lies in parameter-level anomaly isolation and data supply continuity. When a single telemetry measurement experiences byte out-of-bounds errors, bad values, missing dependencies, formula anomalies, or local parsing failures, the telemetry data parsing method of this invention does not terminate the overall parsing of the same telemetry packet. Instead, it writes the abnormal parameters into the quality field and error information, while continuing to output other available parameters from the same packet. This mechanism differs from ordinary error detection, alarms, or outlier removal; its function is to ensure that on-orbit fault diagnosis payloads can still provide usable input to the diagnostic model under abnormal data scenarios.

[0034] This invention also proposes a configuration failure fallback mechanism: it performs file existence, structured parsing, and software capability compatibility checks on the configuration to be applied; when configuration loading fails, parsing fails, or it is incompatible with current software capabilities, it rejects the erroneous configuration and retains the previous stable configuration to avoid interruptions in on-orbit diagnostic data supply caused by erroneous configurations. This further distinguishes it from ordinary configuration file verification or ground software error prompts, reflecting the engineering constraints on the reliability of on-orbit diagnostic payload operation.

[0035] In summary, this invention provides a method and system for constructing and reconstructing telemetry analytical capability models for on-orbit fault diagnosis payloads of variable-structure spacecraft. It constructs the currently effective analytical capability model through homogeneous structured telemetry configuration, reconstructs the model after configuration changes, and ensures that multiple diagnostic applications continuously obtain reliable telemetry input through parameter-level anomaly isolation, quality labeling, standardized telemetry data objects, and local diagnostic distribution mechanisms. Attached Figure Description

[0036] Figure 1 This is a schematic flowchart of a telemetry data parsing method according to an embodiment of the present invention; Figure 2 This is a schematic diagram of the overall architecture of a telemetry data parsing system according to an embodiment of the present invention; Figure 3 This is a schematic diagram of the process of reusing structured telemetry configuration files in a telemetry data parsing method according to an embodiment of the present invention; Figure 4 This is a schematic diagram of the process for constructing telemetry parsing capability using a telemetry data parsing method according to an embodiment of the present invention; Figure 5 This is a schematic diagram of the process of reconstructing parsing capabilities based on a new configuration in a telemetry data parsing method according to an embodiment of the present invention; Figure 6 This is a schematic diagram of the process of single-parameter abnormal quality labeling and other parameters of the same package being output in a telemetry data parsing method according to an embodiment of the present invention. Detailed Implementation

[0037] In this invention, the various embodiments are merely intended to illustrate the solutions of the invention and should not be construed as limiting.

[0038] It should also be noted that within the scope of this invention, the terms "same", "equal", and "equal to" do not mean that the two values ​​are absolutely equal, but allow for a certain reasonable error. In other words, the terms also cover "substantially the same", "substantially equal", and "substantially equal to".

[0039] Furthermore, the numbering of the steps in the methods of the present invention does not limit the execution order of the method steps. Unless otherwise specified, the method steps may be executed in different orders.

[0040] The telemetry data analysis method and system proposed in this invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. The advantages and features of this invention will become clearer from the following description and claims. It should be noted that the drawings are all in a very simplified form and use non-precise proportions, and are only used to facilitate and clarify the illustration of the embodiments of this invention.

[0041] The purpose of this invention is to provide a telemetry data parsing method and system to solve the problem that existing decoding methods cannot automatically adapt to the new telemetry data structure of modified spacecraft.

[0042] To achieve the above objectives, the present invention provides a telemetry data parsing method and system, comprising: a parameter configuration and adjustment unit configured to reuse a structured telemetry configuration file of the same origin as the ground test system; and to adjust the structured telemetry configuration file of the same origin as the ground test system; a telemetry parsing capability construction unit configured to maintain the original core code of the on-orbit fault diagnosis payload; and to establish a telemetry parsing capability model multiple times based on the structured telemetry configuration file of the same origin as the ground test system.

[0043] Embodiments of the present invention provide a telemetry data parsing method, such as... Figure 1 As shown, Figure 1 The process flow of telemetry data parsing is illustrated, including: reusing a structured telemetry configuration file that is the same as the ground test system; adjusting the structured telemetry configuration file that is the same as the ground test system; maintaining the original core code of the on-orbit fault diagnosis payload; and establishing the telemetry parsing capability model multiple times based on the structured telemetry configuration file that is the same as the ground test system.

[0044] In one embodiment of the telemetry data parsing method of the present invention, "telemetry parsing capability" is defined as a capability set composed of APID set, telemetry packet set, parameter set, parameter location, input type, engineering value calculation rules, parameter dependency relationship, quality rules, and standardized output mapping. Configuration changes do not simply modify the parameter table, but rather reconstruct the telemetry parsing capability currently in effect for the diagnostic payload.

[0045] In one embodiment of the telemetry data parsing method of the present invention, the method further includes: It supports loading updated configuration files via configuration loading, switching preset configurations, or application restart. After the new configuration takes effect, newly added APIDs or telemetry values ​​are included in the parsing and output scope, while deleted APIDs or telemetry values ​​stop parsing and output. Modified parameters are parsed according to the new position, new type, or new formula rules. By separating raw byte extraction from type interpretation and formula chain calculation, the main parsing process does not fix the parameter type interpretation logic of specific models or single machines, thereby enhancing the adaptability to different configurations, different single machines, and different telemetry layouts. Through parameter-level anomaly isolation and quality labeling mechanisms, when a single telemetry measurement experiences out-of-bounds, bad values, dependency anomalies, or solution anomalies, the quality status and error information of that telemetry measurement are recorded, while other available telemetry measurements in the same package continue to be output, thereby improving the continuity of on-orbit fault diagnosis data supply. By unifying and standardizing telemetry data objects and local inter-process distribution interfaces, a unified input is provided for multiple upper-layer diagnostic applications, diagnostic models, or scripted diagnostic engines, reducing the coupling of diagnostic models to the underlying telemetry format.

[0046] Figure 2 The overall architecture of the telemetry data parsing system is shown, such as... Figure 2 As shown, the telemetry data parsing method in this embodiment is implemented by the following main components or modules. The modules work together in a chain of "receiving telemetry data, loading the same-source configuration, building the parsing capability model, parsing parameters according to the model, isolating anomalies, standardizing output, and reconstructing and rolling back the configuration": (1) Telemetry Reception and Frame Synchronization Preprocessing Unit 10: This unit is used to receive the full amount of telemetry data sent by the satellite platform through an external communication interface, and to perform synchronization header lookup, length verification, frame type verification, and complete frame extraction. This unit belongs to the system's front-end data processing part and can be implemented using UDP reception, bus reception, or other onboard communication interfaces.

[0047] (2) Same-source configuration loading module 20: Used to load structured telemetry configuration files that are from the same source as the ground test system. The configuration file describes APID, telemetry packets, parameter encoding, parameter bytes or bits, input type, byte order, formula chain, conditional expression, parameter dependency, output unit, and quality rules. The XML configuration file in the current project can be used as a preferred embodiment.

[0048] (3) Telemetry parsing capability model construction module 30: used to parse the configuration file into a currently executable telemetry parsing capability model, the model including APID mapping table, telemetry package definition table, parameter extraction table, input type table, formula chain execution table, parameter dependency context and standardized output description.

[0049] (4) APID and parameter mapping module 40: used to match the corresponding telemetry packet based on the APID in the complete telemetry frame and determine the set of telemetry parameters to be parsed. For APIDs that do not exist in the new configuration, the system does not generate corresponding parsing results.

[0050] (5) Raw byte extraction module 50: used to extract the raw bytes or bit segments involved in the target parameters from the telemetry payload data according to the bytes or bits described in the configuration file.

[0051] (6) Type interpretation and formula chain solution module 60: used to convert raw bytes or intermediate values ​​into engineering values ​​based on input type, byte order, formula chain, conditional expression and parameter dependency context.

[0052] (7) Parameter-level anomaly isolation and quality labeling module 70: When a single telemetry measurement is out of bounds, has a bad value, missing dependency, formula anomaly, or local parsing failure, it writes a quality field and error information to the telemetry measurement and keeps other telemetry measurements parsing.

[0053] (8) Standardized output module 80: used to organize the parsing results into a unified data object, wherein the unified data object includes at least packet-level metadata, parameter encoding, parameter name, raw bytes, engineering value, unit, quality field and error information.

[0054] (9) Diagnostic Application Distribution Interface Module (Local Inter-Process Distribution Interface 90): Used to distribute standardized telemetry data objects to multiple upper-layer diagnostic applications, diagnostic models, or scripted diagnostic engines through a local inter-process communication interface. UDS and Protobuf in the current project are preferred embodiments, but not the only implementation methods.

[0055] (10) Optional enhancement module: In a preferred embodiment, the system may further include a configuration verification and previous stable configuration retention module, which is used to check the file existence, structured parsing results and software capability compatibility of the configuration to be effective, and to retain the previous stable configuration when the configuration loading fails or the application restart fails.

[0056] Figure 3 This embodiment illustrates the data flow diagram of the telemetry data parsing method, including telemetry reception, frame synchronization, APID mapping, raw byte extraction, formula chain solution, quality labeling, and normalized output. Figure 3 As shown, when the telemetry data parsing system (hereinafter referred to as the system) is working, the telemetry receiving and frame synchronization preprocessing unit receives all telemetry data from the satellite platform and extracts complete telemetry frames from continuous data streams or packetized data. The extracted telemetry frames enter the APID and parameter mapping module.

[0057] The same-source configuration loading module loads the structured telemetry configuration file after system startup or configuration update. After parsing, the configuration file is sent to the telemetry resolution capability model building module, which generates an APID mapping table, parameter extraction table, input type table, formula chain execution table, parameter dependency context, and standardized output description. This process enables the system to form the currently effective telemetry resolution capability model.

[0058] The APID and parameter mapping module extracts APIDs from the complete telemetry frame and determines the target telemetry packet and the set of parameters to be parsed based on the currently effective telemetry parsing capability model. If the current configuration does not contain a certain APID, that APID will not enter the subsequent parsing output process; if the configuration contains a newly added APID, that APID will enter the parsing scope after the configuration takes effect.

[0059] The raw byte extraction module extracts the raw bytes or bit fields related to each parameter from the target telemetry frame according to the parameter extraction table. This module is only responsible for extracting raw data according to the configuration and does not fix the specific data type interpretation in the main process.

[0060] The type interpretation and formula chain solution module performs engineering value calculations on the raw data based on the input type, byte order, formula chain, conditional expression, and parameter dependency context. For telemetry data without dependent parameters, the system first completes the basic calculation and generates a context result; for telemetry data that depends on other parameters, the system performs subsequent calculations based on the already generated context. The current project supports multiple telemetry function nodes, expression functions, conditional branch functions, and cross-parameter references.

[0061] The parameter-level anomaly isolation and quality labeling module does not terminate the overall parsing process when parameters exceed limits, contain outdated values, have abnormal formulas, lack dependencies, or fail to resolve locally. Instead, it marks the corresponding parameter as having an abnormal quality state and records the error information. For other parameters within the same telemetry packet that are not affected by this anomaly, the system continues to complete the parsing and output.

[0062] The standardized output module organizes the parsed results into a unified data object, which is then passed to the diagnostic application distribution interface module for output to upper-layer diagnostic applications or diagnostic models. This unified data object can be represented using a unified serialization protocol, facilitating consumption by diagnostic applications using different languages ​​or processes.

[0063] Figure 4 The flowchart illustrating the configuration of the telemetry data parsing method in this embodiment, including configuration uploading / preset switching / application restart and reconstruction of parsing capabilities based on the new configuration, is shown below. Figure 4 As shown, when a spacecraft undergoes a single-unit replacement, external payload access, change in combination mode, or reconfiguration of onboard software, the ground test system first updates and verifies the source configuration file, then uploads the new configuration to the on-orbit fault diagnosis payload via the uplink remote control link, or the on-orbit side selects a preset configuration according to instructions. Based on engineering constraints, the system can pause the current real-time service flow and restart the telemetry adaptation and resolution application without power interruption to the payload, or reload the target configuration. After the configuration takes effect, the system rebuilds the APID mapping table, parameter extraction table, formula chain execution table, parameter dependency context, and output description based on the new configuration, thereby reconstructing the current telemetry resolution capability.

[0064] Figure 5 The diagram illustrates the reconstruction of parsing capabilities based on the new configuration after adding or deleting an APID and modifying parameter positions. Figure 5As shown, in a telemetry data parsing method according to an embodiment of the present invention, for newly added APIDs or newly added telemetry measurements, the system establishes corresponding parsing and output relationships after the new configuration takes effect; for deleted APIDs or deleted telemetry measurements, the system no longer generates parsing results for them, nor does it distribute corresponding data to the upper-layer diagnostic application; for telemetry measurements whose parameter positions, input types, formula chains, or dependencies have changed, the system performs parsing according to the new configuration.

[0065] In one embodiment of the telemetry data parsing method described in this invention, the system can further compare the currently effective configuration with the configuration to be effective, identify newly added items, deleted items, and changed items, and generate a configuration change record. This difference identification can be used to shorten configuration verification time and assist ground backtracking, but it is not the only way necessary for this solution to achieve zero-code adaptation.

[0066] Figure 6 This diagram illustrates a flowchart of a telemetry data parsing method according to an embodiment of the present invention, showing the single-parameter anomaly quality labeling while other parameters in the same packet are continued to be output. Figure 6 As shown, in a telemetry data parsing method according to an embodiment of the present invention, the system can retain the previous stable configuration. When the configuration file to be implemented does not exist, structured parsing fails, or it is incompatible with the current software capabilities, the system refuses to use the configuration and retains the previous stable configuration to support the continued operation of the fault diagnosis payload.

[0067] In summary, this invention may include a main telemetry resolution process and a configuration update and reconstruction process. The main telemetry resolution process includes: S1, the fault diagnosis payload side receives telemetry frames or telemetry packets from the satellite platform and loads a structured telemetry configuration file of the same origin as the ground test system; S2 performs checks on the existence of the configuration file to be implemented, structured parsing, and software capability compatibility; if the checks fail, the faulty configuration is rejected and the previous stable configuration is retained; S3 will resolve the approved configuration into the currently effective telemetry resolution capability model; S4, Identify APID from telemetry frames or telemetry packets, and determine the target telemetry packet and the set of parameters to be parsed based on the currently active model, to obtain the parameter list P1...Pn; S5, select the current parameter Pi to be parsed, and extract the original bytes or bit fields of the target parameter according to the parameter extraction table; S6, type interpretation, parameter dependency resolution and formula chain calculation, solves the project value according to input type, byte order, formula chain and parameter dependency context; S7. If Pi parsing is successful, output normal parameter samples; otherwise, isolate parameter-level anomalies (without interrupting the entire packet process). Write the quality field and error information to the single parameter with parsing anomalies, while continuing to parse and output other parameters in the same packet. Merge them into the current telemetry packet output set, determine if there are any subsequent parameters, and repeat the above steps if there are; otherwise, update the packet-level statistics. S8 organizes the parsed results into standardized telemetry data objects and provides them to fault diagnosis applications or diagnostic models through a local distribution interface.

[0068] The configuration update and rebuild process includes: S9 repeats the configuration verification and capability model construction process after configuration annotation, preset configuration switching, or application restart, and rebuilds the currently effective telemetry resolution capability model based on the new configuration.

[0069] In one embodiment of the telemetry data parsing method described in this invention, the adaptation of the reconstructed satellite computer software is performed. Due to a mission upgrade, the satellite's computer software is reconstructed, resulting in changes to the telemetry sequence, byte positions, and engineering value calculation relationships in several APIDs output to the fault diagnosis payload. The ground test system first updates the same-source telemetry configuration file and completes ground verification, then sends the configuration file to the on-orbit fault diagnosis payload via the uplink remote control link. The on-orbit payload pauses its current real-time data service flow and restarts the telemetry adaptation and parsing application without power interruption. After the application starts, it loads the new configuration, reconstructs the APID mapping table, parameter extraction table, and formula chain execution table, and resumes outputting standardized telemetry data to the diagnostic model. The entire process requires no modification to the core code of the on-orbit diagnostic payload.

[0070] In one embodiment of the telemetry data parsing method of the present invention, adaptation is performed after adding new external payloads or replacing a single unit. After the spacecraft combines new external payloads or replaces a single unit of a platform in orbit, new APIDs and telemetry sets are introduced. On the ground, a homogeneous configuration file is generated or updated for the newly added unit and uploaded to the in-orbit diagnostic payload. After the configuration takes effect, the newly added APIDs automatically enter the parsing range, and the newly added telemetry measurements begin to be output to the diagnostic model as a unified data object.

[0071] In one embodiment of the telemetry data parsing method of the present invention, adaptation is performed after deleting an APID or disabling a single machine. After disabling some single machines or deleting an APID in a certain task phase, the new configuration file no longer contains that APID. After the system loads the new configuration, parameter parsing is no longer performed on that APID, nor are corresponding results distributed to the upper-layer diagnostic application, thereby preventing the diagnostic model from continuing to consume expired data objects.

[0072] In one embodiment of the telemetry data parsing method of the present invention, adaptation is performed after changes in parameter positions or formula chains. A certain APID still exists, but the byte positions, input types, or engineering value calculation formulas of some telemetry measurements within it have changed. The system regenerates the parameter extraction table and formula chain execution table based on the new configuration, enabling telemetry measurements under the same APID to calculate engineering values ​​according to the new positions and formula rules.

[0073] In one embodiment of the telemetry data parsing method of the present invention, cross-parameter dependency solving is performed. A certain engineering value parameter depends on the parsing result of another telemetry parameter within the same package. The system first parses the parameters without dependencies and forms a context, and then performs formula chain solving of the dependent parameters based on the context, thereby supporting cross-parameter references defined in the configuration file.

[0074] In one embodiment of the telemetry data parsing method of the present invention, parameter-level anomaly isolation is implemented. If some parameters within a telemetry packet cannot be correctly calculated for their engineering values ​​due to out-of-bounds bytes or bad values, the system outputs an anomaly quality flag and error information for that parameter, while continuing to parse other normal parameters and outputting them to the diagnostic model. The diagnostic model can decide whether to ignore the parameter, downgrade its use, or trigger anomaly diagnostic logic based on the quality field.

[0075] In one embodiment of the telemetry data parsing method described in this invention, multiple diagnostic applications consume data in parallel. The fault diagnosis payload internally contains a rule-based diagnostic model, a trend analysis model, and a scripted diagnostic engine. Each application accesses the telemetry data adaptation and parsing system through a local inter-process communication interface, consuming a unified, standardized data object. When the underlying APID structure changes, only the configuration needs to be updated and the parsing capability rebuilt; upper-layer diagnostic applications do not need to modify the underlying parsing logic separately.

[0076] An embodiment of the present invention also provides a telemetry data parsing system in which a parameter configuration and adjustment unit is configured to reuse a structured telemetry configuration file of the same origin as the ground test system; and to adjust the structured telemetry configuration file of the same origin as the ground test system; a telemetry parsing capability construction unit is configured to maintain the original core code of the on-orbit fault diagnosis payload; and to establish a telemetry parsing capability model multiple times based on the structured telemetry configuration file of the same origin as the ground test system.

[0077] The beneficial effects of this invention include: (1) Since the structured configuration file with the same source as the ground test system is adopted, the telemetry description that has been verified on the ground can be directly used as the basis for constructing the analytical capability of the on-orbit diagnostic payload, reducing the risk of inconsistency between the ground and on-orbit analytical rules.

[0078] (2) Since the APID set, telemetry package set, parameter set, parameter location, engineering value calculation rules, parameter dependency relationship, quality rules and output mapping are jointly modeled as telemetry analysis capability model, the system can describe which telemetry measurements the diagnostic load can currently analyze and output from the capability level, rather than just describing a single parameter table.

[0079] (3) Since APID mapping, parameter extraction, formula chain and output description can be reconstructed based on the new configuration after configuration changes, the on-orbit diagnostic payload can adapt to the newly added, deleted or adjusted telemetry structure without modifying the core code.

[0080] (4) Because the original byte extraction and type interpretation and formula chain solution are separated, the parsing main process does not fix the specific telemetry type interpretation logic, and can adapt to different single machines, different APIDs and different parameter layouts.

[0081] (5) Due to the adoption of parameter-level anomaly isolation and quality labeling mechanism, a single telemetry anomaly will not cause other telemetry failures in the same package. The diagnostic model can decide whether to use, ignore or downgrade the corresponding parameter based on the quality field.

[0082] (6) Due to the adoption of standardized telemetry data objects and higher-level local inter-process distribution interfaces, multiple upper-level diagnostic applications can share the same parsing results, reducing the cost of repeatedly adapting to the underlying telemetry format.

[0083] (7) Since the specific communication protocol, configuration format and serialization method can be replaced, the system can be adapted to different models, different load platforms and different diagnostic application deployment methods, and has good engineering scalability.

[0084] In this invention, the modules of the system according to the invention can be implemented using software, hardware, firmware, or a combination thereof. When a module is implemented using software, its function can be implemented through computer program flow. For example, the module can be implemented using code segments (such as code segments in languages ​​like C and C++) stored in a storage device (such as a hard disk, memory, etc.), wherein the corresponding function of the module can be implemented when the code segment is executed by a processor. When a module is implemented using hardware, its function can be implemented by setting a corresponding hardware structure. For example, the module's function can be implemented by hardware programming a programmable device such as a field-programmable gate array (FPGA), or by designing an application-specific integrated circuit (ASIC) that includes multiple transistors, resistors, capacitors, and other electronic devices. When a module is implemented using firmware, the module's function can be written into a read-only memory such as an EPROM or EEPROM in the form of program code, and the corresponding function of the module can be implemented when the program code is executed by a processor. In addition, some functions of the module may need to be implemented by separate hardware or by working in cooperation with the hardware. For example, the detection function is implemented by a corresponding sensor (such as a proximity sensor, accelerometer, gyroscope, etc.), the signal transmission function is implemented by a corresponding communication device (such as a Bluetooth device, infrared communication device, baseband communication device, Wi-Fi communication device, etc.), the output function is implemented by a corresponding output device (such as a display, speaker, etc.), and so on.

[0085] While some embodiments of the present invention have been described in this application, those skilled in the art will understand that these embodiments are merely illustrative. Numerous variations, alternatives, and improvements will arise in those skilled in the art under the teachings of this invention without departing from its scope. The appended claims are intended to define the scope of the invention and thereby cover the methods and structures within the scope of the claims themselves and their equivalents in power conversion.

Claims

1. A method for parsing telemetry data, characterized in that, include: Use a structured telemetry configuration file that is the same as the one used in the ground testing system; Adjust the structured telemetry configuration file; as well as Based on the structured telemetry configuration file, a telemetry resolution capability model is established.

2. The telemetry data parsing method as described in claim 6, characterized in that, Also includes: The modified spacecraft and / or satellite platform fully receives telemetry data, on-orbit fault diagnosis payloads, and on-board intelligent payload data, performs data processing, ground testing, and on-orbit homogeneous configuration reuse; The data supply for building and reconstructing diagnostic models is built within the on-orbit fault diagnosis payload; Modified spacecraft include reconfiguration of spacecraft software, replacement of individual platform components, access to external payloads, changes in mission combination modes, and adjustments to telemetry APID or parameter structure. The core code of the fault diagnosis payload is fixed, and the recovery or update of the diagnostic payload affects the parsing, quality labeling and standardized distribution of platform telemetry.

3. The telemetry data parsing method as described in claim 1, characterized in that, The parameters of the telemetry resolution capability model include APID set, telemetry packet set, parameter set, parameter location, input type, engineering value calculation rules, parameter dependency relationship, quality rules and / or standardized output mapping.

4. The telemetry data parsing method as described in claim 1, characterized in that, The use of a structured telemetry configuration file derived from the same source as the ground testing system includes: The updated configuration file is loaded via betting configuration, preset configuration switching, or application restart; and After the new configuration takes effect, newly added APIDs or telemetry data will be included in the parsing and output scope, while deleted APIDs or telemetry data will stop being parsed and output, in order to modify the parameters of the telemetry parsing capability model; and The establishment of the telemetry resolution capability model based on the structured telemetry configuration file includes: The parameters of the modified telemetry resolution capability model are analyzed according to the new location, new type, or new formula rules to reconstruct the telemetry resolution capability model that is effective for the current diagnostic payload.

5. The telemetry data parsing method as described in claim 4, characterized in that, Also includes: By extracting the original bytes and interpretation types from the structured telemetry configuration file, and separating the formula chain solution, the parameter type interpretation logic of the main parsing process for specific models or single machines is adjusted to adapt to various configurations, single machines, and telemetry layouts. Through parameter-level anomaly isolation and quality labeling mechanisms, when a single telemetry measurement experiences out-of-bounds, bad values, dependency anomalies, or solution anomalies, the quality status and error information of that telemetry measurement are recorded. At the same time, other available telemetry measurements in the same package continue to be output to continuously provide on-orbit fault diagnosis data. as well as By unifying and standardizing telemetry data objects and local inter-process distribution interfaces, a unified input is provided for multiple upper-layer diagnostic applications, diagnostic models, or scripted diagnostic engines, thereby decoupling the on-orbit fault diagnosis model from the underlying telemetry format.

6. The telemetry data parsing method as described in claim 5, characterized in that, Also includes: The telemetry receiving and frame synchronization preprocessing unit receives the full telemetry data sent by the satellite platform through an external communication interface, and performs synchronization header lookup, length verification, frame type verification and complete frame extraction. The same-source configuration loading module loads a structured telemetry configuration file that is the same as the ground test system. The structured telemetry configuration file describes APID, telemetry packets, parameter encoding, parameter bytes or bits, input type, byte order, formula chain, conditional expression, parameter dependency relationship, output unit and quality rules. The telemetry parsing capability model construction module parses the structured telemetry configuration file into a currently executable telemetry parsing capability model. The telemetry parsing capability model includes an APID mapping table, a telemetry package definition table, a parameter extraction table, an input type table, a formula chain execution table, a parameter dependency context, and a standardized output description. The APID and parameter mapping module matches the corresponding telemetry packet with the APID in the complete telemetry frame and determines the set of telemetry parameters to be parsed. The raw byte extraction module extracts the raw bytes or bit segments related to the target parameters from the telemetry payload data based on the bytes or bits described in the structured telemetry configuration file. The type interpretation and formula chain solving module converts raw bytes or intermediate values ​​into engineering values ​​based on input type, byte order, formula chain, conditional expression, and parameter dependency context. When a single telemetry measurement experiences an out-of-bounds error, bad value, missing dependency, formula anomaly, or local parsing failure, the parameter-level anomaly isolation and quality labeling module writes a quality field and error message to that telemetry measurement and allows other telemetry measurements to continue parsing. The standardized output module organizes the parsing results into a unified data object, which includes packet-level metadata, parameter encoding, parameter name, raw bytes, engineering value, unit, quality field, and error information. The diagnostic application distribution interface module distributes standardized telemetry data objects to multiple upper-layer diagnostic applications, diagnostic models, or scripted diagnostic engines through a local inter-process communication interface.

7. The telemetry data parsing method as described in claim 1, characterized in that, Also includes: When a spacecraft undergoes a single-unit replacement, external payload access, combination mode change, or satellite service software reconfiguration, the ground test system updates and verifies the same-source configuration file, and uploads the new configuration to the on-orbit fault diagnosis payload via the uplink remote control link, or the on-orbit side selects the preset configuration according to the command. Based on engineering constraints, pause the current real-time service flow and restart the telemetry adaptation and parsing application without interrupting the power supply to the load, or reload the target configuration. After the configuration takes effect, the APID mapping table, parameter extraction table, formula chain execution table, parameter dependency context, and output description are rebuilt based on the new configuration to rebuild the current telemetry parsing capability.

8. The telemetry data parsing method as described in claim 7, characterized in that, Also includes: For newly added APIDs or telemetry data, after the new configuration takes effect, the corresponding parsing and output relationships will be established. When an APID or telemetry measurement is deleted, the generation of parsing results is stopped and the corresponding data is no longer distributed to upper-layer diagnostic applications. For telemetry measurements where parameter location, input type, formula chain, or dependencies have changed, perform parsing according to the new configuration.

9. The telemetry data parsing method as described in claim 7, characterized in that, Also includes: Compare the currently effective configuration with the configuration to be effective, identify newly added, deleted, and changed items, and generate a configuration change record; The configuration change record identification assists in ground backtracking; Retain the stable configuration of the previous version; If the configuration file to be used does not exist, structured parsing fails, or it is incompatible with the current software capabilities, the configuration will be rejected, and the previous stable configuration will be retained to support the continued operation of the fault diagnosis load.

10. A telemetry data parsing system, characterized in that, include: The parameter configuration and adjustment unit is configured to reuse the structured telemetry configuration file of the same origin as the ground test system; as well as Adjust the structured telemetry configuration file that is identical to the ground test system; The telemetry resolution capability building unit is configured to maintain the original core code for on-orbit fault diagnosis payloads; as well as Based on the structured telemetry configuration file that is the same as the ground test system, a telemetry analysis capability model was established multiple times.

Images