A configurable general satellite mission management method and device

Abstract

The application provides a configurable general satellite task management method and device, which decomposes satellite tasks into tasks, subtasks and subevents according to a tree structure from general to specific; stores the content and internal logical relationship of the tasks, subtasks and subevents in the on-board storage space; executes corresponding satellite tasks according to the content and internal logical relationship of the tasks, subtasks and subevents; and designs, edits, modifies and uploads the content and internal logical relationship of all the tasks, subtasks and subevents in the satellite task to the on-board storage and execution according to the on-orbit use requirement. The application generalizes and models the satellite task flow, effectively realizes the fast task design, task modification and task reconstruction of the satellite management software, effectively improves the satellite task flow design efficiency and satellite management efficiency, and solves the on-orbit task flow fast modification and task reconstruction requirement problem.

Description

Technical Field

[0001] This invention belongs to the field of satellite mission management technology, and relates to a satellite mission management method, particularly a configurable universal satellite mission management method and apparatus. Background Technology

[0002] Currently, with technological advancements, the on-orbit missions of my country's satellites are becoming increasingly complex and diverse, leading to more intricate mission process designs. Furthermore, as the understanding of the mission deepens during the design process, the mission process is continuously adjusted and modified. Additionally, during satellite operation, changes in external conditions or mission requirements also necessitate adjustments or modifications to the mission process.

[0003] The increasing complexity and diversity of satellite missions, along with the continuous adjustments and changes during mission design, have brought certain challenges to the design and management of satellite mission management software. At the same time, the adjustment requirements of on-orbit missions have placed demands on the mission reconfigurability of satellite mission management software. Summary of the Invention

[0004] To overcome the shortcomings of existing technologies, the inventors have conducted intensive research and provided a configurable general satellite mission management method and device. This method generalizes and models the satellite mission process, effectively enabling rapid mission design, modification, and reconfiguration in satellite mission management software. It significantly improves the efficiency of satellite mission process design and satellite mission management, and solves the problem of rapid modification and reconfiguration of on-orbit mission processes.

[0005] The technical solution provided by this invention is as follows:

[0006] Firstly, a configurable, universal satellite mission management method includes:

[0007] The satellite mission is decomposed into missions, sub-missions, and sub-events in a tree structure from general to specific. Each mission includes at least one sub-mission, and each sub-mission includes at least one sub-event.

[0008] The contents of tasks and subtasks, the output of sub-events, and the internal logical relationships between subtasks are classified and stored in the on-board storage space.

[0009] Execute the corresponding satellite mission based on the content and internal logical relationships of the mission, sub-mission, and sub-event.

[0010] Based on the requirements for use in orbit, the ground team designs, edits, modifies, and uploads the content and internal logical relationships of all tasks, sub-tasks, and sub-events in the satellite mission to the satellite for storage and execution.

[0011] Secondly, a configurable universal satellite mission management device includes:

[0012] The file management module includes a file configuration and index area, a task event storage area, a data area, and a program area. The file configuration and index area stores configuration information for on-board storage space and index information for subtasks. The program area stores the timing schedule and internal logical relationships of subtasks within each task. The data area mainly stores the output content of sub-events. The task event storage area is divided into a pre-storage area and a reconstruction area. The pre-storage area stores multiple pre-configured subtasks for ground use, which can be combined for configuration. The reconstruction area stores subtasks newly configured and uploaded by the ground for on-orbit use. Subtasks in the reconstruction area and subtasks in the pre-storage area can be reconfigured and combined into new tasks for on-orbit use.

[0013] The judgment and execution module is used to call and execute subtasks in the task event storage area according to the timing and internal logical relationship of subtasks in each task stored in the program area, based on the file configuration and the index information of subtasks stored in the index area, and to retrieve the data required for executing subtasks from the data area.

[0014] According to the present invention, a configurable universal satellite mission management method and apparatus have the following features:

[0015] Beneficial effects:

[0016] This invention provides a configurable, universal satellite mission management method and apparatus. By generalizing and modeling the satellite mission process and classifying and storing different mission data in space, it enables rapid and effective modification and reconfiguration of satellite missions from the ground, effectively improving the efficiency of satellite mission process design and satellite management, and solving the problem of rapid modification and reconfiguration of on-orbit mission processes. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the task structure decomposition of the task management method of the present invention;

