A system and method for scheduling space launch missions in a swarm

Abstract

This invention relates to the field of aerospace launch technology, and provides a swarm-based aerospace launch mission scheduling system and method. The system includes: a mission planning subsystem, a planning evaluation subsystem, a mission resource data pool, and a mission implementation process control subsystem. The mission planning subsystem is connected to the mission resource data pool and is used to generate a swarm-based launch draft. The planning evaluation subsystem is connected to the mission planning subsystem and is used to evaluate the swarm-based launch draft and write the swarm-based launch draft and 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 approve the swarm-based launch draft and evaluation results, and convert the swarm-based launch draft into a launch plan output. This solution enables online automatic planning for launching a large number of satellites in different orbits in a short period of time, effectively solving the problems of low efficiency, difficulty in plan optimization, and susceptibility to errors in manual scheduling and planning for large-scale satellite launches.

Description

Technical Field

[0001] This invention relates to the field of aerospace launch technology, and in particular to a swarm-based aerospace launch mission scheduling system and method. Background Technology

[0002] With the continuous advancement of aerospace technology, more and more satellites are being sent into space. Multiple satellite launches on a single rocket refer to 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 wide-ranging disaster relief operations, high-density observation of hotspot areas, and enhancement of satellite communications in a specific region during a specific period, there is a need to launch numerous satellites in different orbits within a short period of time.

[0004] Meanwhile, in the past three years (2022-2024), the number of human space launches has continued to grow at a double-digit rate. With the increase in the number of space launches, the scheduling of space launches is particularly important. If the scheduling problem of space launches is not solved, it will reduce the efficiency of launching a large number of satellites and cause errors with irreversible consequences.

[0005] Therefore, there is a need to provide a swarm-based 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, effectively solving the problems of low efficiency, difficulty in scheme optimization, and susceptibility to errors in manual scheduling and planning for large-scale satellite launches.

[0006] The information disclosed in the background section is only intended to enhance the understanding of the background of this application, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0007] The main purpose of this invention is to overcome the problem of ineffective satellite launch scheduling in a short period of time, and to provide a swarm-style space launch mission scheduling system and method that can launch a large number of satellites in different orbits online automatically in a short period of time, effectively solving the problems of low efficiency, difficulty in scheme optimization and easy error in manual scheduling and planning of large batches of satellite launches.

[0008] To achieve the above objectives, the first aspect of the present invention provides a swarm-based 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 and is used to generate swarm launch drafts;

[0010] The planning evaluation subsystem and the mission planning subsystem are connected and used to evaluate the swarm launch draft and write the swarm launch draft and 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 approve swarm launch drafts and evaluation results, and to convert swarm launch drafts into launch plans for output.

[0012] The swarm method involves setting up multiple launch sites around the assembly site, similar to a swarm of bees, and assigning launch missions 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 workshop scheduling module based on the completion of all tasks, a workshop 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.

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

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

[0018] The draft generation module is used to generate a swarm launch draft. If all tasks can be completed on schedule, a swarm launch draft is generated based on the workshop scheduling module based on task completion. If the launch time is insufficient to complete all tasks, a swarm launch draft is generated based on the workshop scheduling module based on task contribution.

[0019] As an example embodiment of the present invention, the swarm-based 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, mission database, and mission resource data pool to manage available resources and mission process data for swarm-style space launches.

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

[0022] As an example embodiment of the present invention, the swarm launch mission scheduling system further includes a mission status acquisition subsystem, which is connected to the mission resource data pool and is used to acquire mission status and update data in the mission resource data pool.

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

[0024] According to a second aspect of the present invention, the present invention provides a swarm-based space launch scheduling method, employing the aforementioned swarm-based space launch mission scheduling system, comprising the following steps:

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

[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 approves the swarm launch draft and evaluation results, and transforms the swarm launch draft into a launch plan output.

[0028] As an example 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] Once all missions are completed, the workshop scheduling module will schedule and sort all space launch missions based on the shortest path.

[0032] The workshop scheduling module based on task contribution sorts all space launch missions according to their contribution.

