Task scheduling and management and control method for aerospace satellite application industry

Abstract

The invention discloses a spaceflight satellite application industry task scheduling and management and control method. The method comprises the following steps of performing visual modeling on a data processing flow of a high-resolution satellite; according to the data processing flow after high-resolution satellite modeling, a new satellite data processing flow model can be dynamically published online; and completing various business logics defined by the process work according to the process model in cooperation with the activities in the process. On the basis of a unified modeling language, an open-source and continuously-updated spaceflight satellite task scheduling algorithm library and a test set are created, the compatibility problem of different types of satellite processing task scheduling models is solved, and the method is suitable for more spaceflight satellite task scheduling problems with universal significance.

Description

Technical Field

[0001] The present invention belongs to the technical field of satellite applications, and particularly relates to a method for task scheduling and control in the aerospace satellite application industry. Background Art

[0002] To adapt to large-scale and complex aerospace satellite applications, the task scheduling technology of aerospace satellites that integrates modern operations research, computational science, and knowledge in related fields plays a crucial role.

[0003] By sorting out relevant models and algorithms for task scheduling and analyzing their characteristics and development trends, it is found that most of them focus on satellite task scheduling models or algorithms for a certain type of aerospace satellite (such as remote sensing satellites) or a certain application scenario (such as autonomous collaboration). There are few discussions from the global perspective of the aerospace technology application field on the common characteristics and differences of different types of satellite task scheduling models, and the applicability and coding characteristics of different scheduling algorithms are not analyzed. In the future, aerospace satellite task scheduling models must meet the characteristics of complexity and networking, and scheduling algorithms also need to meet the optimization requirements of large-scale and rapid response. This requires relevant practitioners to have a profound understanding and proficient application of various satellite task scheduling models and algorithms, and get rid of the traditional thinking of "problem - model - algorithm" tight coupling. Summary of the Invention

[0004] The purpose of the present invention is to provide a method for task scheduling and control in the aerospace satellite application industry. Based on the unified modeling language, the present invention creates an open-source and continuously updated aerospace satellite task scheduling algorithm library and test set to solve the compatibility problem of different types of satellite processing task scheduling models, and is applicable to more aerospace satellite task scheduling problems with general significance.

[0005] To achieve the above purpose, the technical solutions adopted by the present invention are as follows:

[0006] A method for task scheduling and control in the aerospace satellite application industry includes the following steps:

[0007] S1, visually model the data processing process of high-resolution satellites;

[0008] S2, online dynamically publish a new satellite data processing process model according to the data processing process of high-resolution satellites after modeling;

[0009] S3, according to the process model, cooperate with the activities within the process to complete various business logics defined by the process work.

[0010] Preferably, the specific steps in S3 are as follows:

[0011] S301, trigger the normal flow operation of the process instance activity node through manual operation and external interfaces;

[0012] S302. The mission management platform provides a Kafka interface for the startup process to create a task instance.

[0013] S303. Through the created task instance, the mission management platform automatically matches the task orchestration process and starts the regular production process and the standard product ordering process according to the task orchestration process.

[0014] Preferably, in S303, the specific steps of the task orchestration process include:

[0015] A1. The mission planning subsystem starts the task orchestration process, formulates a collection plan, and orchestrates data instructions to be sent to the satellite TT&C center for instruction execution.

[0016] A2. After the instruction injection of the satellite TT&C center is completed, it gives a task feedback to the mission planning subsystem.

[0017] A3. After receiving the task feedback from the satellite TT&C center, the mission planning subsystem sends a processing plan to the mission management platform.

[0018] A4. The mission management platform sends the received plan to the ground station and waits for task execution.

[0019] A5. The ground station transmits the received raw data to the mission management platform for data archiving.

[0020] A6. The mission management platform feeds back the situation of receiving the processing plan to the mission planning subsystem.

[0021] A7. The mission planning subsystem formulates a tracking plan, sends it to the mission management platform, and completes the task orchestration process.

