Swarm spaceflight launch task scheduling system and method

Abstract

The invention relates to the technical field of spaceflight launch, and provides a swarm-type spaceflight launch task scheduling system and method, and the system comprises a task planning subsystem, a planning evaluation subsystem, a task resource data pool, and a task implementation process control subsystem. The task planning subsystem is connected with the task resource data pool and is used for generating a bee colony type launching draft; the planning evaluation subsystem is connected with the task planning subsystem, and is used for evaluating the bee colony type launch draft and writing the bee colony type launch draft and an evaluation result into the task resource data pool; and the task implementation process control subsystem is connected with the task resource data pool, and is used for examining and approving the bee colony type launch draft and the evaluation result, and converting the bee colony type launch draft into a launch scheme to be output. According to the scheme, a large number of satellites with different orbits can be launched in a short time for online automatic planning, and the problems of low launching efficiency, difficulty in scheme optimization, high error rate and the like of manual scheduling and planning of large-batch satellites are effectively solved.

Description

Technical Field

[0001] The present invention relates to the field of space launch technology, and in particular to a swarm-type space launch mission scheduling system and method. Background Art

[0002] With the continuous advancement of aerospace technology, more and more satellites are being sent into space. Multiple satellite launches (MSLs) refer to the process of sending two or more satellites or payloads into different orbits in a single rocket launch mission.

[0003] In specific scenarios, such as large-scale or large-scale disaster relief activities, high-density observation of hot spots, and enhanced satellite communications in a certain area during specific periods of time, there is a need to launch many satellites in different orbits in a short period of time.

[0004] At the same time, in the past three years (2022-2024), the number of human space launches has continued to maintain double-digit growth. With the increase in the number of space launches, the scheduling of space launches is particularly important. If the scheduling problem of space launches cannot be solved, the efficiency of large-scale satellite launches will be reduced, and errors will cause irreversible consequences.

[0005] Therefore, it is necessary to provide a swarm-type space launch mission scheduling system and method that can automatically plan the launch of a large number of satellites in different orbits in a short period of time online, and effectively solve the problems of low efficiency, difficult solution optimization and easy errors in manual scheduling and planning of large-scale satellite launches.

[0006] The above information disclosed in this Background section is only for enhancement of understanding of the background of the application and therefore it may contain information that does not form the prior art that is already known to a person of ordinary skill in the art. Summary of the Invention

[0007] The main purpose of the present invention is to overcome the problem of being unable to effectively schedule satellite launches in a short period of time, and to provide a swarm-type space launch mission scheduling system and method, which can launch a large number of satellites in different orbits in a short period of time for online automatic planning, and effectively solve the problems of low efficiency, difficult solution optimization and easy errors in manual scheduling and planning of large-scale satellite launches.

[0008] To achieve the above-mentioned purpose, the first aspect of the present invention provides a swarm-type space launch mission scheduling system, comprising: a mission planning subsystem, a planning evaluation subsystem, a mission resource data pool, and a mission implementation process control subsystem;

[0009] The mission planning subsystem is connected to the mission resource data pool to generate a swarm launch draft;

[0010] The planning and evaluation subsystem is connected to the mission planning subsystem and is used to evaluate the swarm launch draft and write the swarm launch draft and the evaluation results into the mission resource data pool;

[0011] The mission implementation process control subsystem is connected to the mission resource data pool, and is used to review and approve the swarm launch draft and evaluation results, and convert the swarm launch draft into a launch plan output.

[0012] The swarm type is to configure multiple launch sites around the assembly site, similar to a swarm of bees, and assign launch tasks to each launch site for launch.

[0013] As an example embodiment of the present invention, the task planning subsystem includes a shortest path planning module, a dynamic contribution calculation module, a shop scheduling module based on full task completion, a shop scheduling module based on task contribution, and a draft generation module;

[0014] The shortest path planning module is used to calculate the shortest path from the current process site to the next process site for each launch mission;

[0015] The dynamic contribution calculation module is used to calculate the contribution of each space launch mission completion;

[0016] The workshop scheduling module based on the completion of all tasks is used to schedule and sort all space launch tasks according to the shortest path;

[0017] The task contribution-based workshop scheduling module is used to schedule and sort all space launch tasks according to their contributions;

[0018] The draft generation module is used to generate a swarm launch draft. If the launch time can complete all tasks as scheduled, a swarm launch draft is generated according to the workshop scheduling module based on the completion of all tasks; if the launch time is not enough to complete all tasks, a swarm launch draft is generated according to the workshop scheduling module based on task contribution.

[0019] As an exemplary embodiment of the present invention, the swarm-type space launch mission scheduling system further includes a mission data management subsystem, a resource database, and a mission database;

[0020] The mission data management subsystem is connected to the resource database, the mission database and the mission resource data pool, and is used to manage the available resources and mission process data of swarm space launches.

[0021] As an example embodiment of the present invention, the swarm-type space launch mission scheduling system also includes a mission process demonstration / reproduction subsystem, which is connected to the mission resource data pool and the mission data management subsystem, and is used to use the data in the mission resource data pool to simulate and display the actual situation during mission implementation, and is also used to load historical mission data through the data management subsystem to reproduce the historical mission implementation process.

[0022] As an exemplary embodiment of the present invention, the swarm launch task scheduling system further includes a task status collection subsystem connected to the task resource data pool for collecting task status and updating data in the task resource data pool.