[0033] The draft generation module generates a swarm launch draft. If all tasks can be completed on schedule, the swarm launch draft is generated based on the workshop scheduling module based on task completion. If the launch time is insufficient to complete all tasks, the swarm launch draft is generated based on the workshop scheduling module based on task contribution.

[0034] As an example 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 Contribution Indicates launch mission M i Its inherent value Indicates launch mission M i The networking value, Indicates launch mission M i The value of time Indicates launch mission M i The chance value is denoted by α, β, γ, and ξ, which are weighting coefficients, and the sum of α, β, γ, and ξ 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 missions according to the shortest path, including:

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

[0039] Define priority rules based on the assumption that all tasks can be completed on schedule. For a task set M = {M1, M2, ..., M...} n Each task M to be completed in} i Prioritize those with earlier launch windows, then prioritize those with fewer launch windows; where i and n are both natural numbers greater than 1.

[0040] Sort according to priority rules;

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

[0042] The advantages of this invention are:

[0043] In specific situations, such as large-scale or wide-ranging disaster relief operations, high-density observation of hotspot areas, or enhancement of satellite communications in a specific region during a particular period, there is a need to launch numerous satellites in different orbits within a short period of time.

[0044] This solution provides a technical approach for an online automatic planning and scheduling system for launching a large number of satellites in different orbits in a short period of time. Based on a swarm-style space launch system, it schedules space launch missions and effectively solves problems such as low efficiency, difficulty in optimizing plans, and susceptibility to errors associated with manual scheduling and planning for large-scale satellite launches.

[0045] The technology provided in this solution is highly robust and can effectively improve the survivability of the system under intense confrontation conditions. Attached Figure Description

[0046] The above and other objects, features, and advantages of this application will become more apparent from the detailed description of exemplary embodiments with reference to the accompanying drawings. The drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0047] Figure 1 The diagram schematically illustrates the structure of a swarm-type space launch system.

[0048] Figure 2 The diagram illustrates the structure of a swarm-based space launch scheduling system.

[0049] Figure 3 The diagram illustrates the steps of a swarm-based space launch scheduling method. Detailed Implementation

[0050] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that this application will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0051] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

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