[0022] Preferably, in S303, the specific steps of the regular production process include:

[0023] B1. The mission management platform calls the data preprocessing program provided by the data entry subsystem, enables the single-channel preprocessing method, and feeds back the processing result.

[0024] B2. The mission management platform calls the data management subsystem to start the on-board data archiving program.

[0025] B3. The mission management platform calls the data sorting program, scene division program, and level 0 generation program provided by the data entry subsystem, and feeds back the processing result.

[0026] B4. The mission management platform calls the data management subsystem to start the level 0 archiving program.

[0027] B5. The mission management platform calls the high-precision attitude determination program provided by the data processing subsystem to perform attitude determination and data update.

[0028] B6. The mission management platform calls the data management subsystem to start the attitude determination result data archiving and level 0 update archiving procedures;

[0029] B7. The mission management platform calls the level 1 product production program provided by the data processing subsystem to perform the level 1 product production task and feedback the processing result;

[0030] B8. The mission management platform calls the data management subsystem to start the level 1 data archiving and level 1 update procedures.

[0031] Preferably, in S303, the specific steps of the standard product ordering process are as follows:

[0032] C1. The user issues a product order requirement through the distribution service subsystem;

[0033] C2. The distribution service subsystem queries through the data management subsystem whether the order has been produced. If it has not been produced, it starts the unproduced order process and applies to the mission management platform for an order task; if it has been produced, it starts the produced order process, calls the data management subsystem to extract product data, and feedbacks to the user.

[0034] Preferably, in C2, the specific steps for the distribution service subsystem to apply to the mission management platform for an order task are as follows:

[0035] C2101. The mission management platform applies to the data management subsystem for the application product number of the required L0-level product and requests feedback;

[0036] C2102. The mission management platform performs production scheduling according to the application feedback and sends a production scheduling instruction to the data processing subsystem;

[0037] C2103. The data processing subsystem performs product production and gives production feedback to the mission management platform after completion;

[0038] C2104. After receiving the production feedback, the mission management platform sends a product data archiving request to the data management subsystem and receives an archiving feedback message;

[0039] C2105. The mission management platform updates the product data and the metadata status to the distribution service subsystem and receives update feedback;

[0040] C2106. The mission management platform calls the data management subsystem to perform data upload and order information upload.

[0041] Preferably, in C2, the specific steps for the distribution service subsystem to call the data management subsystem to extract product data and feedback to the user are as follows:

[0042] C2201. The data management subsystem completes the extraction and preparation of the order products and uploads them to the distribution service subsystem to complete the product upload;

[0043] In C2201, the distribution service subsystem completes the order and feeds back to the user, and at the same time calls the data management subsystem to complete the data upload feedback.

[0044] In C2201, the data management subsystem calls the management platform to complete the order feedback.

[0045] The beneficial effects of the present invention are as follows: The present invention adopts a unified modeling language, making the task scheduling and control algorithm no longer limited to a specific aerospace application scenario, but applicable to more aerospace satellite task scheduling problems of general significance. Based on the unified modeling language, an open-source and continuously updated aerospace satellite task scheduling and control algorithm library is built, which helps to create a development environment for relevant scholars and business personnel across the country to jointly research and share. At the same time, to test the algorithm performance and promote healthy competition, an aerospace satellite task scheduling standard test set with functions such as algorithm testing, teaching, and new case release is created. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 It is a flowchart of the method of the present invention.

[0047] Figure 2 It is a flowchart of the task choreography process.

[0048] Figure 3 It is a flowchart of the conventional production process.

[0049] Figure 4 It is a flowchart of the standard product ordering process. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0050] To make the objectives, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention.

[0051] A method for task scheduling and control in the aerospace satellite application industry adopts a unified modeling language.

