Spacecraft fault handling flow chart construction and executable script generation method and device

Abstract

The invention provides a spacecraft fault handling flow chart construction method and device and an executable script generation method and device, and can be applied to the technical field of computers. According to the spacecraft fault disposal flow chart construction and executable script generation method and device provided by the embodiment of the invention, the fault disposal process is described by adopting the state nodes, the fault disposal process is bound in a graphical manner, the fault disposal process is visually displayed, the operation is easy, the binding correctness of the fault disposal process is conveniently checked, and the fault disposal efficiency is improved. According to the fault disposal process description method based on the structured text, a starting node serves as a starting point, an ending node serves as an ending point, a node relation network is traversed according to a connection relation, graphical nodes and the relation network are converted into a fault disposal process structured description text, and the fault disposal process description text is converted into a fault disposal program. And the spacecraft fault can be automatically handled.

Description

Technical Field

[0001] This application relates to the field of spacecraft fault handling technology, specifically to a method and apparatus for constructing a spacecraft fault handling flowchart and generating an executable script. Background Technology

[0002] In current spacecraft malfunction handling procedures, the ground-based team typically follows a pre-established malfunction response plan step by step. These plans are usually in text format and require personnel to coordinate and direct multiple participants, assess the status in real time, and report back to ensure the correct execution of the procedures. The entire spacecraft malfunction handling process relies heavily on manual operation and status assessment, resulting in relatively low efficiency. Summary of the Invention

[0003] To address the problems in the prior art, this application provides a method and apparatus for constructing a spacecraft fault handling flowchart and generating an executable script, which can at least partially solve the problems existing in the prior art.

[0004] This application proposes a method for constructing a spacecraft fault handling flowchart, including:

[0005] The basic unit for establishing a spacecraft fault handling process includes a control node, a gateway node, and an action node.

[0006] By filling in node parameters in the control node, gateway node, and action node, multiple status nodes are obtained.

[0007] Based on the connections between the multiple state nodes and the specified nodes, a relationship network between the state nodes is constructed.

[0008] The configuration information of each state node is filled into the relationship network to obtain the spacecraft fault handling flowchart.

[0009] In some embodiments, the control node is used to determine the execution order of the fault handling process, including sequential execution, cyclic execution, and jump execution;

[0010] The gateway node is used to select the execution branch in the fault handling process, including branch nodes, parallel nodes, and program judgment nodes;

[0011] The action node is used to perform specific operations in the fault handling process, including sending remote control command interface, sending remote control command link port, and sending collaborative handling command.

[0012] In some embodiments, the list of state nodes is as follows:

[0013]

[0014] This application also proposes a method for generating structured descriptive text for spacecraft fault handling procedures, including:

[0015] Construct the mapping relationship between each status node and XML tag in the spacecraft fault handling flowchart;

[0016] Based on the state nodes and mapping relationships in the spacecraft fault handling flowchart, a structured description text of the spacecraft fault handling process is generated.

[0017] In some embodiments, generating a structured description text of the spacecraft fault handling process based on each state node in the spacecraft fault handling flowchart and the mapping relationship between each state node and XML tags includes:

[0018] Based on the mapping relationship, the state nodes and the relationships between the nodes in the spacecraft fault handling flowchart are converted into XML tags and the nesting relationships between the XML tags to obtain the structured description text of the spacecraft fault handling process.

[0019] In some embodiments, the mapping relationship between each state node and XML tag is shown in the following table:

[0020]

[0021]

[0022] This application also provides a method for generating an executable script for spacecraft fault handling, including:

[0023] Scripting languages ​​were developed for the control nodes, gateway nodes, and action nodes in the spacecraft fault handling process.

[0024] Establish the mapping relationship between the scripting language and XML tags of the control node, gateway node, and action node;

[0025] Based on the mapping relationship, the structured description text of the spacecraft fault handling process is converted into an executable script for spacecraft fault handling.