[0053] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[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. Therefore, the first component discussed below may be referred to as the second component without departing from the teachings of this application. As used herein, the term "and / or" includes all combinations of any one and more of the associated listed items.

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

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

[0057] The swarm method involves setting up multiple launch sites around the assembly site, similar to a swarm of bees, and assigning launch missions to each launch site for launch.

[0058] Swarm-style space launch systems, such as Figure 1 As shown, it includes: honeycomb system, nectar source system, bee journey system, and bee system.

[0059] The cellular system is the technical area for space launches. Figure 1 Within the central circular dotted line area, it is connected to the honey source system through the bee path system to complete the star-arrow combination.

[0060] The Hive system includes a space launch vehicle storage area / factory, a space launch vehicle testing facility, a satellite storage and testing facility, a rocket storage and testing facility, a satellite-rocket docking facility / workstation, a satellite-rocket assembly transfer facility / workstation, and connecting roads within the Hive.

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

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

[0063] Satellite storage and testing facilities are used to store satellites and to complete satellite assembly and testing.

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

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

[0066] The spacecraft-rocket assembly transfer station / workstation is used to transfer the spacecraft-rocket assembly to the space launch vehicle.

[0067] The connecting roads inside the hive connect various locations within the hive system, enabling road traffic and transportation between these locations.

[0068] One or more basic units can be set within the hive, depending on the 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 U-shaped structure in the nectar source system is the launch site.

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

[0071] The launch pad is where the space launch vehicle is parked before ignition and launch.

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

[0073] A launch site typically has multiple launch pads to support multiple space launch vehicles operating simultaneously.

[0074] The straight-line distance between the hive system and the nectar source system is 5-150 kilometers, enabling the coordinated operation of the satellite-rocket combination within a small area to complete multiple launch missions, allowing satellites in different orbits to be launched from different launch sites in a short period of time. The 5km distance is a safe distance to account for potential damage to the hive in the event of an accident in the nectar source system; the 150km distance is to ensure that the bees' maneuvering time within the hive system is not too long.

[0075] The Swarm system connects the launch site and the Swarm system, and includes multiple access routes. Figure 1 In the process, the launch vehicle, acting as a "bee," travels on roads, and the Bee Path system facilitates the smooth arrival of the space launch vehicle at the launch site.

[0076] The Bee system comprises multiple launch units, which are the essential elements required to complete a space launch. A launch unit includes a satellite, rocket, launch vehicle, and operational support equipment; these are all fundamental elements necessary for a space launch and can independently carry out space launch missions within a certain scope.

[0077] The swarm-based space launch mission scheduling system is the brain of swarm launches, the core of effectively realizing swarm launches, and undertakes the core functions of system structure building, reorganization, and mission distribution. It is crucial for the effectiveness and enhancement of the entire swarm-based space launch system. For example... Figure 2As shown, the swarm-based 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 real-time data acquisition subsystem, and exercise and training subsystem.

[0078] The task resource data pool is connected to the task data management subsystem, task planning subsystem, task implementation process control subsystem, task process demonstration / reproduction subsystem, exercise and training subsystem, and task real-time data acquisition subsystem, and is used to store task resource data.

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

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

[0081] — Launch unit data management, including personnel, equipment, and supplies used for swarm-style space launches;

[0082] —Supports unit data management, including logistical support personnel, equipment, and materials for supporting swarm-style space launches;

[0083] —Data management of available aerospace products, including available satellites, launch vehicles and their associated spare parts;

[0084] —Storage warehouse data management, including warehouse information used to store satellites, rockets, and launch vehicles;

[0085] —Data management of product assembly and testing facilities, including facility 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 location locations;

[0087] —Data management of launch sites and locations, including data on launch sites, locations, and their status;

[0088] — Launch procedure data, including the basic procedures for swarm space launches, the coupling constraints between procedures, and the time required for each task;

[0089] —Resource data import: Available resource data can be imported from the resource database in real time;

[0090] —Task data export: Data in the task pool can be exported 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, task resource data pool initialization involves two steps: first, using the data import function to load resource data into the task data pool; second, standardizing the data of tasks assigned by superiors and constraint coupling conditions to form a task list and loading it into the task data pool.

[0093] —Repair task process data, backing up data from the task data pool to the task database in real time.

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

[0095] The task planning subsystem includes a shortest path planning module, a dynamic contribution calculation module, a workshop scheduling module based on the completion of all tasks, a workshop scheduling module based on task contribution, and a 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 is used to calculate the contribution of each space launch mission. Due to differences in the number, size, function, and performance of satellites launched in each space launch, the contribution of each launch to the mission objective will also vary. The dynamic contribution calculation module can calculate the contribution of each space launch to the mission objective in real time, so that the mission planning subsystem can prioritize launches with higher contributions.

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

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

[0100] The draft generation module is used to generate a swarm launch draft. If all tasks can be completed on schedule, the swarm launch draft is generated based on the workshop scheduling module based on the completion of all tasks. If the launch time is insufficient to complete all tasks, the swarm launch draft is generated based on the workshop scheduling module based on the contribution of tasks.

[0101] Based on the assigned mission, the mission planning subsystem uses available resources to generate a swarm-style space launch draft in real time under given constraints.

[0102] 1) Initial draft design:

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

[0104] (2) Use mission planning and evaluation methods to evaluate the draft of swarm-style space launch;

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

[0106] 2) Scheme design during task implementation:

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

[0108] (2) Generating a mission reset point; When a space launch mission is in progress, such as during the docking of a satellite and rocket, it is impossible to stop the mission to accept a new mission. Therefore, a "mission safety reset point algorithm" is required. For a launch vehicle, a "mission safety reset point" is generally defined as the launch vehicle completing one launch mission, but the next launch mission has not yet started. This is a "mission safety reset point" for the launch vehicle. Just like a crane lifting an object, it must stop before a new mission can be set for it.

[0109] (3) Using the set of mission reset points as the starting point of the mission, call the mission planning subsystem to generate a draft of a swarm-style space launch;

