Spacecraft dynamic test execution method based on telemetry data
By aligning and dynamically adjusting spacecraft telemetry data, the problems of inconsistent telemetry data transmission and inaccurate timing of automatic test tools were solved, achieving efficient, accurate and reliable data support for spacecraft dynamic testing, and ensuring the accuracy and security of test results.
Patent Information
- Application Number
- CN202411801846.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-09
- Publication Date
- 2025-09-19
- Estimated Expiration
- 2044-12-09
AI Technical Summary
During the dynamic testing of spacecraft, the bandwidth capacity of telemetry data, measurement and control methods, and mission requirements lead to inconsistent status data transmission time. The time-driven mechanism of the automatic testing tool leads to inaccurate timing of command sending and interpretation, affecting the accuracy and reliability of the test results.
By aligning the telemetry data from various data sources of the spacecraft, analyzing its quality index, and dynamically adjusting it based on the average duration of telemetry control instructions, data synchronization and accuracy are ensured, and the timing control engine is used to achieve timing synchronization between the test tool and the target machine.
It improves the accuracy and reliability of spacecraft dynamic testing, ensures the accuracy and consistency of data, avoids errors in test results, improves test response speed and safety, and provides accurate decision-making support for space missions.
Smart Images

Figure CN119611784B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data adjustment technology, and in particular to a method for executing spacecraft dynamic tests based on telemetry data. Background Art
[0002] The execution of telemetry-based dynamic testing of spacecraft stems from the complexity and high risk involved in spacecraft launch, on-orbit operation, and mission execution. Telemetry technology has emerged to ensure the reliability and stability of spacecraft systems in extreme environments. By acquiring real-time operational data on spacecraft, including temperature, vibration, attitude, and power system status, ground control centers can monitor the spacecraft's health and predict and address potential failures.
[0003] The prior art, such as the invention patent announcement with announcement number: CN115617023B, discloses a method and device for locating anomalies in a spacecraft attitude control system, wherein the method includes: determining an information set of sample telemetry data to be detected, the sample telemetry data to be detected including: the name of the telemetry parameter to be detected, the parameter characteristics and data values corresponding to each telemetry parameter name to be detected; pre-processing the sample telemetry data to be detected to obtain processed telemetry data; performing attitude determination mode telemetry and attitude control mode telemetry parameter change sequence detection on the processed telemetry data according to preset spacecraft characteristics; marking the attitude determination mode telemetry and attitude control mode telemetry parameter change sequence according to a preset data marking method to generate an attitude fault feature sequence; and automatically locating the abnormal device components in the attitude control system according to the attitude fault feature sequence.
[0004] The prior art, such as the invention patent announcement with announcement number: CN104834305B, discloses a distribution network automation terminal telemetry anomaly analysis system and method based on the DMS system, including a current anomaly monitoring module and a voltage anomaly monitoring module. The current anomaly monitoring module and the voltage anomaly monitoring module are respectively connected to the DMS system and the distribution network production system. The current anomaly monitoring module compares the real-time telemetry data of the three-phase current of the DMS system with its historical telemetry data and the feeder switch current in the DMS system to determine whether the telemetry current of the distribution network automation terminal is abnormal so as to issue a telemetry anomaly work order to the distribution network production system; the voltage anomaly monitoring module compares the real-time telemetry data of the phase-to-phase voltage on the power side and the phase-to-phase voltage on the load side of the DMS system with the historical telemetry data and the limit voltage to determine whether the telemetry voltage of the distribution network automation terminal is abnormal so as to issue a telemetry anomaly work order to the distribution network production system.
[0005] Current dynamic testing of spacecraft using telemetry data presents several challenges. First, during spacecraft software testing, telemetry data is limited by bandwidth capacity, measurement and control methods, and mission requirements. This can result in state data for a given control cycle arriving at different times when transmitted to the ground via telemetry channels. During automated testing, the most recently received telemetry parameters may not accurately reflect the state of the spacecraft software within the same control cycle, leading to test failures. Second, traditional automated testing tools are all time-driven, querying the system time or telemetry data of the software under test at a fixed frequency and initiating test execution when execution conditions are met. Because the automated test driver software and the test environment execute asynchronously, and due to delays in query intervals, test execution response delays, and command and data transmission delays, the timing of command transmission and data interpretation during automated testing cannot be precisely controlled. This presents risks of delayed command transmission and interpretation, resulting in test conclusions that do not accurately reflect the software status. Summary of the Invention
[0006] In view of the deficiencies of the prior art, the present invention provides a method for executing spacecraft dynamic tests based on telemetry data, which can effectively solve the problems involved in the above-mentioned background technology.
[0007] To achieve the above objectives, the present invention is implemented through the following technical solutions: a spacecraft dynamic test execution method based on telemetry data, including collecting telemetry data from various data sources of the spacecraft, testing and analyzing the telemetry data from various data sources of the spacecraft, obtaining the alignment results of the telemetry data from various data sources of the spacecraft, and aligning the telemetry data from various data sources of the spacecraft to obtain telemetry alignment data of various data sources of the spacecraft.
[0008] The telemetry alignment data of each spacecraft data source are analyzed to obtain the quality index of the telemetry alignment data of each spacecraft data source, and the telemetry alignment data of each spacecraft data source are interpreted and processed according to the quality index of the telemetry alignment data of each spacecraft data source to obtain the interpretation result of the telemetry alignment data of each spacecraft data source.
[0009] According to the interpretation results of the telemetry alignment data of each data source of the spacecraft and the average duration of the telemetry control instructions of the spacecraft, the collection of telemetry data is adjusted, and the dynamic adjustment quality results of the telemetry data are obtained.
[0010] Furthermore, the telemetry data of each data source of the spacecraft includes the time point of sending each test command, the time point of starting to execute each test command, the time point of sending each telemetry data, the time point of receiving each telemetry data, the time interval of collecting telemetry data, and the average query interval delay of telemetry data.
[0011] Furthermore, the telemetry data of each data source of the spacecraft is tested and analyzed, and the specific analysis process is: extracting the time point of sending each test command of each data source of the spacecraft and the time point of starting to execute each test command, and performing difference processing to obtain the test execution response delay of each test command.
[0012] The time points of receiving telemetry data and sending telemetry data of each data source of the spacecraft are extracted, and the difference processing is performed to obtain the transmission delay of each telemetry data.
[0013] The test execution response delay of each test command of each data source of the spacecraft, the delay of each telemetry data transmission, the collection time interval of the telemetry data and the average query interval delay of the telemetry data are extracted, and the alignment requirement index of the telemetry data of each data source of the spacecraft is obtained after processing. The alignment requirement index of the telemetry data of each data source of the spacecraft is used to evaluate the degree of synchronization of the telemetry data.
[0014] Furthermore, the alignment results of the telemetry data of each data source of the spacecraft are obtained, and the specific analysis conditions are: extracting the alignment requirement index of the telemetry data of each data source of the spacecraft, and comparing it with the alignment requirement index threshold of the telemetry data of each data source of the spacecraft stored in the database to obtain the alignment results of the telemetry data of each data source of the spacecraft. The alignment results of the telemetry data of each data source of the spacecraft include those that need alignment and those that do not need alignment. If the alignment requirement index of the telemetry data of a certain data source of the spacecraft is higher than or equal to the alignment requirement index threshold of the telemetry data of the spacecraft, the alignment result of the telemetry data of the spacecraft's data source is defined as requiring alignment, and alignment processing is performed on the telemetry data of the spacecraft's data source. If the alignment requirement index of the telemetry data of a certain data source of the spacecraft is lower than the alignment requirement index threshold of the telemetry data of the spacecraft's data source, the alignment result of the telemetry data of the spacecraft's data source is defined as not requiring alignment.
[0015] Furthermore, the telemetry data of each data source of the spacecraft are aligned to obtain the telemetry alignment data of each data source of the spacecraft. The specific process is: according to the alignment result of the telemetry data of each data source of the spacecraft, the telemetry data of each data source of the spacecraft are aligned; if the alignment result of the telemetry data of a certain data source of the spacecraft needs to be aligned, the telemetry data of the data source of the spacecraft is aligned, and the telemetry data of the data source of the spacecraft is marked as the telemetry alignment data of each data source of the spacecraft; if the alignment result of the telemetry data of a certain data source of the spacecraft does not need to be aligned, the telemetry data of the data source of the spacecraft is directly marked as the telemetry alignment data of each data source of the spacecraft, thereby obtaining the telemetry alignment data of each data source of the spacecraft.
[0016] Furthermore, the telemetry alignment data of each spacecraft data source are analyzed to obtain the quality index of the telemetry alignment data of each spacecraft data source. The specific analysis process is: counting the data collection time points in each spacecraft data source, and extracting the data collection time points in each spacecraft data source, extracting the reference time points stored in the database, and performing absolute value processing on the difference between the reference time points and the data collection time points in each spacecraft data source to obtain the collection time difference of each data in each spacecraft data source.
[0017] The mean error of the acquisition time of each data in each spacecraft data source is calculated, and the data missing rate in each spacecraft data source is calculated. After processing, the quality index of the telemetry alignment data of each spacecraft data source is obtained. The quality index of the telemetry alignment data of each spacecraft data source is used to indicate the reliability of the alignment quality of the telemetry data.
[0018] Furthermore, the telemetry alignment data of each spacecraft data source are interpreted and processed to obtain the interpretation results of the telemetry alignment data of each spacecraft data source. The specific process is: according to the quality index of the telemetry alignment data of each spacecraft data source, and compared with the quality index threshold of the telemetry alignment data of each spacecraft data source stored in the database, the interpretation results of the telemetry alignment data of each spacecraft data source are obtained.
[0019] Furthermore, the interpretation results of the telemetry alignment data of each data source of the spacecraft include normal and abnormal. If the quality index of the telemetry alignment data of a certain data source of the spacecraft is higher than or equal to the quality index threshold of the telemetry alignment data of the data source of the spacecraft, the interpretation result of the telemetry alignment data of the data source of the spacecraft is defined as normal. If the quality index of the telemetry alignment data of a certain data source of the spacecraft is lower than the quality index threshold of the telemetry alignment data of the data source of the spacecraft, the interpretation result of the telemetry alignment data of the data source of the spacecraft is defined as abnormal.
[0020] Furthermore, the telemetry data collection is adjusted based on the judgment result of the telemetry alignment data of each data source of the spacecraft and the average duration of the telemetry control instructions of the spacecraft, and the dynamic adjustment quality result of the telemetry data is obtained. The specific process is: if the judgment result of the telemetry alignment data of a certain data source of the spacecraft is normal, there is no need to collect and adjust the telemetry data; if the judgment result of the telemetry alignment data of a certain data source of the spacecraft is abnormal, the average duration of the telemetry control instructions of the spacecraft is obtained, and the reference duration of the telemetry control instructions of the spacecraft stored in the database is extracted, and the average duration of the telemetry control instructions of the spacecraft is compared with the reference duration of the telemetry control instructions of the spacecraft stored in the database; if the average duration of the telemetry control instructions of the spacecraft is higher than or equal to the reference duration of the telemetry control instructions of the spacecraft, the telemetry data of the data source of the spacecraft is re-collected and an alarm is triggered; if the average duration of the telemetry control instructions of the spacecraft is lower than the reference duration of the telemetry control instructions of the spacecraft, the frequency of sending the telemetry control instructions is reduced.
[0021] The sending of telemetry control instructions is monitored to obtain dynamic adjustment data of the telemetry control instructions, including telemetry data transmission delay, data loss rate, and number of timed instructions, and a dynamic adjustment quality index of the telemetry data is obtained. The dynamic adjustment quality index of the telemetry data indicates the accuracy of the telemetry system in completing data transmission and control tasks during the dynamic adjustment process.
[0022] According to the dynamic adjustment quality index of the telemetry data, it is compared with the dynamic adjustment quality index threshold of the telemetry data stored in the database. If the dynamic adjustment quality index of the telemetry data is higher than or equal to the dynamic adjustment quality index threshold of the telemetry data, the dynamic adjustment quality result of the telemetry data is marked as qualified; if the dynamic adjustment quality index of the telemetry data is lower than the dynamic adjustment quality index threshold of the telemetry data, the dynamic adjustment quality result of the telemetry data is marked as unqualified, and the number of retransmissions of the data packet is reduced.
[0023] Furthermore, the alignment requirement index of the telemetry data of each data source of the spacecraft is specifically analyzed under the following conditions:
[0024]
[0025] Where A j represents the alignment requirement index of the telemetry data of the jth data source of the spacecraft, t j→k represents the test execution response delay of the kth test command from the jth data source of the spacecraft, t j→g represents the g-th telemetry data transmission delay from the j-th data source of the spacecraft, ω j T represents the time interval for collecting telemetry data from the jth data source of the spacecraft. jrepresents the average query interval delay of the telemetry data of the jth data source of the spacecraft, Δt1 represents the test execution boundary response delay of the set test command, Δt2 represents the set telemetry data transmission boundary delay, Δω represents the set reference collection time interval of the telemetry data, ΔT represents the set reference query interval delay of the telemetry data, α1 represents the correction factor corresponding to the set test execution response delay, α2 represents the correction factor corresponding to the set telemetry data transmission delay, α3 represents the correction factor corresponding to the set collection time interval of the telemetry data, α4 represents the correction factor corresponding to the set average query interval delay of the telemetry data, j represents the number of each data source, m represents the total number of data sources, k represents the number of each test command, s represents the total number of test commands, g represents the number of each test of telemetry data transmission delay, and h represents the total number of tests of telemetry data transmission delay.
[0026] The present invention has the following beneficial effects:
[0027] (1) The present invention provides a method for executing spacecraft dynamic tests based on telemetry data. First, the telemetry data from each data source is collected and tested and analyzed. In addition, the telemetry data from multiple data sources of the spacecraft are subjected to real-time benchmark alignment and data interpretation, thereby identifying the validity and accuracy of the data. Finally, based on the interpretation results and the average duration of the telemetry control instructions, the telemetry data collection strategy is optimized to ensure the efficiency and accuracy of the data collection process, which helps to ensure the accuracy and reliability of the spacecraft dynamic test. The timing of the telemetry data is guaranteed by means of low-complexity time performance. Furthermore, the method of using the telemetry data sent by the tested software as a timing control point and performing timing synchronization control on the automatic test tool and the test target machine through the timing control engine avoids test result errors caused by test timing mismatch.
[0028] (2) The present invention obtains the alignment requirement index of telemetry data, aligns the telemetry data of each data source, and synchronizes it when necessary. This can help testers identify the time deviation between different data sources, adjust and correct data synchronization problems in a timely manner, ensure the accuracy and consistency of the data, and provide strong data support for dynamic testing and task execution.
[0029] (3) The present invention helps to ensure the accuracy and reliability of telemetry data by obtaining the quality index of each data source of telemetry data, and helps to avoid analysis deviations or test result distortions caused by data delays or errors. Secondly, it makes the data monitoring of spacecraft during flight more efficient, and can quickly identify abnormal data or potential faults, thereby improving the response speed and safety of the test. In addition, the evaluation of the quality index not only helps to judge the data quality, but also provides strong support for subsequent spacecraft performance analysis and problem diagnosis, reduces potential risks, and provides a more accurate decision-making basis for the smooth execution of space missions, avoiding test result errors caused by test timing mismatch.
[0030] (4) The present invention analyzes the interpretation results of the telemetry alignment data of each data source of the spacecraft and compares the average duration of the telemetry control instructions of the spacecraft with the reference duration, thereby effectively avoiding the incomplete or inaccurate telemetry data collection caused by insufficient execution time of the control instructions, thereby improving the quality of the telemetry data and the efficiency of the test.
[0031] Of course, any product implementing the present invention does not necessarily need to achieve all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] Figure 1 Schematic diagram of the method flow of the present invention;
[0033] Figure 2 This is a logic flow chart of telemetry reference alignment and test interpretation of the present invention;
[0034] Figure 3 This is a timing control flow chart of the automatic test execution mechanism based on timing synchronization of the present invention. DETAILED DESCRIPTION
[0035] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.
[0036] In the description of the present invention, it should be understood that the terms "opening", "upper", "lower", "thickness", "top", "middle", "length", "inside", "around" and the like indicating orientation or positional relationship are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the components or elements referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as limiting the present invention.
[0037] See also Figure 1As shown, an embodiment of the present invention provides a technical solution for a spacecraft dynamic test execution method based on telemetry data: a spacecraft dynamic test execution method based on telemetry data, including collecting telemetry data from various data sources of the spacecraft, testing and analyzing the telemetry data from various data sources of the spacecraft, obtaining alignment results of the telemetry data from various data sources of the spacecraft, and aligning the telemetry data from various data sources of the spacecraft to obtain telemetry alignment data of various data sources of the spacecraft.
[0038] The telemetry alignment data of each spacecraft data source are analyzed to obtain the quality index of the telemetry alignment data of each spacecraft data source, and the telemetry alignment data of each spacecraft data source are interpreted and processed according to the quality index of the telemetry alignment data of each spacecraft data source to obtain the interpretation result of the telemetry alignment data of each spacecraft data source.
[0039] According to the interpretation results of the telemetry alignment data of each data source of the spacecraft and the average duration of the telemetry control instructions of the spacecraft, the collection of telemetry data is adjusted, and the dynamic adjustment quality results of the telemetry data are obtained.
[0040] It should be noted that this embodiment creatively proposes a real-time benchmark alignment method with O(1) time complexity, and uses each telemetry data transmission as a timing control point. The timing of each operation is controlled by the timing synchronization servo engines deployed on the test tool and the target machine respectively. This will not affect the execution logic of the software under test itself, and will achieve timing synchronization between the test script and the software under test.
[0041] Specifically, the telemetry data of each data source of the spacecraft include the time point of sending each test command, the time point of starting to execute each test command, the time point of sending each telemetry data, the time point of receiving each telemetry data, the time interval of collecting telemetry data, and the average query interval delay of telemetry data.
[0042] Specifically, the telemetry data of each data source of the spacecraft are tested and analyzed. The specific analysis process is: extract the time point of sending each test command of each data source of the spacecraft and the time point of starting to execute each test command, and perform difference processing to obtain the test execution response delay of each test command.
[0043] The time points of receiving telemetry data and sending telemetry data of each data source of the spacecraft are extracted, and the difference processing is performed to obtain the transmission delay of each telemetry data.
[0044] The test execution response delay of each test command of each data source of the spacecraft, the delay of each telemetry data transmission, the collection time interval of the telemetry data and the average query interval delay of the telemetry data are extracted, and the alignment requirement index of the telemetry data of each data source of the spacecraft is obtained after processing. The alignment requirement index of the telemetry data of each data source of the spacecraft is used to evaluate the degree of synchronization of the telemetry data.
[0045] Specifically, the alignment results of the telemetry data of each data source of the spacecraft are obtained, and the specific analysis conditions are: extracting the alignment requirement index of the telemetry data of each data source of the spacecraft, and comparing it with the alignment requirement index threshold of the telemetry data of each data source of the spacecraft stored in the database to obtain the alignment results of the telemetry data of each data source of the spacecraft. The alignment results of the telemetry data of each data source of the spacecraft include those that need alignment and those that do not need alignment. If the alignment requirement index of the telemetry data of a certain data source of the spacecraft is higher than or equal to the alignment requirement index threshold of the telemetry data of the spacecraft, the alignment result of the telemetry data of the spacecraft's data source is defined as requiring alignment, and alignment processing is performed on the telemetry data of the spacecraft's data source. If the alignment requirement index of the telemetry data of a certain data source of the spacecraft is lower than the alignment requirement index threshold of the telemetry data of the spacecraft's data source, the alignment result of the telemetry data of the spacecraft's data source is defined as not requiring alignment.
[0046] Specifically, the telemetry data of each data source of the spacecraft are aligned to obtain the telemetry alignment data of each data source of the spacecraft. The specific process is: according to the alignment result of the telemetry data of each data source of the spacecraft, the telemetry data of each data source of the spacecraft are aligned; if the alignment result of the telemetry data of a certain data source of the spacecraft needs to be aligned, the telemetry data of the data source of the spacecraft is aligned, and the telemetry data of the data source of the spacecraft is marked as the telemetry alignment data of each data source of the spacecraft; if the alignment result of the telemetry data of a certain data source of the spacecraft does not need to be aligned, the telemetry data of the data source of the spacecraft is directly marked as the telemetry alignment data of each data source of the spacecraft, thereby obtaining the telemetry alignment data of each data source of the spacecraft.
[0047] It should be noted that the alignment of telemetry data from various spacecraft data sources is a process that ensures the coordination and consistency of multi-source data and meets time synchronization requirements. This involves aligning data from different sensors, devices, or systems to the same timestamp using time synchronization technology for joint analysis. This alignment typically results in a unified time series, facilitating comparison of data output from different sensors or systems. In this embodiment, a GPS clock is used to provide a unified time reference for all devices, processing data from different sensors, platforms, at different times, or from different signal sources to ensure that they match for further analysis, decision-making, or control operations. This process typically includes steps such as data alignment, time synchronization, calibration, and interpolation.
[0048] Specifically, the telemetry alignment data of each spacecraft data source are analyzed to obtain the quality index of the telemetry alignment data of each spacecraft data source. The specific analysis process is: count the data collection time points in each spacecraft data source, extract the data collection time points in each spacecraft data source, extract the reference time points stored in the database, perform absolute value processing on the difference between the reference time points and the data collection time points in each spacecraft data source, and obtain the collection time difference of each data in each spacecraft data source.
[0049] The mean error of the acquisition time of each data in each spacecraft data source is calculated, and the data missing rate in each spacecraft data source is calculated. After processing, the quality index of the telemetry alignment data of each spacecraft data source is obtained. The quality index of the telemetry alignment data of each spacecraft data source is used to indicate the reliability of the alignment quality of the telemetry data.
[0050] It should be noted that the quality index of telemetry alignment data from various spacecraft data sources is analyzed under the following specific conditions:
[0051]
[0052] Where R j The quality index of the telemetry alignment data of the jth data source of the spacecraft, T 1 j→i T represents the acquisition time difference of the i-th data in the j-th data source of the spacecraft, 2 j→i represents the mean error of the acquisition time of the i-th data in the j-th data source of the spacecraft, E j represents the data missing rate of the jth data source of the spacecraft, ΔT 1 Indicates the set data collection limit time difference, ΔT 2 represents the set collection time mean boundary error, ΔE represents the set data missing rate of the data source, μ1 represents the correction factor corresponding to the set data collection time difference, μ2 represents the correction factor corresponding to the set data collection mean time error, and μ3 represents the correction factor corresponding to the set data missing rate.
[0053] It should be noted that the time difference between each data source on a spacecraft, the mean error in the time of collection, and the data missing rate are complexly correlated and mutually impact each other. First, the time difference between each data source on a spacecraft directly impacts data synchronization and system responsiveness. Time difference refers to the time deviation between data from different sensors or systems at the same time. If the time difference is large, it means that the information from different data sources may be time-inconsistent, which can lead to errors in spacecraft status monitoring. Second, the mean error in the time of collection for each data source on a spacecraft is closely related to the timeliness and accuracy of the data. The mean error in the time of collection for each data source on a spacecraft is the average of the differences between the actual time of all data acquisitions and the corresponding expected time of collection. It directly affects the timeliness of data analysis. An increase in the mean error can lead to inaccurate system monitoring of changes, which in turn affects spacecraft command and control decisions. Furthermore, the data missing rate is closely related to the time difference and mean error. A high data missing rate often indicates system failures or network issues that prevent data from being collected properly. Missing data often exacerbates synchronization problems caused by acquisition time differences. Therefore, under conditions of higher mean error, the data missing rate is usually higher, especially in scenarios where the system needs to collect and process data more frequently.
[0054] In a specific embodiment, the correction factor corresponding to the data collection time difference typically ranges from 0 to 1. During use, the correction factor corresponding to the data collection time difference can be directly obtained from a database. The correspondence between the data collection time difference and the correction factor is determined by a pre-set mapping table. For example, a mapping table is constructed by combining the data collection time difference and the correction factor corresponding to the data collection time difference. By inputting the real-time detected collection time difference into the mapping table, the correction factor corresponding to the data collection time difference can be obtained, thereby optimizing the synchronization of data collection and reducing the impact of time deviation.
[0055] In a specific embodiment, the correction factor corresponding to the mean time error of data collection generally ranges from 0 to 1. When in use, the correction factor corresponding to the mean time error of data collection can be directly obtained from the database. The correspondence between the mean time error of data collection and the correction factor is determined by a pre-set mapping table. For example, a mapping table is constructed by the mean time error of data collection and the correction factor corresponding to the mean time error of data collection. By inputting the mean time error of data collection detected in real time into the mapping table, the correction factor corresponding to the mean time error of data collection can be obtained, thereby optimizing the time accuracy of the data and reducing the data inconsistency caused by the time error.
[0056] In a specific embodiment, the correction factor corresponding to the data missing rate typically ranges from 0 to 1. During use, the correction factor corresponding to the data missing rate can be directly obtained from the database. The correspondence between the data missing rate and the correction factor is determined by a pre-set mapping table. For example, a mapping table is constructed by inputting the data missing rate and the correction factor corresponding to the data missing rate into the mapping table. By inputting the real-time detected data missing rate into the mapping table, the correction factor corresponding to the data missing rate can be obtained, thereby optimizing data integrity and reducing query delays and data processing errors caused by missing data.
[0057] Specifically, the telemetry alignment data of each spacecraft data source are interpreted and processed to obtain the interpretation results of the telemetry alignment data of each spacecraft data source. The specific process is: according to the quality index of the telemetry alignment data of each spacecraft data source, and compared with the quality index threshold of the telemetry alignment data of each spacecraft data source stored in the database, the interpretation results of the telemetry alignment data of each spacecraft data source are obtained.
[0058] It should be noted that in this embodiment, the telemetry alignment data of each data source of the spacecraft are aligned and interpreted, wherein the alignment and interpretation of the telemetry alignment data of each data source of the spacecraft includes telemetry data baseline alignment and interpretation logic and an automatic test execution mechanism based on timing synchronization.
[0059] It should be noted that if Figure 2 As shown, Figure 2 This is a flowchart of the telemetry benchmark alignment and test interpretation logic. The telemetry data benchmark alignment and interpretation logic specifically follows: Before the test begins, the benchmark parameters x1 and x2 of the two telemetry frames to be interpreted are pre-specified, along with a formula describing their timing relationship, such as x1 – (x2 + 5) = 0 (Equation 1). Then, the rules for all telemetry parameters to be interpreted after benchmark alignment are provided, such as y1 – y2 = 0 (Equation 2). Furthermore, a telemetry frame with a faster update cycle is specified. This faster-updated telemetry frame serves as the benchmark comparison source during the benchmark interpretation phase. Benchmark interpretation involves benchmarking the two telemetry frames using Equation 1 as the reference, then determining whether Equation 2 is satisfied. Benchmark interpretation dynamically buffers a portion (e.g., 10 frames) of telemetry data during the test.
[0060] It should be noted that if Figure 3 As shown, Figure 3This is a timing control flow chart for an automatic test execution mechanism based on timing synchronization. The dynamic test execution mechanism based on timing synchronization consists of three components: a script execution engine, a test target machine, and a timing synchronization servo engine. The script execution engine parses the automatic test script and executes the script commands within it. The test target machine simulates the target environment of the software under test, simulating the software under test while also adding timing control. The timing synchronization servo engine is the core of timing control. It interacts with the script execution engine to control the execution timing of script commands that require synchronization, and with the test target machine to control the simulation of the software under test. These three components form the core operation of timing synchronization control.
[0061] Specifically, the interpretation results of the telemetry alignment data of each data source of the spacecraft include normal and abnormal. If the quality index of the telemetry alignment data of a certain data source of the spacecraft is higher than or equal to the quality index threshold of the telemetry alignment data of the data source of the spacecraft, the interpretation result of the telemetry alignment data of the data source of the spacecraft is defined as normal. If the quality index of the telemetry alignment data of a certain data source of the spacecraft is lower than the quality index threshold of the telemetry alignment data of the data source of the spacecraft, the interpretation result of the telemetry alignment data of the data source of the spacecraft is defined as abnormal.
[0062] Specifically, based on the interpretation results of the telemetry alignment data of each spacecraft data source and the average duration of the spacecraft's telemetry control instructions, the telemetry data collection is adjusted, and the dynamic adjustment quality results of the telemetry data are obtained. The specific process is as follows:
[0063] If the judgment result of the telemetry alignment data of a certain data source of the spacecraft is normal, there is no need to collect and adjust the telemetry data. If the judgment result of the telemetry alignment data of a certain data source of the spacecraft is abnormal, the average duration of the telemetry control instructions of the spacecraft is obtained, and the reference duration of the telemetry control instructions of the spacecraft stored in the database is extracted. The average duration of the telemetry control instructions of the spacecraft is compared with the reference duration of the telemetry control instructions of the spacecraft stored in the database. If the average duration of the telemetry control instructions of the spacecraft is higher than or equal to the reference duration of the telemetry control instructions of the spacecraft, the telemetry data of the data source of the spacecraft is re-collected and an alarm is triggered. If the average duration of the telemetry control instructions of the spacecraft is lower than the reference duration of the telemetry control instructions of the spacecraft, the frequency of sending the telemetry control instructions is reduced.
[0064] It should be noted that reducing the frequency of sending telemetry control instructions means, for example, that if the average duration of the telemetry control instructions of a spacecraft is lower than the reference duration of the telemetry control instructions of the spacecraft, the frequency of sending instructions needs to be reduced by 10%-30% to improve the efficiency of the system, reduce the system load, and ensure that the required data can be efficiently obtained under limited bandwidth conditions.
[0065] The sending of telemetry control instructions is monitored to obtain dynamic adjustment data of the telemetry control instructions, including telemetry data transmission delay, data loss rate, and number of timed instructions, and a dynamic adjustment quality index of the telemetry data is obtained. The dynamic adjustment quality index of the telemetry data indicates the accuracy of the telemetry system in completing data transmission and control tasks during the dynamic adjustment process.
[0066] According to the dynamic adjustment quality index of the telemetry data, it is compared with the dynamic adjustment quality index threshold of the telemetry data stored in the database. If the dynamic adjustment quality index of the telemetry data is higher than or equal to the dynamic adjustment quality index threshold of the telemetry data, the dynamic adjustment quality result of the telemetry data is marked as qualified; if the dynamic adjustment quality index of the telemetry data is lower than the dynamic adjustment quality index threshold of the telemetry data, the dynamic adjustment quality result of the telemetry data is marked as unqualified, and the number of retransmissions of the data packet is reduced.
[0067] It should be noted that reducing the number of retransmissions of a data packet means reducing the number of retransmissions by 1-3 times based on the original number of retransmissions to ensure a minimum number of retransmission attempts and setting a minimum value, such as 1 time, or directly abandoning the current data packet.
[0068] It should be noted that the dynamic adjustment quality index of telemetry data is analyzed based on the following specific conditions:
[0069]
[0070] Where V represents the dynamically adjusted quality index of telemetry data, Y represents the data transmission delay, d represents the data loss rate, c represents the number of timeout instructions, ΔY represents the set bounded data transmission delay, Δd represents the set bounded data loss rate, Δc represents the set bounded number of timeout instructions, τ1 represents the correction factor corresponding to the set data transmission delay, τ2 represents the correction factor corresponding to the set data loss rate, and τ3 represents the correction factor corresponding to the set number of timeout instructions.
[0071] It's important to note that telemetry data transmission delay, data loss rate, and the number of timed-out commands are not independent parameters; rather, they are interrelated and mutually influential. First, telemetry data transmission delay directly impacts data timeliness. When transmission delay is significant, the system may not be able to receive and process telemetry data on time, resulting in reduced data validity. This delay can further increase the data loss rate, as delays can prevent data packets from being transmitted within the valid window, increasing the probability of packet loss. Second, a high data loss rate can impact the reliability of system command execution. For example, the loss of critical telemetry data can prevent commands from being judged based on complete information, increasing the probability of timed-out commands. Especially in complex test scenarios, a high loss rate can force the system to frequently retransmit or resend commands, further prolonging data transmission time and exacerbating system responsiveness. Conversely, frequent timed-out commands can exacerbate data transmission delays, as the system must handle additional error recovery and re-execution, increasing link load.
[0072] In a specific embodiment, the correction factor corresponding to the data transmission delay typically ranges from 0 to 1. During use, the correction factor corresponding to the data transmission delay can be directly obtained from a database. The correspondence between the correction factor corresponding to the data transmission delay and the data transmission delay is determined by a pre-set mapping table. For example, a mapping table is constructed between data transmission delay and its corresponding correction factor. During the test process, by inputting the real-time detected data transmission delay into the mapping table, the corresponding correction factor can be quickly obtained, thereby helping to adjust the tolerance range for transmission delay in the test and improving the real-time performance and accuracy of the data.
[0073] In a specific embodiment, the correction factor corresponding to the data loss rate also ranges from 0 to 1. The test system obtains the corresponding correction factor by statistically analyzing the data loss rate of the current link and combining it with a predefined mapping table. In specific applications, the real-time detected data loss rate is used as input to query the mapping table to obtain the corresponding correction factor, which is used to dynamically optimize the data transmission strategy and reduce test deviations caused by link congestion or packet loss.
[0074] In one specific embodiment, the correction factor corresponding to the number of timed-out instructions is also between 0 and 1, and this correction factor is determined by a pre-set mapping table. For example, a mapping table is constructed between the number of timed-out instructions and their correction factors. During the test process, the system monitors the number of timed-out instruction executions in real time and enters this value into the mapping table to quickly obtain the corresponding correction factor. This correction factor can be used to dynamically adjust the timeout period of test instructions or optimize system resource allocation, thereby reducing the impact of timed-out instructions on the accuracy of test results.
[0075] Specifically, the alignment requirement index of telemetry data from various spacecraft data sources is analyzed under the following conditions:
[0076]
[0077] Where A j represents the alignment requirement index of the telemetry data of the jth data source of the spacecraft, t j→k represents the test execution response delay of the kth test command from the jth data source of the spacecraft, t j→g represents the g-th telemetry data transmission delay from the j-th data source of the spacecraft, ω j T represents the time interval for collecting telemetry data from the jth data source of the spacecraft. j represents the average query interval delay of the telemetry data of the jth data source of the spacecraft, Δt1 represents the test execution boundary response delay of the set test command, Δt2 represents the set telemetry data transmission boundary delay, Δω represents the set reference collection time interval of the telemetry data, ΔT represents the set reference query interval delay of the telemetry data, α1 represents the correction factor corresponding to the set test execution response delay, α2 represents the correction factor corresponding to the set telemetry data transmission delay, α3 represents the correction factor corresponding to the set collection time interval of the telemetry data, α4 represents the correction factor corresponding to the set average query interval delay of the telemetry data, j represents the number of each data source, m represents the total number of data sources, k represents the number of each test command, s represents the total number of test commands, g represents the number of each test of telemetry data transmission delay, and h represents the total number of tests of telemetry data transmission delay.
[0078] It's important to note that parameters such as the test execution response delay for each test command, the telemetry data transmission delay for each test, the telemetry data collection interval, and the average query interval delay for telemetry data are not independent but rather interdependent and closely related. First, the test command response delay directly impacts the timing of telemetry data acquisition. A long test command response time indicates a delay in the system's reception and processing of telemetry data, leading to increased telemetry data transmission delay. Particularly in complex test environments, test commands with significant response delays can reduce the timeliness of telemetry data transmission, impacting the real-time nature of the data. Second, there's a close relationship between the telemetry data collection interval and the average query interval delay. The telemetry data collection interval determines the frequency of data collection, while the query interval delay determines the timeliness with which data can be acquired and further processed. A long collection interval can prevent the system from responding to rapidly changing events, especially when high-frequency data collection is required. Conversely, a long query interval delay can prevent the system from obtaining real-time telemetry data, impacting the monitoring of equipment or spacecraft status. Long transmission delays often mean telemetry data cannot be fed back to the command and control system quickly, which in turn affects the scheduling of collection and query intervals. When data transmission delays are large, the system may need to increase the collection interval to ensure that data is not lost during transmission, and may also need to adjust the query interval delay to account for the data transmission lag. Conversely, shorter transmission delays can improve the real-time nature of the data flow and reduce the need for system interval adjustments.
[0079] It should be noted that query interval delay refers to the difference between the actual query time and the expected query time during continuous telemetry data query processes. To accurately measure query interval delay, a preset time base is usually used, such as the clock inside the spacecraft or the Universal Time (UTC) synchronized with the ground station. Test execution response delay refers to the time delay between when a test command is sent and when the spacecraft responds and begins to execute the test command. This delay is usually the time difference between the instruction being sent to the spacecraft and the start of the test command execution. Data transmission delay refers to the time delay between the data being sent from the ground control center and the spacecraft receiving these instructions or data and starting to process them.
[0080] In a specific embodiment, the value range of the correction factor corresponding to the test execution response delay is generally between 0 and 1. When in use, the correction factor corresponding to the test execution response delay can be directly obtained from the database. The correspondence between the correction factor corresponding to the test execution response delay and the test execution response delay is determined by a pre-set mapping table. For example, a mapping table is constructed of the test execution response delay and the correction factor corresponding to the test execution response delay. By inputting the test execution response delay detected in real time into the mapping table, the corresponding correction factor can be quickly obtained, thereby helping to optimize the delay problem in the test execution process.
[0081] In a specific embodiment, the correction factor corresponding to the telemetry data transmission delay typically ranges from 0 to 1. During use, the correction factor corresponding to the telemetry data transmission delay can be directly obtained from a database. The correspondence between the correction factor corresponding to the telemetry data transmission delay and the telemetry data transmission delay is determined by a pre-defined mapping table. For example, a mapping table is constructed of the telemetry data transmission delay and the correction factor corresponding to the telemetry data transmission delay. By inputting the real-time detected telemetry data transmission delay into the mapping table, the corresponding correction factor can be quickly obtained, thereby helping to improve the delay effect during the data transmission process.
[0082] In a specific embodiment, the correction factor corresponding to the telemetry data collection time interval typically ranges from 0 to 1. During use, the correction factor corresponding to the telemetry data collection time interval can be directly obtained from a database. The correspondence between the correction factor corresponding to the telemetry data collection time interval and the telemetry data collection time interval is determined by a pre-set mapping table. For example, a mapping table is constructed of the telemetry data collection time interval and the correction factor corresponding to the telemetry data collection time interval. By inputting the real-time detected telemetry data collection time interval into the mapping table, the corresponding correction factor can be quickly obtained, thereby helping to adjust the collection cycle and optimize data collection efficiency.
[0083] In a specific embodiment, the correction factor corresponding to the average query interval delay of the telemetry data generally ranges from 0 to 1. When in use, the correction factor corresponding to the average query interval delay of the telemetry data can be directly obtained from the database. The correspondence between the correction factor corresponding to the average query interval delay of the telemetry data and the average query interval delay of the telemetry data is determined by a pre-set mapping table. For example, a mapping table is constructed of the average query interval delay of the telemetry data and the correction factor corresponding to the average query interval delay of the telemetry data. By inputting the real-time detected telemetry data query delay into the mapping table, the corresponding correction factor can be quickly obtained, thereby helping to optimize the data query interval and reduce the query delay.
[0084] It should be noted that a method for executing dynamic tests of spacecraft based on telemetry data also includes a database for storing the alignment requirement index threshold of telemetry data of each data source of the spacecraft, the reference time point, the quality index threshold of telemetry alignment data of each data source of the spacecraft, the reference duration of the telemetry control instructions of the spacecraft, the dynamic adjustment quality index threshold of the telemetry data, the definition of data transmission delay, the definition of data loss rate, the definition of the number of timeout instructions, the correction factor corresponding to the data transmission delay, the correction factor corresponding to the data loss rate, the correction factor corresponding to the number of timeout instructions, the data collection definition time difference, the collection time mean definition error, the data loss rate of the data source, the correction factor corresponding to the data collection time difference, the correction factor corresponding to the data collection mean time error, the correction factor corresponding to the data loss rate, the test execution definition response delay of the test command, the telemetry data transmission definition delay, the reference collection time interval of telemetry data, the reference query interval delay of telemetry data, the correction factor corresponding to the test execution response delay, the correction factor corresponding to the telemetry data transmission delay, the correction factor corresponding to the collection time interval of telemetry data, and the correction factor corresponding to the average query interval delay of telemetry data.
[0085] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus.
[0086] The preferred embodiments of the present invention disclosed above are intended only to help illustrate the present invention. These preferred embodiments do not exhaustively describe all details, nor do they limit the present invention to the specific embodiments described. Obviously, many modifications and variations are possible based on the content of this specification. These embodiments are selected and described in detail in this specification to better explain the principles and practical applications of the present invention, thereby enabling those skilled in the art to better understand and utilize the present invention. The present invention is limited only by the claims and their full scope and equivalents.
Claims
1. A method for executing spacecraft dynamic testing based on telemetry data, characterized in that: include: Collecting telemetry data from various data sources of the spacecraft, testing and analyzing the telemetry data from various data sources of the spacecraft to obtain alignment results of the telemetry data from various data sources of the spacecraft, and performing alignment processing on the telemetry data from various data sources of the spacecraft to obtain telemetry alignment data from various data sources of the spacecraft; Analyzing the telemetry alignment data of each spacecraft data source to obtain a quality index of the telemetry alignment data of each spacecraft data source, and interpreting and processing the telemetry alignment data of each spacecraft data source based on the quality index of the telemetry alignment data of each spacecraft data source to obtain an interpretation result of the telemetry alignment data of each spacecraft data source; According to the interpretation results of the telemetry alignment data of each data source of the spacecraft, combined with the average duration of the spacecraft's telemetry control instructions, the telemetry data collection is adjusted, and the dynamic adjustment quality results of the telemetry data are obtained to adjust the number of retransmissions of the data packet; The telemetry alignment data of each spacecraft data source is analyzed to obtain the quality index of the telemetry alignment data of each spacecraft data source. The specific analysis process is as follows: Counting the data collection time points of each spacecraft data source, extracting the data collection time points of each spacecraft data source, extracting the reference time points stored in the database, performing absolute value processing on the difference between the reference time points and the data collection time points of each spacecraft data source, and obtaining the collection time difference of each data in each spacecraft data source; Calculate the mean error of the acquisition time of each data in each spacecraft data source, and calculate the data missing rate in each spacecraft data source. After processing, obtain the quality index of the telemetry alignment data of each spacecraft data source. The quality index of the telemetry alignment data of each spacecraft data source is used to indicate the reliability of the alignment quality of the telemetry data. The telemetry data collection is adjusted based on the average duration of the telemetry control instructions of the spacecraft, and the dynamic adjustment quality result of the telemetry data is obtained to adjust the number of retransmissions of the data packet. The specific process is as follows: If the interpretation result of the telemetry alignment data of a certain data source of the spacecraft is normal, there is no need to collect and adjust the telemetry data; if the interpretation result of the telemetry alignment data of a certain data source of the spacecraft is abnormal, the average duration of the telemetry control instructions of the spacecraft is obtained, and the reference duration of the telemetry control instructions of the spacecraft stored in the database is extracted, and the average duration of the telemetry control instructions of the spacecraft is compared with the reference duration of the telemetry control instructions of the spacecraft stored in the database; if the average duration of the telemetry control instructions of the spacecraft is higher than or equal to the reference duration of the telemetry control instructions of the spacecraft, the telemetry data of the data source of the spacecraft is re-collected and an alarm is triggered; if the average duration of the telemetry control instructions of the spacecraft is lower than the reference duration of the telemetry control instructions of the spacecraft, the frequency of sending the telemetry control instructions is reduced; Monitoring the transmission of telemetry control instructions to obtain dynamic adjustment data of the telemetry control instructions, including telemetry data transmission delay, data loss rate, and number of timed instructions, and obtaining a dynamic adjustment quality index of the telemetry data, which indicates the accuracy of the telemetry system in completing data transmission and control tasks during the dynamic adjustment process; According to the dynamic adjustment quality index of the telemetry data, it is compared with the dynamic adjustment quality index threshold of the telemetry data stored in the database. If the dynamic adjustment quality index of the telemetry data is higher than or equal to the dynamic adjustment quality index threshold of the telemetry data, the dynamic adjustment quality result of the telemetry data is marked as qualified; if the dynamic adjustment quality index of the telemetry data is lower than the dynamic adjustment quality index threshold of the telemetry data, the dynamic adjustment quality result of the telemetry data is marked as unqualified, and the number of retransmissions of the data packet is reduced.
2. The method for executing spacecraft dynamic testing based on telemetry data according to claim 1, characterized in that: The telemetry data of each data source of the spacecraft includes the time point of sending each test command, the time point of starting to execute each test command, the time point of sending each telemetry data, the time point of receiving each telemetry data, the time interval of collecting telemetry data and the average query interval delay of telemetry data.
3. The method for executing spacecraft dynamic testing based on telemetry data according to claim 2, characterized in that: The telemetry data from various spacecraft data sources are tested and analyzed. The specific analysis process is as follows: Extract the sending time of each test command from each data source of the spacecraft and the starting time of each test command, perform difference processing to obtain the test execution response delay of each test command; Extract the time points of each telemetry data reception and each telemetry data transmission of each data source of the spacecraft, and perform difference processing to obtain the delay of each telemetry data transmission; The test execution response delay of each test command of each data source of the spacecraft, the delay of each telemetry data transmission, the collection time interval of the telemetry data and the average query interval delay of the telemetry data are extracted, and the alignment requirement index of the telemetry data of each data source of the spacecraft is obtained after processing. The alignment requirement index of the telemetry data of each data source of the spacecraft is used to evaluate the degree of synchronization of the telemetry data.
4. The method for executing spacecraft dynamic testing based on telemetry data according to claim 2, characterized in that: The alignment results of telemetry data from various spacecraft data sources are obtained, and the specific analysis conditions are as follows: The alignment requirement index of the telemetry data of each data source of the spacecraft is extracted, and compared with the alignment requirement index threshold of the telemetry data of each data source of the spacecraft stored in the database to obtain the alignment result of the telemetry data of each data source of the spacecraft. The alignment result of the telemetry data of each data source of the spacecraft includes alignment required and alignment not required. If the alignment requirement index of the telemetry data of a certain data source of the spacecraft is higher than or equal to the alignment requirement index threshold of the telemetry data of the spacecraft data source, the alignment result of the telemetry data of the spacecraft data source is defined as alignment required, and the telemetry data of the spacecraft data source is aligned. If the alignment requirement index of the telemetry data of a certain data source of the spacecraft is lower than the alignment requirement index threshold of the telemetry data of the spacecraft data source, the alignment result of the telemetry data of the spacecraft data source is defined as alignment not required.
5. The method for executing spacecraft dynamic testing based on telemetry data according to claim 4, characterized in that: The telemetry data of each spacecraft data source are aligned to obtain the telemetry alignment data of each spacecraft data source. The specific process is as follows: The telemetry data of each data source of the spacecraft are aligned according to the alignment results of the telemetry data of each data source of the spacecraft. If the alignment result of the telemetry data of a certain data source of the spacecraft requires alignment, the telemetry data of the data source of the spacecraft will be aligned, and the telemetry data of the data source of the spacecraft will be marked as the telemetry alignment data of each data source of the spacecraft. If the alignment result of the telemetry data of a certain data source of the spacecraft does not require alignment, the telemetry data of the data source of the spacecraft will be directly marked as the telemetry alignment data of each data source of the spacecraft, thereby obtaining the telemetry alignment data of each data source of the spacecraft.
6. The method for executing spacecraft dynamic testing based on telemetry data according to claim 1, characterized in that: The telemetry alignment data of each spacecraft data source are interpreted and processed to obtain the interpretation results of the telemetry alignment data of each spacecraft data source. The specific process is as follows: According to the quality index of the telemetry alignment data of each spacecraft data source, it is compared with the quality index threshold of the telemetry alignment data of each spacecraft data source stored in the database to obtain the interpretation result of the telemetry alignment data of each spacecraft data source.
7. The method for executing spacecraft dynamic testing based on telemetry data according to claim 6, characterized in that: The interpretation results of the telemetry alignment data of each data source of the spacecraft include normal and abnormal. If the quality index of the telemetry alignment data of a certain data source of the spacecraft is higher than or equal to the quality index threshold of the telemetry alignment data of the data source of the spacecraft, the interpretation result of the telemetry alignment data of the data source of the spacecraft is defined as normal. If the quality index of the telemetry alignment data of a certain data source of the spacecraft is lower than the quality index threshold of the telemetry alignment data of the data source of the spacecraft, the interpretation result of the telemetry alignment data of the data source of the spacecraft is defined as abnormal.
8. The method for executing spacecraft dynamic testing based on telemetry data according to claim 3, characterized in that: The alignment requirement index of the telemetry data from each data source of the spacecraft is analyzed under the following specific conditions: ; Where, represents the alignment requirement index of the telemetry data of the jth data source of the spacecraft, represents the test execution response delay of the kth test command of the jth data source of the spacecraft, represents the g-th telemetry data transmission delay of the j-th data source of the spacecraft, represents the time interval for collecting telemetry data from the jth data source of the spacecraft, represents the average query interval delay of the telemetry data of the jth data source of the spacecraft, Indicates the test execution bounded response delay of the set test command, Indicates the set telemetry data transmission limit delay, Indicates the reference collection time interval of the set telemetry data. Indicates the reference query interval delay of the set telemetry data. Indicates the correction factor corresponding to the set test execution response delay, Indicates the correction factor corresponding to the set telemetry data transmission delay, Indicates the correction factor corresponding to the set telemetry data collection time interval, Indicates the correction factor corresponding to the set average query interval delay of telemetry data, j represents the number of each data source, m represents the total number of data sources, k represents the number of each test command, s represents the total number of test commands, g represents the number of each test for telemetry data transmission delay, and h represents the total number of tests for telemetry data transmission delay.
Citation Information
Patent Citations
DMS system-based telemetry anomaly analysis system and method for distribution network automation terminal
CN104834305B
Methods and devices for locating anomalies in spacecraft attitude control systems
CN115617023B
Spacecraft rendezvous and docking flight control intelligent data analysis and decision support system
CN110262280A
Comprehensive state evaluation method and device for deep space spacecraft
CN113032905A