Low-orbit giant constellation resource management and control method, device, equipment and medium

Abstract

The embodiment of the invention provides a low-orbit giant constellation resource management and control method, device and equipment and a medium, and relates to the technical field of low-orbit giant constellation system architecture design. The method comprises the following steps: dividing a constellation operation sky domain into a plurality of sky domain partitions according to a C-60 molecular structure, dividing satellites in each satellite cluster into a main satellite and a plurality of auxiliary satellites at each operation moment, generating a satellite cluster division table of each satellite, and formulating a management rule base, and each satellite operates in orbit according to the stored management rule base and the satellite cluster division table. A low-orbit giant constellation is uniformly divided into a plurality of satellite clusters without omission according to a C-60 molecular structure, so that the pressure of a ground centralized management and control center is relieved, constellation resource management and control and task management distributed deployment are realized, meanwhile, a satellite cluster division table is determined, the in-orbit calculation amount of a satellite is reduced, the task response speed is increased, and the task management efficiency is improved. The method is suitable for the satellite detection task of the low-orbit giant constellation on the time-sensitive moving target.

Description

Technical Field

[0001] The present application relates to the technical field of low-earth orbit (LEO) mega-constellation architecture design. Specifically, it relates to a method, device, equipment, and medium for resource management and control of LEO mega-constellations. Background Art

[0002] LEO mega-constellations, with their characteristics of a huge number of nodes, seamless spatio-temporal coverage, and diverse platform payload capabilities, have always been a hot research topic in the aerospace field worldwide. However, they also face technical challenges such as constellation management and control, mission management, and space-ground / inter-satellite network transmission.

[0003] For large-scale constellations with thousands of satellite nodes, the strategies and methods for resource management and control and mission management are fundamental issues. The scientific and efficient design of the mega-constellation management and control strategy directly affects its overall performance. In traditional constellation networks with dozens of satellite nodes, centralized ground control strategies are generally used for resource management and control and mission management. This strategy can better complete the functions of constellation resource management and control and mission management when the number of satellite nodes is small. However, when the constellation scale grows exponentially, the centralized ground mission control strategy becomes somewhat ineffective. Especially for satellite reconnaissance missions of time-sensitive moving targets on land, sea, and air, limited ground nodes, complex transmission links, and long time delays make it difficult for the centralized ground mission operation control strategy to meet mission requirements.

[0004] Therefore, a more efficient resource management and control strategy for LEO mega-constellations is urgently needed. Summary of the Invention

[0005] Based on the above technical problems, the embodiments of the present application provide a method, device, equipment, and medium for resource management and control of LEO mega-constellations, aiming to more efficiently manage and control the resources of LEO mega-constellations to cope with satellite reconnaissance missions of time-sensitive moving targets.

[0006] The first aspect of the embodiments of the present application provides a method for resource management and control of LEO mega-constellations, the method including:

[0007] Dividing the constellation operation celestial domain into multiple celestial domain partitions according to the C-60 molecular structure, and the satellites in each celestial domain partition form a satellite cluster of the celestial domain partition;

[0008] According to the operation trajectories of the respective satellites, at each operation moment, the satellites in each satellite cluster are divided into a main star and multiple auxiliary stars;

[0009] In response to the completion of the division of the satellites in each satellite cluster at each operation moment within the operation cycle, generating a satellite cluster division table for each satellite, the satellite cluster division table at least including: operation moment, belonging satellite cluster, belonging main star, and controlled auxiliary stars;

[0010] Formulate a management rule library. The primary satellite controls each secondary satellite within the star cluster according to the management rule library, and the secondary satellite executes the task instructions sent by the primary satellite within the star cluster according to the management rule library;

[0011] Store the management rule library and the star cluster division table in each satellite, and each satellite operates in orbit according to the management rule library and the star cluster division table.

[0012] Optionally, each satellite in the celestial region partition forms a star cluster of the celestial region partition. The method includes:

[0013] Calculate the position of each satellite at each running moment within the running period according to the predicted running trajectories of the satellites;

[0014] Calculate the angular distance formed between the line connecting each satellite to the earth's center and the line connecting the center of each celestial region partition to the earth's center at each running moment, and divide the satellite into the star cluster of the celestial region partition with the smallest angular distance;

[0015] When there are multiple celestial region partitions with the smallest angular distance at the same time, divide the satellite into the star clusters of the multiple celestial region partitions.

[0016] Optionally, divide the satellites at each running moment and in each star cluster into one primary satellite and multiple secondary satellites. The method includes:

[0017] According to the angular distance formed between the line connecting each satellite in each star cluster to the earth's center and the line connecting the center of the celestial region partition of the star cluster to the earth's center at each running moment within the running period, divide the satellite with the smallest angular distance into the primary satellite of the star cluster, and divide the other satellites within the star cluster into secondary satellites;

[0018] Set a primary satellite switching time threshold, and adjust the division of primary satellites and secondary satellites in each star cluster at each moment according to the time threshold.

[0019] Optionally, each satellite operates in orbit according to the management rule library and the star cluster division table. The method includes:

[0020] In response to receiving a task from the ground control center, the primary satellite within the star cluster divides the task into multiple subtasks and assigns them to each satellite within the star cluster for execution;

[0021] The secondary satellites within the star cluster execute the subtasks assigned by the primary satellite within the star cluster and transmit task interaction information to other secondary satellites;

[0022] Each satellite within the star cluster feeds back the execution status of the subtask to the primary satellite within the star cluster;

[0023] The main satellite in the star cluster regularly feeds back the execution status of the mission to the ground control center.

[0024] Optionally, each satellite operates in orbit according to the management rule base and the star cluster partition table, and the method further includes:

[0025] The auxiliary satellite in the star cluster periodically transmits working status information to the primary satellite in the star cluster, wherein the working status information is used to represent the normal working status of the satellite;

[0026] The main satellite in the star cluster periodically transmits the working status information of each satellite in the star cluster to the ground control center.

[0027] Optionally, each satellite operates in orbit according to the management rule base and the star cluster partition table, and the method further includes:

[0028] Each satellite in the star cluster checks the stored star cluster partition table at each operating moment;

[0029] Before the main star in the star cluster is converted into an auxiliary star at the next operating moment, the task status information in the star cluster is transmitted to the main star that takes over at the next moment, and the task status information at least includes: subtask allocation status and subtask execution status.

[0030] Optionally, each satellite operates in orbit according to the management rule base and the star cluster partition table, and the method further includes:

[0031] When the primary star in the star cluster is replaced, the secondary star in the star cluster is aligned with the new primary star and transmits working status information;

[0032] When the auxiliary star in the star cluster flies to the next star cluster, it is aimed at the main star of the next star cluster and transmits the working status information.

[0033] Optionally, each satellite operates in orbit according to the management rule base and the star cluster partition table, and the method further includes:

[0034] At each operating moment, the satellites in the star cluster determine the identity of the primary or secondary satellite at the current operating moment according to the stored star cluster division table;

[0035] When the satellite within the star cluster is the primary star at the current operating moment, it controls and manages each secondary star within the star cluster according to the management rule library, including: receiving the working status information and task status information transmitted by each secondary star within the star cluster, and transmitting the working status information and task status information to the ground control center; receiving the task information sent by the ground control center, dividing the task into multiple subtasks and allocating them to each secondary star within the star cluster for execution; before flying away from the star cluster, transmitting the task status information within the star cluster to the succeeding primary star;