[0023] As an example embodiment of the present invention, the swarm-type space launch mission scheduling system further includes an exercise and training subsystem connected to the mission resource data pool, for using the mission resource data pool to drive full-system exercises and personnel training.

[0024] According to a second aspect of the present invention, a swarm-type space launch scheduling method is provided, which uses the swarm-type space launch task scheduling system, comprising the following steps:

[0025] The mission planning subsystem generates a swarm launch draft;

[0026] The planning and evaluation subsystem evaluates the swarm launch draft and writes the swarm launch draft and evaluation results into the mission resource data pool;

[0027] The mission implementation process control subsystem reviews the swarm launch draft and evaluation results, and converts the swarm launch draft into a launch plan output.

[0028] As an exemplary embodiment of the present invention, the mission planning subsystem generates a swarm launch draft including:

[0029] The shortest path planning module calculates the shortest path from the current process site to the next process site for each launch mission;

[0030] The dynamic contribution calculation module calculates the contribution of each space launch mission;

[0031] The workshop scheduling module based on the completion of all tasks will schedule and sort all space launch tasks according to the shortest path;

[0032] The workshop scheduling module based on task contribution schedules and sorts all space launch tasks according to their contribution;

[0033] The draft generation module generates a swarm launch draft. If the launch time can complete all tasks as scheduled, a swarm launch draft is generated according to the workshop scheduling module based on the completion of all tasks; if the launch time is not enough to complete all tasks, a swarm launch draft is generated according to the workshop scheduling module based on the task contribution.

[0034] As an exemplary embodiment of the present invention, the dynamic contribution calculation module calculates the contribution of each space launch mission using the following formula:

[0035]

[0036] in, Indicates launch mission M i The contribution of Indicates launch mission M i The inherent value of Indicates launch mission M i The networking value, Indicates launch mission M i The time value, Indicates launch mission M i is the value of the number of opportunities, α, β, γ, ξ are weight coefficients, and the sum of α, β, γ, ξ is 1.

[0037] According to an exemplary embodiment of the present invention, the workshop scheduling module based on the completion of all tasks schedules and sorts all space launch tasks according to the shortest path, including:

[0038] Extract mission features, including the time window for space launch;

[0039] Define the priority rule, based on the assumption that all tasks can be completed on time, for the task set M = {M1, M2, ..., M n Each task M to be completed in i , specifying the priority of the transmission window in the front, and then giving priority to the transmission window with fewer windows; where i and n are both natural numbers greater than 1;

[0040] Sort by priority rules;

[0041] Call the shortest path planning module to calculate the path for each space launch mission M i Select the shortest path and allocate corresponding resources, including satellites, rockets, launch vehicles, assembly and testing plants, mobile routes and launch sites.

[0042] The advantages of the present invention are:

[0043] In certain circumstances, such as large-scale or wide-scale disaster relief activities, high-density observation of hot spots, and enhanced satellite communications in a certain area during specific periods of time, there is a need to launch many satellites in different orbits in a short period of time.

[0044] This proposal provides a technical solution for an online automatic planning and scheduling system for launching a large number of satellites in different orbits in a short period of time. It schedules space launch missions based on a swarm-type space launch system, and can effectively solve the problems of low efficiency, difficulty in optimizing plans, and proneness to errors in manual scheduling and planning for large-scale satellite launches.

[0045] The technology provided by this solution is highly robust and can effectively improve the survivability of the system under intense confrontation conditions. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The above and other objects, features, and advantages of the present application will become more apparent by describing in detail exemplary embodiments thereof with reference to the accompanying drawings. The drawings described below are merely some embodiments of the present application, and it is apparent to those skilled in the art that other drawings can be derived from these drawings without inventive effort.

[0047] Figure 1 The structural diagram of the swarm space launch system is schematically shown.

[0048] Figure 2 The structure of the swarm space launch scheduling system is schematically shown.

[0049] Figure 3 The diagram schematically shows the steps of the swarm space launch scheduling method. DETAILED DESCRIPTION

[0050] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be embodied in many forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the concepts of the example embodiments to those skilled in the art. Like reference numerals in the drawings represent like or similar parts, and thus repetitive description thereof will be omitted.

[0051] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner.In the following description, many specific details are provided so as to provide a full understanding of the embodiments of the present application. However, it will be appreciated by those skilled in the art that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps etc. can be adopted. In other cases, known methods, devices, implementations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0052] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0053] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0054] It should be understood that although the terms first, second, third, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another. Thus, the first component discussed below could be referred to as the second component without departing from the teachings of the present invention. As used herein, the term "and / or" includes any one and all combinations of one or more of the associated listed items.

[0055] Those skilled in the art will understand that the drawings are merely schematic diagrams of example embodiments, and the modules or processes in the drawings are not necessarily necessary for implementing the present application, and therefore cannot be used to limit the scope of protection of the present application.

[0056] According to a first specific embodiment of the present invention, the present invention provides a swarm-type space launch mission scheduling system, which is a scheduling system for a swarm-type space launch system.

[0057] The swarm type is to configure multiple launch sites around the assembly site, similar to a swarm of bees, and assign launch tasks to each launch site for launch.

[0058] Swarm space launch systems, such as Figure 1 As shown, it includes: beehive system, nectar source system, bee path system and bee system.

[0059] The honeycomb system is the technical area for space launch. Figure 1 Within the dotted line of the central circle, it is connected to the nectar source system through the bee path system to complete the star-rocket combination.