[0052] Java is used as the backend development language, and the SpringMVC and SpringBoot frameworks are used. The operation of the system depends on the Java 1.8 runtime environment. The front end uses the VUE framework as the development framework, and the front-end code will ultimately be compiled into html + css + js. Any browser that supports html5, such as Firefox and Chrome, can be used to access this software. This software uses MySQL and PostgreSQL for long-term data storage and Redis for cached data storage. For some unstructured data or large amounts of data, the file system is used for storage.

[0053] Based on the task sequencing model and resource allocation model, using a reasonable spacecraft task scheduling model and unified modeling language, as well as targeted genetic algorithm improvement measures, when the genetic algorithm is used to solve the spacecraft task scheduling problem, the genetic algorithm can better complete the representation of solutions and problem solving, without losing high-quality solutions, and improve the algorithm iteration and search efficiency.

[0054] The key elements of the genetic algorithm in task scheduling usually include population initialization, fitness function, selection, crossover, mutation and termination conditions. In particular, chromosome encoding, fitness calculation, and genetic operations are combined with the existing spacecraft task scheduling model to form a task scheduling and control method for the aerospace satellite application industry. A task scheduling and control method for the aerospace satellite application industry follows the following principles:

[0055] 1. Chromosome encoding logic

[0056] 1.1 Encoding structure

[0057] Double-chain encoding design:

[0058] Task sequence chain: A permutation sequence representing the task execution order. Each gene unit corresponds to the index of a task ID, and it is necessary to ensure no repetition and cover all tasks.

[0059] Resource allocation chain: A sequence of the same length as the task sequence chain. Each gene unit represents the index of the resource ID allocated to the corresponding task.

[0060] Time implicit encoding: The actual start time is not directly encoded, but dynamically decoded and calculated through resource allocation constraints.

[0061] 1.2 Encoding constraints

[0062] Hard constraints: The task sequence chain must be a complete permutation (all tasks appear and only appear once), and the index values of the resource allocation chain must be within the available resource range.

[0063] Soft constraints: High-priority tasks tend to be in the front position in the sequence chain, and resource allocation needs to match the effective time window of the task.

[0064] 2. Fitness function design

[0065] 2.1 Evaluation dimensions

[0066] Core indicators:

[0067] (1) Task priority score: ∑(priority weights of completed tasks), reflecting the completion degree of high-value tasks.

[0068] (2) Time penalty term:

[0069] Timeout penalty: the cumulative difference between the task completion time and the deadline.

[0070] Window offset penalty: the deviation between the actual start time of the task and the start time of the effective window.

[0071] (3) Resource utilization rate: the ratio of the effective usage duration of the resource to the total available duration.

[0072] 2.2. Weight assignment

[0073] Dynamic weight strategy:

[0074] During peak business hours: the weight coefficient of the time penalty term is increased by 30%.

[0075] In resource-constrained scenarios: the weight of resource utilization is increased to 1.5 times.

[0076] In priority-sensitive scenarios: the weight of the task priority score is doubled.

[0077] 3. Genetic operation logic

[0078] 3.1. Selection operation

[0079] Tournament selection:

[0080] (1) Randomly select 5% of the individuals from the population to form a candidate pool.

[0081] (2) Select the top 10% of the individuals with the highest fitness in the pool to enter the mating pool.

[0082] (3) Retain the best individual in each generation (elitist retention) to prevent the loss of excellent genes.

[0083] 3.2. Crossover operation

[0084] Hierarchical crossover strategy:

[0085] Task sequence chain: Use the OX (Order Crossover) order crossover method to retain the task segment order of the parent.

[0086] Resource allocation chain: Use the two-point crossover method to exchange the resource allocation intervals of the parent.

[0087] Conflict handling:

[0088] Detect and repair conflicts for duplicate task indices.

[0089] Automatically replace invalid resource allocations with the nearest available resources.

[0090] 3.3. Mutation operation

[0091] Directed mutation mechanism:

[0092] (1) Task sequence mutation:

[0093] Swap mutation: Randomly swap the positions of two tasks (probability 0.15).

[0094] Reverse mutation: Randomly select a segment and reverse its order (probability 0.05).

[0095] (2) Resource allocation mutation:

[0096] Neighborhood mutation: Select adjacent resources from the same type of resource pool (probability 0.2).

[0097] Random mutation: Completely randomly select new resources (probability 0.1).

[0098] 4. Handling time window constraints

[0099] 4.1 Dynamic decoding rules

[0100] Resource timeline tracking:

[0101] (1) Maintain the last available timestamp for each resource.

[0102] (2) The actual start time of the task = max(task effective window start time, resource last available time).

[0103] (3) The end time of the task = actual start time + task duration.

[0104] 4.2 Handling invalid solutions

[0105] (1) Early elimination mechanism:

[0106] If the task end time > min(task effective window end time, resource available end time), then directly mark it as an infeasible solution.

[0107] (2) Repair strategy:

[0108] When the time window is out of bounds, automatically backtrack and adjust the previous task allocation.

[0109] When resource conflicts occur, trigger local rescheduling: Search for swappable tasks in the task sequence after the current position.

[0110] 5. Algorithm optimization strategies

[0111] 5.1 Memoization acceleration: Establish a chromosome hash library to cache the fitness values of evaluated chromosomes and avoid repeated calculations.

[0112] 5.2 Parallel computing: Use multi-threaded sharding to calculate the fitness of the population, and each thread processes 20% of the chromosomes.

[0113] 5.3 Adaptive parameters

[0114] Dynamically adjust according to the convergence of the evolutionary generation:

[0115] When convergence stagnates: the mutation probability is increased from 0.1 to 0.25.

[0116] During the rapid evolution stage: the crossover probability is increased from 0.7 to 0.9.

[0117] 6. Business integration logic

[0118] 6.1 Input-output mapping

[0119] Input adaptation layer:

[0120] (1) Convert the task data of the business system into a standard task object (including important resources, priority, duration).

[0121] (2) Abstract physical resources (servers, personnel, equipment) into allocable resource objects.

[0122] 6.2 Real-time processing

[0123] Incremental evolution mechanism:

[0124] (1) When a new task arrives dynamically, insert a new gene segment based on the existing optimal solution.

[0125] (2) Trigger local re-optimization for the affected task subsequence.

[0126] 6.3 Multi-objective balance

[0127] Pareto front screening:

[0128] (1) Optimize three objectives simultaneously: task completion value, total delay time, resource usage cost.

[0129] (2) Use the NSGA-II algorithm to maintain the non-dominated solution set.

[0130] 7. Typical exception handling

[0131] 7.1 Deadlock scenario

[0132] Detection mechanism: Trigger an alarm when the optimal solution has not improved for 20 consecutive generations.

[0133] Solution:

[0134] (1) Inject random new individuals to refresh the population diversity.

[0135] (2) Temporarily relax the time window constraint for exploration.

[0136] 7.2 Resource overload

[0137] Elastic processing:

[0138] (1) Automatically split long tasks into multiple subtasks.

[0139] (2) Enable virtual shadow resources for tentative allocation.

[0140] A set of data processing algorithms for high-resolution series satellites, satellite orbit calculation algorithms, imaging data processing algorithms, and various satellite command test algorithm clusters. Through these algorithms, a task scheduling and control method for the aerospace satellite application industry is formed. As Figure 1 shown, a task scheduling and control method for the aerospace satellite application industry includes the following steps:

[0141] S1, visually model the data processing process of high-resolution satellites.

[0142] High-resolution satellites include Gaofen-1 satellite, Gaofen-2 satellite, Gaofen-4 satellite, etc. The data processing process of high-resolution satellites can be visually modeled according to the working mode of the high-resolution satellite payload, and multiple data processing processes can correspond to each type of satellite.