[0026] In some embodiments, the scripting languages ​​for constructing the control nodes, gateway nodes, and action nodes in the spacecraft fault handling process respectively include:

[0027] For the action nodes in the spacecraft fault handling process, construct corresponding command operation-related functions and provide interfaces for external calls to the command operation-related functions;

[0028] For the control node and gateway node in the spacecraft fault handling process, dynamic scripting languages ​​are constructed for the control node and gateway node respectively.

[0029] In some embodiments, the mapping relationship between the scripting languages ​​and XML tags of the control node, gateway node, and action node is shown in the following table:

[0030]

[0031] This application also proposes an apparatus for constructing a spacecraft fault handling flowchart, comprising:

[0032] The first module is used to establish the basic units of the spacecraft fault handling process, wherein the basic units include control nodes, gateway nodes and action nodes;

[0033] The first filling module is used to fill in node parameters in the control node, gateway node and action node respectively to obtain multiple status nodes;

[0034] The first construction module is used to construct a relationship network between the multiple state nodes and the specified nodes based on the connections between them.

[0035] The second filling module is used to fill in the configuration information of each state node in the relationship network to obtain a spacecraft fault handling flowchart.

[0036] This application also proposes a structured description text generation device for spacecraft fault handling procedures, including:

[0037] The second building module is used to construct the mapping relationship between each status node and XML tag in the spacecraft fault handling flowchart;

[0038] The generation module is used to generate a structured description text of the spacecraft fault handling process based on each state node in the spacecraft fault handling flowchart and the mapping relationship.

[0039] This application also provides an apparatus for generating an executable script for spacecraft fault handling, comprising:

[0040] The third building module is used to build the scripting languages ​​for the control nodes, gateway nodes, and action nodes in the spacecraft fault handling process, respectively.

[0041] The second module is used to establish the mapping relationship between the scripting language and XML tags of the control node, gateway node and action node;

[0042] The conversion module is used to convert the structured description text of the spacecraft fault handling process into an executable script for spacecraft fault handling based on the mapping relationship.

[0043] This application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps of the method described in any of the above embodiments.

[0044] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the method described in any of the above embodiments.

[0045] This application also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the method described in any of the above embodiments.

[0046] The spacecraft fault handling flowchart construction and executable script generation method and apparatus provided in this application embodiment use state nodes to describe the fault handling process, and bind the fault handling process in a graphical way, intuitively displaying the fault handling process, which is easy to operate and facilitates checking the correctness of the fault handling process binding. The fault handling process description method based on structured text takes the "start" node as the starting point and the "end" node as the ending point, traverses the node relationship network according to the connection relationship, and transforms the graphical node and relationship network into a structured description text of the fault handling process, and transforms the fault handling process description text into a fault handling program to realize the automatic handling of spacecraft faults. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in the embodiments of this application 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 only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0048] Figure 1 This is a schematic flowchart of a spacecraft fault handling process construction method provided in an embodiment of this application.

[0049] Figure 2 This is a flowchart illustrating a method for generating structured descriptive text of a spacecraft fault handling process according to an embodiment of this application.

[0050] Figure 3 This is a schematic flowchart of a spacecraft fault handling executable script generation method provided in an embodiment of this application.

[0051] Figure 4 This is a flowchart illustrating an automatic execution method for handling spacecraft malfunctions, provided in one embodiment of this application.

[0052] Figure 5 This is a flowchart of the fault handling process nodes for TT01 type provided in an embodiment of this application.

[0053] Figure 6 This is a schematic diagram of a device for constructing a spacecraft fault handling flowchart according to an embodiment of this application.

[0054] Figure 7 This is a schematic diagram of a structured description text generation device for spacecraft fault handling procedures provided in an embodiment of this application.

[0055] Figure 8 This is a schematic flowchart of a spacecraft fault handling executable script generation device provided in an embodiment of this application.