[0036] When the satellite within the star cluster is a secondary star at the current operating moment, it executes the instructions issued by the primary star within the star cluster according to the management rule library, including: receiving the subtasks issued by the primary star within the star cluster; transmitting the execution status of the subtasks to the primary star within the star cluster, and transmitting task interaction information to other secondary stars within the star cluster; regularly transmitting the working status information to the primary star within the star cluster; after flying away from the star cluster, aligning with the primary star of the next star cluster and transmitting the working status information.

[0037] The second aspect of the embodiment of the present application provides a low-earth orbit giant constellation resource management and control device, and the device includes:

[0038] A celestial domain partition module, configured to divide the constellation operating celestial domain into multiple celestial domain partitions according to the C-60 molecular structure, and the satellites in each celestial domain partition form the star cluster of the celestial domain partition;

[0039] A satellite division module, configured to divide the satellites in each star cluster at each operating moment into one primary star and multiple secondary stars according to the operating trajectories of the respective satellites;

[0040] A star cluster division table generation module, configured to generate a star cluster division table for each satellite in response to the completion of the division of the satellites in each star cluster at each operating moment within the operating cycle, and the star cluster division table at least includes: operating moment, belonging star cluster, belonging primary star, controlled secondary stars;

[0041] A management rule library formulation module, configured to formulate a management rule library, the primary star controls and manages each secondary star within the star cluster according to the management rule library, and the secondary star executes the task instructions issued by the primary star within the star cluster according to the management rule library;

[0042] An on-orbit operation module, configured to store the management rule library and the star cluster division table in each satellite, and each satellite operates on orbit according to the management rule library and the star cluster division table.

[0043] Optionally, the celestial domain partition module includes:

[0044] A satellite position calculation sub-module, which is used to calculate the positions of the satellites at each running moment within the running period according to the predicted running trajectories of the satellites;

[0045] An angular distance calculation sub-module, which is used to calculate the angular distance formed between the line connecting the satellite to the earth's center and the line connecting the center of each celestial domain partition to the earth's center at each running moment, and divide the satellite into the cluster of the celestial domain partition with the smallest angular distance;

[0046] A multi-partition satellite division sub-module, which is used to divide the satellite into the clusters of the multiple celestial domain partitions when there are multiple celestial domain partitions with the smallest angular distance at the same time.

[0047] Optionally, the satellite division module includes:

[0048] A satellite identity division sub-module, which is used to divide the satellite with the smallest angular distance into the main star of the cluster and the other satellites in the cluster into auxiliary stars according to the angular distance formed between the line connecting each satellite in each cluster to the earth's center and the line connecting the center of the celestial domain partition of the cluster to the earth's center at each running moment within the running period;

[0049] A switching time threshold setting sub-module, which is used to set the main star switching time threshold and adjust the division of the main star and the auxiliary star in each moment and each cluster according to the time threshold.

[0050] Optionally, the on-orbit operation module includes:

[0051] A sub-task division sub-module, which is used to, in response to receiving a task from the ground control center, divide the task into multiple sub-tasks by the main star in the cluster and allocate them to each satellite in the cluster for execution;

[0052] A sub-task execution sub-module, which is used for the auxiliary stars in the cluster to execute the sub-tasks assigned by the main star in the cluster and transmit the task interaction information to other auxiliary stars;

[0053] A sub-task feedback sub-module, which is used for each satellite in the cluster to feedback the execution situation of the sub-task to the main star in the cluster;

[0054] A task execution situation feedback sub-module, which is used for the main star in the cluster to regularly feedback the execution situation of the task to the ground control center.

[0055] Optionally, the on-orbit operation module further includes:

[0056] A working state information transmission sub-module, which is used for the auxiliary stars in the cluster to regularly transmit the working state information to the main star in the cluster, and the working state information is used to characterize the normal working state of the satellite;

[0057] The working status information feedback sub-module is used for the primary satellite in the satellite cluster to regularly transmit the working status information of each satellite in the satellite cluster to the ground control center.

[0058] Optionally, the on-orbit operation module further includes:

[0059] The satellite cluster division table checking sub-module is used for each satellite in the satellite cluster to check the stored satellite cluster division table at each running moment;

[0060] The task status information transfer sub-module is used for the primary satellite in the satellite cluster to transfer the task status information in the satellite cluster to the succeeding primary satellite at the next running moment before being converted into a secondary satellite. The task status information at least includes: sub-task allocation situation and sub-task execution situation.

[0061] Optionally, the on-orbit operation module further includes:

[0062] The working status information transmission sub-module is used for when the primary satellite in the satellite cluster is replaced, the secondary satellite in the satellite cluster aligns with the new succeeding primary satellite and transmits the working status information;

[0063] The working status information transmission sub-module is used for when the secondary satellite in the satellite cluster flies to the next satellite cluster, it aligns with the primary satellite of the next satellite cluster and transmits the working status information.

[0064] Optionally, the on-orbit operation module further includes:

[0065] The identity confirmation sub-module is used for the satellite in the satellite cluster to determine the identity of the primary satellite or secondary satellite at the current running moment according to the stored satellite cluster division table at each running moment;

[0066] The primary satellite working sub-module is used for when the current running moment of the satellite in the satellite cluster is the primary satellite, to control each secondary satellite in the satellite cluster where it is located according to the management rule library, including: receiving the working status information and task status information transmitted by each secondary satellite in the satellite cluster and transmitting the working status information and task status information to the ground control center; receiving the task information sent by the ground control center, dividing the task into multiple sub-tasks and allocating them to each secondary satellite in the satellite cluster for execution; before flying away from the satellite cluster, transmitting the task status information in the satellite cluster to the succeeding primary satellite;

[0067] The secondary satellite working sub-module is used to execute the instructions sent by the primary satellite in the satellite cluster when the satellite in the cluster is a secondary satellite at the current running moment. The operations include: receiving the subtasks sent by the primary satellite in the cluster; transmitting the execution status of the subtasks to the primary satellite in the cluster and transmitting task interaction information to other secondary satellites in the cluster; regularly transmitting the working status information to the primary satellite in the cluster; after flying out of the cluster, aligning with the primary satellite of the next cluster and transmitting the working status information.

[0068] In the third aspect of the embodiments of the present application, an electronic device is provided. The electronic device includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the computer program is executed by the processor, it implements the low-earth orbit giant constellation resource management and control method in the first aspect of the embodiments of the present application.

[0069] In the fourth aspect of the embodiments of the present application, a computer-readable storage medium is provided. A computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, it implements the low-earth orbit giant constellation resource management and control method in the first aspect of the embodiments of the present application.

[0070] In the fifth aspect of the embodiments of the present application, a computer program product is provided, including a computer program. When the computer program is executed by a processor, it implements the low-earth orbit giant constellation resource management and control method in the first aspect of the embodiments of the present application.

[0071] Through the low-earth orbit giant constellation resource management and control method of the embodiments of the present application, the constellation operation sky area is divided into multiple sky area partitions according to the C-60 molecular structure. There is a satellite cluster in each sky area partition. Then, according to the running trajectories of the respective satellites, the satellites in each running moment and each satellite cluster are divided into one primary satellite and multiple secondary satellites. The primary satellite is responsible for managing the secondary satellites in the cluster. Then, the cluster to which each satellite belongs at each running moment and the information in the cluster are written into the cluster division table, and the running rules of the satellites in the low-earth orbit giant constellation are saved as the management rule library and stored in each satellite. Each satellite operates normally in orbit according to the management rule library and the cluster division table and executes various tasks.