[0143] S2, online dynamically publish the data processing process model of new satellites according to the data processing process of high-resolution satellites after modeling.

[0144] S3, according to the process model, cooperate with the activities within the process to complete various business logics defined by the process work.

[0145] S301, according to the process model, trigger the normal transfer operation of the process instance activity node through manual operation and external interfaces.

[0146] When the execution of the activity task is abnormal, personalized rollback operations can be processed.

[0147] S302, the task management platform provides a kafka interface for starting the process to create a task instance.

[0148] The task management platform provides a kafka interface for starting the process. After the data transmission module completes the transmission of the original data, the consumption business subsystem receives the kafka message and starts the process. After the consumption business subsystem completes the data verification, it passes the received parameters to the regular production startup application of the task management module in an asynchronous mode, reads the task execution plan and the original task data, and simultaneously reads the process template information such as regular production and standard product ordering from the database, thereby creating a task instance.

[0149] S303, through the created task instance, the task management platform automatically matches the task orchestration process and starts the regular production process and the standard product ordering process according to the task orchestration process.

[0150] In the conventional production process and standard product ordering process, each sub-process calls the interface of the data processing subsystem (PGS) to execute data production tasks.

[0151] (1) Task scheduling process

[0152] The task scheduling process is used to send instructions to the satellite and send a reception plan to the ground station. The ground station receives the data transmitted by the satellite according to the reception plan and starts the conventional production process and standard product ordering process of satellite data to produce data according to different business scenarios.

[0153] Such as Figure 2 shown: The specific steps of the task scheduling process include:

[0154] A1, The task planning subsystem (TSSS) starts the task scheduling process, formulates a collection plan, and arranges data instructions to be sent to the satellite measurement and control center (XSCC) for instruction execution.

[0155] A2, After the instruction upload of the satellite measurement and control center (XSCC) is completed, it gives a task feedback to the task planning subsystem (TSSS).

[0156] A3, After receiving the task feedback from the satellite measurement and control center, the task planning subsystem (TSSS) sends a processing plan to the mission management platform (TMP).

[0157] A4, The mission management platform (TMP) sends the reception plan to the ground station (RS) and waits for task execution.

[0158] A5, The ground station (RS) transmits the received raw data to the mission management platform (TMP) for data archiving.

[0159] A6, The mission management platform (TMP) gives a feedback on the reception of the processing plan to the task planning subsystem (TSSS).

[0160] A7, After receiving the feedback on the reception of the processing plan from the mission management platform (TMP), the task planning subsystem (TSSS) formulates a tracking plan and sends it to the mission management platform (TMP) to complete the task scheduling process.

[0161] (2) Conventional production process

[0162] The conventional production process is used to process the raw data into level 0 data and submit it for archiving.

[0163] Such as Figure 3 shown: The specific steps of the conventional production process are as follows:

[0164] B1, The mission management platform (TMP) calls the data preprocessing program provided by the data entry subsystem (DIS), enables the single-channel preprocessing mode and gives a processing result feedback.

[0165] B2. The Mission Management Platform (TMP) calls the Data Management Subsystem (DAIMS) to start the on-orbit data archiving program.

[0166] B3. The Mission Management Platform (TMP) calls the data sorting program, the scene division program, and the level 0 generation program provided by the Data Input Subsystem (DIS), and feeds back the processing results.

[0167] B301. The Mission Management Platform (TMP) determines the payload type, calls the data sorting program provided by the Data Input Subsystem (DIS) to complete data decompression and data sorting, and feeds back the processing results.

[0168] B302. The Mission Management Platform (TMP) calls the scene division program provided by the Data Input Subsystem (DIS). Each call executes the data sorting task and feeds back the processing results.

[0169] B303. The Mission Management Platform (TMP) calls the level 0 generation program provided by the Data Input Subsystem (DIS). Each call executes the level 0 product production task and feeds back the processing results.