[0110] (4) Use 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 to evaluate swarm launch proposals and write the proposals and evaluation results into the mission resource data pool. Based on mission objectives, the planning and evaluation subsystem assesses the mission completion rate and implementation risks of the swarm launch proposals in real time. Mission completion assessment compares and evaluates the mission completion rate of the space launch plans based on the mission list and mission priorities. Mission risk assessment compares and evaluates the implementation risks of the space launch plans based on warning line standards.

[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 standardization to form task data. The task data management subsystem also reads 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 approve the swarm launch draft and evaluate the results. If the approval is successful, the swarm launch draft is converted into a launch plan output and the launch unit and support unit are notified. If the approval is unsuccessful, the swarm launch draft is regenerated.

[0115] The mission execution process control subsystem adjusts the launch target in real time based on the actual mission situation and designates and issues swarm launch commands:

[0116] 1) Task Startup:

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

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

[0119] (3) Receive notifications from the task planning subsystem and approve drafts:

[0120] (4) Based on the assessment results, determine whether to replan: If replanning is required, at least one of the available resources, mission list or constraints should be modified, and the work of developing the swarm launch draft in (2) above should be repeated; otherwise, the space launch draft should be approved as a formal plan.

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

[0122] 2) Task process control:

[0123] (1) Real-time task data is collected through the task data acquisition subsystem;

[0124] (2) A new swarm launch scheme can be developed through the mission planning subsystem when the following situations occur:

[0125] —A new task is assigned by the superior or the original task plan is changed;

[0126] —The mission environment has changed, and the current plan cannot be completed as scheduled;

[0127] —A launch unit or support unit has been forced to withdraw from the mission due to a malfunction, or its capabilities have been significantly reduced, making it impossible to complete the current plan as scheduled;

[0128] —A certain resource has been damaged, and the current plan cannot be completed as scheduled.

[0129] (3) Receive notification from the mission planning subsystem and approve the swarm launch draft: Based on the evaluation results, determine whether to replan the swarm launch draft: If replanned, at least one of the available resources, mission list or constraints should be modified, and the work of (2) above in developing the swarm launch draft should be repeated; otherwise, approve the launch draft as a formal plan.

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

[0131] The mission real-time data acquisition subsystem is used to collect mission real-time data and update the data in the mission resource data pool. Specifically, the mission real-time data acquisition subsystem gathers real-time data on the implementation progress of the swarm launch scheme and the actual mission implementation data through launch and support unit data reporting, video surveillance networks, and the deployment and sensing of various sensors, and corrects the data in the mission resource data pool accordingly.

[0132] The exercise and training subsystem is used to drive system-wide exercises and personnel training using a task resource data pool. This subsystem is only applicable when the system is operating in system-wide exercise and personnel training mode. Based on the requirements of system-wide exercises and personnel training, it receives guidance content from the directing group in real time, processes the data through data normalization, and loads it into the task resource data pool. It constructs a human-computer interaction interface between the exercise and training directing group and the system, manages the task resource data pool in real time according to the directing group's requirements, and uses the task resource data pool to drive the orderly implementation of system-wide exercises and personnel training. "Directing" is a term used in military exercise and training; the "directing group" refers to a group of people who set up exercise scenarios and content in real time based on the progress of military exercise and training.

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

[0134] (2) During the exercise and training, the task resource data pool was modified through the real-time data acquisition subsystem.

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

[0136] The task process demonstration / reproduction subsystem, connected to the task data management subsystem, uses data from the task resource data pool to simulate and display the actual task implementation. It also loads historical task data through the data management subsystem to reproduce the implementation process of past tasks. During task implementation, it uses animations, forms, and network diagrams to display the entire process in real time, including task assignment, plan formulation, task implementation, anomaly handling, task results, and performance analysis, facilitating real-time monitoring of task progress and trends. After task completion, near real-time replay of the task resource data accurately and completely reproduces the task implementation process, assisting in fault analysis, defect identification, and improvement planning.

[0137] According to a second specific embodiment of the present invention, the present invention provides a swarm-based space launch scheduling method, which adopts the swarm-based space launch mission scheduling system of the first specific embodiment, such as... Figure 3 As shown, it includes the following steps:

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