[0072] In this application, the huge low-earth orbit (LEO) giant constellation is evenly and without omission divided into multiple star clusters according to the C-60 molecular structure. Each star cluster is divided into a primary satellite and secondary satellites. The direct interaction between the original LEO giant constellation and the ground is transformed into information transmission among three levels: the ground control center, the star cluster, and the satellites within the star cluster, greatly reducing the pressure on the ground centralized management and control center and realizing the distributed deployment of constellation resource management and task management. At the same time, since the star cluster division table is established in advance according to the orbits of each satellite, each satellite only needs to look up the table to determine the star cluster it belongs to at the current running time, greatly reducing the on-orbit calculation amount of the satellite. And it executes various satellite imaging tasks according to the instructions issued by the primary satellite within the star cluster, improving the response speed to tasks and being more suitable for executing satellite imaging tasks for time-sensitive moving targets on land, sea, and air. Moreover, the method proposed in this application has universality and can be applied not only to the resource management scenario of the LEO giant constellation but also to various constellations of different scales. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] To more clearly illustrate the technical solutions of the embodiments of this application, the following will briefly introduce the drawings required for the description of the embodiments of this application. Obviously, the following drawings are only some embodiments of this application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0074] Figure 1 is a flowchart of a method for managing resources of a LEO giant constellation proposed in an embodiment of this application;

[0075] Figure 2 is a schematic diagram of celestial domain partitioning based on the C-60 molecular structure proposed in an embodiment of this application;

[0076] Figure 3 is a schematic diagram of the primary and secondary satellite division method proposed in an embodiment of this application;

[0077] Figure 4 is a schematic diagram of the information interaction process of a method for managing resources of a LEO giant constellation proposed in an embodiment of this application;

[0078] Figure 5 is a schematic diagram of the resource management process of a LEO giant constellation proposed in an embodiment of this application;

[0079] Figure 6 is a structural block diagram of a device for managing resources of a LEO giant constellation provided in an embodiment of this application;

[0080] Figure 7 is a schematic diagram of an electronic device shown in an embodiment of this application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0081] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0082] In the accompanying drawings, sometimes for clarity, the sizes of the constituent elements, the thicknesses of the layers, or the areas may be exaggerated. Therefore, any implementation of the present disclosure is not necessarily limited to the sizes shown in the figures, and the shapes and sizes of the components in the figures do not reflect the true proportions. In addition, the accompanying drawings schematically show ideal examples, and any implementation of the present disclosure is not limited to the shapes or values shown in the accompanying drawings.

[0083] In the related art, the control method for low-earth orbit mega-constellations usually directly controls each satellite by the ground control center. When a certain task needs to be executed, the ground control center sends the task requirements to a certain satellite in the constellation, and then uses this satellite as the cluster head of the cluster to establish a cluster for executing this task. The cluster head needs to obtain the relevant information of other satellites operating around, and screen out the satellites to be added to the cluster, and then the task information can be distributed to other satellites to execute the task. After the task is completed, the cluster will be disbanded, and until the next task is issued, a new cluster will be formed again according to the task requirements. Although this method can gather the resources of multiple satellites in the constellation to jointly execute tasks, since it does not have pre-divided clusters, it takes a lot of preparation time from receiving the task to starting to execute the task, which is not conducive to coping with the surveillance scenarios of time-sensitive targets. And because the communication resources between satellites and between satellites and the ground are limited, it takes a lot of communication resources to collect satellite information until a cluster is formed. The complex communication link will also bring longer time delays, increasing the pressure on the control of mega-constellations.

[0084] Based on the problems existing in the control method for low-earth orbit mega-constellations in the related art, a more efficient control method for low-earth orbit mega-constellation resources is proposed in the present application. For details, please refer to Figure 1 , Figure 1 which is a flowchart of a control method for low-earth orbit mega-constellation resources in the present application. As Figure 1 shown, the method may include steps S101 to S105:

[0085] Step S101: Divide the constellation operation sky area into multiple sky area partitions according to the C-60 molecular structure, and the satellites in each sky area partition form the cluster of the sky area partition;

[0086] Step S102: According to the operation trajectories of the respective satellites, divide the satellites at each operation moment and in each satellite cluster into one main satellite and multiple auxiliary satellites;

[0087] Step S103: In response to the completion of the division of the satellites at each operation moment and in each satellite cluster within the operation cycle, generate a satellite cluster division table for each satellite, where the satellite cluster division table at least includes: operation moment, affiliated satellite cluster, affiliated main satellite, and controlled auxiliary satellites;

[0088] Step S104: Formulate a management rule library, where the main satellite controls each auxiliary satellite within its satellite cluster according to the management rule library, and the auxiliary satellite executes the task instructions issued by the main satellite within its satellite cluster according to the management rule library;

[0089] Step S105: Store the management rule library and the satellite cluster division table in each satellite, and each satellite operates in orbit according to the management rule library and the satellite cluster division table.

[0090] In the embodiment of the present application, the method for managing the resources of a low-earth orbit giant constellation can generally be divided into two parts: an offline division process and an in-orbit working process. Among them, the offline division process refers to the process of formulating the division of each satellite in the low-earth orbit giant constellation into multiple satellite clusters. Specifically, first, the celestial domain in which the low-earth orbit giant constellation operates needs to be divided according to rules, and is evenly divided into multiple celestial domain partitions with reference to the C-60 molecular model; then, it is also necessary to calculate the positions of the satellites at each operation moment within one operation cycle of the satellites, and determine the satellite clusters to which the satellites belong at each operation moment according to the positions and the divided celestial domain partitions; then, according to the distance of the satellites from the center of the celestial domain, the satellites within each satellite cluster at the same operation moment are divided into one main satellite and multiple auxiliary satellites; finally, the satellite clusters to which each satellite belongs at each moment within the operation cycle and the identities of the satellites in the satellite clusters are recorded as a satellite cluster division table and stored in the satellites as the basis for in-orbit operation.

[0091] On the other hand, during the in-orbit working process of the satellites, the satellites query the stored satellite cluster division table at each operation moment to determine the affiliated satellite cluster and their identities in the satellite cluster, and execute tasks according to the formulated management rule library.

[0092] Through the two processes of offline division and in-orbit working, hierarchical management of each satellite in the low-earth orbit giant constellation is realized. And since the specific satellite cluster division method has been calculated during the offline division process, the calculation amount during the in-orbit operation of the satellites is reduced, and the occupation of satellite communication resources is also reduced. When it is necessary to execute the satellite imaging mission for time-sensitive targets, the satellite cluster in the corresponding celestial domain partition can be directly determined according to the target position to execute the mission, reducing the time from the user demand to the completion of the satellite cluster construction, and greatly accelerating the response speed of the satellite imaging mission for time-sensitive targets.

[0093] Step S101: Divide the celestial domain where the constellation operates into multiple celestial domain partitions according to the C-60 molecular structure, and the satellites in each celestial domain partition form a satellite cluster of the celestial domain partition.

[0094] In the embodiment of the present application, since it is necessary to formulate a division plan for each satellite in the constellation before the actual operation of the low-earth orbit giant constellation, it is necessary to divide all satellites according to a certain rule. Therefore, the principles to be followed should at least include two points: uniform division, without repetition or omission. Therefore, in the present application, a method of partitioning the extraterrestrial celestial domain with reference to the C-60 molecular structure is proposed. The C-60 molecule is a molecular structure similar to a football, also known as "buckminsterfullerene". This structure consists of 60 vertices and 32 faces, including 12 regular pentagonal faces and 20 regular hexagonal faces. Its shape is uniform and the areas of each part are relatively small, which can meet the needs of partitioning the celestial domain in the present application.

[0095] In a specific implementation manner, an embodiment of the present application provides a celestial domain division method, referring to Figure 2 , Figure 2 is a schematic diagram of celestial domain partitioning based on the C-60 molecular structure provided by an embodiment of the present application. As shown in Figure 2 , the celestial domain is divided into 12 regular pentagonal faces and 20 regular hexagonal faces according to the C-60 molecular structure, and the longitude and latitude of the center points of the 32 faces of the celestial domain partition are initialized as the basis for subsequent defining the celestial domain partition to which the satellite belongs, as shown in Table 1:

[0096] Table 1 Central coordinates of celestial domain partitions

[0097] Serial number Longitude Latitude Remarks Serial number Longitude Latitude Remarks 1 0.00 90.00 Regular pentagon 17. 0.00 52.62 Regular hexagon 2 36.00 26.57 Regular pentagon 18. 72.00 10.81 Regular hexagon 3 -72.00 26.57 Regular pentagon 19. -36.00 10.81 Regular hexagon 4 0.00 26.57 Regular pentagon 20. 36.00 10.81 Regular hexagon 5 72.00 26.57 Regular pentagon 21. -72.00 10.81 Regular hexagon 6 -36.00 26.57 Regular pentagon 22. 0.00 10.81 Regular hexagon 7 -72.00 -26.57 Regular pentagon 23. -72.00 -10.81 Regular hexagon 8 0.00 -26.57 Regular pentagon 24. 0.00 -10.81 Regular hexagon 9 72.00 -26.57 Regular pentagon 25. 72.00 -10.81 Regular hexagon 10 -36.00 -26.57 Regular pentagon 26. -36.00 -10.81 Regular hexagon 11 36.00 -26.57 Regular hexagon 27. 36.00 -10.81 Regular hexagon 12 0.00 -90.00 Regular hexagon 28. 36.00 -52.62 Regular hexagon 13 72.00 52.62 Regular hexagon 29. -72.00 -52.62 Regular hexagon 14 -36.00 52.62 Regular hexagon 30. 0.00 -52.62 Regular hexagon 15 36.00 52.62 Regular hexagon 31. 72.00 -52.62 Regular hexagon 16 -72.00 52.62 Regular hexagon 32. -36.00 -52.62 Regular hexagon

[0098] Dividing the celestial domain according to the C-60 molecular structure can not only achieve uniform division, without repetition or omission, but also determine the celestial domain partition to which the task target belongs in a timely manner when satellite reconnaissance tasks need to be carried out, and quickly issue task instructions to the satellite cluster in the corresponding celestial domain partition to execute the tasks.

[0099] Step S102: According to the running trajectories of the satellites, divide the satellites in each star cluster at each running moment into one main star and multiple auxiliary stars.

[0100] In the embodiments of the present application, after determining the division of the celestial domain partitions, it is also necessary to determine the celestial domain partitions to which each satellite belongs according to the orbits of the satellites. Since the satellites operate in space according to the planned orbits and periods, based on the orbital elements of each satellite, the positions of the satellite at each operating moment during the operating period can be deduced, and the celestial domain partition where the satellite is located can be calculated accordingly, and the satellite is divided into the satellite cluster of this celestial domain partition. According to the proximity principle, the satellites included in each satellite cluster are distinguished into a main satellite and multiple auxiliary satellites, and certain adjustments are made to ensure the rationality of the division of the main and auxiliary satellites.

[0101] Step S103: In response to the completion of the division of the satellites in each satellite cluster at each operating moment during the operating period, a satellite cluster division table of each satellite is generated. The satellite cluster division table at least includes: operating moment, belonging satellite cluster, belonging main satellite, and controlled auxiliary satellites.

[0102] In the embodiments of the present application, it is also necessary to form a satellite cluster division table for the satellite cluster division situation of each satellite at each operating moment during the operating period. Since the number of satellites in the low-earth orbit giant constellation is huge, each satellite does not need to store the position information of all satellites, but only needs to store the satellite cluster to which it belongs at each operating moment during its operating period, and the satellite information that may have an interaction relationship in these satellite clusters. This not only saves storage space, but also can realize the control of satellites according to a predetermined rule.

[0103] In the satellite cluster division table, at least all the operating moments of the satellite's operating period should be included, with an interval of a minimum time step. It is also necessary to include which satellite cluster the satellite belongs to at these operating moments and its identity in this satellite cluster. If the identity of the satellite in the satellite cluster is the main satellite, it is also necessary to know which auxiliary satellites are included in this satellite cluster at each operating moment when it serves as the main satellite, as well as the next main satellite and the handover moment; if the identity of the satellite in the satellite cluster is the auxiliary satellite, then it is necessary to determine the main satellite in the satellite cluster at each operating moment.

[0104] In the present application, the division of the satellites in each satellite cluster is carried out in the offline division stage. Although the in-orbit operation of the satellites is a dynamic process, by splitting according to the operating moments, the static positions of the satellites at multiple operating moments are obtained, and based on this, the members within the satellite cluster and the division of labor between the main and auxiliary satellites are determined. Therefore, the satellite cluster division method proposed in the present application is a "quasi-dynamic" division method, which not only saves the in-orbit calculation amount for satellite cluster division during the in-orbit operation of the satellites, but also can truly divide the satellite cluster according to the actual situation of the satellite operation.

[0105] In an alternative embodiment, there is also a situation where new satellites need to be added to the LEO mega-constellation or existing satellites are no longer available. Before the new satellites start operating, it is also necessary to calculate and store the cluster division table. For the existing satellites in the LEO mega-constellation, their cluster division tables need to be updated to add the newly added satellites or delete the unavailable satellites.

[0106] Step S104: Formulate a management rule library. The master satellite controls each slave satellite within the cluster according to the management rule library, and the slave satellite executes the task instructions issued by the master satellite within the cluster according to the management rule library.

[0107] In the embodiment of the present application, it is also necessary to specify a management rule library for the on-orbit operation of satellites, including the task division between the master satellite and the slave satellite, how the master satellite manages multiple slave satellites within the cluster, how the slave satellite receives instructions from the master satellite within the cluster, and the work process of receiving tasks from the master satellite, allocating tasks to each slave satellite, and reporting the task progress to the ground control center. These are the criteria for the on-orbit operation of each satellite in the LEO mega-constellation.

[0108] Step S105: Store the management rule library and the cluster division table in each satellite, and each satellite operates on orbit according to the management rule library and the cluster division table.

[0109] In the embodiment of the present application, after determining the division of each cluster at each operation moment, each satellite in the LEO mega-constellation also needs to operate on orbit according to the division result. Therefore, it is necessary to store the cluster division table of each satellite and the management rule library for on-orbit operation in the satellite, which is used as the basis for on-orbit operation. At each operation moment, only by looking up the table to determine the cluster to which it belongs and its identity in the cluster, it can execute the on-orbit work tasks according to the work rules in the management rule library. In this way, the control of the mega-constellation is more planned, and the task of satellite clustering is simplified, with simple operation and easy implementation.

[0110] Combined with the above embodiments, in one implementation manner, the present application also provides a method for resource control of a LEO mega-constellation. Each satellite in the celestial domain partition forms a cluster of the celestial domain partition, and specifically includes the following content:

[0111] First, according to the predicted operation trajectories of each satellite, calculate the positions of the satellites at each operation moment within the operation period.

[0112] In the embodiment of the present application, as described above, during the process of determining the cluster division table, according to its operation trajectory, it is necessary to determine the positions of each satellite at each operation moment within the operation period, and use this as the basis to determine which cluster the satellite belongs to.

[0113] For each satellite, determine which star cluster the satellite belongs to based on the position of the satellite, including: calculating the angular distance of the angle formed between the line connecting the satellite to the earth's center at each running moment and the line connecting the center of each celestial domain partition to the earth's center, and dividing the satellite into the star cluster of the celestial domain partition with the smallest angular distance.

