Bag structure spacecraft task planning system based on unified design

Abstract

The invention belongs to the technical field of spacecraft task planning, and particularly relates to a package structure spacecraft task planning system based on unified design, all related files in the spacecraft task planning system, including all input, output, configuration and intermediate result files related to planning, are definitely defined, naming rules are given, and all the files are named. The files which do not conform to the naming rule are invalid package files; according to the package structure spacecraft task planning system, on the basis of the design of planning data management of files, directories and packages, in task planning, global newest configuration directories, working directories, output caches, input caches and historical records are maintained all the time, configuration files related to planning processing are read from the configuration directories, and the configuration files are stored in the working directories. An intermediate processing result and a final result are stored in a working directory, and a configuration directory and the working directory are compressed and stored in a historical record directory after each time of planning, so that problems can be queried and positioned conveniently.

Description

Technical Field

[0001] The present invention belongs to the technical field of spacecraft mission planning, and in particular relates to a package structure spacecraft mission planning system based on a unified design. Background Art

[0002] As an important guarantee for human deep space exploration, spacecrafts involve a wide variety of complex on-orbit tasks and supporting materials during their operation. In order to ensure the long-term and stable on-orbit operation of spacecrafts, it is necessary to coordinate and plan the on-orbit tasks of spacecrafts within a certain period of time before the mission is carried out to ensure the smooth implementation of on-orbit tasks. However, the task planning of each stage of spacecraft work was done manually in the early days. The complete manual task planning cannot make full use of the resources of the spacecraft and ensure the safety of the spacecraft. With the increasing complexity of space missions, especially with the development of deep space exploration, formation flying, constellation technology, and space robot technology, its importance is increasing, and a variety of spacecraft mission planning system frameworks have emerged on the market. Therefore, there is an urgent need for a large-scale complex flight control mission planning system that can handle inter-system coordination, multiple target tasks, multiple stage planning, complex constraint input, dynamic instruction planning, collaborative work generation, and integrate openness, reusability, dynamicity, integration, and componentization.

[0003] In the actual mission planning project, due to the planning time span and planning time granularity of each layer of task planning, the specific execution time range of the task cannot be predicted in advance. It is necessary to calculate the executable time interval of the task by setting the time constraints between tasks. In addition, due to the constraint relationship between tasks, the tasks are not discrete, but are related to each other to form a task chain. It is necessary to realize the constraint detection and error feedback functions under complex coupling constraint conditions to make the obtained task plan more accurate. In addition to time constraints, the planned tasks of spacecraft also include many different types of resource constraints, such as astronaut resources, robotic arm resources, electric energy, etc., which also need to be considered and processed in the process of mission planning and constraint detection. For the above-mentioned complex time and resource constraints, the traditional method has a slow processing speed and a large search space, which is less applicable to spacecraft mission planning.

[0004] The spacecraft mission planning system is complex, involving multiple planning tasks, multiple spacecraft targets, different planning requirements, multiple planning stages, various complex input files, and planning business processing procedures. The system presents a development trend of openness, reusability, dynamism, integration, and componentization, which leads to an exponential increase in the difficulty of processing tasks at all levels and managing complex resources during the planning process, reducing the system's collaborative capabilities and directly affecting work efficiency. Therefore, how to establish a model to solve the design problems of mission planning software resources and task management, and provide high-level resource management structure reuse for mission planning, is one of the problems that need to be solved in spacecraft mission planning.

[0005] Spacecraft mission planning activities will trigger multiple mission function calls. When the system is initialized, the corresponding functions are executed according to the fixed business process. It is impossible to dynamically load or intervene in the tasks during the operation of the system, which makes the system lack dynamic scalability. Some business attributes of multiple tasks are seriously repeated and tightly coupled. When the business changes, they need to be modified one by one, which is prone to omissions and unmodifiable situations. Therefore, it is a key part of realizing spacecraft mission planning to quickly provide customized functional components for different functional processing, reduce task function coupling, and realize functional component reuse.