[0056] Figure 9 This is a schematic diagram of the physical structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0057] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments and their descriptions are used to explain this application, but are not intended to limit this application. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily arranged.

[0058] The terms “first,” “second,” etc., used in this document are not intended to specifically refer to order or sequence, nor are they used to limit this application; they are merely used to distinguish elements or operations described using the same technical terms.

[0059] The terms “include,” “including,” “have,” “contain,” etc., used in this article are all open-ended terms, meaning that they include but are not limited to.

[0060] The term "and / or" as used in this document includes any or all of the items mentioned.

[0061] To better understand this application, the research background of this application will be explained below.

[0062] Text-based spacecraft malfunction handling plans are not intuitive. While they describe the entire malfunction handling process, they can be represented by flowcharts, allowing ground personnel to quickly and easily grasp the process and facilitate subsequent operations. Furthermore, graphically presented spacecraft malfunction handling procedures are not only visually appealing but can also be easily converted into software execution flows. This allows for a degree of automation in the malfunction handling process, thereby improving its efficiency.

[0063] Based on this, embodiments of this application propose a method for constructing a spacecraft fault handling flowchart, a method for generating structured descriptive text for a spacecraft fault handling process, and a method for generating an executable script for spacecraft fault handling.

[0064] The execution subject of the method provided in this application embodiment includes, but is not limited to, a computer.

[0065] Figure 1 This is a schematic flowchart of a spacecraft fault handling process construction method provided in an embodiment of this application, as shown below. Figure 1 As shown in the embodiments of this application, the method for constructing a spacecraft fault handling flowchart includes:

[0066] S11. Establish the basic unit of the spacecraft fault handling process, wherein the basic unit includes a control node, a gateway node, and an action node;

[0067] S12. Fill in the node parameters in the control node, gateway node and action node respectively to obtain multiple status nodes;

[0068] S13. Based on the connections between the multiple state nodes and the specified nodes, construct a relationship network between the state nodes;

[0069] S14. Fill in the configuration information of each state node in the relationship network to obtain the spacecraft fault handling flowchart.

[0070] The spacecraft fault handling flowchart construction method provided in this application establishes basic units for the spacecraft fault handling process, wherein the basic units include control nodes, gateway nodes, and action nodes. Node parameters are filled into the control nodes, gateway nodes, and action nodes to obtain multiple state nodes. A relationship network between the multiple state nodes and designated nodes is constructed based on the connections between the state nodes. Configuration information of each state node is filled into the relationship network to obtain the spacecraft fault handling flowchart. In this way, the fault handling process is described using state nodes, and the fault handling process is graphically bound together, intuitively displaying the fault handling process, which is easy to operate and facilitates checking the correctness of the bound fault handling flowchart.

[0071] In some embodiments, the control node is used to determine the execution order of the fault handling process, including sequential execution, loop execution, and jump execution; the gateway node is used to select the execution branch in the fault handling process, including branch node, parallel node, and program judgment node; the action node is used to execute specific operations in the fault handling process, including sending remote control command interface, sending remote control command link port, and sending collaborative handling command.

[0072] Specifically, three main categories of state nodes—control nodes, gateway nodes, and action nodes—are created to represent the fault handling process. Control nodes define the execution order of the fault handling process, including sequential, loop, and jump operations. Gateway nodes select execution branches within the fault handling process, including branch nodes, parallel nodes, and program decision nodes. Action nodes execute specific operations within the fault handling process, including sending remote control commands via interfaces, sending remote control commands via links, and sending collaborative handling commands. Based on this, a relational network-based method for editing the fault handling process is created. This method constructs a relational network between state nodes and outputs the network as a fault handling process file, thus completing the editing of the fault handling process.

[0073] In some embodiments, three main types of nodes—control, gateway, and action—are established as the basic units of the fault handling process. Control nodes are sequential process nodes, gateway nodes are branch selection nodes, and action nodes are specific operation nodes. The handling process unit parameters are filled into these nodes to complete the establishment of the status nodes. The list of status nodes is shown in Table 1 below:

[0074] Table 1. List of State Nodes

[0075]

[0076]

[0077] Operators select the aforementioned nodes, construct a relationship network between status nodes by connecting the nodes, and write the handling process by filling in the node configuration information, thus completing the binding of the graphical fault handling process.

[0078] Figure 2 This is a flowchart illustrating a method for generating structured descriptive text for spacecraft fault handling procedures, as provided in an embodiment of this application. Figure 2 As shown in the embodiments of this application, the method for generating structured description text of spacecraft fault handling procedures includes:

[0079] S21. Construct the mapping relationship between each status node and XML tag in the spacecraft fault handling flowchart;

[0080] S22. Based on each state node in the spacecraft fault handling flowchart and the mapping relationship, generate a structured description text of the spacecraft fault handling process.

[0081] The method for generating structured description text of spacecraft fault handling procedures provided in this application embodiment constructs a mapping relationship between each state node in the spacecraft fault handling procedure diagram and XML tags; based on each state node in the spacecraft fault handling procedure diagram and the mapping relationship, it generates structured description text of the spacecraft fault handling procedure. Thus, this fault handling procedure description method based on structured text, starting with the "START" node and ending with the "END" node, traverses the node relationship network according to the connection relationships, transforming the graphical node and relationship network into structured description text of the fault handling procedure.

[0082] In some embodiments, generating a structured description text of the spacecraft fault handling process based on each state node in the spacecraft fault handling flowchart and the mapping relationship between each state node and XML tags includes: converting each state node in the spacecraft fault handling flowchart and the relationship between each node into XML tags and the nesting relationship between XML tags according to the mapping relationship, thereby obtaining a structured description text of the spacecraft fault handling process.

[0083] Specifically, for sequential fault handling processes, nodes are converted into XML tags in order of flow. For fault handling processes involving loops or branches, the processes or branches to be executed can be sub-tags of tags such as LOOP and SWITCH. Through these correspondences, the graphical nodes and relationship network are converted into XML tags, and the nesting relationships between tags are used to transform the fault handling flowchart into structured fault handling process description text.

[0084] In some embodiments, the mapping relationship between each state node and XML tag is shown in Table 2 below:

[0085] Table 2. Mapping relationship between each state node and XML tag

[0086]

[0087]

[0088] Figure 3 This is a flowchart illustrating a spacecraft fault handling executable script generation method according to an embodiment of this application, as shown below. Figure 3 As shown in the embodiments of this application, the spacecraft fault handling executable script generation method includes:

[0089] S31. Construct scripting languages ​​for the control nodes, gateway nodes, and action nodes in the spacecraft fault handling process, respectively.

[0090] S32. Establish the mapping relationship between the scripting language and XML tags of the control node, gateway node and action node;

[0091] S33. Based on the mapping relationship, convert the structured description text of the spacecraft fault handling process into an executable script for spacecraft fault handling.

[0092] The spacecraft fault handling executable script generation method provided in this application involves constructing scripting languages ​​for control nodes, gateway nodes, and action nodes in a spacecraft fault handling process; establishing a mapping relationship between the scripting languages ​​of the control nodes, gateway nodes, and action nodes and XML tags; and based on the mapping relationship, converting the structured description text of the spacecraft fault handling process into an executable script for spacecraft fault handling. In this way, the fault handling process description text is transformed into a fault handling program, enabling the automatic handling of spacecraft faults.

[0093] In some embodiments, the scripting languages ​​for constructing the control nodes, gateway nodes, and action nodes in the spacecraft fault handling process respectively include:

[0094] S311. For the action nodes in the spacecraft fault handling process, construct corresponding command operation-related functions and provide interfaces for external calls to the command operation-related functions;

[0095] S312. For the control node and gateway node in the spacecraft fault handling process, construct dynamic scripting languages ​​for the control node and gateway node respectively.