[0139] The mission planning subsystem generates a draft of a swarm launch, 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] The shortest path is calculated by using the current work site of each launch mission as the starting point and employing Dijkstra's algorithm to find the shortest path from that site to the next work site. Dijkstra's algorithm, also known as the greedy algorithm, is based on the idea of ​​starting from the initial point and gradually expanding the set of points 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 of the launched satellite, its networking value, its time value, and its opportunity value. Inherent value reflects the cost of the satellite; the higher the cost, the higher the inherent value. Networking value reflects the value of the satellite in networking with other satellites; the higher the usability after successful networking, the higher the networking value. Time value reflects the urgency of the need for the launched satellite; the more urgent the need, the higher the time value. Opportunity value reflects the number of launch opportunities available for the satellite; the more opportunities, the lower the opportunity value. Therefore, the contribution of each space launch is calculated using the inherent value of the launch mission, its networking value, its time value, and its opportunity value.

[0144] The inherent value of the launch mission:

[0145] Each satellite has a different function, performance, and other attributes, resulting in varying practical value. Since its practical value is sometimes difficult to assess, we typically categorize the satellite's intrinsic value (V) based on its construction cost. use Divided into 5 levels, as shown in 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 sequentially from 1 to 5.

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

[0149] Satellites are conventionally classified according to their orbital altitude (low Earth orbit, medium Earth orbit, high Earth orbit, etc.), their purpose (scientific satellites, technological experimental satellites, and application satellites), function (communication satellites, remote sensing satellites, and navigation satellites), and size (large satellites, small and medium-sized satellites, microsatellites, nanosatellites, and picosatellites). The functional performance of a satellite is usually related to its cost; therefore, we choose the cost of a satellite to evaluate its inherent value.

[0150] Satellites costing over 2 billion are valued at 5.

[0151] Satellites costing between 1 billion and 2 billion are valued at 4.

[0152] Satellites costing between 100 million and 1 billion are valued at 3.

[0153] Satellites costing between 10 million and 100 million have an inherent value set at 2;

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

[0155] A certain launch mission M i It can launch m satellites, and the intrinsic value of the j-th satellite is... Then launch mission M i The intrinsic value is obtained using Formula 2:

[0156]

[0157] in, Indicating the inherent value of the launch mission, M i Let m represent a launch mission, and m represent the launch mission M. i The number of satellites that can be launched, where j represents the j-th satellite. Let m represent 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] During network deployment, in addition to the varying actual usability of each satellite, the satellites also gain network value from collaborative satellite operations upon successful network deployment. The network gain value V is calculated based on the actual value gained after successful network deployment. add Divided into 5 levels, as shown in 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 sequentially from 1 to 5.

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

[0163] Large constellations or constellations costing over 100 billion yuan have a network value of 5, such as the BeiDou global navigation constellation;

[0164] Medium-sized constellations or constellations costing over 10 billion are valued at 4 for networking, such as the U.S. Navy's tactical communications network;

[0165] The networking value of small constellations or constellations costing more than 1 billion yuan is set at 3, such as the "4+1+4" Chinese Siwei New Generation Commercial Remote Sensing Satellite System.

[0166] The networking value of a constellation that works in collaboration with multiple satellites or costs more than 100 million is set at 2, such as the Fengyun satellite network;

[0167] The networking value of a constellation consisting of several small satellites or costing less than 100 million is set at 1.

[0168] The gain value obtained after a successful network formation cannot be simply distributed equally among the launches of each satellite. In fact, if a network consists of 3 satellites, the network gain value can only be obtained after all 3 satellites have been successfully launched.

[0169] Consider a satellite network consisting of n satellites. The network gain value after successful network formation is V. add The networking gain value of launching the h-th satellite is... That is, the networking gain value of the h-th satellite is obtained using Formula 4:

[0170]

[0171] A satellite constellation consisting of n satellites has a network value of V after successful network formation. add The networking gain value of the h-th satellite in this network is Both n and h are natural numbers greater than or equal to 1.

[0172] A certain launch mission M i It can launch m satellites, of which l satellites have networking value. Among the l satellites, the k-th satellite is the j-th satellite in the networking satellite group, and its networking gain value is... Then launch mission M i Network value Formula 5 is used to obtain it:

[0173]

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

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

[0176] Time value of a launch mission:

[0177] In specific situations, due to varying time requirements for satellite usage, the value of each space launch is time-dependent. For example, in an emergency rescue launch for a space station, because rescue time is extremely precious, the earlier the launch, the greater the chance of safe rescue for the astronauts. Missing the optimal rescue window could lead to a significant risk of astronaut loss of life. The time value V is assigned according to the urgency of the usage time. tim Divided into 5 levels, as shown in Formula 6:

[0178]

[0179] Among them, 5 has the highest value, and 1 has the lowest value, with the value increasing sequentially from 1 to 5. tim1, tim2, tim3, tim4, and tim5 refer to the urgency of the task.

[0180] TIMM5 ​​indicates a general space launch mission with an urgency level of "common," typically without specific time requirements. Most space launch missions fall into this category, such as ordinary remote sensing satellites, communication satellites, and space technology demonstration satellites.

[0181] tim4 indicates a space launch mission with an urgency level of "urgent". These missions are typically space engineering projects with significant commercial or social value that require urgent deployment by the nation or society. Space launch missions related to this can be classified as "urgent", such as the launch mission for the construction of the BeiDou satellite navigation system.

[0182] tim3 indicates a space launch mission with an urgency level of "extremely urgent," which usually refers to a space engineering construction mission urgently needed by the nation, such as the launch mission of the Mars probe "Tianwen-1."

[0183] tim2 indicates a space launch mission with an urgency level of "critical". This usually refers to missions urgently needed for national disaster relief, space emergency rescue, and military operations, such as emergency rescue launch missions for space stations.

[0184] tim1 indicates a space launch mission with an urgency level of "top urgent", which usually refers to a space launch mission related to space warfare.

[0185] A certain launch mission M i It can launch m satellites, where the time value of the j-th satellite is . The time value of the launch mission The result is obtained using formula 7:

[0186]

[0187] in, M represents the time value of a launch mission. i Let m represent a launch mission, and m represent the launch mission M. i The number of satellites that can be launched, where the time value of the j-th satellite is...

[0188] The value of the launch mission's opportunity count:

[0189] Due to time constraints or evaluation periods, the number of launch windows for each satellite in the launch window information is limited, and the number of available launch windows varies for different satellites. This problem can be solved by establishing a minimum slack priority principle, where slack specifically refers to the number of available launch windows for each space launch within a certain period of time.

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

[0191] Launch Mission M i The task cycle is T cyc During the evaluation period D tim There are usually w available launch windows. The number w available for launch windows 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, and T cyc D represents the mission cycle of the launch mission. tim This represents the evaluation period, where w is a natural number greater than or equal to 1.

[0194] Among them, the evaluation period D tim This refers to a time span of assessed space launches, such as prioritizing all space missions scheduled to launch in May, June, and July of 2024. In this case, D... tim The value is 3 months. The value of the launch mission's opportunity count. The result is obtained using formula 9:

[0195]

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

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

[0198] The contribution of a launch mission is determined using Formula 10, which considers the mission's inherent value, networking value, time value, and opportunity value.

[0199]

[0200] Right now

[0201] in, Indicates the contribution to the launch mission. This indicates the inherent value of the launch mission. This indicates the networking value of the launch mission. Indicates the time value of a launch mission. This represents the opportunity value of a launch mission. α, β, γ, and ξ are weighting coefficients, and the sum of α, β, γ, and ξ is 1.

[0202] In a preferred embodiment, α, β, γ, and ξ are taken as 0.3, 0.2, 0.4, and 0.1, respectively.

[0203] Steps S11 and S12 can be performed simultaneously or asynchronously.

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

[0205] Based on the basic procedures of each space launch, namely rocket unloading test, satellite unloading test, rocket-satellite docking test, launch vehicle unloading test, transfer of rocket-satellite assembly to launch vehicle, launch unit transfer, launch unit pre-launch preparation, launch, launch vehicle post-launch recovery, and launch vehicle withdrawal, a priority-based heuristic scheduling algorithm is used to schedule and sort all space launch missions.

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

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