[0018] Figure 2 This is a sub-event structure diagram of the task management method of the present invention;

[0019] Figure 3 This is a subtask structure diagram of the task management method of the present invention;

[0020] Figure 4 This is a task structure diagram of the task management method of the present invention;

[0021] Figure 5 This is a diagram showing the on-board storage space partitioning structure of the task management method of the present invention. Detailed Implementation

[0022] The features and advantages of the present invention will become clearer and more apparent from the following detailed description.

[0023] The term “exemplary” as used herein means “serving as an example, embodiment, or illustration.” Any embodiment illustrated herein as “exemplary” is not necessarily to be construed as superior to or better than other embodiments.

[0024] According to a first aspect of the present invention, a configurable general satellite mission management method is provided, such as... Figure 1 As shown, this includes: decomposing satellite missions into missions, sub-missions, and sub-events in a tree structure from general to specific, with each mission including at least one sub-mission and each sub-mission including at least one sub-event;

[0025] The contents of tasks and subtasks, the output of sub-events, and the internal logical relationships between subtasks are classified and stored in the on-board storage space.

[0026] The corresponding satellite missions are executed according to the content and internal logical relationships of the missions, sub-missions, and sub-events. The ground can design, edit, and modify the content and internal logical relationships of all missions, sub-missions, and sub-events according to the on-orbit usage requirements, and upload them to the satellite for storage and execution.

[0027] like Figure 2 As shown, the sub-event structure includes the sub-event start condition, sub-event content, and sub-event end flag. The sub-event start condition is generally a remote control command, a time node, or the end flag of another sub-event. The sub-event end flag is an internal flag or a telemetry flag. The sub-event content includes the trigger condition, criterion, judgment period, execution / output content, and stop status. The trigger condition is triggered by a combination of one or more conditions, such as a remote control command, a time node, or changes in telemetry parameters. The criterion is a combination of one or more criteria, such as a time node or changes in telemetry parameters. The judgment period refers to the time or number of judgments after the criteria are met, and can be modified. The execution / output content is any combination of one or more programmable commands, changes in telemetry parameters, or flag settings. The stop status stops the current sub-event state; the default is not to stop, and can be modified.

[0028] Taking the sub-event "Star-Rocket Separation" as an example, the sub-event structure is shown in Table 1.

[0029] Table 1 Example of Sub-Event Structure

[0030]

[0031] like Figure 3As shown, the subtask structure includes subtask start conditions, subtask content, and subtask end flags. The subtask start condition is triggered by a remote control command, a time node, or the end flag of another subtask. The subtask content consists of multiple sub-events. Subtasks are divided into two main categories: serial subtasks and parallel subtasks. Serial subtasks are executed in series by multiple sub-events in a single thread, while parallel subtasks are executed in parallel by multiple sub-events in multiple threads. After all sub-events have been executed, the subtask end flag is set. This subtask end flag can be an internal flag or a telemetry flag. The subtask structure also has a stop state, which can stop the execution of related subtasks through ground remote control commands.

[0032] The subtask "Star-Rocket Separation and Initial State Establishment" is used as an example for illustration. The subtask structure is shown in Table 2.

[0033] Table 2 Example of Subtask Structure

[0034]

[0035] like Figure 4 As shown, the task structure includes task start conditions, task content, and task end flag; the task start condition is remote triggering; the task content is composed of multiple subtasks, and multiple subtasks are executed serially during task execution, while regular subtasks are executed in parallel; after all subtasks have been executed, the task end flag is set, which can be an internal flag or a telemetry flag.

[0036] Taking the "active segment" of the task as an example, the task structure is shown in Table 3.

[0037] Table 3 Example of Task Structure

[0038]

[0039] like Figure 5 As shown, different task data are stored in the file configuration and index area, task event storage area, data area, and program area to implement data classification and storage. The file configuration and index area stores the configuration information of the on-board storage space (including partitions and address space allocation of the program area, data area, and task event storage area) and subtask index information, etc. Examples of stored data are shown in Table 4. The program area stores the timing scheduling and internal logical relationships of subtasks within each task, as shown in Table 5. The data area mainly stores the content output by sub-events, such as program control instruction information, as shown in Table 6. The task event storage area is divided into a pre-storage area and a reconfiguration area. The pre-storage area stores multiple pre-configured subtasks for combined configuration use on the ground. The reconfiguration area stores subtasks newly configured and uploaded by the ground during on-orbit operation, as shown in Table 7. These subtasks and the subtasks in the pre-storage area can be reconfigured and combined into new tasks for on-orbit use.