[0060] The honeycomb system includes a space launch vehicle storage area / factory, a space launch vehicle test factory, a satellite storage and testing factory, a rocket storage and testing factory, a satellite-rocket docking factory / station, a satellite-rocket assembly transfer factory / station, and connecting roads inside the honeycomb.

[0061] The space launch vehicle storage area / factory is used to store space launch vehicles.

[0062] The space launch vehicle test plant is used to complete the testing, repair and maintenance of space launch vehicles.

[0063] The satellite storage and testing plant is used to store satellites and complete satellite assembly and testing.

[0064] The rocket storage and testing plant is used to store rockets and complete rocket assembly and testing work.

[0065] The satellite-rocket docking plant / workstation is used to complete the docking and testing of satellites and rockets.

[0066] The satellite-rocket assembly transfer plant / workstation is used to complete the work of transferring the satellite-rocket assembly to the space launch vehicle.

[0067] The connecting roads inside the honeycomb connect various places within the honeycomb system, realizing road traffic and transportation in each place.

[0068] One or more basic units in the honeycomb can be set according to task requirements.

[0069] There are multiple nectar source systems surrounding the honeycomb system. Figure 1 There are 5 nectar source systems, each of which includes multiple launch sites. The concave structure in the nectar source system is the launch site.

[0070] The launch site includes multiple launch pads and standby areas.

[0071] The launch site apron is the parking place for space launch vehicles before ignition and launch.

[0072] The standby area is where the space launch vehicle waits to enter the launch procedure.

[0073] A launch site usually has multiple launch pads to support multiple space launch vehicles carrying out activities at the same time.

[0074] The straight-line distance between the hive system and the nectar source system ranges from 5 to 150 kilometers, enabling the dispatch of satellite-rocket combinations to complete multiple launch missions within a small area, enabling satellites in different orbits to be launched from different launch sites in a short period of time. The 5km distance is a safety distance to account for potential damage to the hive in the event of an incident in the nectar source system; the 150km distance is to ensure that bees can maneuver within the hive system to a minimum.

[0075] The bee route system connects the launch sites and the honeycomb system and includes multiple traffic roads. Figure 1 In the video, the launch vehicle, acting as a "bee", travels on the traffic road, and the bee-path system facilitates the space launch vehicle to reach the launch site smoothly.

[0076] The Bee system comprises multiple launch units, which are the essential elements required to complete a space launch. These units include satellites, rockets, launch vehicles, and support equipment. These are the essential elements required to complete a space launch and can independently carry out space launch missions within a certain range.

[0077] The swarm space launch mission scheduling system is the brain of the swarm launch and the core of the effective implementation of the swarm launch. It undertakes the core functions of system structure construction, reorganization and task distribution, and is the key to the performance and improvement of the entire swarm space launch system. Figure 2As shown in the figure, the swarm space launch mission scheduling system includes: mission planning subsystem, planning evaluation subsystem, mission resource data pool, mission implementation process control subsystem, mission data management subsystem, resource database, mission database, mission process demonstration / reproduction subsystem, mission live collection subsystem, and exercise and training subsystem.

[0078] The mission resource data pool is connected to the mission data management subsystem, mission planning subsystem, mission implementation process control subsystem, mission process demonstration / reproduction subsystem, exercise and training subsystem, and mission live collection subsystem to store mission resource data.

[0079] The mission data management subsystem is connected to the resource database and the mission database to manage the available resources and mission process data of swarm space launches. Specifically, in addition to providing data support for various related subsystems, it also has classification statistics, query, addition and deletion, and editing functions. The mission data also has real-time or quasi-real-time replay functions.

[0080] Available resources and task process data mainly include:

[0081] - Launch unit data management, including personnel, equipment, and supplies used to implement swarm space launches;

[0082] - Support unit data management, including logistics personnel, equipment, and supplies used to support swarm space launches;

[0083] - Data management of available aerospace products, including available satellites, launch vehicles and their supporting accessories;

[0084] - Storage warehouse data management, including warehouse information for storing satellites, rockets, and launch vehicles;

[0085] --Product assembly and testing plant data management, including plant data used for satellite and launch vehicle testing, satellite-rocket docking, and satellite-rocket assembly transfer;

[0086] Traffic data management, including traffic network data connecting product storage warehouses, assembly and testing plants, launch sites, and launch site locations;

[0087] - Launch site location and point data management, including data on launch sites, points and their status;

[0088] - Launch program data, including the basic procedures for swarm space launch, the coupling constraints between procedures, and the time required for each work item;

[0089] ——Resource data import, which can import available resource data from the resource database in real time;

[0090] ——Task data export, which can export data in the task pool to the task database in real time;

[0091] ——Data creation and editing: users can create and edit resource data through the resource data management interface;

[0092] ——Task resource data pool management and initialization: First, use the data import function to load resource data into the task data pool; second, standardize the tasks and constraint coupling condition data issued by the superior, form a task list and load it into the task data pool;

[0093] ——Task process data backup, real-time backing up the data in the task data pool to the task database.

[0094] The mission planning subsystem is connected to the mission resource data pool to generate swarm launch drafts.

[0095] The task planning subsystem includes the shortest path planning module, the dynamic contribution calculation module, the workshop scheduling module based on the completion of all tasks, the workshop scheduling module based on the task contribution and the draft generation module.

[0096] The shortest path planning module is used to calculate the shortest path from the current process site to the next process site for each launch mission.