[0114] Specifically, the method for calculating which star cluster a satellite belongs to is based on the line connecting the earth's center and the center of each celestial domain as a reference, then determining the line connecting the position of the satellite to the earth's center at each running moment, and finally calculating the angular distance of the angle formed by these two lines. The smaller the angular distance, the closer the position of the satellite at that running moment is to the center of the celestial domain partition. By comparing the angular distances between the satellite and the centers of each celestial domain partition, the satellite is divided into the star cluster of the celestial domain partition with the smallest angular distance.

[0115] Finally, when there are multiple celestial domain partitions with the smallest angular distance at the same time, divide the satellite into the star clusters of the multiple celestial domain partitions.

[0116] In the embodiments of the present application, there is also a situation where there are multiple celestial domain partitions with the smallest angular distance. Then at that running moment, the satellite is exactly between several celestial domain partitions. At this time, the satellite is divided into the star clusters of multiple celestial domain partitions at the same time.

[0117] Combined with the above embodiments, in one implementation manner, the present application also provides a method for managing and controlling resources of a low-earth orbit giant constellation, dividing the satellites in each running moment and each star cluster into a main star and multiple auxiliary stars, specifically including the following content:

[0118] First, according to the angular distance of the angle formed between the line connecting each satellite in each running moment and each star cluster to the earth's center and the line connecting the center of the celestial domain partition of the star cluster to the earth's center during the running period, divide the satellite with the smallest angular distance into the main star of the star cluster, and divide the other satellites in the star cluster into auxiliary stars.

[0119] In the embodiments of the present application, after determining the satellites included in each star cluster at each running moment, it is also necessary to determine the main star and auxiliary stars in the star cluster. The main star is preferably located at the center of the celestial domain partition to control each auxiliary star in the star cluster. Therefore, the process of determining the main star will first compare the angular distances of all satellites in the star cluster from the center of the celestial domain partition at each running moment, and select the satellite with the smallest angular distance as the main star, and the other satellites as the auxiliary stars in the constellation.

[0120] Then, set a main star switching time threshold, and adjust the division of the main star and auxiliary stars in each moment and each star cluster according to the time threshold.

[0121] In the embodiments of the present application, since the operation of a satellite is a dynamic process and the position of the satellite is constantly changing, it is possible that the satellites closest to the center of the celestial domain are different at several consecutive operating moments. If the main satellite is determined only according to the principle of proximity, it is possible that the main satellite is frequently replaced in a short period of time (such as in areas where satellite distribution is dense near the north and south poles), which is likely to cause congestion in the network communication links between satellites. Therefore, on the basis of determining the main satellite according to the angular distance, adjustment and optimization are also required. In an alternative embodiment, by setting a main satellite handover time threshold to specify the minimum duration for which a satellite serves as the main satellite, the satellite can only relinquish its identity as the main satellite after passing this time threshold, and the next satellite takes over as the main satellite, so as to avoid frequent replacement of the main satellite caused by determining the main satellite only according to the angular distance.

[0122] In a specific implementation manner, an embodiment of the present application provides a main and auxiliary satellite partitioning method. Referring to Figure 3 , Figure 3 is a schematic diagram of a main and auxiliary satellite partitioning method provided by an embodiment of the present application. As shown in Figure 3 , the hexagon in the figure is a schematic diagram of multiple celestial domain partitions, and the dotted lines thereon are the operating trajectories of the satellites. There are multiple satellites on one operating trajectory. In each region, according to the minimum angular distance and the main satellite handover time threshold, the satellites in the satellite cluster are distinguished into main satellites and auxiliary satellites, where the black solid circles represent the main satellites in the satellite cluster, and the white hollow circles represent the auxiliary satellites in the satellite cluster.

[0123] Combined with the above embodiments, in one implementation manner, the present application further provides a method for managing and controlling resources of a low-Earth orbit giant constellation. Each satellite operates in orbit according to the management rule library and the satellite cluster partitioning table, and specifically includes the following content:

[0124] First, in response to receiving a task from the ground control center, the main satellite in the satellite cluster divides the task into multiple subtasks and assigns them to each satellite in the satellite cluster for execution.

[0125] In the embodiments of the present application, each satellite in the low-Earth orbit giant constellation operates normally in orbit according to the satellite cluster partitioning table and the management rule library. The main satellite in each satellite cluster is responsible for the unified scheduling and allocation of task resources of each satellite in the satellite cluster. Only the main satellite in each satellite cluster conducts information interaction with the ground control center, while each auxiliary satellite only conducts inter-satellite information interaction within the satellite cluster. In this way, it is avoided that all satellites directly transmit information to the ground control center, causing a burden on the ground control center and congestion in the communication links.

[0126] In the present application, after the main satellite in the satellite cluster receives a task issued by the ground control center, it determines the auxiliary satellites in the satellite cluster that can execute the task according to the satellite cluster partitioning table, and divides the task into multiple subtasks and assigns them to the auxiliary satellites in the satellite cluster for execution.

[0127] Then, the secondary satellites within the satellite cluster execute the subtasks assigned by the primary satellite within the satellite cluster and transmit task interaction information to other secondary satellites.

[0128] In the embodiments of the present application, the secondary satellites execute the subtasks distributed by the primary satellite within the satellite cluster. During the specific implementation process, there may be some surveillance targets that require multiple satellites to jointly execute tasks, and information interaction between satellites is needed. At this time, the secondary satellites in the satellite cluster also need to transmit task interaction information to other secondary satellites in the satellite cluster according to the instructions of the subtasks to complete the tasks in cooperation with other secondary satellites.

[0129] Next, each satellite within the satellite cluster feeds back the execution status of the subtasks to the primary satellite within the satellite cluster.

[0130] In the embodiments of the present application, since the secondary satellites do not directly communicate with the ground control center, the execution status of the tasks needs to be summarized at the primary satellite. Each secondary satellite needs to feed back the execution status of the subtasks it executes to the primary satellite within the satellite cluster, and the primary satellite then summarizes according to the execution status of the subtasks and continues to manage and control the task execution.

[0131] Finally, the primary satellite within the satellite cluster regularly feeds back the execution status of the tasks to the ground control center.

[0132] In the embodiments of the present application, after summarizing the execution status of the subtasks of each secondary satellite within the satellite cluster, the primary satellite within the satellite cluster also needs to regularly feed back the execution status of the tasks to the ground control center so that technicians can monitor the progress of the tasks. In this way, part of the information processing is decentralized to the primary satellite, greatly reducing the task execution pressure on the ground control center and being beneficial to improving the constellation elasticity.

[0133] Combined with the above embodiments, in one implementation manner, the present application also provides a method for managing and controlling resources of a low-earth orbit giant constellation. Each satellite operates in orbit according to the management rule library and the satellite cluster division table, and specifically includes the following contents:

[0134] First, the secondary satellites within the satellite cluster regularly transmit working status information to the primary satellite within the satellite cluster, and the working status information is used to characterize the normal working state of the satellite.

[0135] In the embodiments of the present application, the primary satellite needs to determine whether each satellite within the satellite cluster is in a normal working state where it can be contacted. Therefore, the secondary satellites within the satellite cluster need to regularly send working status information, that is, "heartbeat" information, to the primary satellite to indicate the normal working state, and the primary satellite receives the working status information and summarizes it.

[0136] Then, the primary satellite within the satellite cluster regularly transmits the working status information of each satellite within the satellite cluster to the ground control center.

[0137] In the embodiment of the present application, after receiving the working status information of each auxiliary satellite, the main satellite also needs to transmit the working status information of all satellites in the cluster back to the ground control center. In the low-orbit giant constellation resource management method proposed in the present application, the ground control center is mainly responsible for monitoring and verifying the operating status of each satellite, as well as managing emergency tasks.

