Flight control task planning method and system based on execution items and execution scripts
By constructing flight control task planning methods with execution items and execution scripts, the problem that traditional flight control task planning methods cannot adapt to the needs of changeable tasks is solved, efficient resource management and rapid processing are achieved, and automatic planning and emergency planning are supported.
Patent Information
- Application Number
- CN202510426317.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-07
- Publication Date
- 2025-07-11
AI Technical Summary
Traditional flight control task planning methods cannot adapt to changing task needs, have fixed resources and few branches, and require frequent manual adjustments, which cannot meet the characteristics of rapidly changing tasks.
Using the flight control task planning method based on execution items and execution scripts, multiple preset planning execution items are constructed, a set of target planning execution items are generated, and an execution script is generated based on the association relationship, and executed in the preset order to generate planning results.
It improves the efficiency of flight control mission planning, provides a high-level resource management structure, reduces task function coupling, realizes functional composition reuse, and supports one-click automatic planning and emergency heavy planning.
Smart Images
Figure CN120295282A_ABST
Abstract
Description
Background Art
[0002] The main task of flight control mission planning is to collect multi-party mission requirements, generate executable instruction-level and operation-level plans after hierarchical planning. Traditional flight control missions have a single status, fixed conditional constraints, few branches and traversable ones, fixed TT&C resources. Planning requires writing configuration files for all branches according to requirements, generating corresponding execution plans with one-key planning for each branch, and making decisions based on the mission status for use. However, with the change and development of flight control missions, new mission characteristics such as more mission requirements, more working condition branches, frequent changes in measurement station resources, increased frequency of emergency replanning, and the need for manual intervention and adjustment have become increasingly obvious. Traditional flight control mission planning can no longer meet the mission requirements.
[0003] Therefore, it is urgent to provide a technical solution to solve the above problems. Summary of the Invention
[0004] To solve the above technical problems, the present invention provides a flight control mission planning method and system based on execution items and execution scripts.
[0005] In the first aspect, the present invention provides a flight control mission planning method based on execution items and execution scripts. The technical solution of this method is as follows:
[0006] Construct a plurality of preset planning execution items for flight control mission planning, and generate a set of target planning execution items corresponding to each stage of each subtask in the to-be-planned mission; wherein, each set of target planning execution items respectively contains a corresponding number of preset planning execution items selected from all preset planning execution items;
[0007] Based on the association relationships between the planning execution items in each set of target planning execution items, respectively generate a target planning execution script corresponding to each set of target planning execution items, and execute each target planning execution script according to the first preset order between each subtask in the to-be-planned mission and the second preset order between each stage in the subtask, so as to generate the planning result of the to-be-planned mission.
[0008] The beneficial effects of a flight control mission planning method based on execution items and execution scripts of the present invention are as follows:
[0009] The method of the present invention can solve the design problems of software resources and task management in flight control mission planning, provide reuse of high-level resource management structures for flight control mission planning, provide customized functional components for fast processing of different functions, reduce task function coupling, realize reuse of function components, and thus improve the efficiency of flight control mission planning.
[0010] On the basis of the above solution, a flight control mission planning method based on execution items and execution scripts of the present invention can also be improved as follows.
[0011] In an alternative manner, when the task to be planned is a monthly planning task, all subtasks in the task to be planned include: a monthly rough planning task and weekly planning tasks corresponding to each week respectively.
[0012] In an alternative manner, the phases corresponding to the monthly rough planning task include: an initialization workspace and confirmation phase, a planning preprocessing and confirmation phase, and a monthly event strategy generation and confirmation phase; the phases corresponding to each weekly planning task all include: an initialization workspace and confirmation phase, a planning preprocessing and confirmation phase, a monthly event strategy generation and confirmation phase, an instruction-level planning and confirmation phase for the clearly defined flight control events, a requirements aggregation and full-set flight control event modeling and confirmation phase, an instruction-level planning and confirmation phase for the full-set flight control events, and a job item planning and confirmation phase.
[0013] In an alternative manner, the association relationships between the various planning execution items include at least one of: a sequential association relationship, a cyclic association relationship, and a branch association relationship.
[0014] In an alternative manner, before the steps of respectively executing each target planning execution script, it further includes:
[0015] Executing the global script of the task to be planned.
[0016] In a second aspect, the present invention provides a flight control task planning system based on execution items and execution scripts, and the technical solution of this system is as follows:
[0017] It includes: a generation module and a planning module;
[0018] The generation module is used to: construct a plurality of preset planning execution items for flight control task planning, and generate a set of target planning execution items for each phase corresponding to each subtask in the task to be planned; wherein, each set of target planning execution items respectively contains a corresponding number of preset planning execution items selected from all the preset planning execution items.
[0019] The planning module is used to: based on the association relationships between the various planning execution items in each set of target planning execution items, respectively generate a target planning execution script corresponding to each set of target planning execution items, and execute each target planning execution script in accordance with the first preset order between each subtask in the task to be planned and the second preset order between each phase in the subtask, so as to generate the planning result of the task to be planned.
[0020] The beneficial effects of a flight control task planning system based on execution items and execution scripts of the present invention are as follows:
[0021] The system of the present invention can solve the design problems of software resources and task management in flight control mission planning, provide the reuse of high-level resource management structures for flight control mission planning, provide customized functional components for fast processing of different functions, reduce task function coupling, achieve the reuse of functional components, and thus improve the efficiency of flight control mission planning.
[0022] Based on the above solution, a flight control mission planning system based on execution items and execution scripts of the present invention can also be improved as follows.
[0023] In an optional manner, when the to-be-planned task is a monthly planning task, all subtasks in the to-be-planned task include: a monthly rough planning task and weekly corresponding weekly planning tasks.
[0024] In an optional manner, the phases corresponding to the monthly rough planning task include: an initialization workspace and confirmation phase, a planning preprocessing and confirmation phase, and a monthly event strategy generation and confirmation phase; the phases corresponding to each weekly planning task all include: an initialization workspace and confirmation phase, a planning preprocessing and confirmation phase, a monthly event strategy generation and confirmation phase, an instruction-level planning and confirmation phase for clearly defined flight control events, a requirements summary and full-set flight control event modeling and confirmation phase, an instruction-level planning and confirmation phase for the full-set flight control events, and a job item planning and confirmation phase.
[0025] In a third aspect, a technical solution of an electronic device of the present invention is as follows:
[0026] It includes a memory, a processor, and a program stored on the memory and running on the processor. When the processor executes the program, it implements the steps of the flight control mission planning method based on execution items and execution scripts of the present invention.
[0027] In a fourth aspect, a technical solution of a computer-readable storage medium provided by the present invention is as follows:
[0028] Instructions are stored in the computer-readable storage medium. When the computer-readable storage medium reads the instructions, it causes the computer-readable storage medium to execute the steps of the flight control mission planning method based on execution items and execution scripts of the present invention.
[0029] The above description is only an overview of the technical solution of the present invention. In order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the specification. And in order to make the above and other purposes, features, and advantages of the present invention more obvious and understandable, the specific embodiments of the present invention are specifically exemplified below. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] The accompanying drawings are only used to illustrate the embodiments and are not considered to limit the present invention. Moreover, throughout the drawings, the same reference numerals are used to represent the same components. In the drawings:
[0031] Figure 1 is a schematic flowchart of an embodiment of a flight control task planning method based on execution items and execution scripts according to the present invention;
[0032] Figure 2 is a schematic flowchart of the specific stages of the planning task;
[0033] Figure 3 is a schematic structural diagram of an embodiment of a flight control task planning system based on execution items and execution scripts according to the present invention;
[0034] Figure 4 is a schematic structural diagram of an embodiment of an electronic device according to the present invention. Detailed implementation manners
[0035] Hereinafter, exemplary embodiments of the present invention will be described in more detail with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein.
[0036] Figure 1 shows a schematic flowchart of an embodiment of a flight control task planning method based on execution items and execution scripts provided by the present invention. The flight control task planning method based on execution items and execution scripts can be executed by an electronic device such as a terminal device or a server. Among them, the terminal device can be any fixed or mobile terminal such as a user equipment (UE), a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc. The server can be a single server or a server cluster composed of multiple servers. Any electronic device can implement the flight control task planning method based on execution items and execution scripts by a processor calling computer-readable instructions stored in a memory. As Figure 1 shown, it includes the following steps:
[0037] S1. Construct a plurality of preset planning execution items for flight control task planning, and generate a set of target planning execution items for each stage corresponding to each subtask in the to-be-planned task.
[0038] Among them, the planning execution item is the smallest processing unit obtained by disassembling each processing function in the entire flight control mission planning. Based on the operation framework of the planning execution item, the requirements of each task can be allocated to a combination of multiple execution items to complete. The planning execution script consists of planning execution items and can implement functions such as sequential execution, loop processing, and branch processing of the planning execution items.
[0039] Among them, the number of preset planning execution items is multiple, covering all functions in the flight control mission planning. Each task to be planned corresponds to multiple subtasks, each subtask corresponds to multiple stages, and each stage corresponds to a set of target planning execution items. Each set of target planning execution items respectively contains the corresponding number of preset planning execution items selected from all preset planning execution items. Specifically, when the task to be planned is a monthly planning task, all subtasks in the task to be planned include: monthly rough planning task and weekly planning tasks corresponding to each week. The stages corresponding to the monthly rough planning task include: initialization of the work space and confirmation stage, planning preprocessing and confirmation stage, and monthly event strategy generation and confirmation stage; the stages corresponding to each weekly planning task all include: initialization of the work space and confirmation stage, planning preprocessing and confirmation stage, monthly event strategy generation and confirmation stage, command-level planning and confirmation stage for the flight control events that have been clarified, requirement summary and full-set flight control event modeling and confirmation stage, command-level planning and confirmation stage for the full-set flight control events, and job item planning and confirmation stage.
[0040] S2. Based on the association relationships among the planning execution items in each set of target planning execution items, respectively generate the target planning execution scripts corresponding to each set of target planning execution items, and execute each target planning execution script according to the first preset order among each subtask in the task to be planned and the second preset order among each stage in the subtask, so as to generate the planning result of the task to be planned.
[0041] Among them, the association relationships between the planning execution items include at least one of sequential association relationship, loop association relationship, and branch association relationship, which can be specifically determined according to the configuration parameters of the planning execution items (such as the specific content and objectives of the planning execution items). The first preset order and the second preset order can be determined according to the actual situation. When the task to be planned is a monthly planning task, the first preset order is: first execute the multiple target planning execution scripts corresponding to the monthly rough planning task, and then execute the multiple target planning execution scripts corresponding to each weekly planning task simultaneously or sequentially. In the monthly rough planning task, the second preset order is: sequentially execute the target planning execution scripts corresponding to the initialization workspace and confirmation phase, the planning preprocessing and confirmation phase, and the monthly event strategy generation and confirmation phase. In each weekly planning task, the second preset order is: sequentially execute the target planning execution scripts corresponding to the initialization workspace and confirmation phase, the planning preprocessing and confirmation phase, the monthly event strategy generation and confirmation phase, the command-level planning and confirmation phase of the defined flight control events, the requirement summary and full-set flight control event modeling and confirmation phase, the command-level planning and confirmation phase of the full-set flight control events, and the job item planning and confirmation phase.
[0042] It should be noted that the technical solution of this embodiment provides a running framework design based on execution items to solve the deficiencies of the current flight control task planning. In the process of generating the job-level plan, it is necessary to solve flexible configuration problems such as multi-objectives, specific instruction deletion, movement, renaming, optional injection arrangement, and optional fault handling. Therefore, various possible selections are set as rules and uniformly managed by the rule library. When generating a job-level plan once and a certain rule needs to be adopted, a rule instance is created and related parameters are defined, such as target identification, start circle number, specified time, etc. The design of this kind of planning and stack in the job-level plan generation function is realized on the client software through the software design rule template and rule object management, and this design idea can be extended to the overall running framework of the entire task planning system, and there are the following improvements:
[0043] ① Expand the rule into an execution item, and each execution item will be processed as an independent thread or a Run interface processing object on a specific running thread on the background server. ② For the input parameters of the rule, after expanding into an execution item, the definition of the input file or output file needs to be added. For example, for the execution item of station forecast preprocessing, it is necessary to specify the station forecast of a specific target as the input, which requires the support of "planning data management based on files, directories, and packages". ③ Rule instances are executed sequentially in the stack, while execution items may need to implement loop or branch processes, so the design of execution scripts is further proposed. ④ The rule type is currently limited to the relevant content of job-level planning. When designing the execution item, it runs through all processing links of the entire task planning system. Therefore, as the functions of this system are continuously improved, the types of execution items will also be continuously expanded. At the same time, this design is also beneficial to the division of labor during system development and the upgrade and improvement of the system. ⑤ The rule corresponds to the program classes and objects completed in software design, but the execution item is directly configured to correspond to the Java Run interface class, and through configuration modification, the expansion and upgrade of the execution item can be dynamically realized, solving the problem of a large number of new requirements that may be faced in flight control task planning. ⑥ Based on the execution item, an extensible plug-in design can also be realized. Each execution item can be managed by a script as a plug-in, which can also replace the design of embedding plug-ins in some complex execution items. The planning job integration support design based on execution scripts runs the underlying layer into a mature scripting language. In the planning system, due to unified Java language coding, the underlying layer is converted into a Groovy dynamic scripting language based on the JVM virtual machine to run.
[0044] The technical solution of this embodiment supports the integration of planning and job. Specifically: ① The planning system cooperates with the job system. When arranging the plan, the next or subsequent branch planning items are used as the content of the job item. When the job is triggered, the job system sends a planning application to the planning system in turn, and the planning system automatically completes the planning calculations of multiple branches. ② The planning system cooperates with the automatic monitoring system. After a fault handling application is sent, the planning system quickly completes the relevant planning calculations for emergency planning. Each fault handling corresponds to a planning execution script. ③ The automatic planning calculation requires the execution script to have: automatically select the configuration package and script package, and automatically create the planning package, stage package, and running package.
[0045] In an optional manner, before the step of executing each target planning execution script respectively, it further includes:
[0046] Execute the global script of the to-be-planned task.
[0047] Among them, the content corresponding to the global script includes:
[0048] 1) Processing flow. In the global workspace outside all planning packages, there are multiple globally script files with unique names. Their function is to create planning packages, bind configuration packages and script packages, and start the first script. The globally script files should be uniformly designed and completed before the task, and new scripts can be added or existing script content can be edited at any time during the task to adapt to new planning requirements. For example, for the emergency response plan for XXX failures, starting the "Automatic Disposal Global Script for XXX Failures" externally can automatically complete relevant planning preprocessing, instruction-level planning, and planning result publishing. In addition, after the planning package is created, when the planning package is opened on the page, the script package inside the planning package should be loaded first, and all the scripts in the package should be displayed on the page and can be started manually at any time. There are clear prompts on the page for the script operation logs, and the log files generated by the scripts can also be viewed on the page at any time. For the execution of scripts at each stage, regardless of whether intermediate results are generated, a stage package directory needs to be created. When the script is executed, if the stage package already exists, an alarm should be prompted. Under each planning package, each stage package can only appear once, and all calculation results are saved in the stage package. The planning results that need to be published externally within the planning package are saved in the externally published directory under the planning package and are copied into it by the implementation item of the execution item.
[0049] 2) Related planning execution items: ① Creation of the planning package; ② Copying of the configuration package and the script package; ③ Starting of the script package (the script package contains the corresponding planning execution items); ④ Publishing of the planning results (optional).
[0050] 3) Planning execution script.
[0051] ① Planning execution item: Creation of the planning package.
[0052] a) Create a planning package directory named "Automatic Disposal of XXX Failures_XXX_20240501_20240507_timestamp" based on the task code, task objective, start time, end time, and timestamp.
[0053] b) Return the name of the newly created planning package directory.
[0054] ② Planning execution item: Copying of the configuration package and the script package.
[0055] a) Copy the configuration package to the specified planning package directory.
[0056] b) Copy the script package to the specified planning package directory.
[0057] ③ Planning execution item: Starting of the script package (each script package has a unique configuration file indicating the first target planning execution script and the target planning execution scripts corresponding to each stage).
[0058] a) Read the configuration file under the script package and run the first target planning execution script. Usually, the target planning execution scripts in multiple stages will start the first target planning execution script.
[0059] b) Associate each target planning execution script with each stage page (optional).
[0060] ④ Planning execution item: Release of planning results (optional).
[0061] a) If it is an automatically running script, all planning results can be automatically released.
[0062] It should be noted that when a new monthly planning task is received, multiple planning tasks are started, including the monthly rough planning task and the weekly planning tasks corresponding to each week (from the first week to the fourth week). Each planning needs to first create a planning package, select the configuration package and the script package, and then conduct the planning in stages. For hour-level planning such as fault handling, a complete planning package still needs to be created, but it only needs to be completed within one stage. The division of the stage package is based on whether manual confirmation is required. As long as there is a link that needs to be confirmed by the participants after being released, a stage needs to be divided. For hour-level planning such as fault handling, generally, there are few types of generated plans, and only need to be confirmed uniformly after generation, so only one stage is required throughout the process. For a complex planning, the whole process involves the tracking plan of the measurement and control network, the application of measurement stations, the collection and release of resources, the collection and summary release of requirements, the generation of planning results for various instruction items, and the generation of planning results for various operation items. There are multiple links that need to be confirmed by the participants, so it needs to be divided into multiple stages, and each stage has clear input and output results. At the same time, in each stage, from the perspective of software implementation, the same context is also used as much as possible to improve the processing efficiency. As Figure 2 shown, the specific stages of the planning task include: Stage A: Initialization of the working space and confirmation stage; Stage B: Planning preprocessing and confirmation stage; Stage C: Generation and confirmation stage of monthly event strategies; Stage D: Instruction-level planning and confirmation stage for clearly defined flight control events; Stage E: Requirement summary and full-set flight control event modeling and confirmation stage; Stage F: Instruction-level planning and confirmation stage for the full-set flight control events; Stage G: Operation item planning and confirmation stage. Specifically, taking a spacecraft as an example:
[0063] Stage A: The content corresponding to the initialization of the working space and confirmation stage includes:
[0064] 1) Processing flow: ① In the global receiving cache or other directories, find all resource release files, monthly event plans, forecasts, and control parameter files related to the current planning task target according to the rules, copy them to the receiving cache in the planning package directory, and divide them into subdirectories according to the type. ② Explanation of the global receiving cache: The global receiving cache directory needs to be maintained daily and cleaned continuously. Some job scheduling can be used to complete the automatic maintenance of the global receiving cache. In addition, some important planning results (such as sorting out tracking and control conditions) also need to be received by the global receiving cache for subsequent planning processing. ③ Give summary statistics information and prompt the user for manual confirmation. ④ In the manual confirmation stage, files can be added, deleted, or uploaded from the local. Finally, ensure that all files related to this planning are placed in the receiving cache of the planning package.
[0065] 2) Related planning execution items: ① Copy files; ② Summarize and statistically analyze the receiving cache.
[0066] 3) Planning execution script.
[0067] ① Planning execution item: Copy files. Multiple instances can be arranged for different task targets.
[0068] a) Filter the files to be processed in the source file directory according to the file update time or the timestamp in the file name (if any).
[0069] b) Implement copying all types of resource release files, monthly event plans, forecasts, and control strategies from the source directory to the target directory.
[0070] ② Planning execution item: Summarize and statistically analyze the receiving cache.
[0071] a) Generate a summary statistics result document, count the total number of forecasts and control strategies for all targets, file names, etc., and provide them for the user to view and confirm. Intermediate results or final results such as result documents should be placed in the directory of this stage package.
[0072] Contents corresponding to Phase B: Planning preprocessing and confirmation phase include:
[0073] 1) Processing flow: ① Parse all files in the receiving cache, rename the file names according to the file content, copy them to the read-only input directory, and divide them into directories according to the type. ② Conduct tracking and control condition sorting and output the sorted results. ③ Convert the monthly event plan into a monthly event strategy. ④ The user makes a manual confirmation. If the monthly strategy is unreasonable, it can be modified manually.
[0074] 2) Related planning execution items: ① Copy and rename files; ② Sort out tracking and control conditions; ③ Convert the monthly event plan into a monthly event strategy.
[0075] 3) Planning execution script.
[0076] ① Planning execution item: Copy and rename files, and multiple instances can be arranged for different task objectives.
[0077] a) Analyze the file content, rename it according to the naming rule, and copy it to the target directory.
[0078] b) Implement copying all types of prediction and control strategies from the source directory to the target directory after renaming.
[0079] ② Planning execution item: Sort out measurement and control conditions and process multiple targets simultaneously.
[0080] a) Analyze and sort out all feature points and various continuous arc segments to generate a document of the sorted measurement and control conditions.
[0081] ③ Planning execution item: Convert the monthly event plan to a monthly event strategy, and multiple instances can be divided according to the number of files in the monthly event plan.
[0082] a) The monthly event plan here is not the original monthly event plan provided by the planning center, but a modified monthly event plan with expandable time after manual revision.
[0083] b) According to the monthly event plan, combine the monthly event attributes in the configuration package to generate a monthly event strategy, and fill in all constraint attributes according to the monthly event configuration.
[0084] c) Manually confirm, and the content of each attribute in the monthly event strategy can be manually supplemented or corrected.
[0085] Phase C: The content corresponding to the monthly event strategy generation and confirmation phase includes:
[0086] 1) Processing flow: ① Read the monthly event strategy in the read-only input directory, calculate the earliest start and latest end times according to the attributes of each item in the strategy, and expand the confirmed flight control events according to the monthly event parameters. ② Generate a configuration file for the use of the measurement and control network according to the monthly event strategy and the sorted measurement and control conditions. ③ Generate a tracking plan file for the measurement and control network according to the configuration file for the use of the measurement and control network. ④ Generate a station application file according to the configuration file for the use of the measurement and control network. ⑤ The monthly event strategy is displayed on the Gantt chart, and the rationality is manually confirmed. If it is unreasonable, first, the monthly event strategy can be modified (equivalent to modifying the result of Phase B), and Phase C can be re-performed; second, the monthly event can be directly dragged to the appropriate position on the graph.
[0087] 2) Related planning execution items: ① Calculate the time attributes of the monthly event strategy; ② Generate a configuration for the use of the measurement and control network; ③ Generate a tracking plan and a station application for the measurement and control network.
[0088] 3) Planning execution script.
[0089] ① Planning execution item: Calculate the time attributes of the monthly event strategy, which can be divided into multiple instances according to the number of files in the monthly event plan.
[0090] a) Calculate the time attributes of each monthly event according to the attributes of the monthly event strategy other than the time arrangement.
[0091] ② Planning execution item: Generate the configuration for the TT&C network usage, and process multiple targets simultaneously.
[0092] a) According to the TT&C mode requirements of the reference monthly events in the re-planned monthly event strategy after the previous execution item, the TT&C network usage strategy of the measurement station can be determined.
[0093] ③ Planning execution item: Generate the TT&C network tracking plan and the measurement station application, and process multiple targets simultaneously.
[0094] a) Generate the TT&C network tracking plan according to the TT&C network usage configuration.
[0095] b) Generate the measurement station application according to the TT&C network tracking plan.
[0096] Phase D: The content corresponding to the instruction-level planning and confirmation phase of the flight control events that have been clarified includes:
[0097] 1) Processing flow: ① The monthly event strategy generated in Phase C already includes the available time range for each monthly event (for timely arranged monthly events, the time range also needs to be determined). However, among these monthly events, some monthly events can be directly disassembled into clarified flight control events according to the configuration, and some need to wait for the requirements to be determined before clarifying how the monthly events are disassembled into which flight control events. ② The disassemblable and already clarified flight control events are the sub-nodes of each monthly event instance in the monthly event strategy. The default time constraint is generated by the software in Phase C and can be modified by manual participation before the start of Phase D. ③ According to the attributes of each clarified flight control event in the monthly event strategy, calculate the earliest start time and the latest end time of each flight control event, and expand the flight control events to the instruction level to form a detailed plan. ④ The monthly event strategy is displayed on the Gantt chart, and the rationality is manually confirmed. If it is unreasonable, first, the attributes of the flight control events in the monthly event strategy can be modified (equivalent to modifying the results of Phase B, but this is allowed), and Phase C can be re-performed; second, the flight control events can be directly dragged to the appropriate position on the chart.
[0098] 2) Related planning execution items: ① Calculate the flight control event time attributes of the monthly event strategy; ② Expand the detailed plan.
[0099] 3) Planning execution script.
[0100] ① Planning execution item: Calculate the flight control event time attributes of the monthly event strategy. It can be divided into multiple instances according to the number of files in the monthly event plan.
[0101] a) Calculate the schedule for each flight control event based on the attributes of each flight control event in the monthly event strategy other than the schedule.
[0102] ② Planning execution items: Expand the detailed plan and handle multiple objectives simultaneously.
[0103] a) Read in the flight control event configuration, instruction sequence configuration, and instruction configuration.
[0104] b) Generate a detailed instruction-level plan based on the monthly event strategy.
[0105] Phase E: The content corresponding to the requirement aggregation and full set of flight control event modeling and confirmation phase includes:
[0106] 1) Processing flow: ① Publish the monthly event strategy, TT&C network tracking plan, and planned available resources to each support center; ② Based on the monthly events in the monthly event strategy that have not been disassembled, and in combination with the Gantt chart display, the support center submits the corresponding flight control event requirements, and a continuously updated status is maintained on the Gantt chart until the requirements of each center are submitted. ③ Collect all flight control requirements, create new flight control events according to the requirement content, and automatically arrange internal instructions. ④ Conduct requirement modeling for the full set of flight control events. ⑤ Improve the monthly event strategy document.
[0107] 2) Related planning execution items: ① Create flight control events according to requirements; ② Conduct requirement modeling for flight control events; ③ Generate a complete monthly event strategy.
[0108] 3) Planning execution script.
[0109] ① Planning execution item: Create flight control events according to requirements.
[0110] a) Read all the flight control event requirements collected, create new flight control events, and for new instructions, new instruction configurations are required.
[0111] b) Create a new flight control event configuration file, which together with the original flight control event configuration constitutes all available flight control event configurations.
[0112] c) Add a new monthly event configuration file to replace the monthly event with the same name in the original monthly event configuration.
[0113] ② Planning execution item: Conduct requirement modeling for flight control events.
[0114] a) Read in the instruction configuration, flight control event configuration, new instruction configuration, and flight control event configuration file.
[0115] b) Complete requirement modeling and create an AD model.
[0116] c) Conduct model verification and give summary information.
[0117] ③Planning execution items: Generate a complete monthly event strategy.
[0118] a) Based on the original monthly event strategy, the previously unsplit monthly events are split, and the time attributes of the split flight control events are filled.
[0119] Phase F: The instruction-level planning and confirmation phase of the entire flight control event includes:
[0120] 1) Processing flow: ① Combine the flight control event instruction planning data of phase D with the flight control event modeling data of phase E. ② Combine the Gantt chart display to maintain a continuously updated state, collect all flight control requirements, create new flight control events based on the requirements, and automatically arrange internal instructions. ③ Plan instructions for the entire set of flight control events.
[0121] 2) Related planning execution items: ① Generate detailed instruction plans; ② Categorize and output various instruction plans
[0122] 3) Plan and execute the script.
[0123] ①Planning execution items: generating detailed instruction plans.
[0124] a) When there is no conflict in the instruction-level expansion planning results, a detailed instruction plan is generated.
[0125] ②Planning execution items: Classify and output various instruction plans.
[0126] a) Output configuration according to instruction items and output various instruction plans according to categories.
[0127] Phase G: The corresponding contents of the work item planning and confirmation phase include:
[0128] 1) Processing flow: ① Read various instruction-level planning results and generate detailed job item planning results. ② Use execution item combinations to adjust planning results as required. ③ Classify and output collaborative work programs. ④ Classify and output to generate job scheduling plans. ⑤ Classify and output to generate automatic monitoring collaborative work programs.
[0129] 2) Related planning execution items: ① Generate detailed work item planning results; ② Categorize and output work item planning results; ③ Various execution items used to adjust planning results.
[0130] The technical solution of this embodiment designs an automatic planning architecture based on execution items and execution scripts, supporting functions such as manual phased planning, manual intervention adjustment, and partial replanning; designs the execution item as the smallest processing unit for function execution, and various requirements can be assigned to a combination of multiple execution items based on the operation framework of the execution item to complete; designs an execution script based on the operation of the execution item, which can implement functions such as 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-key automatic planning and automatic replanning. The technical solution of this embodiment can solve the design problems of flight control task planning software resources and task management, provide reuse of high-level resource management structures for flight control task planning, provide customized function components for fast processing of different functions, reduce task function coupling, and achieve reuse of function components, thereby improving the efficiency of flight control task planning.
[0131] Figure 3 Fig. 4 shows a schematic structural diagram of an embodiment of a flight control task planning system 200 provided by the present invention based on execution items and execution scripts. As Figure 3 shown, the system 200 includes: a generation module 210 and a planning module 220;
[0132] The generation module 210 is used to: construct a plurality of preset planning execution items for flight control task planning, and generate a set of target planning execution items corresponding to each stage of each subtask in the to-be-planned task; wherein, each set of target planning execution items respectively includes a corresponding number of preset planning execution items selected from all the preset planning execution items;
[0133] The planning module 220 is used to: based on the association relationship between the planning execution items in each set of target planning execution items, respectively generate a target planning execution script corresponding to each set of target planning execution items, and execute each target planning execution script according to the first preset order between each subtask in the to-be-planned task and the second preset order between each stage in the subtask, so as to generate a planning result of the to-be-planned task.
[0134] In an optional manner, when the to-be-planned task is a monthly planning task, all the subtasks in the to-be-planned task include: a monthly rough planning task and weekly planning tasks corresponding to each week respectively.
[0135] In an alternative manner, the stages corresponding to the monthly rough planning task include: an initialization workspace and confirmation stage, a planning preprocessing and confirmation stage, and a monthly event strategy generation and confirmation stage; the stages corresponding to each weekly planning task include: an initialization workspace and confirmation stage, a planning preprocessing and confirmation stage, a monthly event strategy generation and confirmation stage, an instruction-level planning and confirmation stage for the clarified flight control events, a requirements summary and full-set flight control event modeling and confirmation stage, an instruction-level planning and confirmation stage for the full-set flight control events, and a job item planning and confirmation stage.
[0136] In an alternative manner, the association relationships between the planning execution items include at least one of: a sequential association relationship, a cyclic association relationship, and a branching association relationship.
[0137] In an alternative manner, the planning module 220 is further configured to:
[0138] Execute the global script of the to-be-planned task.
[0139] It should be noted that the beneficial effects of the flight control task planning system based on execution items and execution scripts provided in the above embodiments are the same as those of the flight control task planning method based on execution items and execution scripts, and will not be elaborated here. In addition, when the system provided in the above embodiments implements its functions, only the division of the above function modules is used for illustration. In practical applications, the above functions can be allocated to different function modules according to needs, that is, the system can be divided into different function modules according to the actual situation to complete all or part of the functions described above. In addition, the system and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments and will not be elaborated here.
[0140] Among them, the flight control task planning system based on execution items and execution scripts of the present invention can be a computer program (including program code) running in a computer device. For example, the flight control task planning system based on execution items and execution scripts of the present invention is an application software, which can be used to execute the corresponding steps in the flight control task planning method based on execution items and execution scripts of the present invention.
[0141] In some embodiments, the flight control task planning system based on execution items and execution scripts of the present invention can be implemented in a combination of software and hardware. As an example, the flight control task planning system based on execution items and execution scripts of the present invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the flight control task planning method based on execution items and execution scripts of the present invention. For example, the processor in the form of a hardware decoding processor can adopt one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field programmable gate arrays (FPGAs) or other electronic components.
[0142] Among them, the modules involved in the embodiments of the present invention can be implemented in software or in hardware. Among them, the name of the module does not constitute a limitation to the module itself in some cases.
[0143] An electronic device according to an embodiment of the present invention includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, it implements any one of the above-mentioned flight control task planning methods based on execution items and execution scripts. That is to say, an electronic device according to an embodiment of the present invention may include, but is not limited to: a processor and a memory; the memory is used to store a computer program; the processor is used to execute the flight control task planning method based on execution items and execution scripts shown in any embodiment of the present invention by calling the computer program.
[0144] In an alternative embodiment, an electronic device is provided, as Figure 4 shown, Figure 4 The electronic device 4000 shown includes: a processor 4001 and a memory 4003. Among them, the processor 4001 and the memory 4003 are connected, such as connected through a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, and the transceiver 4004 can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data, etc. It should be noted that in practical applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation to the embodiments of the present invention.
[0145] The processor 4001 can be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of the present invention. The processor 4001 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
[0146] The bus 4002 can include a path for transferring information between the above components. The bus 4002 can be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 4002 can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 4 only a thick line is used to represent the bus 4002 in the figure, but it does not mean that there is only one bus or one type of bus.
[0147] The memory 4003 can be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, or it can also be an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.
[0148] The memory 4003 is used to store the application program code (computer program) for implementing the solution of the present invention, and is controlled by the processor 4001 for execution. The processor 4001 is used to execute the application program code stored in the memory 4003 to implement the content shown in the foregoing method embodiments.
[0149] Among them, the electronic device may also be a terminal device, and the terminal device may be any terminal device that can install an application and access a web page through the application, including at least one of a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, a smart TV, and a smart vehicle-mounted device.
[0150] It should be noted that Figure 4 the electronic device shown is only an example and should not impose any limitation on the functions and usage scope of the embodiments of the present invention.
[0151] A computer-readable storage medium according to an embodiment of the present invention has a computer program stored thereon, and when the computer program is executed by a processor, the above-mentioned flight control task planning method based on an execution item and an execution script is implemented.
[0152] Optionally, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, etc.
[0153] In an exemplary embodiment, a computer program product or a computer program is further provided. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the above-mentioned flight control task planning method based on an execution item and an execution script.
[0154] Computer program code for performing the operations of the present invention may be written in one or more programming languages or combinations thereof. The above-mentioned programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (for example, by connecting through the Internet using an Internet service provider).
[0155] It should be understood that the flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code that contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system for performing the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.
[0156] The computer-readable storage medium provided by the embodiments of the present invention may be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
[0157] The above computer-readable storage medium stores one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments.
[0158] The above description is only a preferred embodiment of the present invention and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of disclosure involved in the present invention is not limited to the technical solutions formed by the specific combination of the above technical features, but also covers other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosure concept. For example, the technical solutions formed by mutually replacing the above features with the (but not limited to) technical features with similar functions disclosed in the present invention.
[0159] It should be noted that the terms "first", "second", etc. in the description and claims of this application are used to distinguish similar objects, and represent a limitation on a specific order or sequence. Under appropriate circumstances, the order of use of similar objects can be interchanged so that the embodiments of the present application described here can be implemented in an order other than the illustrated or described order.
[0160] Those skilled in the art know that the present invention can be implemented as a system, a method or a computer program product. Therefore, the present invention can be specifically implemented in the following forms, that is, it can be completely hardware, or completely software (including firmware, resident software, microcode, etc.), or a combination of hardware and software, which is generally referred to as "circuit", "module" or "system" in this article. In addition, in some embodiments, the present invention can also be implemented in the form of a computer program product in one or more computer-readable media, which contains computer-readable program code.
[0161] Although the embodiments of the present invention have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those of ordinary skill in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.
Claims
1. A flight control task planning method based on execution items and execution scripts, characterized in that, Including: Constructing a plurality of preset planning execution items for flight control task planning, and generating a set of target planning execution items for each stage corresponding to each subtask in the task to be planned; wherein, each set of target planning execution items respectively includes a corresponding number of preset planning execution items selected from all the preset planning execution items; Based on the association relationships among the planning execution items in each set of target planning execution items, respectively generating a target planning execution script corresponding to each set of target planning execution items, and executing each target planning execution script respectively according to a first preset order among each subtask in the task to be planned and a second preset order among each stage in the subtask, so as to generate a planning result of the task to be planned.
2. The flight control task planning method based on execution items and execution scripts according to claim 1, wherein When the task to be planned is a monthly planning task, all the subtasks in the task to be planned include: a monthly rough planning task and weekly planning tasks corresponding to each week respectively.
3. The flight control task planning method based on execution items and execution scripts according to claim 2, wherein The stages corresponding to the monthly rough planning task include: an initialization workspace and confirmation stage, a planning preprocessing and confirmation stage, and a monthly event strategy generation and confirmation stage; the stages corresponding to each weekly planning task all include: an initialization workspace and confirmation stage, a planning preprocessing and confirmation stage, a monthly event strategy generation and confirmation stage, an instruction-level planning and confirmation stage for the flight control events that have been clarified, a requirements summary and full-set flight control event modeling and confirmation stage, an instruction-level planning and confirmation stage for the full-set flight control events, and a job item planning and confirmation stage.
4. The flight control task planning method based on execution items and execution scripts according to any one of claims 1 to 3, characterized in that The association relationships among the planning execution items include at least one of: a sequential association relationship, a cyclic association relationship, and a branch association relationship.
5. The flight control task planning method based on execution items and execution scripts according to any one of claims 1 to 3, characterized in that Before the step of executing each target planning execution script respectively, it further includes: Executing the global script of the task to be planned.
6. A flight control task planning system based on execution items and execution scripts, characterized in that, Including: A generation module and a planning module; The generation module is used for: constructing a plurality of preset planning execution items for flight control task planning, and generating a set of target planning execution items for each stage corresponding to each subtask in the task to be planned; wherein, each set of target planning execution items respectively includes a corresponding number of preset planning execution items selected from all the preset planning execution items; The planning module is used for: based on the association relationships among the planning execution items in each set of target planning execution items, respectively generating a target planning execution script corresponding to each set of target planning execution items, and executing each target planning execution script respectively according to a first preset order among each subtask in the task to be planned and a second preset order among each stage in the subtask, so as to generate a planning result of the task to be planned.
7. The flight control task planning system based on execution items and execution scripts according to claim 6, wherein, When the task to be planned is a monthly planning task, all the subtasks in the task to be planned include: a monthly rough planning task and weekly planning tasks corresponding to each week respectively.
8. The flight control task planning system based on execution items and execution scripts according to claim 7, characterized in that, The phases corresponding to the monthly rough planning tasks include: initialization of the work space and confirmation phase, planning preprocessing and confirmation phase, and monthly event strategy generation and confirmation phase; the phases corresponding to each weekly planning task include: initialization of the work space and confirmation phase, planning preprocessing and confirmation phase, monthly event strategy generation and confirmation phase, command-level planning and confirmation phase for the flight control events that have been identified, requirement aggregation and full-set flight control event modeling and confirmation phase, command-level planning and confirmation phase for the full-set flight control events, and job item planning and confirmation phase.
9. An electronic device, characterized in that, The electronic device includes a processor, the processor is coupled to a memory, and at least one computer program is stored in the memory. The at least one computer program is loaded and executed by the processor so that the electronic device implements the flight control task planning method based on the execution item and the execution script according to any one of claims 1 to 5.
10. A computer-readable storage medium, characterized in that, At least one computer program is stored in the computer-readable storage medium. The at least one computer program is loaded and executed by a processor so that the computer-readable storage medium implements the flight control task planning method based on the execution item and the execution script according to any one of claims 1 to 5.