[0097] The dynamic contribution calculation module calculates the contribution of each space launch to mission completion. Due to differences in the number, size, functionality, and performance of satellites in each launch, each launch's contribution to mission objectives also varies. The dynamic contribution calculation module calculates each launch's contribution to mission objectives in real time, enabling the mission planning subsystem to prioritize launches with the highest contribution.

[0098] The workshop scheduling module based on the completion of all tasks is used to schedule and sort all space launch tasks according to the shortest path.

[0099] The workshop scheduling module based on task contribution is used to schedule and sort all space launch tasks according to their contribution.

[0100] The draft generation module is used to generate a swarm launch draft. If the launch time can complete all tasks as scheduled, a swarm launch draft is generated according to the workshop scheduling module based on the completion of all tasks; if the launch time is not enough to complete all tasks, a swarm launch draft is generated according to the workshop scheduling module based on the task contribution.

[0101] The mission planning subsystem generates swarm space launch drafts in real time based on the assigned missions and using available resources under given constraints.

[0102] 1) Initial draft design:

[0103] (1) Calling the mission planning algorithm to generate a swarm space launch draft;

[0104] (2) Use the mission planning evaluation method to evaluate the swarm space launch draft;

[0105] (3) Write the evaluation results into the task resource data pool and notify the task implementation process control subsystem for approval.

[0106] 2) Plan design during task implementation:

[0107] (1) Collect data from the current task resource data pool;

[0108] (2) Generate a mission reset point. When a space launch mission is in progress, such as docking a satellite with a rocket, it is impossible to stop the mission to accept a new mission. Therefore, a "mission safety reset point algorithm" is needed. For the launch vehicle's "mission safety reset point", it is generally when the launch vehicle completes a launch mission and the next launch mission has not yet begun. At this time, it is a "mission safety reset point" for the launch vehicle. For example, when a crane is lifting something, it must stop before it can be assigned a new mission.

[0109] (3) Taking the mission reset point set as the mission starting point, the mission planning subsystem is called to generate a swarm space launch draft;

[0110] (4) Calling the planning and evaluation subsystem to evaluate the draft of the swarm space launch;

[0111] (5) Write the evaluation results into the task resource data pool and notify the task implementation process control subsystem for approval.

[0112] The planning and evaluation subsystem is connected to the mission planning subsystem and is responsible for evaluating swarm launch plans and storing them and the evaluation results in the mission resource data pool. Based on mission objectives, the planning and evaluation subsystem provides real-time assessments of the mission completion and implementation risks of swarm launch plans. Mission completion assessments compare and evaluate the mission completion of space launch plans based on the task list and mission priorities. Mission risk assessments compare and evaluate the implementation risks of space launch plans based on red-line criteria.

[0113] The task implementation process control subsystem is connected to the task data management subsystem. The task data management subsystem reads the task order and constraints and performs data normalization processing to form task data. The task data management subsystem reads the available resource data and uses "task data + resource data" to initialize the task resource data pool.

[0114] The mission implementation process control subsystem is also used to review and approve the swarm launch draft and evaluation results. If approved, the swarm launch draft will be converted into a launch plan output and the launch unit and support unit will be notified. If not approved, the swarm launch draft will be regenerated.

[0115] The mission implementation process control subsystem adjusts the launch target in real time according to the mission status, and specifies and issues swarm launch commands:

[0116] 1) Task start:

[0117] (1) Initialize the task resource data pool data through the data management subsystem;

[0118] (2) Develop a swarm space launch plan through the mission planning subsystem;

[0119] (3) Receive notification from the mission planning subsystem and review and approve the draft:

[0120] (4) Determine whether to re-plan based on the evaluation results: If re-planning is required, at least one of the available resources, task orders, or constraints should be modified, and the work of formulating the swarm launch draft mentioned in (2) should be repeated; otherwise, the space launch draft should be approved as the official plan;

[0121] (5) Issue commands to the launch unit and support unit according to the plan.

[0122] 2) Task process control:

[0123] (1) Collecting the task status in real time through the task status collection subsystem;

[0124] (2) When the following situations occur, a new swarm launch plan can be formulated through the mission planning subsystem:

[0125] ——Superiors assign new tasks or the original task plan changes;

[0126] ——The mission environment conditions have changed and the current plan cannot be completed as planned;

[0127] - A launch unit or support unit fails to complete its mission due to a malfunction, or its capabilities are significantly reduced, making it impossible to complete the current plan as planned;

[0128] ——A certain resource is damaged and the current plan cannot be completed as planned.

[0129] (3) Accept notification from the mission planning subsystem and review the draft of the swarm space launch: Based on the evaluation results, determine whether to re-plan the draft of the swarm space launch: If re-planned, usually at least one of the available resources, task orders or constraints should be modified, and the work of formulating the swarm launch draft mentioned above (2) should be repeated; otherwise, approve the launch draft as the official plan;

[0130] (5) Issue commands to the launch unit and support unit according to the swarm space launch plan.

[0131] The mission live status collection subsystem is used to collect mission live status and update the data in the mission resource data pool. Specifically, the mission live status collection subsystem collects real-time data on the progress of swarm space launch plans and the real-time data of mission implementation through data reporting from launch and support units, video surveillance networks, and the deployment and perception of various sensors. It then adjusts the data in the mission resource data pool in real time based on this data.