[0138] In an optional embodiment, since the inter-satellite communication links between satellites and the satellite-to-ground communication links between satellites and the ground have high speed and low speed, communication links of different speeds can be selected according to the urgency of the information to ensure the timeliness of the emergency information and avoid congestion of the communication links. The mission instructions and the mission interaction information required for executing missions between satellites as described above are information with a high degree of urgency, and a high-speed communication link is used, while the satellite's working status information reported regularly, i.e., heartbeat information, and some global mission instructions are information with a low degree of urgency, and a low-speed communication link is used.

[0139] In combination with the above embodiments, in one implementation, the present application further provides a method for managing and controlling resources of a low-orbit giant constellation, wherein each satellite operates in orbit according to the management rule library and the star cluster partition table, and specifically includes the following contents:

[0140] First, each satellite in the cluster checks the stored cluster partition table at each operating moment.

[0141] In the embodiment of the present application, each satellite in the cluster needs to check its stored cluster division table at each operating moment to determine the cluster to which it belongs and its identity in the cluster at the current operating moment, so as to use this as a basis for normal in-orbit operation and execution of tasks.

[0142] Then, before the main star in the star cluster is converted into an auxiliary star at the next operating moment, the task status information in the star cluster is transmitted to the main star that takes over at the next moment, and the task status information at least includes: subtask allocation status and subtask execution status.

[0143] In the embodiment of the present application, each main star in the star cluster needs to resign from the main star responsibilities before flying away from the star cluster, transfer the main star identity to the next successor main star, and transmit the task status information in the star cluster to the successor main star, including the subtask allocation of existing tasks and the execution status of each subtask reported by each auxiliary star, so as to avoid the normal execution of tasks being affected by the alternation of the main star.

[0144] In a specific implementation, an embodiment of the present application provides a cluster information transmission process, referring to Figure 4 , Figure 4 : is a schematic diagram of an information interaction flow of a low-orbit giant constellation resource management method provided by an embodiment of the present application, such asFigure 4 As shown in the figure, the ground control center only exchanges information with the primary satellite within the satellite cluster. The primary satellite receives the "heartbeat" information transmitted by the secondary satellites and issues task instructions to the secondary satellites. The secondary satellites transmit task interaction information. Before flying away from the satellite cluster, the primary satellite transmits task status information to the succeeding primary satellite.

[0145] Combined with the above embodiments, in one implementation, the present application also provides a method for managing and controlling resources of a low-earth orbit giant constellation. Each satellite operates in orbit according to the management rule library and the satellite cluster division table, specifically including the following:

[0146] First, when the primary satellite within the satellite cluster is replaced, the secondary satellites within the satellite cluster align with the new succeeding primary satellite and transmit their working status information.

[0147] In the embodiments of the present application, in the case of alternation of the primary satellite within the satellite cluster, the secondary satellites within the satellite cluster need to determine the next succeeding primary satellite according to the satellite cluster division table, align with the new primary satellite, and report their working status information, that is, the "heartbeat" information, to ensure that the succeeding primary satellite can manage and control each satellite within the satellite cluster.

[0148] Then, when the secondary satellite within the satellite cluster flies to the next satellite cluster, it aligns with the primary satellite of the next satellite cluster and transmits its working status information.

[0149] In the embodiments of the present application, during the operation process, there is also a situation where a secondary satellite flies away from the original satellite cluster and flies into a new satellite cluster. After flying into the new satellite cluster, the secondary satellite needs to promptly align with the primary satellite in the newly flown-in satellite cluster and report its working status information to the primary satellite in the new satellite cluster, so as to receive the subtasks issued by the primary satellite in the new satellite cluster.

[0150] Combined with the above embodiments, in one implementation, the present application also provides a method for managing and controlling resources of a low-earth orbit giant constellation. Each satellite operates in orbit according to the management rule library and the satellite cluster division table, specifically including the following:

[0151] First, at each operating moment, the satellite within the satellite cluster determines its identity as the primary satellite or the secondary satellite according to the stored satellite cluster division table.

[0152] In the embodiments of the present application, different from the satellite management and control methods in the related art, each satellite in the low-earth orbit giant constellation can determine the satellite cluster it is in at each operating moment and the role it undertakes within the satellite cluster according to the satellite cluster division table it stores. During its operation in orbit, it executes tasks according to the role it undertakes. This is a management and control method from the perspective of the satellite, different from the previous task-oriented temporary clustering method.

[0153] Then, when the satellite in the star cluster is the primary star at the current running moment, it controls and manages each secondary star in the star cluster according to the management rule library, including: receiving the working status information and task status information transmitted by each secondary star in the star cluster, and transmitting the working status information and task status information to the ground control center; receiving the task information sent by the ground control center, dividing the task into multiple subtasks and assigning them to each secondary star in the star cluster for execution; before flying out of the star cluster, transmitting the task status information in the star cluster to the succeeding primary star.

[0154] In the embodiment of the present application, each satellite undertakes different tasks according to its role in the star cluster where it is located. When it is the primary star in the star cluster, the satellite needs to control and manage the entire star cluster according to the management rule library, receive the working status information and task status information transmitted by the secondary stars, and allocate, monitor, and report the tasks of the ground control center. It also needs to report the working status information and task status information to the ground control center, and when relinquishing the identity of the primary star, hand over the task status information to the succeeding primary star.

[0155] Finally, when the satellite in the star cluster is the secondary star at the current running moment, it executes the instructions issued by the primary star in the star cluster according to the management rule library, including: receiving the subtasks issued by the primary star in the star cluster; transmitting the execution status of the subtasks to the primary star in the star cluster, and transmitting task interaction information to other secondary stars in the star cluster; regularly transmitting the working status information to the primary star in the star cluster; after flying out of the star cluster, aligning with the primary star of the next star cluster and transmitting the working status information.

[0156] In the embodiment of the present application, when the identity of the satellite is the secondary star, it needs to execute the instructions issued by the primary star according to the management rule library. First, it needs to receive and execute the subtasks issued by the primary star. During the execution process, it may need to interact with other secondary stars, and also needs to report the execution status of the subtasks and its own working status information to the primary star. And it also needs to align with the primary star of the new star cluster and report the working status information when arriving at the new star cluster according to the running trajectory.

[0157] In a specific implementation manner, an embodiment of the present application provides a management process for a low-Earth orbit giant constellation. Refer to Figure 5 , Figure 5 which is a schematic diagram of the resource management process for a low-Earth orbit giant constellation provided by an embodiment of the present application. As shown in Figure 5As shown, first, the orbital parameters of the low-orbit giant constellation need to be initialized, and the low-orbit giant constellation to be divided is divided into multiple sky domain partitions according to the C-60 molecular structure. Then, according to the satellite's orbit, the position of the satellite at each operating time in the future operation cycle is calculated, and then the star cluster to which the satellite belongs is calculated, the main star and auxiliary star in the star cluster are determined, and the manually adjusted star cluster division is recorded as a star cluster division table and stored in each satellite. The above is the content that can be completed before the low-orbit giant constellation is operated, which is called the offline workflow, followed by the workflow of the in-orbit operation of each satellite in the low-orbit giant constellation. First, at a running moment, it needs to determine its own primary and secondary satellite identity according to the cluster division table. When acting as a primary satellite, it needs to update the task status within the cluster and allocate satellite resources within the cluster. Then it needs to pass the allocation of subtasks to each secondary satellite, and then receive the subtask execution status and work status information of the secondary satellite, and report to the ground control center. When it resigns as the primary satellite, it passes the task status information to the successor primary satellite. Then the satellite's on-orbit work content as a secondary satellite is to receive the task information sent by the primary satellite, execute subtasks and assist other secondary satellites in sending task interaction information, and report the subtask execution status to the primary satellite.