[0040] Table 4. Examples of File Configuration and Index Area Data Storage

[0041]

[0042] Table 5 Examples of data stored in the program area

[0043]

[0044] Table 6 Example of data storage in the data area

[0045] serial number Programmable instruction number Content of programmable instruction output 1 K001 Programmable command: Forward the GNC subsystem star-rocket separation status. 2 K002 Programmable command: Solar array clamping point unlocking command … … …

[0046] Table 7 Example of data stored in the task event storage area

[0047]

[0048] When executing a task, the subtasks in the task are called and executed according to the timing and internal logical relationships of the subtasks stored in the program area, based on the file configuration and the index information of the subtasks stored in the index area. The data required for executing the subtasks is retrieved from the data area through mapping.

[0049] When adjustments to the task output are needed, only the data area needs to be modified; when changes to the task flow or task restructuring are needed, only the subtasks in the task event storage area need to be modified or new subtasks need to be added.

[0050] According to a second aspect of the present invention, a configurable universal satellite mission management device is also provided, comprising:

[0051] The file management module includes a file configuration and index area, a task event storage area, a data area, and a program area. The file configuration and index area stores configuration information for onboard storage space and index information for subtasks. The program area stores the timing schedule and internal logical relationships of subtasks within each task. The data area primarily stores the output content of sub-events, such as instruction information. The task event storage area is divided into a pre-storage area and a reconstruction area. The pre-storage area stores multiple pre-configured subtasks on the ground for combined configuration. The reconstruction area stores subtasks newly configured and uploaded by the ground for on-orbit use. Subtasks in the reconstruction area and pre-storage areas can be reconfigured and combined into new tasks for on-orbit use. The content of each area in the file management module allows for modification of the data area's data entries when adjusting task output content; and modification of the data entries or uploading of new subtasks in the task event storage area when changing the task flow or reconstructing the task.

[0052] The judgment and execution module is used to call and execute subtasks in the task event storage area according to the timing and internal logical relationship of subtasks in each task stored in the program area, based on the file configuration and the index information of subtasks stored in the index area, and to retrieve the data required for executing subtasks from the data area.

[0053] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the device described above can be referred to the corresponding process in the aforementioned method, and will not be repeated here.

[0054] The device technology solution of this application, in essence, or the part that contributes to the prior art, or all or 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 a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0055] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this invention can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0056] The present invention has been described in detail above with reference to specific embodiments and exemplary examples; however, these descriptions should not be construed as limiting the present invention. Those skilled in the art will understand that various equivalent substitutions, modifications, or improvements can be made to the technical solutions and embodiments of the present invention without departing from the spirit and scope of the invention, and all such modifications and improvements fall within the scope of the present invention. The scope of protection of the present invention is defined by the appended claims.

[0057] The contents not described in detail in this specification are common knowledge to those skilled in the art.

Claims