[0132] The Exercise and Training Subsystem uses the mission resource data pool to drive system-wide exercises and personnel training. This subsystem only operates in system-wide exercise and personnel training mode. Based on the requirements of these exercises and personnel training, it receives guidance and command content from the command and control group in real time, normalizes the data, and then loads it into the mission resource data pool. A human-computer interface is established between the exercise and training command and control group and the system. The mission resource data pool is managed in real time according to the command and control group's requirements, and is used to drive the orderly implementation of system-wide exercises and personnel training. "Command and control" is a term used in military exercises and training, and the "command and control group" refers to the team that sets the exercise scenario and content in real time based on the progress of the exercise and training.

[0133] (1) Before the drill training, initialize the task resource data pool through the data management subsystem;

[0134] (2) During the drill training process, the task resource data pool is modified through the live acquisition subsystem.

[0135] The exercise and training subsystem is activated only when the system is working in the exercise and training mode.

[0136] The mission process demonstration / reproduction subsystem, connected to the mission data management subsystem, uses data from the mission resource data pool to simulate the actual mission execution. It also loads historical mission data from the data management subsystem to reproduce the historical mission execution process. During mission execution, the entire process—from mission assignment, plan development, mission execution, exception handling, mission results, and performance analysis—is displayed in real time using animations, forms, and network diagrams, facilitating real-time monitoring of mission progress and trends. After mission completion, near-real-time replay of mission resource data provides a realistic and complete reconstruction of the mission execution process, assisting in fault analysis, defect detection, and solution improvement.

[0137] According to a second specific embodiment of the present invention, the present invention provides a swarm-type space launch scheduling method, which adopts the swarm-type space launch task scheduling system of the first specific embodiment, such as Figure 3 As shown, the following steps are included:

[0138] S1: The mission planning subsystem generates a swarm launch draft.

[0139] The mission planning subsystem generates a swarm launch draft including:

[0140] S11: The shortest path planning module calculates the shortest path from the current process site to the next process site for each launch mission.

[0141] To calculate the shortest path, we use the Dijkstra algorithm, starting from the current process site for each launch mission, to find the shortest path from that site to the next process site. The Dijkstra algorithm, also known as a greedy algorithm, works by gradually expanding the set of points from the starting point in ascending order of distance or duration until all points are included.

[0142] S12: The dynamic contribution calculation module calculates the contribution of each space launch mission.

[0143] The contribution calculation includes the inherent value, networking value, time value, and opportunity value of launching a satellite. Intrinsic value reflects the cost of the satellite; higher-cost satellites have higher intrinsic value. Network value reflects the value of networking the satellite with other satellites; the higher the value of the successful networking, the higher the networking value. Time value reflects the urgency of the need to launch the satellite; the more urgent the need, the higher the time value. Opportunity value reflects the number of available launch opportunities for the satellite; the more opportunities, the lower the opportunity value. Therefore, the contribution of each space launch is calculated based on the inherent value of the launch mission, the networking value of the launch mission, the time value of the launch mission, and the opportunity value of the launch mission.

[0144] The inherent value of the launch mission:

[0145] Each satellite has different functions, performance and other attributes, and its actual use value will also be different. Since its use value is sometimes difficult to evaluate, we usually calculate the inherent value of the satellite according to its cost. use Divided into 5 levels, namely formula 1:

[0146] V use ={1,2,3,4,5} Formula 1;

[0147] Among them, 5 has the highest value, 1 has the lowest value, and the value increases from 1 to 5.

[0148] Satellites are usually considered as a type of spacecraft. For the convenience of description, this application does not distinguish between the concepts of satellites and spacecraft.

[0149] Satellites are typically categorized by their orbital height, such as low-orbit satellites, medium-orbit satellites, and high-orbit satellites; by their purpose, they are categorized as scientific satellites, technological test satellites, and application satellites; by their function, they are categorized as communications satellites, remote sensing satellites, and navigation satellites; and by their weight, they are categorized as large satellites, medium-small satellites, microsatellites, nanosatellites, and picosatellites. A satellite's functional performance is often correlated with its cost, so we use cost as a measure of its inherent value.

[0150] Satellites costing more than $2 billion have their intrinsic value set to 5;

[0151] Satellites costing between $1 billion and $2 billion have their intrinsic value set at 4;

[0152] Satellites costing between $100 million and $1 billion have an intrinsic value of 3.

[0153] Satellites costing between 10 million and 100 million have an intrinsic value of 2.

[0154] Satellites costing less than 10 million have an intrinsic value of 1.

[0155] A launch mission M i m satellites can be launched, and the intrinsic value of the jth satellite is Then the launch mission M i The intrinsic value is obtained using Formula 2:

[0156]

[0157] in, represents the intrinsic value of the launch mission, M i represents a launch mission, m represents launch mission M i The number of satellites that can be launched, j represents the jth satellite, represents the intrinsic value of the j-th satellite, where m and j are both natural numbers greater than or equal to 1.

[0158] The networking value of the launch mission:

[0159] When the network is launched, in addition to the actual use value of each satellite, the satellites that are successfully networked will also add the network value of the satellites working together. The network gain value V will be calculated according to the actual value after the network is successfully established. add Divided into 5 levels, that is, formula 3:

[0160] V add ={1,2,3,4,5} Formula 3;

[0161] Among them, 5 has the highest value, 1 has the lowest value, and the value increases from 1 to 5.

[0162] The added value after successful networking can be comprehensively measured based on its scale and actual cost.

[0163] The network value of large constellations or constellations with a construction cost of more than 100 billion yuan is set to 5, such as the Beidou global navigation constellation;

[0164] The network value of medium-sized constellations or constellations with a construction cost of more than 10 billion is set to 4, such as the US Navy Tactical Communications Network;

