Feature model-based spacecraft control software fault modeling and representing method
By controlling software failure modeling and representation methods based on feature models, the problem of failure comprehensive and expanding in the existing technology in the existing technology, and the systematic modeling and efficient diagnosis of the spacecraft fault mode. The safety and reliability of the spacecraft is guaranteed.
Patent Information
- Application Number
- CN202411512720.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-28
- Publication Date
- 2025-01-21
AI Technical Summary
The fault representation method in existing spacecraft control software relies on expert experience and a set of rules, making it difficult to fully cover all possible fault scenarios, and the rule-based fault representation is not conducive to subsequent modification and maintenance, and lacks scalability.
Adopting a feature model -based spacecraft control software failure modeling and representation method, systematic and formalized modeling expression of spacecraft faults by constructing a feature model, supporting complex situations such as multi -component failure, system -level failure, unknown failure and other complicated situations Fault attribution analysis and cross -model reuse.
The comprehensive and meticulous modeling of the aerospace fault mode is achieved, the possibility of failure and missed reporting and misunderstanding is reduced, the accuracy and efficiency of the spaceware control software in the diagnosis of rail failure, and ensuring the safety and efficiency of the spacecraft Reliability and improve the replication and expansion of the fault diagnostic module.
Smart Images
Figure CN119336619A_ABST
Abstract
Description
Technical Field
[0001] The invention relates to a spacecraft control software fault modeling and representation method based on a feature model, and belongs to the technical field of aerospace. Background Art
[0002] With the continuous development of embedded software systems, feature models, as a powerful modeling tool, have been widely used in software product line engineering, configurable system design and other fields. Feature models express various characteristics of software in a hierarchical tree structure, support systematic management and configuration of different modules, and greatly improve the reusability and maintainability of embedded software. However, the fault representation in existing spacecraft control software is mainly presented in the form of a set of rules formed by expert experience and domain knowledge, which is easy to cause omissions in the rule induction process, and lacks an efficient and comprehensive modeling method for the on-orbit fault mode of spacecraft that the control software needs to handle; and the rule-based fault representation is strongly dependent on the specific configuration parameters of the spacecraft, which is not conducive to subsequent modification and maintenance, as well as software reuse, and lacks scalability.
[0003] In summary, the prior art has the following three problems:
[0004] (1) Existing fault representation methods usually rely on pre-set rules and expert experience. However, due to the limitations of expert experience in depth and breadth, it is difficult to fully cover all possible fault scenarios, especially in complex aerospace embedded systems, which are prone to missed diagnosis and misdiagnosis.
[0005] (2) At present, based on the fault data accumulated during the test phase and on-orbit operation phase of the spacecraft, deep learning methods such as long short-term memory networks and residual networks are used in the fault modeling and diagnosis process; however, due to the uncertainty and unexplainability of the output results of the neural network, it is difficult to ensure the correctness of the fault diagnosis results;
[0006] (3) Existing work solidifies expert experience by establishing a fault knowledge base, rule base, or mathematical model. However, this requires a lot of manual intervention in the event of unknown faults, resulting in high software maintenance costs and limiting the scalability of the system. Summary of the invention
[0007] The technical problem solved by the present invention is: to overcome the shortcomings of the prior art and provide a method for modeling and representing spacecraft control software faults based on a feature model, which can systematically and formally model and express the spacecraft failure modes that the control software needs to handle, support fault attribution analysis of complex situations such as multi-component failures, system-level failures, unknown failures, and cross-model reuse of spacecraft fault representations.
[0008] The technical solution of the present invention is: in the first aspect, a method for modeling and representing spacecraft control software faults based on a feature model, comprising:
[0009] Classify the fault types that need to be diagnosed when the spacecraft control software is on-orbit, build feature models for each fault type, and build a spacecraft on-orbit fault classification model based on the feature models;
[0010] For each type of fault in the spacecraft on-orbit fault classification model, a fault representation model matching events and conditions is constructed;
[0011] For the status information monitored in real time on-orbit, the corresponding fault is matched based on the fault representation model to complete the on-orbit fault diagnosis.
[0012] Furthermore, the construction of a spacecraft on-orbit fault classification model based on a feature model includes: using feature model symbol definitions, decomposing spacecraft on-orbit fault types, constructing a field-oriented feature model symbol system, and using the feature model symbol system to organize the types of spacecraft on-orbit faults to form a spacecraft on-orbit fault classification model; the feature model symbol system includes:
[0013] The first level, according to the types of on-orbit failures of spacecraft, is decomposed into two sub-features with an OR relationship: component-level failure and system-level failure;
[0014] The second layer is decomposed into three sub-features with OR relationships according to the type of component-level faults: sensor fault, controller fault, and actuator fault; according to the type of system-level faults, it is decomposed into four sub-features with OR relationships: attitude reference loss, control performance degradation, excessive thruster jet, and energy security cannot be guaranteed;
[0015] The third layer is decomposed into four sub-features with OR relationships according to the type of sensor failure: ground-sensitive failure, sky-sensitive failure, gyro failure, and star-sensitive failure; according to the type of controller failure, it is decomposed into two sub-features with OR relationships: onboard computer failure and control rate design defect; according to the type of actuator failure, it is decomposed into two sub-features with OR relationships: momentum wheel failure and propulsion system failure;
[0016] The fourth layer is decomposed into two sub-features with an XOR relationship according to the type of star-sensor fault: a single star-sensor data is invalid, and all star-sensor data are invalid; according to the type of propulsion system fault, it is decomposed into two sub-features with an OR relationship: thruster fault and propulsion line fault.
[0017] Furthermore, the construction of a fault representation model matching an event and a condition includes:
[0018] Define event E and condition C respectively; event E is an external abnormal situation triggered by a fault, and condition C is an internal requirement of the system that needs to be met for fault diagnosis;
[0019] Based on the IF-ELSE conditional judgment structure in the preset domain code asset library, event E and condition C are extracted. The outermost conditional expression in the IF-ELSE conditional judgment structure belongs to event E, and the inner conditional expression belongs to condition C.
[0020] The extracted event-condition rules are stored in the EC fault model to form a fault representation model.
[0021] Furthermore, the event-condition rules are stored in a tree data structure.
[0022] Furthermore, in the data structure form of the tree, the judgment result of whether the root node event or condition is true is obtained by combining the relationships such as AND, OR, XOR, etc. between its child nodes.
[0023] Further, matching the corresponding fault based on the fault representation model includes:
[0024] According to the real-time monitored system status and component status information, the fault representation model is used to match fault events and fault conditions;
[0025] According to the feedback results of the fault model, if the fault event of the current abnormality is matched, the fault condition matching is performed; if both the event and the condition are matched successfully, the fault diagnosis result is returned; if the event is matched successfully, the condition is not matched or partially matched successfully, the result is recorded, and after verification, it is confirmed whether the fault feature representation in the fault feature model is modified or updated.
[0026] In the second aspect, a spacecraft control software fault modeling and representation system based on a feature model includes:
[0027] The first module divides the fault types that need to be diagnosed when the spacecraft control software is on-orbit, builds a feature model for each fault type, and builds a spacecraft on-orbit fault classification model based on the feature model;
[0028] The second module constructs a fault representation model matching events and conditions for each type of fault in the spacecraft on-orbit fault classification model;
[0029] The third module is to match the corresponding fault based on the fault representation model for the status information monitored in real time on-orbit, and complete on-orbit fault diagnosis.
[0030] Furthermore, the construction of a spacecraft on-orbit fault classification model based on a feature model includes: using feature model symbol definitions, decomposing spacecraft on-orbit fault types, constructing a field-oriented feature model symbol system, and using the feature model symbol system to organize the types of spacecraft on-orbit faults to form a spacecraft on-orbit fault classification model; the feature model symbol system includes:
[0031] The first level, according to the types of on-orbit failures of spacecraft, is decomposed into two sub-features with an OR relationship: component-level failure and system-level failure;
[0032] The second layer is decomposed into three sub-features with OR relationships according to the type of component-level faults: sensor fault, controller fault, and actuator fault; according to the type of system-level faults, it is decomposed into four sub-features with OR relationships: attitude reference loss, control performance degradation, excessive thruster jet, and energy security cannot be guaranteed;
[0033] The third layer is decomposed into four sub-features with OR relationships according to the type of sensor failure: ground-sensitive failure, sky-sensitive failure, gyro failure, and star-sensitive failure; according to the type of controller failure, it is decomposed into two sub-features with OR relationships: onboard computer failure and control rate design defect; according to the type of actuator failure, it is decomposed into two sub-features with OR relationships: momentum wheel failure and propulsion system failure;
[0034] The fourth layer is decomposed into two sub-features with an XOR relationship according to the type of star sensor failure: single star sensor data is invalid, all star sensor data is invalid; according to the type of propulsion system failure, it is decomposed into two sub-features with an OR relationship: thruster failure, propulsion line failure;
[0035] The fault representation model for building events and conditions that match the fault representation model includes:
[0036] Define event E and condition C respectively; event E is an external abnormal situation triggered by a fault, and condition C is an internal requirement of the system that needs to be met for fault diagnosis;
[0037] Based on the IF-ELSE conditional judgment structure in the preset domain code asset library, event E and condition C are extracted. The outermost conditional expression in the IF-ELSE conditional judgment structure belongs to event E, and the inner conditional expression belongs to condition C.
[0038] The extracted event-condition rules are stored in the EC fault model to form a fault representation model;
[0039] The event-condition rules are stored in the form of a tree data structure;
[0040] In the data structure form of the tree, the result of judging whether the root node event or condition is true is obtained by combining the relationships between its child nodes, such as AND, OR, XOR, etc.;
[0041] The matching of the corresponding fault based on the fault representation model includes:
[0042] According to the real-time monitored system status and component status information, the fault representation model is used to match fault events and fault conditions;
[0043] According to the feedback results of the fault model, if the fault event of the current abnormality is matched, the fault condition matching is performed; if both the event and the condition are matched successfully, the fault diagnosis result is returned; if the event is matched successfully, the condition is not matched or partially matched successfully, the result is recorded, and after verification, it is confirmed whether the fault feature representation in the fault feature model is modified or updated.
[0044] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of a method for modeling and representing spacecraft control software faults based on a feature model.
[0045] A device for modeling and representing spacecraft control software faults based on a feature model, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the method for modeling and representing spacecraft control software faults based on a feature model are implemented.
[0046] The advantages of the present invention compared with the prior art are:
[0047] (1) The present invention introduces a feature model to systematically classify and uniformly represent the fault modes that need to be diagnosed and processed by the spacecraft control software, making the fault modeling more comprehensive and detailed, and reducing the possibility of missed faults and false alarms;
[0048] (2) The present invention uses the feature model to construct an event-condition fault representation model, improves the accuracy and efficiency of on-orbit fault diagnosis of spacecraft control software through the event-condition matching mechanism, and helps to perform fault location analysis, thereby ensuring the safety and reliability of spacecraft on-orbit;
[0049] (3) The present invention proposes an event-condition fault representation model storage method based on a hierarchical tree structure, which not only improves the efficiency of fault model retrieval, modification, deletion, addition and other operations, but also improves the reusability and scalability of the spacecraft fault diagnosis module. BRIEF DESCRIPTION OF THE DRAWINGS
[0050] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:
[0051] Figure 1 It is a flowchart of the method of the present invention;
[0052] Figure 2 The method of the present invention constructs a spacecraft on-orbit fault classification model based on the feature model;
[0053] Figure 3 This is an event-condition fault representation diagram for a single star sensor data invalid fault according to the present invention;
[0054] Figure 4 This is a schematic diagram of the on-orbit fault diagnosis process of a spacecraft based on the event-condition fault representation model proposed in the present invention. DETAILED DESCRIPTION
[0055] In order to better understand the above technical scheme, the technical scheme of the present invention is described in detail below through the accompanying drawings and specific embodiments. It should be understood that the embodiments of the present invention and the specific features in the embodiments are detailed descriptions of the technical scheme of the present invention, rather than limitations on the technical scheme of the present invention. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments can be combined with each other.
[0056] The following is a further detailed description of a method for modeling and representing a spacecraft control software fault based on a feature model provided by an embodiment of the present invention in conjunction with the accompanying drawings. Figure 1 , the specific implementation methods may include:
[0057] Classify the fault types that need to be diagnosed when the spacecraft control software is on-orbit, build feature models for each fault type, and build a spacecraft on-orbit fault classification model based on the feature models;
[0058] For each type of fault in the spacecraft on-orbit fault classification model, a fault representation model matching events and conditions is constructed;
[0059] For the status information monitored in real time on-orbit, the corresponding fault is matched based on the fault representation model to complete the on-orbit fault diagnosis.
[0060] Further, the construction of a spacecraft on-orbit fault classification model based on a feature model includes: using feature model symbol definitions, decomposing spacecraft on-orbit fault types, constructing a field-oriented feature model symbol system, and using the feature model symbol system to organize the types of spacecraft on-orbit faults to form a spacecraft on-orbit fault classification model; the feature model symbol system includes:
[0061] The first level, according to the types of on-orbit failures of spacecraft, is decomposed into two sub-features with an OR relationship: component-level failure and system-level failure;
[0062] The second layer is decomposed into three sub-features with OR relationships according to the type of component-level faults: sensor fault, controller fault, and actuator fault; according to the type of system-level faults, it is decomposed into four sub-features with OR relationships: attitude reference loss, control performance degradation, excessive thruster jet, and energy security cannot be guaranteed;
[0063] The third layer is decomposed into four sub-features with OR relationships according to the type of sensor failure: ground-sensitive failure, sky-sensitive failure, gyro failure, and star-sensitive failure; according to the type of controller failure, it is decomposed into two sub-features with OR relationships: onboard computer failure and control rate design defect; according to the type of actuator failure, it is decomposed into two sub-features with OR relationships: momentum wheel failure and propulsion system failure;
[0064] The fourth layer is decomposed into two sub-features with an XOR relationship according to the type of star-sensor fault: a single star-sensor data is invalid, and all star-sensor data are invalid; according to the type of propulsion system fault, it is decomposed into two sub-features with an OR relationship: thruster fault and propulsion line fault.
[0065] In a possible implementation, the constructing of a fault representation model that matches an event and a condition includes:
[0066] Define event E and condition C respectively; event E is an external abnormal situation triggered by a fault, and condition C is an internal requirement of the system that needs to be met for fault diagnosis;
[0067] Based on the IF-ELSE conditional judgment structure in the preset domain code asset library, event E and condition C are extracted. The outermost conditional expression in the IF-ELSE conditional judgment structure belongs to event E, and the inner conditional expression belongs to condition C.
[0068] The extracted event-condition rules are stored in the EC fault model to form a fault representation model.
[0069] Furthermore, in a possible implementation, the event-condition rule is stored in the form of a tree data structure.
[0070] Optionally, in the data structure form of the tree, the judgment result of whether the root node event or condition is true is obtained by combining the relationships such as AND, OR, XOR, etc. between its child nodes.
[0071] In a possible implementation manner, matching the corresponding fault based on the fault representation model includes:
[0072] According to the real-time monitored system status and component status information, the fault representation model is used to match fault events and fault conditions;
[0073] According to the feedback results of the fault model, if the fault event of the current abnormality is matched, the fault condition matching is performed; if both the event and the condition are matched successfully, the fault diagnosis result is returned; if the event is matched successfully, the condition is not matched or partially matched successfully, the result is recorded, and after verification, it is confirmed whether the fault feature representation in the fault feature model is modified or updated.
[0074] Based on the same inventive concept, the present invention also provides a spacecraft control software fault modeling and representation system based on a feature model, comprising:
[0075] The first module divides the fault types that need to be diagnosed when the spacecraft control software is on-orbit, builds a feature model for each fault type, and builds a spacecraft on-orbit fault classification model based on the feature model;
[0076] The second module constructs a fault representation model matching events and conditions for each type of fault in the spacecraft on-orbit fault classification model;
[0077] The third module is to match the corresponding fault based on the fault representation model for the status information monitored in real time on-orbit, and complete on-orbit fault diagnosis.
[0078] In the solution provided in the embodiment of the present invention, Figure 1 As shown, the steps of a method for modeling and representing a spacecraft control software fault based on a feature model of the present invention are as follows:
[0079] (1) Based on the feature model, a spacecraft on-orbit fault classification model is constructed.
[0080] (2) For each type of on-orbit fault, an event-condition fault representation model is constructed.
[0081] (3) Perform on-orbit fault diagnosis based on the event-condition fault representation model.
[0082] Implementation method of step (1):
[0083] Using the definition of the feature model: the top-level features are continuously refined and decomposed in a tree structure until the bottom-level features, where the child features are the refinement of the parent features, and the relationship between them can be divided into OR and XOR; any child feature can be a required feature or an optional feature after the decomposition of the parent feature, and the relationship between the child features can be dependency, exclusion, etc., to construct an on-orbit fault classification model for spacecraft.
[0084] like Figure 2 As shown, the fault types that need to be diagnosed for the spacecraft control software when it is on orbit are divided into two categories: component level and system level. The relationship between them is OR, which means that they can occur at the same time.
[0085] For component failures, they are divided again according to sensors, controllers and actuators, and their relationship is OR.
[0086] Sensor failures include ground-sensitivity failures, sky-sensitivity failures, gyro failures, and star-sensitivity failures, and their relationship is OR. Star-sensitivity failures include single star-sensitivity data invalid failures and all star-sensitivity data invalid failures, and their relationship is XOR.
[0087] Controller failures include onboard computer failures and control law design defects, and the relationship between them is OR.
[0088] Actuator failures include momentum wheel failures and propulsion system failures, and their relationship is OR. Propulsion system failures include thruster failures and propulsion line failures, and their relationship is OR.
[0089] For system-level failures, including loss of attitude reference, degradation of control performance, excessive thruster jetting, and inability to ensure energy security, the relationship is OR.
[0090] Accordingly, a spacecraft on-orbit fault classification model is constructed based on the feature model.
[0091] Implementation method of step (2):
[0092] For each type of fault in the fault classification model, an event-condition fault representation and matching mechanism is established to improve the efficiency of fault diagnosis of spacecraft on-orbit.
[0093] An event (Event, E) is defined to represent an external abnormal situation that triggers a fault, for example, the star-sensor data is invalid at a certain moment; a condition (Condition, C) represents the internal system requirements that must be met for fault diagnosis (for example, the star-sensor data is invalid for a continuous period of time).
[0094] Events and conditions are extracted based on the IF-ELSE conditional judgment structure in the domain code asset library. The outermost conditional expression in the original fault diagnosis rule belongs to E, and the inner conditional expression belongs to C.
[0095] All extracted event-condition (EC) rules will be uniformly stored in the EC fault model.
[0096] like Figure 3 As shown in the figure, taking the "single star sensor data invalid" fault as an example, it explains how to use the feature model to establish a fault representation model. In the diagnosis process of the single star sensor data invalid fault, the two mandatory features triggered by this event are: "allow fault judgment" at the current moment (that is, the CWst allow fault judgment flag is TRUE) and there are one or more "data invalid types" (for example, attitude quality error, mode error, identification number error, constant fault, etc.). At this time, the event is matched successfully, and then the conditional judgment is performed. In the conditional feature model, there is only one mandatory feature, "data invalid time". When the cumulative star sensor data invalid time reaches 300 seconds, the diagnosis result of "single star sensor data invalid" will be returned, otherwise the time counting will continue.
[0097] Based on the event-condition fault model, the structures EC, EVENT, and CONDITION are designed and stored in the form of a "tree" data structure to improve the efficiency of operations such as matching, querying, and modifying. The judgment result of whether the root node event or condition is true is obtained by combining the AND, OR, XOR, and other relationships between its child nodes.
[0098] The structure EC is designed as follows, id is a unique number identifier, event is the fault event root node, and condition is the fault condition root node:
[0099] typedef struct EC
[0100] {
[0101] int id;
[0102] EVENT*event;
[0103] CONDITION *condition;
[0104] }
[0105] The structure EVENT is designed as follows, root is the root node of the fault event feature tree, and name is the unique event name identifier:
[0106] typedef struct EVENT
[0107] {
[0108] TreeNode*root;
[0109] char name
[20] ;
[0110] }
[0111] The structure CONDITION is designed as follows, root is the root node of the fault condition feature tree, and name is the unique condition name identifier:
[0112] typedef struct CONDITION
[0113] {
[0114] TreeNode*root;
[0115] char name
[20] ;
[0116] }
[0117] Implementation method of step (3):
[0118] like Figure 4 As shown in Figure 1, the on-orbit fault diagnosis process of spacecraft based on the event-condition fault representation model is as follows:
[0119] Step 1: Based on the real-time monitored system status and component status information, the EC fault model is used to match fault events and fault conditions.
[0120] Step 2: According to the feedback result of the fault model, if the current abnormal fault event is matched, the fault condition matching is performed.
[0121] Step 3: If both the event and the condition are matched successfully, the fault diagnosis result is returned. If the event is matched successfully, but the condition is not matched or partially matched successfully, the fault feature model will record the result and wait for expert verification to confirm whether to modify or update the fault feature representation in the fault feature model.
[0122] The present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer executes Figure 1 The method described.
[0123] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.
[0124] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0125] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0126] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0127] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.
[0128] The contents not described in detail in the specification of the present invention belong to the common knowledge of those skilled in the art.
Claims
1. A method for modeling and representing spacecraft control software faults based on a feature model, characterized in that: include: Classify the fault types that need to be diagnosed when the spacecraft control software is on-orbit, build feature models for each fault type, and build a spacecraft on-orbit fault classification model based on the feature models; For each type of fault in the spacecraft on-orbit fault classification model, a fault representation model matching events and conditions is constructed; For the status information monitored in real time on-orbit, the corresponding fault is matched based on the fault representation model to complete the on-orbit fault diagnosis.
2. A method for modeling and representing spacecraft control software faults based on a feature model according to claim 1, characterized in that: The construction of a spacecraft on-orbit fault classification model based on a feature model includes: using feature model symbol definitions, decomposing spacecraft on-orbit fault types, constructing a field-oriented feature model symbol system, and organizing spacecraft on-orbit fault types using the feature model symbol system to form a spacecraft on-orbit fault classification model; the feature model symbol system includes: The first level, according to the types of on-orbit failures of spacecraft, is decomposed into two sub-features with an OR relationship: component-level failure and system-level failure; The second layer is decomposed into three sub-features with OR relationships according to the type of component-level faults: sensor fault, controller fault, and actuator fault; according to the type of system-level faults, it is decomposed into four sub-features with OR relationships: attitude reference loss, control performance degradation, excessive thruster jet, and energy security cannot be guaranteed; The third layer is decomposed into four sub-features with OR relationships according to the type of sensor failure: ground-sensitive failure, sky-sensitive failure, gyro failure, and star-sensitive failure; according to the type of controller failure, it is decomposed into two sub-features with OR relationships: onboard computer failure and control rate design defect; according to the type of actuator failure, it is decomposed into two sub-features with OR relationships: momentum wheel failure and propulsion system failure; The fourth layer is decomposed into two sub-features with an XOR relationship according to the type of star-sensor fault: a single star-sensor data is invalid, and all star-sensor data are invalid; according to the type of propulsion system fault, it is decomposed into two sub-features with an OR relationship: thruster fault and propulsion line fault.
3. The method for modeling and representing spacecraft control software faults based on a feature model according to claim 1, characterized in that: The fault representation model for building events and conditions that match the fault representation model includes: Define event E and condition C respectively; event E is an external abnormal situation triggered by a fault, and condition C is an internal requirement of the system that needs to be met for fault diagnosis; Based on the IF-ELSE conditional judgment structure in the preset domain code asset library, event E and condition C are extracted. The outermost conditional expression in the IF-ELSE conditional judgment structure belongs to event E, and the inner conditional expression belongs to condition C. The extracted event-condition rules are stored in the EC fault model to form a fault representation model.
4. A method for modeling and representing spacecraft control software faults based on a feature model according to claim 3, characterized in that: The event-condition rules are stored in the form of a tree data structure.
5. A method for modeling and representing spacecraft control software faults based on a feature model according to claim 4, characterized in that: In the data structure form of the tree, the judgment result of whether the root node event or condition is true is obtained by combining the relationships such as AND, OR, XOR, etc. between its child nodes.
6. A method for modeling and representing spacecraft control software faults based on a feature model according to claim 1, characterized in that: The matching of the corresponding fault based on the fault representation model includes: According to the real-time monitored system status and component status information, the fault representation model is used to match fault events and fault conditions; According to the feedback results of the fault model, if the fault event of the current abnormality is matched, the fault condition matching is performed; if both the event and the condition are matched successfully, the fault diagnosis result is returned; if the event is matched successfully, the condition is not matched or partially matched successfully, the result is recorded, and after verification, it is confirmed whether the fault feature representation in the fault feature model is modified or updated.
7. A spacecraft control software fault modeling and representation system based on a feature model, characterized in that: include: The first module divides the fault types that need to be diagnosed when the spacecraft control software is on-orbit, builds a feature model for each fault type, and builds a spacecraft on-orbit fault classification model based on the feature model; The second module constructs a fault representation model matching events and conditions for each type of fault in the spacecraft on-orbit fault classification model; The third module is to match the corresponding fault based on the fault representation model for the status information monitored in real time on-orbit, and complete on-orbit fault diagnosis.
8. A spacecraft control software fault modeling and representation system based on feature model according to claim 7, characterized in that: The construction of a spacecraft on-orbit fault classification model based on a feature model includes: using feature model symbol definitions, decomposing spacecraft on-orbit fault types, constructing a field-oriented feature model symbol system, and organizing spacecraft on-orbit fault types using the feature model symbol system to form a spacecraft on-orbit fault classification model; the feature model symbol system includes: The first level, according to the types of on-orbit failures of spacecraft, is decomposed into two sub-features with an OR relationship: component-level failure and system-level failure; The second layer is decomposed into three sub-features with OR relationships according to the type of component-level faults: sensor fault, controller fault, and actuator fault; according to the type of system-level faults, it is decomposed into four sub-features with OR relationships: attitude reference loss, control performance degradation, excessive thruster jet, and energy security cannot be guaranteed; The third layer is decomposed into four sub-features with OR relationships according to the type of sensor failure: ground-sensitive failure, sky-sensitive failure, gyro failure, and star-sensitive failure; according to the type of controller failure, it is decomposed into two sub-features with OR relationships: onboard computer failure and control rate design defect; according to the type of actuator failure, it is decomposed into two sub-features with OR relationships: momentum wheel failure and propulsion system failure; The fourth layer is decomposed into two sub-features with an XOR relationship according to the type of star sensor failure: single star sensor data is invalid, all star sensor data is invalid; according to the type of propulsion system failure, it is decomposed into two sub-features with an OR relationship: thruster failure, propulsion line failure; The fault representation model for building events and conditions that match the fault representation model includes: Define event E and condition C respectively; event E is an external abnormal situation triggered by a fault, and condition C is an internal requirement of the system that needs to be met for fault diagnosis; Based on the IF-ELSE conditional judgment structure in the preset domain code asset library, event E and condition C are extracted. The outermost conditional expression in the IF-ELSE conditional judgment structure belongs to event E, and the inner conditional expression belongs to condition C. The extracted event-condition rules are stored in the EC fault model to form a fault representation model; The event-condition rules are stored in the form of a tree data structure; In the data structure form of the tree, the result of judging whether the root node event or condition is true is obtained by combining the relationships between its child nodes, such as AND, OR, XOR, etc.; The matching of the corresponding fault based on the fault representation model includes: According to the real-time monitored system status and component status information, the fault representation model is used to match fault events and fault conditions; According to the feedback results of the fault model, if the fault event of the current abnormality is matched, the fault condition matching is performed; if both the event and the condition are matched successfully, the fault diagnosis result is returned; if the event is matched successfully, the condition is not matched or partially matched successfully, the result is recorded, and after verification, it is confirmed whether the fault feature representation in the fault feature model is modified or updated.
9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A spacecraft control software fault modeling and representation device based on a feature model, 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, the steps of the method according to any one of claims 1 to 6 are implemented.