1. A configurable, universal satellite mission management method, characterized in that, include: The satellite mission is decomposed into missions, sub-missions, and sub-events in a tree structure from general to specific. Each mission includes at least one sub-mission, and each sub-mission includes at least one sub-event. The contents of tasks and subtasks, the output of sub-events, and the internal logical relationships between subtasks are classified and stored in the on-board storage space. Execute the corresponding satellite mission based on the content and internal logical relationships of the mission, sub-mission, and sub-event. Based on the on-orbit usage requirements, the ground team designs, edits, and modifies the content and internal logical relationships of all tasks, sub-tasks, and sub-events in the satellite mission, and uploads them to the satellite for storage and execution. The structure of a sub-event includes the sub-event start condition, the sub-event content, and the sub-event end flag; The sub-event start condition is a remote control command, a time node, or the end marker of another sub-event; the sub-event end marker is an internal marker or a telemetry marker; the sub-event content includes a trigger condition, a criterion, a judgment period, execution / output content, and a stop state, wherein the trigger condition is triggered by a combination of one or more conditions, including remote control commands, time nodes, or changes in telemetry parameters; wherein the criterion is a combination of one or more criteria, including time nodes or changes in telemetry parameters; wherein the judgment period refers to the time or number of judgments after the criteria are met, and can be modified; wherein the execution / output content is any combination of one or more programmable commands output or changes in telemetry parameters or flags; wherein the stop state is the state of stopping the current sub-event, which is not stopped by default, and can be modified. The step of classifying and storing the content of tasks and subtasks, the output content of sub-events, and the internal logical relationships between subtasks in the on-board storage space includes: dividing the on-board storage space to implement data classification and storage; the divided storage space includes a file configuration and index area, a task event storage area, a data area, and a program area; the file configuration and index area stores the configuration information of the on-board storage space and the index information of subtasks; the program area stores the timing schedule and internal logical relationships of subtasks in each task; the data area mainly stores the output content of sub-events; the task event storage area is divided into two parts: a pre-storage area and a reconstruction area; the pre-storage area stores multiple pre-configured subtasks on the ground for combined configuration; the reconstruction area stores subtasks newly configured and uploaded by the ground for on-orbit use; the subtasks in the reconstruction area and the subtasks in the pre-storage area can be reconfigured and combined into new tasks for on-orbit use; The step of executing the corresponding satellite mission according to the content and internal logical relationship of the mission, sub-mission, and sub-event includes: according to the timing and internal logical relationship of the sub-missions in each mission stored in the program area, and according to the index information of the sub-missions stored in the file configuration and index area, calling and executing the sub-missions in the mission event storage area, and retrieving the data required for executing the sub-missions from the data area. The steps for ground control to design, edit, modify, and upload the content and internal logical relationships of all tasks, sub-tasks, and sub-events in the satellite mission to the satellite for storage and execution, based on on-orbit usage requirements, include: when it is necessary to adjust the mission output content, only the ground needs to modify the annotations of the data area content; when it is necessary to change the mission flow or reconstruct the mission, only the annotations of the sub-tasks in the mission event storage area need to be modified or new sub-tasks need to be uploaded.

2. The configurable general satellite mission management method according to claim 1, characterized in that, The structure of the subtask includes a subtask start condition, subtask content, and subtask end flag. The subtask start condition is a remote control command, a time node, or another subtask end flag. The subtask content is composed of multiple sub-events. Subtasks are divided into two main categories: serial subtasks and parallel subtasks. Serial subtasks are executed in series by a single thread, while parallel subtasks are executed in parallel by multiple threads. The subtask end flag is an internal flag or a telemetry flag, which is set after all sub-events have been executed.

3. The configurable general satellite mission management method according to claim 1, characterized in that, The subtask structure also includes a stop state, allowing the execution of the relevant subtask to be stopped via ground remote control commands.

4. The configurable general satellite mission management method according to claim 1, characterized in that, The task structure includes a task start condition, task content, and task end flag. The task start condition is remote triggering. The task content is composed of multiple subtasks. During task execution, multiple subtasks are executed serially, while regular subtasks are executed in parallel. The task end flag is an internal flag or a telemetry flag. The task end flag is set after all subtasks have been executed.

5. A configurable universal satellite mission management device, characterized in that, include: The file management module includes a file configuration and index area, a task event storage area, a data area, and a program area. The file configuration and index area stores configuration information for on-board storage space and index information for subtasks. The program area stores the timing schedule and internal logical relationships of subtasks within each task. The data area mainly stores the output content of sub-events. The task event storage area is divided into a pre-storage area and a reconstruction area. The pre-storage area stores multiple pre-configured subtasks for ground use, which can be combined for configuration. The reconstruction area stores subtasks newly configured and uploaded by the ground for on-orbit use. Subtasks in the reconstruction area and subtasks in the pre-storage area can be reconfigured and combined into new tasks for on-orbit use. The judgment and execution module is used to call and execute subtasks in the task event storage area according to the timing and internal logical relationship of subtasks in each task stored in the program area, based on the file configuration and the index information of subtasks stored in the index area, and to retrieve the data required for executing subtasks from the data area.

6. The configurable universal satellite mission management device according to claim 5, characterized in that, The file management module allows modification of annotations in each area, including: modifying annotations in the data area when adjusting task output; and modifying annotations or adding new subtasks to the task event storage area when changing the task flow or refactoring the task.

Images