[0006] In the spacecraft mission planning system, there are multiple requirements, multiple planning stages, flexible configuration of multiple types of inputs, and multiple business operation units that need to be processed in an orderly manner according to rules. The key issue is how to reuse the orchestration rules in completed tasks and customize the work content for special parts to quickly form executable business processes. Therefore, how to integrate multiple business units to complete more complex planning business operations and quickly generate the correct task sequence is a key issue in spacecraft autonomous mission planning. Summary of the invention

[0007] 1. Technical issues to be resolved

[0008] The technical problem to be solved by the present invention is: how to provide a package structure spacecraft mission planning system based on a unified design.

[0009] (II) Technical solution

[0010] In order to solve the above technical problems, the present invention provides a spacecraft mission planning system with a package structure based on a unified design. All relevant files in the spacecraft mission planning system, including all planning-related input, output, configuration and intermediate result files, are clearly defined and given naming rules. Files that do not conform to the naming rules are invalid package files, thereby achieving:

[0011] (1) For any file in the planning and processing link, the file type, update time, flight target, and circle number range information of the file can be directly determined based on the file name;

[0012] (2) Any file generated during the planning process can be uniquely named and stored in the planning package according to the file type and content;

[0013] (3) Any file that needs to be processed in the planning and processing stage can be determined as a candidate file based on the target, file type and selection principle.

[0014] Among them, the spacecraft mission planning system also has clear processing requirements for directories based on file naming:

[0015] (1) Global receiving file cache directory;

[0016] (2) Global send file cache directory;

[0017] (3)Global configuration package collection directory;

[0018] (4)Global script package collection directory

[0019] (5)Global planning package collection directory.

[0020] The global planning package set directory contains all planning packages, and each planning package directory stores:

[0021] 1) Read-only input directory related to the planning package;

[0022] 2) Configuration packages related to the planning package;

[0023] 3) Script packages related to the planning package;

[0024] 4) All phase packages related to the planning package, each phase package contains multiple running packages;

[0025] 5) The receiving cache directory related to the planning package;

[0026] 6) The sending cache directory related to the planning package.

[0027] The spacecraft mission planning system has the following processing requirements for package management:

[0028] 1) Package type: configuration package, script package, template package, planning package, stage package;

[0029] 2) Each package needs to have a clear naming rule defined, and packages that do not comply with the naming rule are invalid packages;

[0030] 3) Each package needs to have clear package content when it is encrypted, compressed and packaged;

[0031] 4) Each package can be created and managed manually, and also supports automatic creation and management by executing scripts.

[0032] Among them, the planning data management method of files, directories and packages of the spacecraft mission planning system is the basis for realizing functions such as distributed collaboration, offline planning, and multi-user parallel planning.

[0033] Among them, the spacecraft mission planning system completes all types of file processing in a workspace where a planning package directory is located each time it plans on a monthly or weekly basis; the directory forms a closed set, including all configuration files required for re-planning, scripts, forecasts and strategies, all input files of requirements, and all planning result files, thereby realizing the needs of client planning and offline planning.

[0034] Among them, the spacecraft mission planning system can complete the planning processing of complex processes in stages or by content. The workspace related to each stage processing is the stage package, and the stage package directory is located under the directory of the corresponding planning package; the planning results of the previous stage can be used as the planning input of the next stage, and the planning processing of the next stage can be carried out simultaneously based on the same planning input, thereby realizing multi-user parallel planning.

[0035] Among them, the planning package and stage package of the spacecraft mission planning system can be compressed and packaged. When different strategies are used to generate multiple stage packages for the same stage, they can be provided for planning evaluation and verification, and the planning results can be scored and selected based on the indicator system, and then provided to the next stage as input.

[0036] Each time the spacecraft mission planning system receives a new monthly plan, it starts multiple plannings, including the rough plan for the current month and the weekly plans from the first to the fourth week. Each planning needs to first establish a planning package, select a configuration package and a script package, and then plan in stages. For hourly planning such as fault handling, a complete planning package still needs to be established, but it only needs to be completed in one stage.

[0037] The division of phase packages is based on whether manual confirmation is required. As long as there is a link that needs to be confirmed by the participants after release, a phase needs to be divided. For hourly planning such as fault handling, generally fewer types of plans are generated, and they only need to be confirmed after generation, so only one phase is required for the whole process.