[0165] The network value of small constellations or constellations with a construction cost of more than 1 billion is set at 3, such as the "4+1+4" China Siwei new generation commercial remote sensing satellite system;

[0166] The network value of a constellation with multiple satellites working together or a cost of more than 100 million is set to 2, such as the Fengyun satellite network;

[0167] The network value of a constellation consisting of several small satellites or with a construction cost of less than 100 million is set at 1.

[0168] The gain value obtained after successful networking cannot be simply divided equally among the launch of each satellite. In fact, if the star network consists of three satellites, the networking gain value can only be obtained after all three satellites are successfully launched.

[0169] Suppose there is a star network consisting of n satellites, and the network gain value after the network is successfully established is V add , then the network gain value of launching the hth satellite is That is, the networking gain value of the hth satellite is obtained using formula 4:

[0170]

[0171] Among them, there are n satellites forming a star network, and the network value after the network is successfully established is V add , the network gain value of the hth satellite in the network is Both n and h are natural numbers greater than or equal to 1.

[0172] A launch mission M i m satellites can be launched, of which l satellites have networking value. Among the l satellites, the kth satellite is the jth satellite in the networking satellite, and its networking gain value is Then the launch mission M i Network value The formula 5 is used to obtain:

[0173]

[0174] in, Indicates the networking value of the launch mission, M i represents a launch mission, m represents launch mission Mi The number of satellites that can be launched, of which l satellites have networking value. Among the l satellites, the kth satellite is the kth satellite in this mission, and the jth satellite is the jth satellite in the networking satellite. The networking gain value of the jth satellite is Both l and k are natural numbers greater than or equal to 1.

[0175] k ranges from 1 to l to find the networking value of all satellites in this mission. Of course, the networking value of some satellites is 0.

[0176] Time value of a launch mission:

[0177] In certain situations, due to different requirements for satellite usage time, the value of each space launch is related to time. For example, in a space station emergency rescue launch, since rescue time is very precious, the earlier the launch, the more opportunities for safe rescue of the astronauts on the space station. Once the optimal rescue time period is missed, there will be a significant risk of astronaut sacrifice. According to the urgency of the use time, the time value V tim Divided into 5 levels, namely formula 6:

[0178]

[0179] Among them, 5 has the highest value, 1 has the lowest value, and the values increase in sequence from 1 to 5. tim1, tim2, tim3, tim4, and tim5 refer to the urgency of the task.

[0180] TIM5 represents general space launch missions with an urgency level of "general launch," usually without special time requirements. Most space launch missions fall into this category, such as ordinary remote sensing satellites, communications satellites, and space technology demonstration satellites.

[0181] TIM4 indicates a space launch mission with an "urgent" level of urgency. These missions are usually space engineering construction missions that have significant commercial or social value and that the country or society needs to speed up. Space launch missions related to this can be classified as "urgent" level, such as the launch mission for the construction of the Beidou satellite navigation system.

[0182] tim3 indicates a space launch mission with an "extremely urgent" level of urgency, usually referring to a space engineering construction mission that is urgently needed to be implemented at the national level, such as the launch mission of the Mars rover "Tianwen-1".

[0183] TIM2 indicates a space launch mission with an urgency level of "critical", usually referring to missions urgently needed for national disaster relief, space emergency rescue and military struggle, such as space station emergency rescue launch missions.

[0184] tim1 indicates a space launch mission with an “extremely urgent” level of urgency, usually referring to a space war-related space launch mission.

[0185] A launch mission M i m satellites can be launched, and the time value of the jth satellite is The time value of the launch mission is The formula 7 is used to obtain:

[0186]

[0187] in, represents the time value of the launch mission, M i represents a launch mission, m represents launch mission M i The number of satellites that can be launched, where the time value of the jth satellite is

[0188] The value of launch mission opportunities:

[0189] Due to the limitations of demand time or evaluation time period, the launch window information contains a limited number of launch windows for each satellite, and the number of available launch windows for different satellites varies. This problem can be solved by formulating the minimum slack priority principle. The slack here specifically refers to the number of available launch windows for each space launch within a period of time.

[0190] For each space launch mission, the greater the number of available launch windows within a period, the greater the corresponding slack, and the lower the opportunity value. Conversely, the smaller the corresponding slack, the higher the opportunity value. Therefore, the opportunity value of each space launch can be defined based on the number of available launch time windows within a period.

[0191] Launch Mission M i The task cycle is T cyc , in the evaluation period D tim There are usually w available transmission windows in the transmission window, and the available transmission number w in the transmission window is obtained using formula 8:

[0192]

[0193] Where w represents the number of available launch windows for a launch mission within the evaluation period of the mission cycle, T cyc represents the mission period of the launch mission, D tim represents the evaluation period, where w is a natural number greater than or equal to 1.

[0194] Among them, the evaluation period D tim It refers to the time span of a set of space launches being evaluated. For example, all space missions planned to be launched in May, June, and July 2024 are prioritized. At this time, D tim The value of is 3 months. The number of launch mission opportunities is worth The formula 9 is used to obtain:

[0195]

[0196] in, represents the opportunity value of a launch mission, and w represents the number of available launch windows for a launch mission within the evaluation period of the mission cycle.

[0197] A launch mission M i m satellites can be launched during the evaluation period D tim There are usually w available launch windows within .

[0198] The contribution of the launch mission is obtained based on the inherent value, networking value, time value, and opportunity value of the launch mission using formula 10:

[0199]

[0200] Right now