[0170] B4. The Mission Management Platform (TMP) calls the Data Management Subsystem (DAIMS) to start the level 0 archiving program.

[0171] B5. The Mission Management Platform (TMP) calls the high-precision attitude determination program provided by the Data Processing Subsystem (PGS) to perform attitude determination and data update, and complete attitude and orbit processing.

[0172] B6. The Mission Management Platform (TMP) calls the Data Management Subsystem (DAIMS) to start the attitude determination result data archiving and level 0 update archiving programs.

[0173] Start the attitude determination result data archiving program to complete attitude and orbit archiving.

[0174] B7. The Mission Management Platform (TMP) calls the level 1 product production program provided by the Data Processing Subsystem (PGS) to perform the level 1 product production task and feeds back the processing results.

[0175] B8. The Mission Management Platform (TMP) calls the Data Management Subsystem (DAIMS) to start the level 1 data archiving and level 1 update programs.

[0176] (3) Standard Product Ordering Process

[0177] The standard product ordering process refers to automatically and batch-producing the required products according to user needs. Different payloads will produce different products. The solid-line part in the following figure is the existing production and ordering process, and the dashed-line part is the unproduced ordering process.

[0178] As Figure 4 shown: The specific standard product ordering process is as follows:

[0179] C1. The user issues a product order requirement through the Distribution Service Sub - system (DSS).

[0180] C2. The Distribution Service Sub - system (DSS) queries through the Data Management Sub - system (DAIMS) whether the order has been produced. If not, it starts the unproduced order process, and the Distribution Service Sub - system (DSS) applies to the Task Management Platform for an order task. If it has been produced, it starts the produced order process, and the Distribution Service Sub - system (DSS) calls the Data Management Sub - system (DAIMS) to extract product data and feedback to the user.

[0181] The specific steps for the Distribution Service Sub - system (DSS) to apply to the Task Management Platform for an order task are as follows:

[0182] C2101. The Task Management Platform (TMP) applies to the Data Management Sub - system (DAIMS) for the application product number of the required L0 - level product and requests feedback.

[0183] C2102. The Task Management Platform (TMP) performs production scheduling according to the application feedback and sends a production scheduling instruction to the Data Processing Sub - system (PGS).

[0184] C2103. The Data Processing Sub - system (PGS) produces the product and gives a production feedback to the Task Management Platform after completion.

[0185] Product production includes the production of L2 - level products of EMI and AHSI.

[0186] C2104. After receiving the production feedback, the Task Management Platform (TMP) sends a product data archiving request to the Data Management Sub - system (DAIMS) and receives an archiving feedback message.

[0187] C2105. The Task Management Platform (TMP) updates the product data and the metadata status to the Distribution Service Sub - system (DSS) and receives an update feedback.

[0188] C2106. The Task Management Platform (TMP) calls the Data Management Sub - system (DAIMS) to upload data and order information.

[0189] The specific steps for the Distribution Service Sub - system (DSS) to call the Data Management Sub - system (DAIMS) to extract product data and feedback to the user are as follows:

[0190] C2201. The Data Management Sub - system (DAIMS) completes the extraction and preparation of order products and uploads them to the Distribution Service Sub - system (DSS) to complete product upload.

[0191] C2201, The Distribution Service Sub-System (DSS) completes the order and feeds back to the user, and at the same time calls the Data Management Sub-System (DAIMS) to complete the data upload feedback.

[0192] C2201, The Data Management Sub-System (DAIMS) calls the Task Management Platform (TMP) to complete the order feedback.

Claims

1. A method for task scheduling and control in the aerospace satellite application industry, characterized in that It includes the following steps: S1, visually model the data processing process of high-resolution satellites; S2, online dynamically publish the data processing process model of new satellites according to the data processing process after modeling of high-resolution satellites; S3, according to the process model, cooperate with the activities within the process to complete various business logics defined by the process work.