[0038] For a complex planning, the whole process involves tracking plan of measurement and control network, application of ground-based system, resource collection and release, demand collection and summary release, generation of planning results of various instruction items, generation of planning results of various collaborative items, and multiple links to be confirmed by the participants. Therefore, it needs to be divided into multiple stages, each with clear input and output results. At the same time, in each stage, from the perspective of engineering practice, the same context is used to improve processing efficiency.

[0039] The working process of the spacecraft mission planning system is specifically decomposed as follows:

[0040] Phase A: Initialize workspace and confirm;

[0041] Phase B: planning preprocessing and confirmation;

[0042] Phase C: Monthly event strategy generation and confirmation;

[0043] Phase D: The command-level planning and confirmation of flight control events have been clarified;

[0044] Phase E: Requirements summary and full set of flight control event modeling and confirmation;

[0045] Phase F: Instruction-level planning and confirmation of all flight control events;

[0046] Phase G: Collaborative project planning and confirmation;

[0047] For simple planning, one phase can be used to automate the process;

[0048] Phase X: Automatic instruction-level planning.

[0049] (III) Beneficial effects

[0050] Compared with the prior art, the present invention provides a spacecraft mission planning system with a package structure based on a unified design. Based on the design of planning data management of files, directories and packages, the latest global configuration directory, working directory, output cache, input cache and historical records are always maintained in mission planning. The configuration files related to planning processing are read from the configuration directory, and the intermediate processing results and final results are saved in the working directory. After each planning, the configuration directory and the working directory are compressed and stored in the historical record directory, which is convenient for querying and locating problems.

[0051] The spacecraft mission planning system needs to further have functions such as distributed collaboration, offline planning, and multi-user parallel planning. Therefore, a package management method has been added to the file processing method of mission planning, and clear processing requirements have been put forward for file, directory, and package management.

[0052] Compared with the prior art, the technical solution proposed in the present invention adopts a unified package structure design, designs an automatic planning structure based on execution items and execution scripts, and supports manual phased planning and one-click automatic planning. The execution item is the smallest processing unit after each processing function is disassembled in the entire spacecraft mission planning system. The operation framework based on the execution item can assign various requirements to a combination of multiple execution items to complete. The execution script is composed of execution items, which can realize the functions of sequential execution, loop processing and branch processing of execution items. Each execution script can complete a complete planning process to support planning scenario requirements such as one-click automatic planning and automatic re-planning. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 It is the main flow chart of the technical solution of the present invention. DETAILED DESCRIPTION

[0054] In order to make the purpose, content, and advantages of the present invention more clear, the specific implementation methods of the present invention are further described in detail below in conjunction with the accompanying drawings and examples.

[0055] In order to solve the above technical problems, the present invention provides a spacecraft mission planning system with a package structure based on a unified design. All relevant files in the spacecraft mission planning system, including all planning-related input, output, configuration and intermediate result files, are clearly defined and given naming rules. Files that do not conform to the naming rules are invalid package files, thereby achieving:

[0056] (1) For any file in the planning and processing link, the file type, update time, flight target, and circle number range information of the file can be directly determined based on the file name;

[0057] (2) Any file generated during the planning process can be uniquely named and stored in the planning package according to the file type and content;

[0058] (3) Any file that needs to be processed in the planning and processing stage can be determined as a candidate file based on the target, file type and selection principle.

[0059] Among them, the spacecraft mission planning system also has clear processing requirements for directories based on file naming:

[0060] (1) Global receiving file cache directory;

[0061] (2) Global send file cache directory;

[0062] (3)Global configuration package collection directory;

[0063] (4)Global script package collection directory

[0064] (5)Global planning package collection directory.

[0065] The global planning package set directory contains all planning packages, and each planning package directory stores:

[0066] 1) Read-only input directory related to the planning package;

[0067] 2) Configuration packages related to the planning package;

[0068] 3) Script packages related to the planning package;

[0069] 4) All phase packages related to the planning package, each phase package contains multiple running packages;

[0070] 5) The receiving cache directory related to the planning package;

[0071] 6) The sending cache directory related to the planning package.

[0072] The spacecraft mission planning system has the following processing requirements for package management:

[0073] 1) Package type: configuration package, script package, template package, planning package, stage package;

[0074] 2) Each package needs to have a clear naming rule defined, and packages that do not comply with the naming rule are invalid packages;

[0075] 3) Each package needs to have clear package content when it is encrypted, compressed and packaged;

[0076] 4) Each package can be created and managed manually, and also supports automatic creation and management by executing scripts.

[0077] Among them, the planning data management method of files, directories and packages of the spacecraft mission planning system is the basis for realizing functions such as distributed collaboration, offline planning, and multi-user parallel planning.

[0078] Among them, the spacecraft mission planning system completes all types of file processing in a workspace where a planning package directory is located each time it plans on a monthly or weekly basis; the directory forms a closed set, including all configuration files required for re-planning, scripts, forecasts and strategies, all input files of requirements, and all planning result files, thereby realizing the needs of client planning and offline planning.

[0079] Among them, the spacecraft mission planning system can complete the planning processing of complex processes in stages or by content. The workspace related to each stage processing is the stage package, and the stage package directory is located under the directory of the corresponding planning package; the planning results of the previous stage can be used as the planning input of the next stage, and the planning processing of the next stage can be carried out simultaneously based on the same planning input, thereby realizing multi-user parallel planning.

[0080] Among them, the planning package and stage package of the spacecraft mission planning system can be compressed and packaged. When different strategies are used to generate multiple stage packages for the same stage, they can be provided for planning evaluation and verification, and the planning results can be scored and selected based on the indicator system, and then provided to the next stage as input.

[0081] Each time the spacecraft mission planning system receives a new monthly plan, it starts multiple plannings, including the rough plan for the current month and the weekly plans from the first to the fourth week. Each planning needs to first establish a planning package, select a configuration package and a script package, and then plan in stages. For hourly planning such as fault handling, a complete planning package still needs to be established, but it only needs to be completed in one stage.

[0082] The division of phase packages is based on whether manual confirmation is required. As long as there is a link that needs to be confirmed by the participants after release, a phase needs to be divided. For hourly planning such as fault handling, generally fewer types of plans are generated, and they only need to be confirmed after generation, so only one phase is required for the whole process.

[0083] For a complex planning, the whole process involves tracking plan of measurement and control network, application of ground-based system, resource collection and release, demand collection and summary release, generation of planning results of various instruction items, generation of planning results of various collaborative items, and multiple links to be confirmed by the participants. Therefore, it needs to be divided into multiple stages, each with clear input and output results. At the same time, in each stage, from the perspective of engineering practice, the same context is used to improve processing efficiency.

[0084] The working process of the spacecraft mission planning system is specifically decomposed as follows:

[0085] Phase A: Initialize workspace and confirm;

[0086] Phase B: planning preprocessing and confirmation;

[0087] Phase C: Monthly event strategy generation and confirmation;

[0088] Phase D: The command-level planning and confirmation of flight control events have been clarified;

[0089] Phase E: Requirements summary and full set of flight control event modeling and confirmation;

[0090] Phase F: Instruction-level planning and confirmation of all flight control events;

[0091] Phase G: Collaborative project planning and confirmation;

[0092] For simple planning, one phase can be used to automate the process;

[0093] Phase X: Automatic instruction-level planning.

[0094] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the technical principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A package structure spacecraft mission planning system based on unified design, characterized in that: All relevant files in the spacecraft mission planning system, including all planning-related input, output, configuration and intermediate result files, are clearly defined and given naming rules. Files that do not comply with the naming rules are invalid package files, thereby achieving: (1) For any file in the planning and processing link, the file type, update time, flight target, and circle number range information of the file can be directly determined based on the file name; (2) Any file generated during the planning process can be uniquely named and stored in the planning package according to the file type and content; (3) Any file that needs to be processed in the planning and processing stage can be determined as a candidate file based on the target, file type and selection principle.

2. The package structure spacecraft mission planning system based on unified design as claimed in claim 1, characterized in that: The spacecraft mission planning system also has clear processing requirements for directories based on file naming: (1) Global receiving file cache directory; (2) Global send file cache directory; (3)Global configuration package collection directory; (4)Global script package collection directory (5)Global planning package collection directory.