[0158] Based on the same design concept, an embodiment of the present application provides a low-orbit giant constellation resource management and control device. Figure 6 , Figure 6 1 is a structural block diagram of a low-orbit giant constellation resource management and control device provided by an embodiment of the present application. Figure 6 As shown, the device comprises:

[0159] A sky partition division module is used to divide the constellation operation sky into multiple sky partitions according to the C-60 molecular structure, and each satellite in the sky partition constitutes a star cluster of the sky partition;

[0160] A satellite division module, used for dividing the satellites in each star cluster at each operating time into a primary satellite and multiple auxiliary satellites according to the operating tracks of the satellites;

[0161] A star cluster partition table generation module is used to generate a star cluster partition table for each satellite in response to the completion of satellite partitioning in each star cluster at each operating time in the operating cycle, wherein the star cluster partition table at least includes: operating time, star cluster, primary satellite, and controlled auxiliary satellite;

[0162] A management rule base formulation module is used to formulate a management rule base, according to which the primary star controls each auxiliary star in the star cluster, and the auxiliary star executes the task instructions issued by the primary star in the star cluster according to the management rule base;

[0163] An on-orbit operation module, configured to store the management rule library and the star cluster division table in each satellite, and each satellite operates on orbit according to the management rule library and the star cluster division table.

[0164] Optionally, the celestial region partition module includes:

[0165] A satellite position calculation sub-module, configured to calculate the position of each satellite at each running moment within the running period according to the predicted running trajectories of the satellites;

[0166] An angular distance calculation sub-module, configured to calculate the angular distance of the included angle formed between the line connecting each satellite to the earth's center and the line connecting the center of each celestial region partition to the earth's center at each running moment, and divide the satellite into the star cluster of the celestial region partition with the smallest angular distance;

[0167] A multi-partition satellite division sub-module, configured to divide the satellite into the star clusters of the multiple celestial region partitions when there are multiple celestial region partitions with the smallest angular distance at the same time.

[0168] Optionally, the satellite division module includes:

[0169] A satellite identity division sub-module, configured to divide the satellite with the smallest angular distance into the primary star of the star cluster and divide the other satellites in the star cluster into secondary stars according to the angular distance of the included angle formed between the line connecting each satellite to the earth's center and the line connecting the center of the celestial region partition of the star cluster to the earth's center at each running moment within the running period;

[0170] A switching time threshold setting sub-module, configured to set a primary star switching time threshold and adjust the division of primary stars and secondary stars in each star cluster at each moment according to the time threshold.

[0171] Optionally, the on-orbit operation module includes:

[0172] A sub-task division sub-module, configured to, in response to receiving a task from the ground control center, the primary star in the star cluster divides the task into multiple sub-tasks and assigns them to each satellite in the star cluster for execution;

[0173] A sub-task execution sub-module, configured to the secondary stars in the star cluster execute the sub-tasks assigned by the primary star in the star cluster and transmit task interaction information to other secondary stars;

[0174] A sub-task feedback sub-module, configured to each satellite in the star cluster feeds back the execution situation of the sub-task to the primary star in the star cluster;

[0175] A task execution situation feedback sub-module, configured to the primary star in the star cluster regularly feeds back the execution situation of the task to the ground control center.

[0176] Optionally, the on-orbit operation module further includes:

[0177] A working status information transmission sub-module, configured to periodically transmit working status information of slave satellites in the satellite cluster to the master satellite in the satellite cluster, where the working status information is used to characterize the normal working status of the satellite;

[0178] A working status information feedback sub-module, configured to periodically transmit the working status information of each satellite in the satellite cluster by the master satellite in the satellite cluster to the ground control center.

[0179] Optionally, the on-orbit operation module further includes:

[0180] A satellite cluster division table check sub-module, configured to check the stored satellite cluster division table by each satellite in the satellite cluster at each running moment;

[0181] A task status information transfer sub-module, configured to transfer the task status information in the satellite cluster to the successor master satellite at the next running moment before the master satellite in the satellite cluster is converted into a slave satellite at the next running moment, where the task status information at least includes: sub-task assignment situation and sub-task execution situation.

[0182] Optionally, the on-orbit operation module further includes:

[0183] A working status information transmission sub-module, configured to when the master satellite in the satellite cluster is replaced, the slave satellites in the satellite cluster align with the new successor master satellite and transmit the working status information;

[0184] A working status information transmission sub-module, configured to when the slave satellite in the satellite cluster flies to the next satellite cluster, align with the master satellite of the next satellite cluster and transmit the working status information.

[0185] Optionally, the on-orbit operation module further includes:

[0186] An identity confirmation sub-module, configured to determine the identity of the master satellite or slave satellite at the current running moment according to the stored satellite cluster division table by the satellite in the satellite cluster at each running moment;

[0187] A master satellite working sub-module, configured to when the current running moment of the satellite in the satellite cluster is the master satellite, control each slave satellite in the satellite cluster according to the management rule library, including: receiving the working status information and task status information transmitted by each slave satellite in the satellite cluster, and transmitting the working status information and task status information to the ground control center; receiving the task information sent by the ground control center, dividing the task into multiple sub-tasks and assigning them to each slave satellite in the satellite cluster for execution; before flying away from the satellite cluster, transmitting the task status information in the satellite cluster to the successor master satellite;

[0188] The secondary satellite working sub-module is used to execute the instructions sent by the primary satellite in the satellite cluster when the satellite in the satellite cluster is the secondary satellite at the current running moment. It includes: receiving the subtasks sent by the primary satellite in the satellite cluster; transmitting the execution status of the subtasks to the primary satellite in the satellite cluster and transmitting task interaction information to other secondary satellites in the satellite cluster; regularly transmitting the working status information to the primary satellite in the satellite cluster; after flying out of the satellite cluster, aligning with the primary satellite of the next satellite cluster and transmitting the working status information.

[0189] Based on the same design concept, another embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the steps in the low-earth orbit giant constellation resource management and control method as described in any one of the above embodiments of the present application.

[0190] Based on the same design concept, another embodiment of the present application provides a computer program product, including computer programs / instructions. When the computer programs / instructions are executed by a processor, they implement the steps in the low-earth orbit giant constellation resource management and control method as described in any one of the above embodiments of the present application.

[0191] Based on the same design concept, another embodiment of the present application provides an electronic device, as Figure 7 shown. Figure 7 is a schematic diagram of an electronic device shown in an embodiment of the present application. The electronic device includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes, it implements the steps in the low-earth orbit giant constellation resource management and control method as described in any one of the above embodiments of the present application.

[0192] For the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For the relevant parts, please refer to the partial description of the method embodiment.

[0193] Each embodiment in this specification is described in a progressive manner. The key point of each embodiment is to illustrate the differences from other embodiments. The same or similar parts among the embodiments can be referred to each other.

[0194] Those skilled in the art should understand that the embodiments of the present application can be provided as methods, devices, or computer program products. Therefore, the embodiments of the present application can take the form of completely hardware embodiments, completely software embodiments, or embodiments combining software and hardware aspects. Moreover, the embodiments of the present application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program codes.

[0195] Embodiments of the present application are described with reference to the flowcharts and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing terminal devices generate a device for implementing the functions specified in one process Figure 1 or more processes and / or blocks Figure 1 or a device for implementing the functions specified in one block or more blocks.

[0196] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device that implements the functions specified in one process Figure 1 or more processes and / or blocks Figure 1 or a device for implementing the functions specified in one block or more blocks.