2. The method for task scheduling and control in the aerospace satellite application industry according to claim 1, wherein The specific steps in S3 are: S301, trigger the normal transfer operation of the process instance activity node through manual operation and external interfaces; S302, the management platform provides a kafka interface to start the process and create a task instance; S303, through the created task instance, the management platform automatically matches the task scheduling process and starts the regular production process and the standard product ordering process according to the task scheduling process.

3. The method for task scheduling and control in the aerospace satellite application industry according to claim 2, characterized in that, In S303, the specific steps of the task scheduling process include: A1, the task planning subsystem starts the task scheduling process, formulates a collection plan, and arranges data instructions to be sent to the satellite TT&C center for instruction execution; A2, after the satellite TT&C center completes the instruction upload, it gives a task feedback to the task planning subsystem; A3, after receiving the task feedback from the satellite TT&C center, the task planning subsystem sends a processing plan to the management platform; A4, the management platform sends the received plan to the ground station for task execution; A5, the ground station transmits the received raw data to the management platform for data archiving; A6, the management platform gives the feedback on the received processing plan situation to the task planning subsystem; A7, the task planning subsystem formulates a tracking plan, sends it to the management platform, and completes the task scheduling process.

4. The method for task scheduling and control in the aerospace satellite application industry according to claim 2, characterized in that, In S303, the specific steps of the regular production process include: B1, the management platform calls the data preprocessing program provided by the data entry subsystem, enables the single-channel preprocessing method and gives the processing result feedback; B2, the management platform calls the satellite operation data archiving program of the data management subsystem to start; B3, the management platform calls the data sorting program, scene division program, and level 0 generation program provided by the data entry subsystem and gives the processing result feedback; B4, the management platform calls the level 0 archiving program of the data management subsystem to start; B5, the management platform calls the high-precision attitude determination program provided by the data processing subsystem for attitude determination and data update; B6, the management platform calls the attitude determination result data archiving and level 0 update archiving program of the data management subsystem to start; B7, the management platform calls the level 1 product production program provided by the data processing subsystem to perform the level 1 product production task and gives the processing result feedback; B8, the management platform calls the level 1 data archiving and level 1 update program of the data management subsystem to start.

5. The task scheduling and control method for the aerospace satellite application industry according to claim 2, characterized in that In S303, the specific steps of the standard product ordering process are: C1, the user issues a product ordering order requirement through the distribution service subsystem; C2, the distribution service subsystem queries through the data management subsystem whether the order has been produced. If it has not been produced, it starts the unproduced ordering process and applies to the management platform for an order task; if it has been produced, it starts the produced ordering process, calls the data management subsystem to extract product data, and gives feedback to the user.

6. The method for mission scheduling and control in the aerospace satellite application industry according to claim 5, wherein In C2, the specific steps for the distribution service subsystem to apply to the management platform for an order task are as follows: C2101. The management platform applies to the data management subsystem for the application product number of the required L0-level product and requests feedback. C2102. The management platform performs production scheduling based on the application feedback and sends a production scheduling instruction to the data processing subsystem. C2103. The data processing subsystem produces the product and provides production feedback to the management platform after completion. C2104. After receiving the production feedback, the management platform sends a product data archiving request to the data management subsystem and receives an archiving feedback message. C2105. The management platform updates the product data and the metadata status to the distribution service subsystem and receives update feedback. C2106. The management platform calls the data management subsystem to upload data and order information.

7. The method for task scheduling and control in the aerospace satellite application industry according to claim 5, characterized in that In C2, the specific steps for the distribution service subsystem to call the data management subsystem to extract product data and feedback to the user are as follows: C2201. The data management subsystem completes the extraction and preparation of the ordered products and uploads them to the distribution service subsystem to complete the product upload. C2201. The distribution service subsystem completes the order and feedbacks it to the user, and at the same time calls the data management subsystem to complete the data upload feedback. C2201. The data management subsystem calls the management platform to complete the order feedback.

Images