Simulation method and device for spaceflight TT&C fault
By constructing a fault mode database and its relationships, the simulation challenges of complex and multi-point faults in aerospace telemetry and control fault simulation were solved, realizing an efficient simulation method and device, and improving simulation reliability and scalability.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- BEIJING AEROSPACE CONTROL CENT
- Filing Date
- 2025-11-28
- Publication Date
- 2026-07-21
AI Technical Summary
Existing technologies lack unified modeling for aerospace telemetry and control fault simulation, making it difficult to effectively simulate complex and multi-point faults. They also have limited scalability and are costly to simulate new faults.
By constructing a fault mode database and its relationships, receiving fault loading commands, obtaining fault relationships, determining whether a fault is about to occur and its loading time, and completing the simulation based on the list of faults to be loaded, the simulation of composite faults and multi-point faults in aerospace telemetry and control is realized.
It improves the reliability of aerospace telemetry and control fault simulation, supports rapid simulation of new faults, eliminates the need for separate program coding, and realizes the aggregation, assembly, and associated logic control of various faults.
Smart Images

Figure CN121900362B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of aerospace telemetry, tracking, and command (TT&C) technology, and in particular to a simulation method and device for aerospace TT&C faults. Background Technology
[0002] Spacecraft failure mode simulation is a crucial supporting technology for aerospace flight control exercises. For aerospace telemetry and control missions, there is an urgent need to simulate various possible telemetry and control failures before mission execution for personnel training and flight control scheme verification. Currently, most aerospace telemetry and control failure mode simulations tend to use program coding methods to simulate individual failures.
[0003] The patent "A Spacecraft Orbital Rendezvous Simulation Control Method, Device, Equipment, and Storage Medium," patent number CN118625695B, addresses attitude faults during spacecraft telemetry and control. It employs a binocular measurement and fuzzy mesh strategy for fault simulation, resolving the rule matching conflict problem of traditional fault tree models. This method enables spacecraft telemetry and control fault simulation and diagnosis using binocular measurement and fuzzy mesh methods. It utilizes the construction of multiple physical scenario models to simulate spacecraft telemetry and control faults.
[0004] The above-mentioned existing technologies still have the following disadvantages: (1) There is a lack of unified modeling for various fault modes in the field of aerospace measurement and control, so the scalability is not strong and the cost of simulating new faults is high. (2) They focus on simulating independent faults and lack simulation methods for compound faults and multi-point faults.
[0005] This section is intended to provide background or context for the embodiments of the invention set forth in the claims. The description herein is not an admission that it is prior art simply because it is included in this section. Summary of the Invention
[0006] To address at least one problem in the prior art, this application proposes a simulation method and apparatus for aerospace telemetry and control faults, which can realize the simulation of complex and multi-point faults in aerospace telemetry and control, and improve the reliability of aerospace telemetry and control fault simulation.
[0007] To address the aforementioned technical problems, this application provides the following technical solution: Firstly, this application provides a simulation method for aerospace telemetry and control faults, including: Receive a fault loading command, the fault loading command including: the fault mode number and fault loading time of the aerospace telemetry and control fault; Based on the fault mode number of the aerospace telemetry and control fault, obtain the fault association relationship of the aerospace telemetry and control fault from the fault mode database; Based on the fault association, determine whether the aerospace telemetry and control fault is about to occur, the fault mode number of its corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault. If the associated fault is to be triggered, the fault mode number and fault loading time of the associated fault are added to a preset list of faults to be loaded; if the aerospace telemetry and control fault is to be triggered, the fault mode number and fault loading time of the aerospace telemetry and control fault are added to a preset list of faults to be loaded. Based on the preset list of faults to be loaded, the fault simulation corresponding to the fault loading command is completed.
[0008] In one embodiment, the fault mode database includes: a preset fault mode index table and a preset fault table; The preset fault mode index table includes: task code, target code, fault mode, and the correspondence between the three; The preset fault table includes: task code, target code, fault mode, fault association relationship and the association relationship between the four; Correspondingly, the step of obtaining the fault association relationship of the aerospace telemetry and control fault from the fault mode database based on the fault mode number of the aerospace telemetry and control fault includes: From the preset fault mode index table, obtain the mission code and target code corresponding to the fault mode number of the aerospace telemetry and control fault; Based on the fault mode number of the aerospace telemetry and control fault, its corresponding mission code and target code, the fault association relationship of the aerospace telemetry and control fault is obtained from the preset fault table.
[0009] In one embodiment, the fault association includes: the operator, the fault mode number of the aerospace telemetry and control fault, the fault mode number of the associated fault, and the fault loading time difference between the two. Correspondingly, determining whether the aerospace telemetry and control fault is about to occur, the fault mode number of its corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault based on the fault association relationship includes: If the operator is a fault recovery operator or an operator in which both faults occur, then it is determined that both the aerospace telemetry and control fault and the associated fault are about to occur, and the fault loading time of the associated fault is the fault loading time of the aerospace telemetry and control fault. If the operator is a fault-causing operator for another fault, then it is determined that both the aerospace telemetry and control fault and the associated fault are about to occur, and the fault loading time of the associated fault is the fault loading time of the aerospace telemetry and control fault delayed by the fault loading time difference. If the operator is a spacecraft fault identifier and both the space telemetry and control fault and the associated fault are spacecraft faults, then it is determined that both the space telemetry and control fault and the associated fault are about to occur. The fault loading time of the associated fault is the fault loading time of the space telemetry and control fault delayed by the fault loading time difference. The parameter values shared with the associated fault in the preset fault table are deleted.
[0010] In one embodiment, the step of completing the fault simulation corresponding to the fault loading command based on the preset list of faults to be loaded includes: If there is a target record in the preset list of faults to be loaded with a fault loading time of the current system time, the target record is sent to the fault simulation model corresponding to the fault mode number in the target record. The preset list of faults to be loaded includes: at least one record, and each record includes: fault mode number and fault loading time. The fault simulation model is applied to complete the fault simulation corresponding to the target record.
[0011] In one embodiment, applying the fault simulation model to complete the fault simulation corresponding to the target record includes: Using a spacecraft simulation model, the parameter values corresponding to the fault mode numbers in the target record are obtained from a preset fault table. Based on the parameter values, the fault simulation corresponding to the target record is completed; the fault mode corresponding to the fault mode number is a spacecraft fault.
[0012] In one embodiment, applying the fault simulation model to complete the fault simulation corresponding to the target record includes: Using a telemetry and control network simulation model, the station code and operation type code corresponding to the fault mode number in the target record are obtained from a preset fault table. If the station code is the station code corresponding to the telemetry and control network simulation model, the fault simulation corresponding to the target record is completed according to the operation type code. The fault mode corresponding to the fault mode number is a telemetry and control network fault.
[0013] In one embodiment, applying the fault simulation model to complete the fault simulation corresponding to the target record includes: Using a transceiver simulation model, the operation type code corresponding to the fault mode number in the target record is obtained from a preset fault table. Based on the operation type code, the fault simulation corresponding to the target record is completed. The fault mode corresponding to the fault mode number is a transceiver fault.
[0014] Secondly, this application provides a simulation device for aerospace telemetry and control faults, comprising: The receiving module is used to receive a fault loading command, which includes: the fault mode number and fault loading time of the aerospace telemetry and control fault; The acquisition module is used to obtain the fault association relationship of the aerospace telemetry and control fault from the fault mode database according to the fault mode number of the aerospace telemetry and control fault; The determination module is used to determine, based on the fault association relationship, whether the aerospace telemetry and control fault is about to occur, the fault mode number of the corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault. An add module is used to add the fault mode number and fault loading time of the associated fault to a preset list of faults to be loaded if the associated fault is to be triggered; and to add the fault mode number and fault loading time of the aerospace telemetry and control fault to a preset list of faults to be loaded if the aerospace telemetry and control fault is to be triggered. The simulation module is used to perform fault simulation corresponding to the fault loading command based on the preset list of faults to be loaded.
[0015] Thirdly, this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the aforementioned simulation method for aerospace telemetry and control faults.
[0016] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned simulation method for aerospace telemetry and control faults.
[0017] As can be seen from the above technical solution, this application provides a simulation method and device for aerospace telemetry and control faults. The method includes: receiving a fault loading command, the fault loading command including: a fault mode number and a fault loading time of an aerospace telemetry and control fault; obtaining the fault association relationship of the aerospace telemetry and control fault from a fault mode database based on the fault mode number of the aerospace telemetry and control fault; determining whether the aerospace telemetry and control fault is to occur, the fault mode number of its corresponding associated fault, whether the associated fault is to occur, and the fault loading time of the associated fault based on the fault association relationship; if the associated fault is to occur, adding the fault mode number and fault loading time of the associated fault to a preset list of faults to be loaded; if the aerospace telemetry and control fault is to occur, adding the fault mode number and fault loading time of the aerospace telemetry and control fault to a preset list of faults to be loaded; and completing the fault simulation corresponding to the fault loading command based on the preset list of faults to be loaded, which can realize the simulation of composite faults and multi-point faults in aerospace telemetry and control, and improve the reliability of aerospace telemetry and control fault simulation. Specifically, this invention has been successfully applied to the construction of a practical fault drill simulation system, playing a significant role in the smooth progress and operation of the project. Compared with the methods commonly used in the industry at present, the advantages of this invention are mainly reflected in the following aspects: 1) It classifies and abstracts various fault modes in the field of aerospace telemetry and control, and can define the semantics of the descriptive element set. This is an original technology in the industry and can be promoted within the industry; 2) It can quickly simulate new faults through configuration without the need for separate program coding for new faults; 3) It can simulate fault correlation, realize the aggregation and assembly of various faults, and the associated logic control, and support the generation and simulation of multi-point faults and compound faults. Attached Figure Description
[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings: Figure 1 This is a first flowchart illustrating the simulation method for aerospace telemetry and control faults in the embodiments of this application; Figure 2 This is a second flowchart illustrating the simulation method for aerospace telemetry and control faults in the embodiments of this application; Figure 3 This is a schematic diagram of the third process of the simulation method for aerospace telemetry and control faults in the embodiments of this application; Figure 4 This is a schematic diagram of the fourth process of the simulation method for aerospace telemetry and control faults in the embodiments of this application; Figure 5 This is a schematic diagram of the relationship between the fault simulation models in the application examples of this application; Figure 6 This is a schematic diagram of the structure of a simulation device for aerospace telemetry and control faults in the embodiments of this application; Figure 7 This is a schematic block diagram of the system configuration of an electronic device according to an embodiment of this application. Detailed Implementation
[0019] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0020] To address at least one problem in the existing technology, this application provides a simulation method and apparatus for aerospace telemetry and control faults. With the commencement and successful execution of aerospace telemetry and control missions, a large amount of fault contingency plans and measured fault data from multi-target aerospace telemetry and control processes can be acquired. Through analysis, organization, and abstract modeling, unified fault layer modeling is achieved, and by simulating fault correlations, simulation of compound and multi-point faults is realized. Specifically, parameters for various faults in aerospace telemetry and control, including those related to spacecraft, telemetry and control networks, transceivers, and logic, can be acquired. The characteristic attributes of various parameters are defined, and combination patterns such as constraints and logical relationships between independent faults are modeled. Based on the combination pattern relationship model, algebraic operations, and timing logic control, simulation of compound and multi-point faults is achieved. Based on a large amount of fault contingency plans and measured fault data from multi-target aerospace telemetry and control processes, analysis, organization, and abstract modeling can be performed to achieve unified fault layer modeling, and by simulating fault correlations, simulation of compound and multi-point faults is realized.
[0021] The following examples illustrate this in detail.
[0022] To achieve simulation of complex and multi-point faults in aerospace telemetry and control, and to improve the reliability of aerospace telemetry and control fault simulation, this embodiment provides a simulation method for aerospace telemetry and control faults. The execution subject of this method includes, but is not limited to, a simulation device for aerospace telemetry and control faults. This simulation device can be a fault generator, such as... Figure 1 As shown, this method specifically includes the following: Step 100: Receive the fault loading command, which includes the fault mode number and fault loading time of the aerospace telemetry and control fault.
[0023] Specifically, the failure modes can be categorized as: spacecraft failure, telemetry and control network failure, transceiver failure, and logic failure.
[0024] Step 200: Obtain the fault association relationship of the aerospace telemetry and control fault from the fault mode database according to the fault mode number of the aerospace telemetry and control fault.
[0025] Step 300: Based on the fault association, determine whether the aerospace telemetry and control fault is about to occur, the fault mode number of its corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault.
[0026] Step 400: If the associated fault is to be triggered, add the fault mode number and fault loading time of the associated fault to a preset list of faults to be loaded; if the aerospace telemetry and control fault is to be triggered, add the fault mode number and fault loading time of the aerospace telemetry and control fault to a preset list of faults to be loaded.
[0027] Step 500: Based on the preset list of faults to be loaded, complete the fault simulation corresponding to the fault loading command.
[0028] In one embodiment, the fault mode database includes: a preset fault mode index table and a preset fault table; the preset fault mode index table includes: task code, target code, fault mode, and the correspondence between the three; the preset fault table includes: task code, target code, fault mode, fault association relationship, and the association relationship between the four; correspondingly, such as Figure 2 As shown, step 200 includes: Step 201: Obtain the mission code and target code corresponding to the fault mode number of the aerospace telemetry and control fault from the preset fault mode index table.
[0029] Step 202: Based on the fault mode number of the aerospace telemetry and control fault, its corresponding mission code and target code, obtain the fault association relationship of the aerospace telemetry and control fault from the preset fault table.
[0030] Specifically, prior to step 201, a large amount of fault contingency plans and actual fault measurement data from multi-target aerospace telemetry and control processes can be acquired. Based on these plans and data, the preset fault mode index table and the preset fault table are populated. These tables are then stored in a fault mode database, which can be a relational database such as Oracle. Four tables are created within the relational database, as shown in Tables 1 to 4. The table structure of the preset fault mode index table can be as shown in Table 1.
[0031] Table 1
[0032] Specifically, the preset fault tables may include: a spacecraft fault table, a telemetry, tracking, and command (TT&C) network / data transceiver fault table, and a spacecraft control logic fault table. The structure of the spacecraft fault table can be shown in Table 2, the structure of the TT&C network / data transceiver fault table can be shown in Table 3, and the structure of the spacecraft control logic fault table can be shown in Table 4. The mission code can be used to distinguish different missions. Each spacecraft has its own target code, which can be used to distinguish different spacecraft. The same mission may correspond to multiple targets. The fault mode number is used to distinguish different fault modes, which may include: instrument failure of a spacecraft, antenna failure of a spacecraft, etc. Telemetry parameters can be physical quantities and status information reflecting the spacecraft's operating status, space environment, and payload operation, such as attitude angle, angular velocity, and temperature of key components. Parameter type can represent the data type of parameter values 1 to 4, such as int, float, etc. Parameter values 1 to 4 can represent the values of telemetry parameters, and parameter fault generation functions can be input. Parameter fault generation functions can be used to simulate spacecraft TT&C faults.
[0033] Table 2
[0034] Table 3
[0035] Table 4
[0036] In one embodiment, the fault association includes: the operator, the fault mode number of the aerospace telemetry and control fault, the fault mode number of the associated fault, and the corresponding fault loading time difference between the two; correspondingly, such as Figure 3 As shown, step 300 includes: Step 301: If the operator is a fault recovery operator or a two-fault occurrence operator, then it is determined that both the aerospace telemetry and control fault and the associated fault are about to occur, and the fault loading time of the associated fault is the fault loading time of the aerospace telemetry and control fault.
[0037] Step 302: If the operator is a fault-causing operator for another fault, then it is determined that both the aerospace telemetry and control fault and the associated fault are about to occur, and the fault loading time of the associated fault is the fault loading time of the aerospace telemetry and control fault delayed by the fault loading time difference.
[0038] Step 303: If the operator is a spacecraft fault identifier operator and both the space telemetry and control fault and the associated fault are spacecraft faults, then it is determined that both the space telemetry and control fault and the associated fault are about to occur. The fault loading time of the associated fault is the fault loading time of the space telemetry and control fault delayed by the fault loading time difference. Parameter values common to the space telemetry and control fault and the associated fault are deleted from the preset fault table.
[0039] Specifically, the fault mode number can be used to determine whether the corresponding fault is an aerospace telemetry and control fault.
[0040] Furthermore, if the operator is a fault-free operator, then the fault loading time difference is determined. If the load time difference is greater than 0, then the aerospace telemetry and control fault is determined to be pending, and the associated fault is not pending. If the load time difference is less than 0, then the associated fault is determined to be pending, and the aerospace telemetry and control fault is not pending. The load time of the associated fault is determined to be the load time of the aerospace telemetry and control fault preceding the load time difference. If the load time difference is equal to 0, then both the aerospace telemetry and control fault and the associated fault are determined to be pending, and the load time of the associated fault is the same as the load time of the aerospace telemetry and control fault.
[0041] Specifically, the fault correlation description specification defines the correlation between individual faults, which can be described as follows: .
[0042] The meanings of each element are as follows: Type indicates the type of association relationship; TR represents the timing relationship of fault occurrence, which can be specifically described as follows: This indicates that the fault mode number is The fault and fault mode number are The time difference of the failure occurrence Second, .if If the value is greater than 0, then the fault mode number is: The fault occurred earlier than the fault mode number. If the malfunction occurs, =0 indicates that both faults occur simultaneously. If the value is less than 0, then the fault mode number is: The fault is later than the fault mode number. The malfunction occurred.
[0043] LR represents the logical relationship of fault occurrence, which can be specifically described as follows: L is the fault logic expression, which consists of operands and operators. The operands are a single fault, and the operators include: Unary operators are represented as: “ "That is, the fault recovery operator, which represents fault recovery; The "~" operator indicates that the fault does not occur. Binary operators are represented as: "Y" is the operator for both faults occurring, indicating that both faults occur. “I” indicates that one of the two faults has occurred; “ "That is, the fault-causing-one-fault operator, which means that a certain fault causes another fault; The "-" sign indicates a spacecraft fault operator, meaning that a fault in one spacecraft removes the same parameter from the fault parameter list of another spacecraft.
[0044] like Figure 4 As shown, in one embodiment, step 500 includes: Step 501: If there is a target record in the preset list of faults to be loaded with a fault loading time of the current system time, the target record is sent to the fault simulation model corresponding to the fault mode number in the target record. The preset list of faults to be loaded includes: at least one record, and each record includes: fault mode number and fault loading time.
[0045] Step 502: Apply the fault simulation model to complete the fault simulation corresponding to the target record.
[0046] Specifically, the fault simulation model may include: a spacecraft simulation model, a telemetry, tracking, and command (TT&C) network simulation model, a transceiver simulation model module, and a fault correlation simulation model. The fault generator (i.e., the fault generator simulation model) can be connected to the spacecraft simulation model, the TT&C network simulation model, the transceiver simulation model, and the fault correlation simulation model, respectively. The fault generator, spacecraft simulation model, TT&C network simulation model, transceiver simulation model, and fault correlation simulation model can be deployed on different servers or integrated into the same server. 1) The spacecraft simulation model is primarily used to maintain various parameters and flight procedures of the spacecraft. It receives fault loading commands from the fault generator model. Upon receiving the spacecraft fault loading command, the spacecraft simulation model views the parameter list and parameter fault values (equivalent to viewing a preset fault mode index table and a preset fault table), and sets the parameters according to the fault values. Upon receiving a logic fault loading command, it performs fault simulation according to the specified logic, that is, it can load logical faults according to the specified parameters. The logic fault loading function is provided by the spacecraft simulation model, as follows: public void LoadLogicFault(bool flag, string scPkNo, strings zFileName, string ucFileType, string ucOptTyp) / / Load logic failure 2) The telemetry and control network simulation model is mainly used to maintain the status of each telemetry and control station, including the telemetry, external measurement data reception and forwarding status of the station, and the types, formats, transmission times and frequencies of various types of data forwarded by the station. It receives fault loading commands sent by the fault generator model. Upon receiving the fault loading command, it first determines whether the station code is the current station code. If so, it determines the fault operation type code and performs simulation according to the simulation method in Table 5 based on the operation type code.
[0047] Table 5
[0048] 3) The transceiver simulation model is mainly used to maintain the status of each transceiver link, including the link's connectivity. It receives fault loading commands from the fault generator model. Upon receiving the fault loading command, it determines the fault operation type code and performs simulation according to the simulation methods in Table 6 based on the operation type code.
[0049] Table 6
[0050] 4) Fault correlation simulation model: mainly based on predefined fault correlation relationships, multiple independent faults are assembled into composite faults, and these faults are loaded according to predefined relationships.
[0051] “ "Indicates that the fault has been recovered, setting the fault that has occurred to a state that has not occurred; "~" indicates that the fault does not occur, and if this fault occurs, the other fault will not occur. “Y” indicates that both faults occur, or both faults occur simultaneously. “ "Indicates that one fault causes another fault; "-" indicates that a fault removes the same parameters contained in another fault.
[0052] 5) Fault generator simulation model, mainly used for loading and unloading faults and managing fault relationships.
[0053] In one embodiment, step 502 includes: Using a spacecraft simulation model, the parameter values corresponding to the fault mode numbers in the target record are obtained from a preset fault table. Based on the parameter values, the fault simulation corresponding to the target record is completed; the fault mode corresponding to the fault mode number is a spacecraft fault.
[0054] In one embodiment, step 502 includes: Using a telemetry and control network simulation model, the station code and operation type code corresponding to the fault mode number in the target record are obtained from a preset fault table. If the station code is the station code corresponding to the telemetry and control network simulation model, the fault simulation corresponding to the target record is completed according to the operation type code. The fault mode corresponding to the fault mode number is a telemetry and control network fault.
[0055] In one embodiment, step 502 includes: Using a transceiver simulation model, the operation type code corresponding to the fault mode number in the target record is obtained from a preset fault table. Based on the operation type code, the fault simulation corresponding to the target record is completed. The fault mode corresponding to the fault mode number is a transceiver fault.
[0056] To further illustrate this solution, this application provides an application example of a simulation method for aerospace telemetry and control faults. In this application example, the method includes: Step 1: Extract the parameter set of spacecraft faults, telemetry and control network and transceiver faults, as well as logic faults.
[0057] Specifically, flight parameters and flight phases can be configured first according to mission requirements. Once ready, the spacecraft simulation software drives this software to perform simulation and obtain the simulation data provided by this invention. The spacecraft fault parameter set consists of the following elements: mission identifier of the spacecraft, spacecraft identifier code, fault mode number, fault mode name, parameter name, parameter fault type (divided into: 0-set to a fixed value, 1-increase to a fixed value, 2-set a certain bit to a fixed value, 3-randomly jump within a certain range, 4-monotonically increase within a certain range, 5-monotonically decrease within a certain range, 6-change according to the generating function), parameter generating function, parameter value list, fault description, and fault correlation.
[0058] Specifically, the set of fault parameters for the telemetry, tracking, and command (TT&C) network and transceiver communication consists of the following elements: mission identifier of the spacecraft, spacecraft identifier code, fault mode number, fault mode name, fault type, operation type code, fault station code, fault information type identifier code, parameter list, fault description, and fault association.
[0059] Specifically, the logical fault parameters consist of the following elements: mission identifier of the spacecraft, spacecraft identifier code, fault mode number, fault mode name, implementation process name, data frame or source packet code, data file name, data file type, operation type code, fault description, and fault association.
[0060] Specifically, the fault correlation is represented by fault logic expressions, including fault recovery, fault not occurring, both faults occurring, one of the two faults occurring, one fault causing another fault, and one spacecraft fault removing the same parameters contained in the fault parameter list of another spacecraft.
[0061] Specifically, single-failure modes can be divided into three main categories: spacecraft failure (A), telemetry, tracking, and command (TT&C) and transceiver failure (T), and logic failure (L).
[0062] Spacecraft malfunctions can be described as follows:
[0063] The meanings of each element are as follows: M indicates the mission identifier of the spacecraft; O represents the spacecraft identification code; ID represents the fault mode number; Name represents the fault mode name; PName represents the parameter name; VarType represents the parameter fault type: 0 - set to a fixed value, 1 - increase to a fixed value, 2 - set a certain bit to a fixed value, 3 - randomly jump within a certain range, 4 - monotonically increase within a certain range, 5 - monotonically decrease within a certain range, 6 - change according to the generating function, where the generating function is VarFun; VarFun represents the parameter generation function; PL represents a list of parameter values, used to input the parameter generation function; Des represents the fault description; R represents the fault association.
[0064] The faults in the telemetry and control network and transceiver can be described as follows:
[0065] The meanings of each element are as follows: M indicates the mission identifier of the spacecraft; O represents the spacecraft identification code; ID represents the fault mode number; Name represents the fault mode name; FType indicates the fault type: 0 - telemetry and control network fault, 1 - transceiver fault; OptType represents the operation type code. The specific meaning of the operation type code is related to the fault type FType, as shown in Table 7 below.
[0066] Table 7
[0067] StaCode represents the faulty station code; BCode represents the fault information type identifier code; PL represents the parameter list; Des represents the fault description; R represents the fault association.
[0068] Logical faults can be described as:
[0069] The meanings of each element are as follows: M indicates the mission identifier of the spacecraft; O represents the spacecraft identification code; ID represents the fault mode number; Name represents the fault mode name; ProName represents the implementation process name; PKNo: Data frame or source packet code; FileName represents the data file name; FileType indicates the data file type; OptType represents the operation type code; Des represents the textual description of the fault; R represents the fault association.
[0070] Step 2: Establish a fault simulation model.
[0071] Specifically, fault simulation models are established, including fault generator simulation models, spacecraft simulation models, telemetry and control network simulation models, and transceiver simulation models.
[0072] Step 3: Based on the established fault simulation model, simulate aerospace telemetry and control fault modes through algebraic operations and sequential logic operations. Step 3 specifically includes: Step 31: The operator sends a fault loading command.
[0073] Specifically, the operator sends a fault loading command, which includes at least one of the following: spacecraft fault loading command, telemetry and control network fault loading command, transceiver fault loading command, and logic fault loading command. Each type of fault loading command contains a fault mode number and a fault loading time. For example... Figure 5As shown, the fault generator simulation model can send spacecraft fault loading commands and / or logic fault loading commands to the spacecraft simulation model, send telemetry and control network fault loading commands to the telemetry and control network simulation model, and send transceiver fault loading commands to the transceiver simulation model.
[0074] Step 32: The fault generator processes the original fault loading command and forwards it to each simulation model.
[0075] Specifically, the fault generator processes the original fault loading command and can determine the corresponding fault associations based on the fault mode number. The processing procedure is as follows: Step 321: Create two new lists, subfaults_list and future_list. Subfaults_list is a temporary list that records all faults and associated faults corresponding to fault loading commands. Future_list records faults to be loaded.
[0076] Step 322: Analyze the fault correlation R, first analyze L in LR and TR. , and .
[0077] Step 323: If the operator of L is a unary operator, process it according to the different operator types.
[0078] 1) If the operator is the fault recovery operator " ":Will Add to subfaults_list, where T is The loading time, T is set to Loading time.
[0079] 2) If the operator is the faulty operator "~", the fault will occur later than [previous event]. Remove the fault.
[0080] Specifically, if If the value is greater than 0, then subfaults_list will only add... , =0, then subfaults_list is added , T= Loading time; if If <0, then subfaults_list will only add... T= Early loading time .
[0081] Step 324: If the operator of L is a binary operator, process it according to the different operator types.
[0082] 1) If the operator is "Y" which causes both faults to occur: Add to subfaults_list, where T is The loading time, T is set to Loading time.
[0083] 2) If an operator causes another faulty operator " ":Will Add to subfaults_list, T is set to Loading time delay .
[0084] 3) If the operator is the spacecraft fault identifier "-": if and If all are spacecraft malfunctions, then from The parameter list in PL will The common parameters are removed, meaning that the fault can be removed from the preset fault table. The corresponding record and Removing the common parameter values can Add to subfaults_list, where T is Loading time; if or If there is no spacecraft malfunction, this operator is not processed and can be ignored. and No longer and Add to subfaults_list.
[0085] Step 325: Read all faults in the subfaults_list and add each fault to the future_list of faults to be loaded.
[0086] Step 326: Determine all faults in future_list, and load the corresponding fault when the loading time is reached.
[0087] Step 33: After receiving the fault loading command, the spacecraft simulation model, the telemetry and control network simulation model, and the transceiver simulation model simulate the fault phenomenon according to their respective behaviors.
[0088] Specifically, after receiving the fault loading command (i.e., the target record), the spacecraft simulation model, the telemetry and control network simulation model, and the transceiver simulation model can use the preset fault mode index table, the preset fault table, and the target record to obtain the target fault loading command, and then use the target fault loading command to simulate the fault phenomenon according to their respective behaviors.
[0089] The target fault loading commands can include: target parameter fault loading commands, target telemetry and control network fault loading commands, target data transmission and reception fault loading commands, and target logic fault loading commands. The target parameter fault loading command can include the following: task code, target code, fault mode number, loading time, parameter name, parameter value, parameter change type, and fault association. The target telemetry and control network fault loading command includes the following: task code, target code, fault mode number, loading time, process name, operation type code, station code, parameter value 1, parameter value 2, parameter value 3, and fault association. The target data transmission and reception fault loading command includes the following: task code, target code, fault mode number, loading time, process name, operation type code, station code, parameter value 1, parameter value 2, parameter value 3, and fault association. The target logic fault loading command includes the following: task code, target code, fault mode number, loading time, process name, data frame or source packet code, filename of recorded data, data format in the file, operation type code, and fault association.
[0090] Specifically, after receiving the fault loading command, the spacecraft simulation model, the telemetry and control network simulation model, and the transceiver simulation model simulate the fault phenomenon according to their respective behaviors.
[0091] From a software perspective, in order to simulate complex and multi-point faults in aerospace telemetry and control and improve the reliability of aerospace telemetry and control fault simulation, this application provides an embodiment of a simulation device for aerospace telemetry and control faults that implements all or part of the aforementioned simulation method for aerospace telemetry and control faults. See [link to relevant documentation]. Figure 6 The simulation device for aerospace telemetry and control faults specifically includes the following components: Receiver module 01 is used to receive a fault loading command, which includes: the fault mode number and fault loading time of the aerospace telemetry and control fault; The acquisition module 02 is used to obtain the fault association relationship of the aerospace telemetry and control fault from the fault mode database according to the fault mode number of the aerospace telemetry and control fault; The determination module 03 is used to determine, based on the fault association relationship, whether the aerospace telemetry and control fault is about to occur, the fault mode number of the corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault. Add module 04, which is used to add the fault mode number and fault loading time of the associated fault to a preset list of faults to be loaded if the associated fault is to be occurred; and to add the fault mode number and fault loading time of the aerospace telemetry and control fault to a preset list of faults to be loaded if the aerospace telemetry and control fault is to be occurred. Simulation module 05 is used to perform fault simulation corresponding to the fault loading command based on the preset list of faults to be loaded.
[0092] The embodiments of the simulation device for aerospace telemetry and control faults provided in this specification can be used to execute the processing flow of the embodiments of the simulation method for aerospace telemetry and control faults described above. Its functions will not be repeated here, but can be referred to the detailed description of the embodiments of the simulation method for aerospace telemetry and control faults described above.
[0093] Figure 7 This is a schematic diagram of the physical structure of an electronic device provided in an embodiment of the present invention, such as... Figure 7 As shown, the electronic device includes: a memory 71, a processor 72, and a computer program stored in the memory 71 and executable on the processor 72. When the processor 72 executes the computer program, it implements the following method: Receive a fault loading command, the fault loading command including: the fault mode number and fault loading time of the aerospace telemetry and control fault; Based on the fault mode number of the aerospace telemetry and control fault, obtain the fault association relationship of the aerospace telemetry and control fault from the fault mode database; Based on the fault association, determine whether the aerospace telemetry and control fault is about to occur, the fault mode number of its corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault. If the associated fault is to be triggered, the fault mode number and fault loading time of the associated fault are added to a preset list of faults to be loaded; if the aerospace telemetry and control fault is to be triggered, the fault mode number and fault loading time of the aerospace telemetry and control fault are added to a preset list of faults to be loaded. Based on the preset list of faults to be loaded, the fault simulation corresponding to the fault loading command is completed.
[0094] This embodiment discloses a computer program product, which includes a computer program that, when executed by a processor, implements the following method: Receive a fault loading command, the fault loading command including: the fault mode number and fault loading time of the aerospace telemetry and control fault; Based on the fault mode number of the aerospace telemetry and control fault, obtain the fault association relationship of the aerospace telemetry and control fault from the fault mode database; Based on the fault association, determine whether the aerospace telemetry and control fault is about to occur, the fault mode number of its corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault. If the associated fault is to be triggered, the fault mode number and fault loading time of the associated fault are added to a preset list of faults to be loaded; if the aerospace telemetry and control fault is to be triggered, the fault mode number and fault loading time of the aerospace telemetry and control fault are added to a preset list of faults to be loaded. Based on the preset list of faults to be loaded, the fault simulation corresponding to the fault loading command is completed.
[0095] This embodiment provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the following method: Receive a fault loading command, the fault loading command including: the fault mode number and fault loading time of the aerospace telemetry and control fault; Based on the fault mode number of the aerospace telemetry and control fault, obtain the fault association relationship of the aerospace telemetry and control fault from the fault mode database; Based on the fault association, determine whether the aerospace telemetry and control fault is about to occur, the fault mode number of its corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault. If the associated fault is to be triggered, the fault mode number and fault loading time of the associated fault are added to a preset list of faults to be loaded; if the aerospace telemetry and control fault is to be triggered, the fault mode number and fault loading time of the aerospace telemetry and control fault are added to a preset list of faults to be loaded. Based on the preset list of faults to be loaded, the fault simulation corresponding to the fault loading command is completed.
[0096] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0097] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0098] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0099] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0100] In the description of this specification, the references to terms such as "an embodiment," "a specific embodiment," "some embodiments," "for example," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.
[0101] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A simulation method for aerospace telemetry and control faults, characterized in that, include: Receive a fault loading command, the fault loading command including: the fault mode number and fault loading time of the aerospace telemetry and control fault; Based on the fault mode number of the aerospace telemetry and control fault, obtain the fault association relationship of the aerospace telemetry and control fault from the fault mode database; Based on the fault association, determine whether the aerospace telemetry and control fault is about to occur, the fault mode number of its corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault. If the associated fault is to be triggered, the fault mode number and fault loading time of the associated fault are added to a preset list of faults to be loaded; if the aerospace telemetry and control fault is to be triggered, the fault mode number and fault loading time of the aerospace telemetry and control fault are added to a preset list of faults to be loaded. Based on the preset list of faults to be loaded, the fault simulation corresponding to the fault loading command is completed. The fault association includes: the operator, the fault mode number of the aerospace telemetry and control fault, the fault mode number of the associated fault, and the fault loading time difference between the two. Correspondingly, determining whether the aerospace telemetry and control fault is about to occur, the fault mode number of its corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault based on the fault association relationship includes: If the operator is a fault recovery operator or an operator in which both faults occur, then it is determined that both the aerospace telemetry and control fault and the associated fault are about to occur, and the fault loading time of the associated fault is the fault loading time of the aerospace telemetry and control fault. If the operator is a fault-causing operator for another fault, then it is determined that both the aerospace telemetry and control fault and the associated fault are about to occur, and the fault loading time of the associated fault is the fault loading time of the aerospace telemetry and control fault delayed by the fault loading time difference. If the operator is a spacecraft fault identifier and both the space telemetry and control fault and the associated fault are spacecraft faults, then it is determined that both the space telemetry and control fault and the associated fault are about to occur. The fault loading time of the associated fault is the fault loading time of the space telemetry and control fault delayed by the fault loading time difference. The parameter values shared with the associated fault in the preset fault table are deleted.
2. The simulation method for aerospace telemetry and control faults according to claim 1, characterized in that, The fault mode database includes: a preset fault mode index table and a preset fault table; The preset fault mode index table includes: task code, target code, fault mode, and the correspondence between the three; The preset fault table includes: task code, target code, fault mode, fault association relationship and the association relationship between the four; Correspondingly, the step of obtaining the fault association relationship of the aerospace telemetry and control fault from the fault mode database based on the fault mode number of the aerospace telemetry and control fault includes: From the preset fault mode index table, obtain the mission code and target code corresponding to the fault mode number of the aerospace telemetry and control fault; Based on the fault mode number of the aerospace telemetry and control fault, its corresponding mission code and target code, the fault association relationship of the aerospace telemetry and control fault is obtained from the preset fault table.
3. The simulation method for aerospace telemetry and control faults according to claim 1, characterized in that, The process of simulating the faults corresponding to the fault loading command based on the preset list of faults to be loaded includes: If there is a target record in the preset list of faults to be loaded with a fault loading time of the current system time, the target record is sent to the fault simulation model corresponding to the fault mode number in the target record. The preset list of faults to be loaded includes: at least one record, and each record includes: fault mode number and fault loading time. The fault simulation model is applied to complete the fault simulation corresponding to the target record.
4. The simulation method for aerospace telemetry and control faults according to claim 3, characterized in that, The application of the fault simulation model to complete the fault simulation corresponding to the target record includes: Using a spacecraft simulation model, the parameter values corresponding to the fault mode numbers in the target record are obtained from a preset fault table. Based on the parameter values, the fault simulation corresponding to the target record is completed; the fault mode corresponding to the fault mode number is a spacecraft fault.
5. The simulation method for aerospace telemetry and control faults according to claim 3, characterized in that, The application of the fault simulation model to complete the fault simulation corresponding to the target record includes: Using a telemetry and control network simulation model, the station code and operation type code corresponding to the fault mode number in the target record are obtained from a preset fault table. If the station code is the station code corresponding to the telemetry and control network simulation model, the fault simulation corresponding to the target record is completed according to the operation type code. The fault mode corresponding to the fault mode number is a telemetry and control network fault.
6. The simulation method for aerospace telemetry and control faults according to claim 3, characterized in that, The application of the fault simulation model to complete the fault simulation corresponding to the target record includes: Using a transceiver simulation model, the operation type code corresponding to the fault mode number in the target record is obtained from a preset fault table. Based on the operation type code, the fault simulation corresponding to the target record is completed. The fault mode corresponding to the fault mode number is a transceiver fault.
7. A simulation device for aerospace telemetry and control faults, characterized in that, include: The receiving module is used to receive a fault loading command, which includes: the fault mode number and fault loading time of the aerospace telemetry and control fault; The acquisition module is used to obtain the fault association relationship of the aerospace telemetry and control fault from the fault mode database according to the fault mode number of the aerospace telemetry and control fault; The determination module is used to determine, based on the fault association relationship, whether the aerospace telemetry and control fault is about to occur, the fault mode number of the corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault. An add module is used to add the fault mode number and fault loading time of the associated fault to a preset list of faults to be loaded if the associated fault is to be triggered; and to add the fault mode number and fault loading time of the aerospace telemetry and control fault to a preset list of faults to be loaded if the aerospace telemetry and control fault is to be triggered. The simulation module is used to perform fault simulation corresponding to the fault loading command based on the preset list of faults to be loaded. The fault association includes: the operator, the fault mode number of the aerospace telemetry and control fault, the fault mode number of the associated fault, and the fault loading time difference between the two. Correspondingly, determining whether the aerospace telemetry and control fault is about to occur, the fault mode number of its corresponding associated fault, whether the associated fault is about to occur, and the fault loading time of the associated fault based on the fault association relationship includes: If the operator is a fault recovery operator or an operator in which both faults occur, then it is determined that both the aerospace telemetry and control fault and the associated fault are about to occur, and the fault loading time of the associated fault is the fault loading time of the aerospace telemetry and control fault. If the operator is a fault-causing operator for another fault, then it is determined that both the aerospace telemetry and control fault and the associated fault are about to occur, and the fault loading time of the associated fault is the fault loading time of the aerospace telemetry and control fault delayed by the fault loading time difference. If the operator is a spacecraft fault identifier and both the space telemetry and control fault and the associated fault are spacecraft faults, then it is determined that both the space telemetry and control fault and the associated fault are about to occur. The fault loading time of the associated fault is the fault loading time of the space telemetry and control fault delayed by the fault loading time difference. The parameter values shared with the associated fault in the preset fault table are deleted.
8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the simulation method for aerospace telemetry and control faults as described in any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the simulation method for aerospace telemetry and control faults as described in any one of claims 1 to 6.