3. The package structure spacecraft mission planning system based on unified design as claimed in claim 2, characterized in that: The global planning package collection directory contains all planning packages, and each planning package directory stores: 1) Read-only input directory related to the planning package; 2) Configuration packages related to the planning package; 3) Script packages related to the planning package; 4) All phase packages related to the planning package, each phase package contains multiple running packages; 5) The receiving cache directory related to the planning package; 6) The sending cache directory related to the planning package.

4. The package structure spacecraft mission planning system based on unified design as claimed in claim 3, characterized in that: The spacecraft mission planning system has the following processing requirements for package management: 1) Package type: configuration package, script package, template package, planning package, stage package; 2) Each package needs to have a clear naming rule defined, and packages that do not comply with the naming rule are invalid packages; 3) Each package needs to have clear package content when it is encrypted, compressed and packaged; 4) Each package can be created and managed manually, and also supports automatic creation and management by executing scripts.

5. The package structure spacecraft mission planning system based on unified design as claimed in claim 4, characterized in that: The planning data management method of files, directories and packages of the spacecraft mission planning system is the basis for realizing functions such as distributed collaboration, offline planning, and multi-user parallel planning.

6. The package structure spacecraft mission planning system based on unified design as claimed in claim 5, characterized in that: The spacecraft mission planning system completes all types of file processing in a workspace where a planning package directory is located each time it plans on a monthly or weekly basis; the directory forms a closed set, including all configuration files required for re-planning, scripts, forecasts and strategies, all input files of requirements, and all planning result files, thereby meeting the needs of client planning and offline planning.

7. The package structure spacecraft mission planning system based on unified design as claimed in claim 6, characterized in that: The spacecraft mission planning system can process complex planning processes in stages or by content. The workspace related to each stage processing is the stage package, and the stage package directory is located under the directory of the corresponding planning package. The planning results of the previous stage can be used as the planning input of the next stage, and the planning processing of the next stage can be carried out synchronously based on the same planning input, thus realizing multi-user parallel planning.

8. The package structure spacecraft mission planning system based on unified design as claimed in claim 7, characterized in that: The planning package and phase package of the spacecraft mission planning system can be compressed and packaged. When multiple phase packages are generated for the same phase using different strategies, they can be provided for planning evaluation and verification, and the planning results can be scored and selected based on the indicator system, and then provided to the next phase as input.

9. The package structure spacecraft mission planning system based on unified design as claimed in claim 8, characterized in that: Each time the spacecraft mission planning system receives a new monthly plan, it starts multiple planning, including a rough plan for the current month and weekly plans from the first week to the fourth week; Each planning process requires first creating a planning package, selecting a configuration package and a script package, and then planning in stages; For hourly planning such as fault handling, a complete planning package still needs to be established, but it only needs to be completed in one phase; The division of phase packages is based on whether manual confirmation is required. As long as there is a link that needs to be confirmed by the participants after release, a phase needs to be divided. For hourly planning such as fault handling, generally fewer types of plans are generated, and they only need to be confirmed after generation, so only one phase is required for the whole process. For a complex planning, the whole process involves measurement and control network tracking plan, space-ground base application, resource collection and release, demand collection and summary release, generation of planning results of various instruction items, and generation of planning results of various collaborative items. There are multiple links to be confirmed by the participants, so it needs to be divided into multiple stages, each stage has clear input and output results; at the same time, in each stage, from the perspective of engineering practice, the same context is used to improve processing efficiency.

10. The package structure spacecraft mission planning system based on unified design as claimed in claim 9, characterized in that: The working process of the spacecraft mission planning system is specifically decomposed as follows: Phase A: Initialize workspace and confirm; Phase B: planning preprocessing and confirmation; Phase C: Monthly event strategy generation and confirmation; Phase D: The command-level planning and confirmation of flight control events have been clarified; Phase E: Requirements summary and full set of flight control event modeling and confirmation; Phase F: Instruction-level planning and confirmation of all flight control events; Phase G: Collaborative project planning and confirmation; For simple planning, one phase can be used to automate the process; Phase X: Automatic instruction-level planning.

Images