[0096] Specifically, in the process engine, for action nodes, functions related to issuing commands are pre-written and interfaces for external calls are provided. For control nodes and gateway nodes, these functions are gradually translated into a dynamic scripting language. The fault handling procedure is constructed by calling the command issuance functions through the dynamic scripting language.

[0097] In some embodiments, taking the LUA scripting language as an example, the mapping relationship between the control node, gateway node, action node and LUA scripting language is shown in Table 3 below:

[0098] Table 3. Mapping relationship between scripting languages ​​and XML tags for control nodes, gateway nodes, and action nodes.

[0099]

[0100]

[0101] By leveraging the mapping between XML tags and the LUA language, the fault handling process described in XML is transformed into an executable script, which then calls the command function to automatically build and execute the fault handling program.

[0102] To better understand this application, the method provided in this application will be described in detail below through a specific embodiment.

[0103] This embodiment provides a method for automatically executing spacecraft fault handling procedures. For example... Figure 4 As shown in the figure, this embodiment provides an automatic execution method for spacecraft fault handling procedures. First, a node relationship network is constructed through a visual interface. Then, the fault handling flowchart is converted into a structured fault handling process description text. Finally, the structured text is converted into a fault handling program to complete the fault handling.

[0104] The following example, using the automatic execution of a fault handling procedure for a certain type (number TT01), illustrates the steps of this method:

[0105] The execution of this handling procedure is as follows: After the handling procedure begins, the operator may choose to provide information prompts to the ground system or send remote control commands to Tianhe-1. The handling procedure is completed after the message prompts are completed or the commands are sent.

[0106] Step 1: As Figure 5 As shown in label 1, the operator creates "Start", "SWITCH" (branch), "MESSAGE", "CMD Single Remote Control Command", "SWITCH END", and "End" nodes in the visualization page, fills in the node configuration information, and uses directed connection lines to connect each node to form the fault handling process.

[0107] Step Two: After the node relationships in the handling process are constructed, starting from the "Start" node, the node relationship network is traversed using directed connections. First, a "Start" label is generated, followed by a "Branch Selection" label. The "Branch Selection" label contains nested message prompt and remote control command labels. Then, an "OR End" label is generated. The "OR End" label serves as the end and convergence node in the visualization and has no practical significance. Finally, an "End" label is generated, completing the output of the handling process document. The generated contingency plan XML file is shown below:

[0108]

[0109]

[0110] Step 3: After receiving a TT01 type fault, the fault handling software loads the handling process from the handling process library. The software translates the handling process file into an executable script. Start, End, and OR End are only used as node markers and are not converted. For the SWITCH tag, it is converted into branch selection syntax in the executable script, and the interface name for obtaining the condition is manually selected by the program. Message prompts and sending remote control commands are converted into different branches of the branching logic, and then into the message prompt interface name and the remote control command sending interface name, respectively. The converted Lua script content is shown below:

[0111]

[0112] The backend program interface contains the specific execution logic of the action nodes, and can send the node execution status to the front end for display. After receiving the information of the corresponding node ID, the front end displays the running status of the node, completing the visualization of the entire fault handling process.

[0113] In summary, this application embodiment establishes three main categories of nodes—control, gateway, and action—as the basic units of the spacecraft fault handling process. Based on this, a graphical fault handling process editing interface is implemented, converting text-described spacecraft fault handling processes into graphical processes. Furthermore, this application embodiment also implements a custom conversion relationship between graphical spacecraft fault handling processes and structured text, enabling direct conversion of graphical handling processes into XML text. Additionally, it implements a rule mapping and automated execution method for XML text fault handling processes based on the LUA scripting language.

[0114] This application embodiment describes the fault handling process using state nodes, and binds the fault handling process in a graphical way, which intuitively displays the fault handling process, is easy to operate, and facilitates checking the correctness of the fault handling process binding.