[0201] in, Indicates the contribution of the launch mission, represents the intrinsic value of the launch mission, Indicates the networking value of the launch mission, represents the time value of the launch mission, represents the opportunity value of the launch mission, α, β, γ, and ξ are weight coefficients, and the sum of α, β, γ, and ξ is 1.

[0202] As a preferred embodiment, α, β, γ, and ξ are set to 0.3, 0.2, 0.4, and 0.1, respectively.

[0203] Step S11 and step S12 may be performed synchronously or asynchronously.

[0204] S13: The workshop scheduling module based on the completion of all tasks schedules and sorts all space launch tasks according to the shortest path.

[0205] According to the basic process flow of each space launch, namely, rocket out of the warehouse test, satellite out of the warehouse test, rocket-satellite docking test, launch vehicle out of the warehouse test, transfer of the rocket-satellite combination to the launch vehicle, launch unit transfer, launch unit pre-launch preparation, launch, launch vehicle post-launch recovery, and launch vehicle withdrawal, a heuristic scheduling algorithm based on priority rules is used to schedule and sort all space launch missions.

[0206] The workshop scheduling module based on the completion of all tasks schedules and sorts all space launch tasks according to the shortest path, including:

[0207] Extract mission features, including the time window for space launch;

[0208] Define the priority rule, based on the assumption that all tasks can be completed on time, for the task set M = {M1, M2, ..., M n Each task M to be completed in i First, specify the priority principle of first-come-first-served (FCFS), that is, the one with the earlier transmission window takes priority; second, when the FCFS priorities are the same, follow the priority principle of LLF with the smallest number of opportunities, that is, the one with the smallest transmission window takes priority; where i and n are both natural numbers greater than 1;

[0209] Sort by priority rules;

[0210] Call the shortest path planning module to calculate the path for each space launch mission M i The shortest path is selected and the corresponding resources are allocated. These resources include satellites, rockets, launch vehicles, assembly and testing facilities, maneuvering routes, and launch sites. The shortest path planning module is used to allocate resources. Whether sorting by priority or contribution, the sorting only determines which launch occurs first. The allocation of launch resources needs to be planned based on the shortest path. Because there are many available resources, for example, different types of rockets can be used to launch the same satellite into orbit; there may be multiple stations for satellite assembly and testing, and it is necessary to determine which station to use; after the satellite and rocket are assembled, there are also multiple launch vehicles for launch, and it is also necessary to determine which launch vehicle will perform the launch mission, etc., so it is necessary to plan the shortest path to allocate resources.

[0211] First come first served (FCFS) scheduling algorithm: the simplest scheduling algorithm, which can be used for both job scheduling and program scheduling. When this algorithm is used in job scheduling, the system will schedule jobs in the order in which they arrive, and will prioritize selecting one or more jobs at the head of the queue from the backup queue, bring them into memory, allocate the required resources, create a process, and then put them into the "ready queue". The process scheduler will not allocate the processor to other processes until the process runs to completion or is blocked by some event.

[0212] Lowest Slack Time First (LLF) is a dynamic priority scheduling algorithm that determines the priority of processes based on their remaining processing time and deadline to ensure that the system can complete the most urgent tasks as quickly as possible.

[0213] S14: The workshop scheduling module based on task contribution schedules and sorts all space launch tasks according to their contribution.

[0214] If the launch time is not enough to complete the entire mission, proceed to step S12 and step S14.

[0215] S15: The draft generation module generates a swarm launch draft. If the launch time can complete all tasks as scheduled, a swarm launch draft is generated according to the workshop scheduling module based on the completion of all tasks; if the launch time is not enough to complete all tasks, a swarm launch draft is generated according to the workshop scheduling module based on the task contribution.

[0216] S2: The planning and evaluation subsystem evaluates the swarm launch draft and writes the swarm launch draft and the evaluation results into the mission resource data pool.

[0217] S3: The mission implementation process control subsystem reviews the swarm launch draft and evaluation results, and converts the swarm launch draft into a launch plan output.

[0218] S4: When executing the space launch plan, the mission live status collection subsystem collects the mission live status in real time and loads it into the mission resource data pool.

[0219] Specifically, the mission real-time collection subsystem continuously (until the end of the mission) collects data on each launch unit, support unit, aerospace products, product storage warehouses, product assembly and testing plants, traffic conditions, launch site positions and locations, and updates the data in the mission resource data pool in real time; new tasks and changes in constraints issued by superiors are loaded into the mission resource data pool in real time through the mission data management subsystem.

[0220] When necessary, exercises can be conducted through the exercise and training subsystem and the mission process demonstration / reproduction subsystem can be used for reproduction.

[0221] This plan analyzes the demand for launching large quantities of satellites in different orbits in the short term, and evaluates the practical needs of constructing or using existing systems to build a swarm space launch system; while constructing or using existing systems to build a swarm space launch system, it develops a swarm space launch scheduling system and deploys the swarm space launch scheduling system in the scheduling hall; uses the swarm space launch scheduling system to organize full-system drills for swarm space launches and relevant personnel training; and uses the swarm space launch scheduling system to realize the formal operation of the swarm space launch system.

[0222] In certain circumstances, such as large-scale or wide-scale disaster relief activities, high-density observation of hot spots, and enhanced satellite communications in a certain area during specific periods of time, there is a need to launch many satellites in different orbits in a short period of time.

[0223] This proposal provides a technical solution for an online automatic planning and scheduling system for launching a large number of satellites in different orbits in a short period of time. It schedules space launch missions based on a swarm-type space launch system, and can effectively solve the problems of low efficiency, difficulty in optimizing plans, and proneness to errors in manual scheduling and planning for large-scale satellite launches.

[0224] The technology provided by this solution is highly robust and can effectively improve the survivability of the system under intense confrontation conditions.

[0225] The exemplary embodiments of the present invention are specifically shown and described above. It should be understood that the present invention is not limited to the detailed structure, configuration or implementation described herein; on the contrary, the present invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A swarm-type space launch mission scheduling system, characterized in that: include: Mission planning subsystem, planning evaluation subsystem, mission resource data pool, and mission implementation process control subsystem; The mission planning subsystem is connected to the mission resource data pool to generate a swarm launch draft; The planning and evaluation subsystem is connected to the mission planning subsystem and is used to evaluate the swarm launch draft and write the swarm launch draft and the evaluation results into the mission resource data pool; The mission implementation process control subsystem is connected to the mission resource data pool, and is used to review and approve the swarm launch draft and evaluation results, and convert the swarm launch draft into a launch plan output.

2. The swarm-type space launch mission scheduling system according to claim 1, characterized in that: The task planning subsystem includes a shortest path planning module, a dynamic contribution calculation module, a workshop scheduling module based on task completion, a workshop scheduling module based on task contribution, and a draft generation module: The shortest path planning module is used to calculate the shortest path from the current process site to the next process site for each launch mission; The dynamic contribution calculation module is used to calculate the contribution of each space launch mission completion; The workshop scheduling module based on the completion of all tasks is used to schedule and sort all space launch tasks according to the shortest path; The task contribution-based workshop scheduling module is used to schedule and sort all space launch tasks according to their contributions; The draft generation module is used to generate a swarm launch draft. If the launch time can complete all tasks as scheduled, a swarm launch draft is generated according to the workshop scheduling module based on the completion of all tasks; if the launch time is not enough to complete all tasks, a swarm launch draft is generated according to the workshop scheduling module based on task contribution.

3. The swarm-type space launch mission scheduling system according to claim 1, characterized in that: It also includes the task data management subsystem, resource database, and task database: The mission data management subsystem is connected to the resource database, the mission database and the mission resource data pool, and is used to manage the available resources and mission process data of swarm space launches.

4. The swarm-type space launch mission scheduling system according to claim 3, characterized in that: It also includes a task process demonstration / reproduction subsystem, which is connected to the task resource data pool and the task data management subsystem, and is used to use the data in the task resource data pool to simulate and display the actual situation when the task is implemented, and is also used to load historical task data through the data management subsystem to reproduce the historical task implementation process.

5. The swarm-type space launch mission scheduling system according to claim 1, characterized in that: It also includes a task status collection subsystem, which is connected to the task resource data pool and is used to collect task status and update data in the task resource data pool.

6. The swarm-type space launch mission scheduling system according to claim 1, characterized in that: It also includes an exercise and training subsystem, which is connected to the mission resource data pool and is used to use the mission resource data pool to drive full-system exercises and personnel training.

7. A swarm-type space launch mission scheduling method, characterized in that: The swarm-type space launch mission scheduling system according to any one of claims 1 to 6 comprises the following steps: The mission planning subsystem generates a swarm launch draft; The planning and evaluation subsystem evaluates the swarm launch draft and writes the swarm launch draft and evaluation results into the mission resource data pool; The mission implementation process control subsystem reviews the swarm launch draft and evaluation results, and converts the swarm launch draft into a launch plan output.

8. The swarm-type space launch mission scheduling method according to claim 7, characterized in that: The mission planning subsystem generates a swarm launch draft including: The shortest path planning module calculates the shortest path from the current process site to the next process site for each launch mission; The dynamic contribution calculation module calculates the contribution of each space launch mission; The workshop scheduling module based on the completion of all tasks will schedule and sort all space launch tasks according to the shortest path; The workshop scheduling module based on task contribution schedules and sorts all space launch tasks according to their contribution; The draft generation module generates a swarm launch draft. If the launch time can complete all tasks as scheduled, a swarm launch draft is generated according to the workshop scheduling module based on the completion of all tasks; if the launch time is not enough to complete all tasks, a swarm launch draft is generated according to the workshop scheduling module based on the task contribution.

9. The swarm-type space launch mission scheduling method according to claim 8, characterized in that: The dynamic contribution calculation module calculates the contribution of each space launch mission using the following formula: in, Indicates launch mission M i The contribution of Indicates launch mission M i The inherent value of Indicates launch mission M i The networking value, Indicates launch mission M i The time value, Indicates launch mission M i is the value of the number of opportunities, α, β, γ, ξ are weight coefficients, and the sum of α, β, γ, ξ is 1.

10. The swarm space launch mission scheduling method according to claim 8, characterized in that: The workshop scheduling module based on the completion of all tasks schedules and sorts all space launch tasks according to the shortest path, including: Extract mission features, including the time window for space launch; Define the priority rule, based on the assumption that all tasks can be completed on time, for the task set M = {M1, M2, ..., M n Each task M to be completed in i , specifying the priority of the transmission window in the front, and then giving priority to the transmission window with fewer windows; where i and n are both natural numbers greater than 1; Sort by priority rules; Call the shortest path planning module to calculate the path for each space launch mission M i Select the shortest path and allocate corresponding resources, including satellites, rockets, launch vehicles, assembly and testing plants, mobile routes and launch sites.

Images