[0197] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device, such that a series of operation steps are executed on the computer or other programmable terminal device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable terminal device provide steps for implementing the functions specified in one process Figure 1 or more processes and / or blocks Figure 1 or a device for implementing the functions specified in one block or more blocks.

[0198] Although the preferred embodiments of the embodiments of the present application have been described, those skilled in the art can make additional changes and modifications to these embodiments once they know the basic creative concepts. Therefore, the appended claims are intended to be construed as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.

[0199] Finally, it should also be noted that in this text, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or terminal device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or terminal device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the existence of additional identical elements in the process, method, article or terminal device comprising the said element.

[0200] The above has introduced in detail a method, apparatus, device and medium for resource management and control of a low-earth orbit giant constellation. In this text, specific examples are used to elaborate on the principle and implementation manner of this application. The description of the above embodiments is only used to help understand the method and its core idea of this application; at the same time, for those of ordinary skill in the art, according to the idea of this application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to this application.

Claims

1. A method for managing and controlling resources of a low-orbit giant constellation, characterized in that: include: Dividing the constellation operation sky domain into a plurality of sky domain partitions according to the C-60 molecular structure, wherein each satellite in the sky domain partition forms a star cluster of the sky domain partition; According to the orbits of the satellites, the satellites in each cluster at each operating time are divided into a primary satellite and a plurality of auxiliary satellites; In response to the completion of the division of satellites in each star cluster at each operating time in the operating cycle, a star cluster division table of each satellite is generated, wherein the star cluster division table at least includes: operating time, star cluster, primary satellite, and controlled auxiliary satellite; Formulate a management rule base, the primary star controls each auxiliary star in the star cluster according to the management rule base, and the auxiliary star executes the task instructions issued by the primary star in the star cluster according to the management rule base; The management rule base and the star cluster division table are stored in each satellite, and each satellite operates in orbit according to the management rule base and the star cluster division table.

2. A method for managing and controlling resources of a low-orbit giant constellation according to claim 1, characterized in that: The satellites in the sky domain partition form a star cluster of the sky domain partition, including: Calculate the position of each satellite at each operating time during the operating cycle according to the estimated operating trajectory of each satellite; Calculating the angular distance between the line connecting the satellite to the center of the earth and the line connecting the center of each sky partition to the center of the earth at each operating time, and dividing the satellite into the star cluster of the sky partition with the smallest angular distance; When there are multiple sky partitions with the smallest angular distances at the same time, the satellites are divided into star clusters of the multiple sky partitions.

3. A method for managing and controlling low-orbit giant constellation resources according to claim 1, characterized in that: The satellites in each operating moment and each cluster are divided into a primary satellite and multiple auxiliary satellites, including: According to the angle distance formed by the line connecting each satellite in each star cluster to the center of the earth and the line connecting the center of the sky region of the star cluster to the center of the earth at each operating time in the operating cycle, the satellite with the smallest angle distance is classified as the primary star of the star cluster, and the other satellites in the star cluster are classified as auxiliary stars; A primary star switching time threshold is set, and the division of primary and secondary stars in each star cluster at each moment is adjusted according to the time threshold.

4. A method for managing and controlling resources of a low-orbit giant constellation according to claim 1, characterized in that: Each satellite operates in orbit according to the management rule base and the star cluster division table, including: In response to receiving a task from a ground control center, the master satellite in the star cluster divides the task into a plurality of subtasks and assigns them to each satellite in the star cluster for execution; The auxiliary satellites in the star cluster perform the subtasks assigned by the primary satellites in the star cluster and transmit task interaction information to other auxiliary satellites; Each satellite in the star cluster feeds back the execution status of the subtask to the main satellite in the star cluster; The main satellite in the star cluster regularly feeds back the execution status of the mission to the ground control center.

5. The method for managing and controlling resources of a low-orbit giant constellation according to claim 1, characterized in that: Each satellite is operated in orbit according to the management rule base and the star cluster division table, and further comprises: The auxiliary satellite in the star cluster periodically transmits working status information to the primary satellite in the star cluster, wherein the working status information is used to represent the normal working status of the satellite; The main satellite in the star cluster periodically transmits the working status information of each satellite in the star cluster to the ground control center.

6. A method for managing and controlling resources of a low-orbit giant constellation according to claim 1, characterized in that: Each satellite is operated in orbit according to the management rule base and the star cluster division table, and further comprises: Each satellite in the star cluster checks the stored star cluster partition table at each operating moment; Before the main star in the star cluster is converted into an auxiliary star at the next operating moment, the task status information in the star cluster is transmitted to the main star that takes over at the next moment, and the task status information at least includes: subtask allocation status and subtask execution status.

7. The method for managing and controlling resources of a low-orbit giant constellation according to claim 1, characterized in that: Each satellite is operated in orbit according to the management rule base and the star cluster division table, and further comprises: When the primary star in the star cluster is replaced, the secondary star in the star cluster is aligned with the new primary star and transmits working status information; When the auxiliary star in the star cluster flies to the next star cluster, it is aimed at the main star of the next star cluster and transmits the working status information.

8. A method for managing and controlling resources of a low-orbit giant constellation according to any one of claims 1 to 7, characterized in that: Each satellite is operated in orbit according to the management rule base and the star cluster division table, and further comprises: At each operating moment, the satellites in the star cluster determine the identity of the primary or secondary satellite at the current operating moment according to the stored star cluster division table; When the current operating time of the satellite in the star cluster is the main satellite, each auxiliary satellite in the star cluster is controlled according to the management rule library, including: receiving the working status information and task status information transmitted by each auxiliary satellite in the star cluster, and transmitting the working status information and task status information to the ground control center; receiving the task information sent by the ground control center, dividing the task into multiple subtasks and allocating them to each auxiliary satellite in the star cluster for execution; before flying away from the star cluster, transmitting the task status information in the star cluster to the successor main satellite; When the current operating time of the satellite in the star cluster is an auxiliary star, the command issued by the main star in the star cluster is executed according to the management rule library, including: receiving the subtask issued by the main star in the star cluster; transmitting the subtask execution status to the main star in the star cluster, and transmitting the task interaction information to other auxiliary stars in the star cluster; regularly transmitting the working status information to the main star in the star cluster; after flying away from the star cluster, aiming at the main star of the next star cluster and transmitting the working status information.

9. A low-orbit giant constellation resource management and control device, characterized in that: The device comprises: A sky partition division module is used to divide the constellation operation sky into multiple sky partitions according to the C-60 molecular structure, and each satellite in the sky partition constitutes a star cluster of the sky partition; A satellite division module, used for dividing the satellites in each star cluster at each operating time into a primary satellite and multiple auxiliary satellites according to the operating tracks of the satellites; A star cluster partition table generation module is used to generate a star cluster partition table for each satellite in response to the completion of satellite partitioning in each star cluster at each operating time in the operating cycle, wherein the star cluster partition table at least includes: operating time, star cluster, primary satellite, and controlled auxiliary satellite; A management rule base formulation module is used to formulate a management rule base, according to which the primary star controls each auxiliary star in the star cluster, and the auxiliary star executes the task instructions issued by the primary star in the star cluster according to the management rule base; The on-orbit operation module is used to store the management rule library and the star cluster division table in each satellite, and each satellite operates on-orbit according to the management rule library and the star cluster division table.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the computer program is executed by the processor, the method for managing and controlling resources of a low-orbit giant constellation as described in any one of claims 1 to 8 is implemented.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for managing and controlling resources of a low-orbit giant constellation as claimed in any one of claims 1 to 8 is implemented.

Images