[0115] In this embodiment, the graphical process of fault handling is automatically converted into structured XML text, and then this text is mapped into an executable LUA scripting language, thus achieving automated execution of the spacecraft fault handling process.

[0116] Figure 6 This is a schematic diagram of a device for constructing a spacecraft fault handling flowchart according to an embodiment of this application, as shown below. Figure 6 As shown in the embodiment of this application, the apparatus for constructing a spacecraft fault handling flowchart includes:

[0117] The first module 41 is used to establish the basic unit of the spacecraft fault handling process, wherein the basic unit includes a control node, a gateway node, and an action node.

[0118] The first filling module 42 is used to fill in node parameters in the control node, gateway node and action node respectively to obtain multiple status nodes;

[0119] The first construction module 43 is used to construct a relationship network between the multiple state nodes and the specified nodes based on the connections between them.

[0120] The second filling module 44 is used to fill in the configuration information of each state node in the relationship network to obtain a spacecraft fault handling flowchart.

[0121] The spacecraft fault handling flowchart construction apparatus provided in this application establishes basic units for the spacecraft fault handling process, wherein each basic unit includes a control node, a gateway node, and an action node. Node parameters are filled into each of the control node, gateway node, and action node to obtain multiple state nodes. A relationship network between the multiple state nodes and designated nodes is constructed based on the connections between them. Configuration information for each state node is filled into this relationship network to obtain the spacecraft fault handling flowchart. In this way, state nodes are used to describe the fault handling process, and the fault handling process is graphically bound together, intuitively displaying the fault handling process, making it easy to operate and convenient to check the correctness of the bound fault handling flowchart.

[0122] Figure 7 This is a schematic flowchart of a structured description text generation device for spacecraft fault handling procedures provided in an embodiment of this application, such as... Figure 7 As shown in the embodiment of this application, the structured description text generation device for spacecraft fault handling procedures includes:

[0123] The second construction module 51 is used to construct the mapping relationship between each status node and XML tag in the spacecraft fault handling flowchart;

[0124] The generation module 52 is used to generate a structured description text of the spacecraft fault handling process based on each state node in the spacecraft fault handling flowchart and the mapping relationship.

[0125] The structured description text generation device for spacecraft fault handling procedures provided in this application embodiment constructs a mapping relationship between each state node in the spacecraft fault handling procedure diagram and XML tags; based on each state node in the spacecraft fault handling procedure diagram and the mapping relationship, it generates a structured description text for the spacecraft fault handling procedure. Thus, the fault handling procedure description method based on structured text, starting with the "START" node and ending with the "END" node, traverses the node relationship network according to the connection relationships, transforming the graphical node and relationship network into a structured description text for the fault handling procedure.

[0126] Figure 8 This is a flowchart illustrating an embodiment of the spacecraft fault handling executable script generation device provided in this application, as shown below. Figure 8 As shown in the embodiment of this application, the spacecraft fault handling executable script generation apparatus includes:

[0127] The third construction module 61 is used to construct the scripting languages ​​for the control nodes, gateway nodes, and action nodes in the spacecraft fault handling process, respectively.

[0128] The second establishment module 62 is used to establish the mapping relationship between the script language and XML tags of the control node, gateway node and action node;

[0129] The conversion module 63 is used to convert the structured description text of the spacecraft fault handling process into an executable script for spacecraft fault handling based on the mapping relationship.

[0130] The spacecraft fault handling executable script generation device provided in this application generates script languages ​​for control nodes, gateway nodes, and action nodes in the spacecraft fault handling process by constructing script languages ​​for each node, gateway node, and action node; establishing a mapping relationship between the script languages ​​of the control nodes, gateway nodes, and action nodes and XML tags; and converting the structured description text of the spacecraft fault handling process into an executable script for spacecraft fault handling based on the mapping relationship. In this way, the fault handling process description text is transformed into a fault handling program, enabling automatic handling of spacecraft faults.