[0208] Define priority rules based on the assumption that all tasks can be completed on schedule. For a task set M = {M1, M2, ..., M...} n Each task M to be completed in} i First, the first-come, first-served (FCFS) priority principle is specified, that is, the one with the earlier launch window has priority; second, when the FCFS priorities are the same, the least chance (LLF) priority principle is followed, that is, the one with the fewest launch windows has priority; where i and n are both natural numbers greater than 1.

[0209] Sort according to priority rules;

[0210] Call the shortest path planning module to perform M for each space launch mission. i The shortest path is selected and the corresponding resources are allocated. These resources include the satellite, rocket, launch vehicle, assembly and testing facilities, mobile routes, and launch site. The purpose of the shortest path planning module is to allocate resources. Regardless of whether the ranking is based on priority rules or contribution, the ranking only determines which launch will be carried out first; the resource allocation for the launch needs to be planned according to 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 assembly and testing stations for the satellite, and it is necessary to determine which station to use; after the satellite and rocket are combined, there are also multiple launch vehicles available for launch, and it is also necessary to determine which launch vehicle will perform the launch mission, and so on—it is necessary to plan the shortest path to allocate resources.

[0211] First Come First Service (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 according to the order in which they arrive. It will first select one or more jobs at the head of the queue from the ready queue, load them into memory, allocate the necessary resources, create processes, and then put them into the "ready queue". The process scheduler will only allocate the processor to other processes after the process has finished running or is blocked by some event.

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

[0213] S14: The workshop scheduling module based on mission contribution sorts all space launch missions according to their contribution.

[0214] If the launch time is insufficient to complete all tasks, proceed to steps S12 and S14.

[0215] S15: The draft generation module generates a swarm launch draft. If all tasks can be completed on schedule, the swarm launch draft is generated according to the workshop scheduling module based on the completion of all tasks. If the launch time is insufficient to complete all tasks, the swarm launch draft is generated according to the workshop scheduling module based on task contribution.

[0216] S2: 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.

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

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

[0219] Specifically, the mission data acquisition subsystem continuously (until the mission ends) collects data from various launch units, support units, aerospace products, product storage warehouses, product assembly and testing facilities, traffic conditions, launch site locations, and other data, and updates the data in the mission resource data pool in real time. New missions and changes to constraints issued by higher authorities 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 process can be reproduced through the task process demonstration / reproduction subsystem.

[0221] This plan analyzes the demand for launching a large number of satellites in different orbits in the short term, assesses the practical need to build or utilize existing systems to construct a swarm-type space launch system; while building or utilizing existing systems to construct a swarm-type space launch system, it develops a swarm-type space launch scheduling system and deploys it in the scheduling hall; using the swarm-type space launch scheduling system, it organizes full-system drills and training for relevant personnel; and using the swarm-type space launch scheduling system, it achieves the formal operation of the swarm-type space launch system.

[0222] In specific situations, such as large-scale or wide-ranging disaster relief operations, high-density observation of hotspot areas, or enhancement of satellite communications in a specific region during a particular period, there is a need to launch numerous satellites in different orbits within a short period of time.

[0223] This solution provides a technical approach for an online automatic planning and scheduling system for launching a large number of satellites in different orbits in a short period of time. Based on a swarm-style space launch system, it schedules space launch missions and effectively solves problems such as low efficiency, difficulty in optimizing plans, and susceptibility to errors associated with manual scheduling and planning for large-scale satellite launches.

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

[0225] Exemplary embodiments of the present invention have been specifically shown and described above. It should be understood that the present invention is not limited to the detailed structures, arrangements, or implementations described herein; rather, the present invention is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended claims.

Claims

1. A swarm-based space launch mission scheduling system, characterized in that, include: Task planning subsystem, planning evaluation subsystem, task resource data pool, and task implementation process control subsystem; The task planning subsystem is connected to the task resource data pool and is used to generate swarm launch drafts. The task planning subsystem includes a shortest path planning module, a dynamic contribution calculation module, a workshop scheduling module based on the completion of all tasks, 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; the dynamic contribution calculation module calculates the contribution of each space launch mission using the following formula: ； in, Indicates launch mission M i Contribution Indicates launch mission M i Its inherent value Indicates launch mission M i The networking value, Indicates launch mission M i The value of time Indicates launch mission M i The opportunity value, where α, β, γ, and ξ are weighting coefficients, and the sum of α, β, γ, and ξ is 1; the intrinsic value reflects the cost of the satellite; the networking value reflects the value of the satellite to be launched in networking with other satellites; the time value reflects the urgency of the need for the satellite to be launched; and the opportunity value reflects how many opportunities the satellite to be launched has. The workshop scheduling module based on the completion of all tasks is used to schedule and sort all space launch missions according to the shortest path. The workshop scheduling module based on task contribution is used to schedule and sort all space launch missions according to their contribution. The draft generation module is used to generate a swarm launch draft. If all tasks can be completed on schedule, a swarm launch draft is generated based on the workshop scheduling module based on task completion. If the launch time is insufficient to complete all tasks, a swarm launch draft is generated based on the workshop scheduling module based on task contribution. The planning evaluation subsystem and the mission planning subsystem are connected and used to evaluate the swarm launch draft and write the swarm launch draft and 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 approve the swarm launch draft and evaluation results, and to convert the swarm launch draft into a launch plan output. The swarm-style space launch mission scheduling system is the scheduling system for swarm-style space launch systems. Swarm-style means that multiple launch sites are set up around the assembly site, and launch missions are assigned to each launch site for launch. The swarm-style space launch system includes: honeycomb system, honey source system, bee path system, and bee system. The honeycomb system connects the technical area and the honey source system for space launch via the honeycomb path system, and is used to complete the satellite-rocket combination. There are multiple honey source systems surrounding the honeycomb system. Each honey source system includes multiple launch sites, and each launch site includes multiple launch pads and a standby area. The launch pads are where the space launch vehicles are parked before ignition and launch, and the standby area is where the space launch vehicles wait to enter the pre-launch procedure. The cellular system connects the launch site and the cellular system, and includes multiple access routes; The Bee system comprises multiple launch units, which are the essential elements required to complete a space launch; each launch unit includes a satellite, rocket, launch vehicle, and operational support equipment.

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

3. The swarm-based space launch mission scheduling system according to claim 2, 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. It is used to simulate and display the actual situation during task implementation using data in the task resource data pool, and is also used to load historical task data through the data management subsystem to reproduce the historical task implementation process.

4. The swarm-based space launch mission scheduling system according to claim 1, characterized in that, It also includes a task real-time data acquisition subsystem, which is connected to the task resource data pool and is used to collect task real-time data and update the data in the task resource data pool.

5. The swarm-based 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 task resource data pool and is used to drive the whole system's exercises and personnel training using the task resource data pool.

6. A swarm-based space launch mission scheduling method, characterized in that, The swarm-based space launch mission scheduling system according to any one of claims 1-5 includes the following steps: The mission planning subsystem generates a draft of a swarm launch; 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 approves the swarm launch draft and evaluation results, and transforms the swarm launch draft into a launch plan output.

7. The swarm-based space launch mission scheduling method according to claim 6, characterized in that, The mission planning subsystem generates a draft swarm launch plan, 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. Once all missions are completed, the workshop scheduling module will schedule and sort all space launch missions based on the shortest path. The workshop scheduling module based on task contribution sorts all space launch missions according to their contribution. The draft generation module generates a swarm launch draft. If all tasks can be completed on schedule, the swarm launch draft is generated based on the workshop scheduling module based on task completion. If the launch time is insufficient to complete all tasks, the swarm launch draft is generated based on the workshop scheduling module based on task contribution.

8. The swarm-based space launch mission scheduling method according to claim 7, characterized in that, The workshop scheduling module based on the completion of all missions schedules and sorts all space launch missions according to the shortest path, including: Extract mission features, including the time window for space launch; Define priority rules based on the assumption that all tasks can be completed on schedule. For a task set M = {M1, M2, ..., M...} n Each task M to be completed in} i Prioritize those with earlier launch windows, then prioritize those with fewer launch windows; where i and n are both natural numbers greater than 1. Sort according to priority rules; Call the shortest path planning module to perform M for each space launch mission. i Select the shortest path and allocate the corresponding resources, including satellites, rockets, launch vehicles, assembly and testing facilities, mobile routes, and launch sites.

Images