[0131] The embodiments of the apparatus provided in this application can be used to execute the processing flow of the above-described method embodiments. Its functions will not be repeated here, but can be referred to the detailed description of the above-described method embodiments.

[0132] Figure 9 This is a schematic diagram of the physical structure of an electronic device provided in an embodiment of this application, as shown below. Figure 9 As shown, the electronic device may include a processor 701, a communications interface 702, a memory 703, and a communication bus 704, wherein the processor 701, the communications interface 702, and the memory 703 communicate with each other via the communication bus 704. The processor 701 may call logical instructions in the memory 703 to execute the methods described in any of the above embodiments.

[0133] Furthermore, the logical instructions in the aforementioned memory 703 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0134] This embodiment discloses a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions, and when the program instructions are executed by a computer, the computer can perform the methods provided in the above-described method embodiments.

[0135] This embodiment provides a computer-readable storage medium storing a computer program that causes the computer to perform the methods provided in the above-described method embodiments.

[0136] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application 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.

[0137] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. 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... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0138] 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.

[0139] 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.

[0140] 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 this application. 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.

[0141] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above descriptions are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method for constructing a spacecraft fault handling flowchart, characterized in that, include: The basic unit for establishing a spacecraft fault handling process includes a control node, a gateway node, and an action node. By filling in node parameters in the control node, gateway node, and action node, multiple status nodes are obtained. Based on the connections between the multiple state nodes and the specified nodes, a relationship network between the state nodes is constructed. The configuration information of each state node is filled into the relationship network to obtain the spacecraft fault handling flowchart.

2. The method according to claim 1, characterized in that, The control node is used to determine the execution order of the fault handling process, including sequential execution, loop execution, and jump execution; The gateway node is used to select the execution branch in the fault handling process, including branch nodes, parallel nodes, and program judgment nodes; The action node is used to perform specific operations in the fault handling process, including sending remote control command interface, sending remote control command link port, and sending collaborative handling command.

3. The method according to claim 1 or 2, characterized in that, The list of state nodes is as follows:

4. A method for generating structured descriptive text for spacecraft fault handling procedures, characterized in that, include: Construct the mapping relationship between each status node and XML tag in the spacecraft fault handling flowchart; Based on the state nodes and mapping relationships in the spacecraft fault handling flowchart, a structured description text of the spacecraft fault handling process is generated.

5. The method according to claim 4, characterized in that, The process involves generating a structured description text of the spacecraft fault handling process based on the state nodes in the spacecraft fault handling flowchart and the mapping relationship between each state node and XML tags, including: Based on the mapping relationship, the state nodes and the relationships between the nodes in the spacecraft fault handling flowchart are converted into XML tags and the nesting relationships between the XML tags to obtain the structured description text of the spacecraft fault handling process.

6. The method according to claim 4 or 5, characterized in that, The mapping relationship between each status node and XML tag is shown in the table below:

7. A method for generating executable scripts for spacecraft fault handling, characterized in that, include: Scripting languages ​​were developed for the control nodes, gateway nodes, and action nodes in the spacecraft fault handling process. Establish the mapping relationship between the scripting language and XML tags of the control node, gateway node, and action node; Based on the mapping relationship, the structured description text of the spacecraft fault handling process is converted into an executable script for spacecraft fault handling.

8. The method according to claim 7, characterized in that, The scripting languages ​​used to construct the control nodes, gateway nodes, and action nodes in the spacecraft fault handling process include: For the action nodes in the spacecraft fault handling process, construct corresponding command operation-related functions and provide interfaces for external calls to the command operation-related functions; For the control node and gateway node in the spacecraft fault handling process, dynamic scripting languages ​​are constructed for the control node and gateway node respectively.

9. The method according to claim 7 or 8, characterized in that, The mapping relationship between the scripting language and XML tags of the control node, gateway node, and action node is shown in the table below:

10. 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 program, it implements the steps of the method described in any one of claims 1 to 9.

Images