Space-based resource on-orbit updating and management method and device based on prior historical information

Abstract

The application discloses a space-based resource on-orbit updating and management method and device based on prior historical information, and belongs to the technical field of satellite communication. The method comprises the following steps: a management satellite acquires a plurality of low-orbit satellites which are in the coverage range of the management satellite at a current updating period; the required resource state data volume of each low-orbit satellite is calculated according to the historical information of each low-orbit satellite; a beam time slot allocation strategy is determined according to the resource state data volume, and the resource state information of each low-orbit satellite is acquired according to the beam time slot allocation strategy; a local satellite resource view in the coverage range is constructed according to the resource state information of each low-orbit satellite, and synchronization information is sent to adjacent management satellites of the management satellite. The application can reduce the restriction of the distribution of ground gateway stations and the coverage range of the national border on information updating, and through inter-satellite cooperation, the processing load of the single-satellite resource view is reduced, and the updating efficiency and real-time performance of the satellite resource state information are improved.

Description

Technical Field

[0001] This application belongs to the field of satellite communication technology, and in particular relates to a method and apparatus for on-orbit updating and management of space-based resources based on prior historical information. Background Technology

[0002] As satellite capabilities continue to mature, advanced payloads such as intelligent computing and multi-source sensing have been deployed on various satellites, laying a solid foundation for space situational awareness and supporting on-orbit processing. Current satellite networks comprise not only different types of satellites, such as high-altitude, medium-altitude, low-altitude, general computing, and remote sensing satellites, but also a wide range of resource types, such as computing resources, communication resources, storage resources, and data resources. Real-time acquisition of resource information within the giant satellite constellation is crucial for constellation orchestration and management.

[0003] Currently, satellite network resource information updates primarily rely on ground-based systems. When a satellite passes over a national border, ground gateway stations interact with the satellite to obtain its resource status information. However, this approach is heavily influenced by the distribution of ground gateway stations. Once a satellite leaves the country, the loss of ground gateway stations makes it difficult to transmit satellite resource status information back to the ground for real-time updates. This significantly impacts the scheduling at the control center, requiring updates to occur only the next time the satellite passes over the border, severely affecting the efficiency of satellite resource status information updates. Summary of the Invention

[0004] This application aims to address at least one of the technical problems existing in the prior art. To this end, this application proposes a method and apparatus for on-orbit updating and management of space-based resources based on prior historical information, so as to improve the updating efficiency of satellite resource status information.

[0005] Firstly, this application provides a method for on-orbit updating and management of space-based resources based on prior historical information, including: The control satellite acquires multiple low-orbit satellites that are within the coverage area of ​​the control satellite in the current update cycle; The amount of resource status data that each low-Earth orbit satellite needs to transmit is calculated based on the historical information of each low-Earth orbit satellite; the historical information includes historical resource status information and historical mission information, and the amount of resource status data is the change in the current resource status information of the low-Earth orbit satellite compared to the historical resource status information. The beam slot allocation strategy is determined based on the amount of resource status data, and the resource status information of each low-Earth orbit satellite is obtained based on the beam slot allocation strategy. A local satellite resource view within the coverage area is constructed based on the resource status information of each low-orbit satellite, and synchronization information is sent to the adjacent control satellites of the control satellite; the synchronization information includes the local satellite resource view and low-orbit satellites that will leave the coverage area of ​​the control satellite within a preset time period.

[0006] The space-based resource on-orbit update and management method based on prior historical information provided in this application acquires information from multiple low-Earth orbit (LEO) satellites within its coverage area during the current update cycle via a management satellite. It calculates the required amount of resource status data to be transmitted based on the historical resource status and mission information of each LEO satellite. This allows data transmission only for changes in resource status information compared to historical information, reducing excessive communication pressure in full-volume transmission mode. Based on this resource status data, a beam slot allocation strategy is determined, and the resource status information of each LEO satellite is acquired, improving the utilization rate of inter-satellite link resources. A local satellite resource view is constructed based on the resource status information of each LEO satellite and synchronized information, including this local satellite resource view, is sent to adjacent management satellites. Inter-satellite collaboration updates a complete satellite network resource view, reducing the processing load of single-satellite resource views and achieving distributed collaborative processing. This method enables autonomous on-orbit update and collaborative synchronization of satellite resource status information in a space-based environment independent of ground gateway stations, without waiting for LEO satellites to re-enter the network. This reduces the limitations imposed by ground gateway station distribution and national border coverage on information updates, improving the efficiency and real-time performance of satellite resource status information updates.

[0007] According to one embodiment of this application, acquiring multiple low-Earth orbit satellites that are within the coverage area of ​​the controlled satellites in the current update cycle includes: In response to the information update command periodically initiated by the control satellite, receive information from the neighboring control satellites of the control satellite regarding low-orbit satellites that will leave the coverage area of ​​the neighboring control satellites within a preset time period; Based on the satellite ephemeris, low-orbit satellites that have left the coverage area of ​​the controlled satellite are deleted, and low-orbit satellites that will leave the coverage area of ​​adjacent controlled satellites within a preset time period are added to the coverage area of ​​the controlled satellite, resulting in multiple low-orbit satellites that are within the coverage area of ​​the controlled satellite in the current update cycle.

[0008] In this embodiment, by receiving information from neighboring control satellites about low-Earth orbit (LEO) satellites that will leave their coverage area within a preset time period, the control satellite can obtain information about satellites that are about to enter its coverage area in advance. By combining this information with satellite ephemeris data, the control satellite can delete LEO satellites that have already left its coverage area and add LEO satellites that are about to leave their coverage area, which are transferred by neighboring control satellites, to its coverage area. This reduces the problem of blurred coverage boundaries or satellite omissions caused by satellite movement and improves the continuity of the on-orbit update process of satellite resource status information.

[0009] According to one embodiment of this application, the step of calculating the amount of resource status data required to be transmitted by each low-Earth orbit satellite based on historical information of each low-Earth orbit satellite includes: Based on the historical resource status information, determine the historical resource type and remaining historical resource quantity of each low-orbit satellite; The historical mission priority and execution progress of each low-Earth orbit satellite are determined based on the historical mission information. Based on the historical resource type, the remaining amount of historical resources, the historical task priority, and the historical task execution progress, the data length and data frame format of the data to be transmitted by each low-orbit satellite in the current update cycle are calculated. The data length and data frame format are used as the resource status data volume.

[0010] In this embodiment, by determining the historical resource type and remaining amount of each low-orbit satellite based on historical resource status information, and by combining historical mission information to determine historical mission priority and execution progress, the prior historical information can be fully utilized to accurately reflect the resource usage patterns and mission execution status of low-orbit satellites. This allows the data length and data frame format to accurately reflect the actual update needs of each low-orbit satellite, thereby improving the accuracy of resource status data quantity measurement.

[0011] According to one embodiment of this application, determining the beam slot allocation strategy based on the amount of resource status data includes: According to the data frame format, a unique corresponding communication beam is assigned to each low-Earth orbit satellite; Based on the data length, a corresponding communication time slot is allocated to each low-Earth orbit satellite, and the order of the communication time slots of each low-Earth orbit satellite is adjusted according to the historical mission priority of each low-Earth orbit satellite. The communication beams, communication time slots, and communication time slot order of each low-Earth orbit satellite are used as the beam and time slot allocation strategy.

[0012] In this embodiment, by assigning a unique corresponding communication beam to each low-Earth orbit satellite according to the data frame format, signal interference between different low-Earth orbit satellites can be reduced, and the stability of inter-satellite communication can be improved. By assigning matching communication time slots to each low-Earth orbit satellite according to the data length, the time slot resources can be adapted to the actual transmission needs, improving the utilization efficiency of inter-satellite link resources. By adjusting the order of communication time slots in combination with the historical mission priority of each low-Earth orbit satellite, it can be ensured that satellites corresponding to high-priority missions complete the transmission of resource status information first, improving the efficiency of on-orbit updating of satellite resource status information.

[0013] According to one embodiment of this application, obtaining the resource status information of each low-Earth orbit satellite according to the beam slot allocation strategy includes: According to the communication beam allocated in the beam slot allocation strategy, the communication beam of the control and management satellite is aligned with the corresponding low-Earth orbit satellite to establish a communication link; Within the communication time slots defined by the beam time slot allocation strategy, a resource status acquisition command is sent to the corresponding low-Earth orbit satellite; Receive resource status information fed back by each low-orbit satellite based on the acquisition command.

[0014] In this embodiment, by controlling the communication beam of the satellite to be aligned with the corresponding low-Earth orbit satellite according to the communication beam allocation strategy, the signal conflict and mutual interference of multiple satellites communicating simultaneously can be reduced. Resource status acquisition commands are sent within the allocated communication time slots, so that each low-Earth orbit satellite can respond within the preset time window, thereby reducing channel conflicts caused by concurrent communication of multiple satellites.

[0015] According to one embodiment of this application, constructing a local satellite resource view within the coverage area based on the resource status information of each low-Earth orbit satellite includes: Using the current update cycle as the time node, obtain the orbital position information of each low-orbit satellite at the time node; The time points, the orbital position information of each low-Earth orbit satellite, and the resource status information of each low-Earth orbit satellite are correlated and mapped to form a spatiotemporal status snapshot within the coverage area of ​​the controlled satellite, and the spatiotemporal status snapshot is used as the local satellite resource view.

[0016] In this embodiment, by acquiring the orbital position information of each low-orbit satellite at the given time point, the on-orbit spatial position of each low-orbit satellite at the update time can be located. The time point, the orbital position information of each low-orbit satellite, and the resource status information of each low-orbit satellite are correlated and mapped to form a snapshot of the spatiotemporal status within the coverage area of ​​the control satellite. This allows the local satellite resource view to not only include the real-time resource status of low-orbit satellites, but also synchronously associate the on-orbit position with the update time, further improving the accuracy of on-orbit updates of space-based resources.

[0017] According to one embodiment of this application, the method further includes: Based on the satellite ephemeris, determine the low-orbit satellites that will leave the coverage area of ​​the controlled satellites within a preset time period.

[0018] In this embodiment, by determining the low-orbit satellites that will leave the coverage area of ​​the control satellite within a preset time period based on the satellite ephemeris, the control satellite can accurately identify satellite objects that are about to move out of its control range.

[0019] Secondly, this application provides a space-based resource on-orbit update and management device based on prior historical information, comprising: The satellite control module is used to acquire multiple low-orbit satellites that are within the coverage area of ​​the controlled satellites in the current update cycle; The control strategy determination module is used to calculate the amount of resource status data that each low-Earth orbit satellite needs to transmit based on the historical information of each low-Earth orbit satellite; the historical information includes historical resource status information and historical mission information, and the amount of resource status data is the change in the current resource status information of the low-Earth orbit satellite compared with the historical resource status information; the module determines the beam slot allocation strategy based on the amount of resource status data, and obtains the resource status information of each low-Earth orbit satellite based on the beam slot allocation strategy; The resource view construction module is used to construct a local satellite resource view within the coverage area based on the resource status information of each low-orbit satellite, and send synchronization information to the adjacent control satellites of the control satellite; the synchronization information includes the local satellite resource view and low-orbit satellites that will leave the coverage area of ​​the control satellite within a preset time period.

[0020] According to the space-based resource on-orbit update and management device based on prior historical information of this application, multiple low-orbit satellites within its coverage area are acquired through management satellites within the current update cycle. The required amount of resource status data to be transmitted is calculated based on the historical resource status information and historical mission information of each low-orbit satellite. Data transmission is only performed on the changes in resource status information compared to historical information, reducing the excessive communication pressure in full-volume transmission mode. A beam slot allocation strategy is determined based on this resource status data, and the resource status information of each low-orbit satellite is acquired, improving the utilization rate of inter-satellite link resources. A local satellite resource view is constructed based on the resource status information of each low-orbit satellite and synchronous information, including this local satellite resource view, is sent to adjacent management satellites. Inter-satellite collaboration updates a complete satellite network resource view, reducing the processing load of single-satellite resource views and achieving distributed collaborative processing. This enables autonomous on-orbit update and collaborative synchronization of satellite resource status information in a space-based environment independent of ground gateway stations, without waiting for low-orbit satellites to re-enter the network for updates. This reduces the limitations imposed by the distribution of ground gateway stations and national border coverage on information updates, improving the update efficiency and real-time performance of satellite resource status information.

[0021] Thirdly, this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the on-orbit update and management method for space-based resources based on prior historical information as described in the first aspect above.

[0022] Fourthly, this application provides a satellite for performing the on-orbit updating and management method of space-based resources based on prior historical information as described in the first aspect above.

[0023] Fifthly, this application provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the on-orbit update and management method for space-based resources based on prior historical information as described in the first aspect above.

[0024] In a sixth aspect, this application provides a computer program product, including a computer program that, when executed by a processor, implements the on-orbit update and management method for space-based resources based on prior historical information as described in the first aspect above.

[0025] The above-described one or more technical solutions in the embodiments of this application have at least one of the following technical effects: According to the space-based resource on-orbit update and management method based on prior historical information proposed in this application, multiple low-Earth orbit (LEO) satellites within its coverage area during the current update cycle are acquired by the management satellite. The required amount of resource status data to be transmitted is calculated based on the historical resource status information and historical mission information of each LEO satellite. This allows data transmission only for changes in resource status information compared to historical information, reducing excessive communication pressure in full-volume transmission mode. A beam slot allocation strategy is determined based on this resource status data, and the resource status information of each LEO satellite is acquired, improving the utilization rate of inter-satellite link resources. A local satellite resource view is constructed based on the resource status information of each LEO satellite and synchronous information including this local satellite resource view is sent to adjacent management satellites. Inter-satellite collaboration updates a complete satellite network resource view, reducing the processing load of single-satellite resource views and achieving distributed collaborative processing. This enables autonomous on-orbit update and collaborative synchronization of satellite resource status information in a space-based environment independent of ground gateway station support, without waiting for LEO satellites to re-enter the network for updates. This reduces the limitations imposed by the distribution of ground gateway stations and national border coverage on information updates, improving the update efficiency and real-time performance of satellite resource status information.

[0026] In some embodiments, by receiving information from neighboring control satellites about low-Earth orbit (LEO) satellites that will leave their coverage area within a preset time period, the control satellites can obtain information in advance about satellites that will soon enter their coverage area. By combining this information with satellite ephemeris data, the control satellites can delete LEO satellites that have already left their coverage area and add LEO satellites that are about to leave their coverage area, which are transferred by neighboring control satellites, to their coverage area. This reduces the problem of blurred coverage boundaries or satellite omissions caused by satellite movement and improves the continuity of the on-orbit update process of satellite resource status information.

[0027] In some embodiments, by determining the historical resource type and remaining amount of each low-Earth orbit satellite based on historical resource status information, and by combining historical mission information to determine the historical mission priority and execution progress, prior historical information can be fully utilized to accurately reflect the resource usage patterns and mission execution status of low-Earth orbit satellites. This allows the data length and data frame format to accurately reflect the actual update needs of each low-Earth orbit satellite, thereby improving the accuracy of resource status data quantity measurement.

[0028] In some embodiments, by assigning a unique corresponding communication beam to each low-Earth orbit satellite according to the data frame format, signal interference between different low-Earth orbit satellites can be reduced, and the stability of inter-satellite communication can be improved. By assigning matching communication time slots to each low-Earth orbit satellite according to the data length, the time slot resources can be adapted to the actual transmission requirements, thereby improving the utilization efficiency of inter-satellite link resources. By adjusting the order of communication time slots in combination with the historical mission priorities of each low-Earth orbit satellite, it can be ensured that satellites corresponding to high-priority missions complete the transmission of resource status information first, thereby improving the efficiency of on-orbit updating of satellite resource status information.

[0029] In some embodiments, by controlling the communication beam of the satellite to be aligned with the corresponding low-Earth orbit satellite according to the communication beam allocation strategy, signal conflicts and mutual interference between multiple satellites communicating simultaneously can be reduced. Resource status acquisition commands are sent within the allocated communication time slots, enabling each low-Earth orbit satellite to respond within a preset time window, thereby reducing channel conflicts caused by concurrent communication between multiple satellites.

[0030] In some embodiments, by acquiring the orbital position information of each low-orbit satellite at that time node, the on-orbit spatial position of each low-orbit satellite at the update time can be located. The time node, the orbital position information of each low-orbit satellite, and the resource status information of each low-orbit satellite are correlated and mapped to form a snapshot of the spatiotemporal status within the coverage area of ​​the control satellite. This makes the local satellite resource view not only include the real-time resource status of low-orbit satellites, but also synchronously correlate the on-orbit position and update time, further improving the accuracy of on-orbit updates of space-based resources.

[0031] In some embodiments, by determining low-orbit satellites that will leave the coverage area of ​​the control satellite within a preset time period based on satellite ephemeris, the control satellite can accurately identify satellite objects that are about to move out of its control range.

[0032] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0033] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 This is a schematic diagram of a scenario for the on-orbit updating and management method of space-based resources based on prior historical information provided in an embodiment of this application. Figure 2 This is a flowchart illustrating the method for on-orbit updating and management of space-based resources based on prior historical information provided in this application embodiment; Figure 3 This is a schematic diagram of the structure of the space-based resource on-orbit update and management device based on prior historical information provided in the embodiments of this application; Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0035] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0036] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0037] The method and apparatus for on-orbit updating and management of space-based resources based on prior historical information provided in this application can be applied to any multi-sensor collaborative search scenario, such as multi-sonar sensor collaborative search for underwater targets, and this application does not limit it.

[0038] The following description, in conjunction with the accompanying drawings, details the method and apparatus for on-orbit updating and managing space-based resources based on prior historical information provided in this application, through specific embodiments and application scenarios.

[0039] In this embodiment, the control satellite can be a medium-high orbit satellite, with its orbital altitude distributed at levels such as medium Earth orbit (typically ranging from 2000km to 35786km) and geostationary orbit (approximately 35786km). Compared to low Earth orbit satellites, medium-high orbit satellites have the characteristics of longer orbital periods, lower relative ground motion speeds, and wider single-satellite coverage. A single satellite can provide continuous and stable observation coverage over a large area of ​​airspace below, and global or near-global coverage can be achieved by networking multiple medium-high orbit satellites.

[0040] Low Earth Orbit (LEO) satellites operate at altitudes below 2000 km, typically ranging from several hundred to over a thousand kilometers. They serve as the fundamental terminal nodes and resource carriers of space-based resource networks. LEO satellites are characterized by short orbital periods (usually 90-120 minutes), high orbital speeds (approximately 7.8 km / s), and small coverage areas. A single LEO satellite cannot provide continuous coverage of a specific area on the Earth's surface; therefore, multiple satellites must be networked together, relying on relay coverage between satellites to achieve global communication and resource monitoring.

[0041] In this embodiment, the low-orbit satellite carries various mission payloads and resource modules and needs to perform various space missions such as space observation, data transmission, and communication relay. The resource status information of the low-orbit satellite includes on-board computing resource occupancy rate, remaining storage resources, communication link bandwidth, mission execution progress, etc., and this resource status information is in dynamic change.

[0042] like Figure 1 As shown, due to their low orbital altitude and high speed, the inter-satellite link connection between low-Earth orbit (LEO) satellites and control satellites is time-sensitive. This means that information exchange can occur during the period when the LEO satellite is within the coverage area of ​​the control satellite. As the LEO satellite continues to operate in orbit, it will gradually leave the coverage area of ​​the current control satellite and enter the coverage area of ​​a neighboring control satellite.

[0043] Control satellites need to periodically initiate resource status information updates. Based on historical information from low-Earth orbit satellites within their coverage area, they calculate the amount of data to be transmitted, thereby determining beam slot allocation strategies and constructing a local satellite resource view within the coverage area. Control satellites also need to synchronize information with neighboring control satellites, collaboratively maintaining a complete satellite network resource view through a cooperative model.

[0044] The space-based resource on-orbit update and management method based on prior historical information provided in this application acquires information from multiple low-Earth orbit (LEO) satellites within its coverage area during the current update cycle via a management satellite. It calculates the required amount of resource status data to be transmitted based on the historical resource status and mission information of each LEO satellite. This allows data transmission only for changes in resource status information compared to historical information, reducing excessive communication pressure in full-volume transmission mode. Based on this resource status data, a beam slot allocation strategy is determined, and the resource status information of each LEO satellite is acquired, improving the utilization rate of inter-satellite link resources. A local satellite resource view is constructed based on the resource status information of each LEO satellite and synchronized information, including this local satellite resource view, is sent to adjacent management satellites. Inter-satellite collaboration updates a complete satellite network resource view, reducing the processing load of single-satellite resource views and achieving distributed collaborative processing. This method enables autonomous on-orbit update and collaborative synchronization of satellite resource status information in a space-based environment independent of ground gateway stations, without waiting for LEO satellites to re-enter the network. This reduces the limitations imposed by ground gateway station distribution and national border coverage on information updates, improving the efficiency and real-time performance of satellite resource status information updates.

[0045] The on-orbit update and management method for space-based resources based on prior historical information provided in this application embodiment can be implemented by an electronic device or a functional module or entity within an electronic device that can realize the on-orbit update and management method for space-based resources based on prior historical information. The electronic device mentioned in this application embodiment can be a control satellite. The following description uses a control satellite as the implementing entity to illustrate the on-orbit update and management method for space-based resources based on prior historical information provided in this application embodiment.

[0046] like Figure 2 As shown, the method for on-orbit updating and management of space-based resources based on prior historical information includes steps 210, 220, 230 and 240.

[0047] Step 210: Control satellites acquire multiple low-orbit satellites that are within the coverage area of ​​the control satellites in the current update cycle.

[0048] In this embodiment, the update cycle is the time interval between the control satellite performing a low-orbit satellite resource status update and control. The update cycle can be set according to the mission characteristics of the low-orbit satellite, the frequency of resource status changes, the bandwidth of the inter-satellite communication link, etc. For example, it can be set to 30 seconds, 1 minute or 5 minutes, 1 hour, 2 hours or 4 hours, etc., or it can be set to other durations. This embodiment does not limit this.

[0049] The coverage area of ​​a control satellite refers to the airspace range in which the control satellite can achieve effective communication through its onboard communication equipment. The coverage area of ​​a control satellite is determined by parameters such as the satellite's communication beam capability, transmission power, and antenna gain. It can be a circular area with a certain radius centered on the nadir point or a beam coverage area of ​​a specific shape.

[0050] Control satellites can determine all low-Earth orbit (LEO) satellites within their coverage area during the current update cycle through ephemeris data calculations, inter-satellite link signaling, and orbit prediction algorithms. For example, control satellites can broadcast probe signals via inter-satellite links to receive response signals from LEO satellites within their coverage area, thereby obtaining the identification and orbital position information of LEO satellites within their coverage area. Control satellites can also calculate the real-time positions of each LEO satellite based on pre-stored satellite ephemeris data using orbit extrapolation algorithms, thus determining whether each LEO satellite is within their coverage area.

[0051] Step 220: Calculate the amount of resource status data that each low-orbit satellite needs to transmit based on the historical information of each low-orbit satellite; the historical information includes historical resource status information and historical mission information, and the amount of resource status data is the change in the current resource status information of the low-orbit satellite compared to the historical resource status information.

[0052] In this embodiment, historical resource status information refers to the onboard resource status data reported by the low-Earth orbit (LEO) satellite to the control satellite in the previous update cycle or earlier. Alternatively, it can be determined based on synchronization information from other control satellites adjacent to the control satellite. Historical resource status information may include, but is not limited to, parameters such as onboard energy status, communication payload status, computing and storage resources, and communication beam status. Historical mission information refers to information related to communication missions, remote sensing missions, and navigation enhancement missions performed by the LEO satellite in the previous update cycle, including mission type, mission duration, resource consumption, and mission completion status.

[0053] Resource status data volume refers to the amount of data corresponding to the parameters corresponding to changes in the current actual resource status information of a low-Earth orbit satellite compared to the stored historical resource status information, rather than the total resource status information volume. By calculating the resource status data volume, the amount of data transmitted through inter-satellite links can be reduced, thereby lowering communication overhead.

[0054] The control satellite can estimate the theoretical consumption or changing trend of various resources on board based on historical mission information of each low-Earth orbit satellite and resource consumption models. It then integrates the theoretical estimates with historical resource status information to generate a predicted resource status value. The difference between the predicted value and the historical resource status information is the change in resource status, which represents the amount of resource status data required to be transmitted in the current cycle. For example, if a low-Earth orbit satellite's historical battery remaining power was 80%, and calculations predict the current remaining battery power to be 75%, then only the change data "battery remaining power changed from 80% to 75%" needs to be transmitted.

[0055] Step 230: Determine the beam slot allocation strategy based on the amount of resource status data, and obtain the resource status information of each low-orbit satellite based on the beam slot allocation strategy.

[0056] In this embodiment of the application, the beam and time slot allocation strategy is a set of rules for the management satellite to allocate inter-satellite communication link resources (including communication beam resources and communication time slot resources) to each low-orbit satellite within its coverage area. The purpose is to realize on-demand allocation of communication resources based on the differences in the amount of resource status data of each low-orbit satellite, improve the utilization rate of inter-satellite link resources, and reduce transmission congestion or resource waste caused by unreasonable allocation of communication resources.

[0057] The onboard communication equipment for controlling satellites has multi-beam parallel communication capabilities, which can provide communication services to multiple low-Earth orbit satellites simultaneously. The communication time slot resource divides the communication time into multiple consecutive time segments, and each time segment is allocated to one or more low-Earth orbit satellites for data transmission, so that the communication links of each low-Earth orbit satellite do not interfere with each other.

[0058] In some embodiments, the resource status data of each low-Earth orbit satellite can be sorted, and low-Earth orbit satellites with larger resource status data volumes can be allocated wider beam resources and longer communication time slots, so that low-Earth orbit satellites with larger data volumes can complete data transmission quickly and reduce transmission delay.

[0059] After determining the beam and time slot allocation strategy, the control satellite transmits this strategy to each low-Earth orbit (LEO) satellite via inter-satellite communication links, informing each LEO satellite of the corresponding communication beam, communication time slot, and transmission parameters (such as transmission rate and encoding method). Each LEO satellite, according to the beam and time slot allocation strategy, transmits resource status information—specifically, resource status changes compared to the previous update cycle—to the control satellite within the designated communication time slot using the designated communication beam.

[0060] Step 240: Construct a local satellite resource view within the coverage area based on the resource status information of each low-orbit satellite, and send synchronization information to the adjacent control satellites of the control satellite; the synchronization information includes the local satellite resource view and low-orbit satellites that will leave the coverage area of ​​the control satellite within a preset time period.

[0061] In this embodiment of the application, the local satellite resource view is a visualization data constructed by the control satellite based on the resource status information of all low-orbit satellites within its coverage area, which reflects the distribution and operational status of space-based resources in the covered airspace. It may include the real-time orbital position of each low-orbit satellite, resource status parameters (such as energy, equipment, and payload status), mission execution status, data transmission status, and other information.

[0062] The control satellite can organize, classify, and integrate the resource status information of each low-orbit satellite. Based on the real-time orbital position of each low-orbit satellite, it can locate each low-orbit satellite in the space-based resource coordinate system, associate the resource status parameters of each low-orbit satellite with the positioning information, and generate a visualized local satellite resource view, which facilitates the monitoring of space-based resource status within the coverage area of ​​the control satellite.

[0063] Neighboring control satellites refer to other control satellites whose coverage area is adjacent to that of the current control satellite. Neighboring control satellites can establish fixed communication links through a preset inter-satellite cooperation protocol to achieve synchronization of resource views and form a distributed space-based resource control network.

[0064] Synchronization information includes a local satellite resource view and information on low-Earth orbit (LEO) satellites that will leave the coverage area of ​​the currently managed satellite within a preset timeframe. The preset timeframe refers to the estimated time it will take for a LEO satellite to move from its current location out of the managed satellite's coverage area. This timeframe can be calculated based on the LEO satellite's orbital velocity and the distance from the current location to the coverage area boundary; for example, it can be set to 30 minutes or 1 hour. Proactively informing neighboring managed satellites of LEO satellites that will leave the current managed satellite's coverage area within the preset timeframe allows these neighboring satellites to obtain information about satellites about to enter their coverage area, enabling a seamless handover of LEO satellite control and ensuring uninterrupted updates to resource status information when LEO satellites move across managed satellite coverage areas.

[0065] In some embodiments, low-orbit satellites that will leave the coverage area of ​​controlled satellites within a preset time period can be determined based on satellite ephemeris.

[0066] Satellite ephemeris is a mathematical model of satellite orbital parameters, including Keplerian orbital elements such as the semi-major axis, eccentricity, orbital inclination, right ascension of the ascending node, argument of perigee, and mean perigee, or Cartesian coordinate parameters such as the position and velocity vector. Control satellites store ephemeris data for low-Earth orbit (LEO) satellites and can use orbital recursion algorithms to calculate the positions of each LEO satellite in real time, thereby determining which LEO satellites will leave the control satellite's coverage area within a preset timeframe.

[0067] In this embodiment, by determining the low-orbit satellites that will leave the coverage area of ​​the control satellite within a preset time period based on the satellite ephemeris, the control satellite can accurately identify satellite objects that are about to move out of its control range.

[0068] In some embodiments, the control satellites periodically exchange synchronization information, and each control satellite merges the local satellite resource views of the adjacent areas it receives with its own constructed local satellite resource views to gradually form a satellite network resource view that covers a wider range and has more complete information.

[0069] The space-based resource on-orbit update and management method based on prior historical information provided in this application acquires information from multiple low-Earth orbit (LEO) satellites within its coverage area during the current update cycle via a management satellite. It calculates the required amount of resource status data to be transmitted based on the historical resource status and mission information of each LEO satellite. This allows data transmission only for changes in resource status information compared to historical information, reducing excessive communication pressure in full-volume transmission mode. Based on this resource status data, a beam slot allocation strategy is determined, and the resource status information of each LEO satellite is acquired, improving the utilization rate of inter-satellite link resources. A local satellite resource view is constructed based on the resource status information of each LEO satellite and synchronized information, including this local satellite resource view, is sent to adjacent management satellites. Inter-satellite collaboration updates a complete satellite network resource view, reducing the processing load of single-satellite resource views and achieving distributed collaborative processing. This method enables autonomous on-orbit update and collaborative synchronization of satellite resource status information in a space-based environment independent of ground gateway stations, without waiting for LEO satellites to re-enter the network. This reduces the limitations imposed by ground gateway station distribution and national border coverage on information updates, improving the efficiency and real-time performance of satellite resource status information updates.

[0070] In some embodiments, acquiring multiple low-Earth orbit satellites that are within the coverage area of ​​the controlled satellites during the current update cycle includes: In response to the information update instructions periodically initiated by the control satellite, it receives information from the neighboring control satellites indicating low-orbit satellites that will leave the coverage area of ​​the neighboring control satellites within a preset time period; Based on the satellite ephemeris, low-Earth orbit (LEO) satellites that have left the coverage area of ​​the controlled satellites are deleted, and LEO satellites that will leave the coverage area of ​​adjacent controlled satellites within a preset time period are added to the coverage area of ​​the controlled satellites, resulting in multiple LEO satellites that are within the coverage area of ​​the controlled satellites in the current update cycle.

[0071] In this embodiment, the information update command is an internal trigger signal automatically generated by the control satellite at the start of each update cycle, used to initiate the update process of the current resource status information. This information update command can be triggered by an onboard timer or driven by a preset update schedule; this embodiment does not limit its generation.

[0072] The control satellites establish stable communication connections through inter-satellite links and exchange synchronization information using agreed-upon communication protocols. During the current update cycle, the control satellites receive synchronization messages from neighboring control satellites, parse the list of low-Earth orbit (LEO) satellites that are about to leave the coverage area of ​​neighboring control satellites contained in the synchronization messages, and determine information such as the satellite identifier, current orbital position, resource status summary, and estimated arrival time of these LEO satellites.

[0073] The control satellite can traverse and filter all low-Earth orbit (LEO) satellites based on satellite ephemeris data. LEO satellites that have moved outside the control satellite's coverage area are removed from the current coverage list. Furthermore, LEO satellites received from neighboring control satellites that are about to leave their coverage area within a preset timeframe are added to the current control satellite's coverage list. This results in a list of LEO satellites within the control satellite's coverage area during the current update cycle. It should be noted that the LEO satellites added to the current control satellite's coverage list are those that are about to leave the coverage area of ​​neighboring control satellites located behind the control satellite in its direction of movement.

[0074] In this embodiment, by receiving information from neighboring control satellites about low-Earth orbit (LEO) satellites that will leave their coverage area within a preset time period, the control satellite can obtain information about satellites that are about to enter its coverage area in advance. By combining this information with satellite ephemeris data, the control satellite can delete LEO satellites that have already left its coverage area and add LEO satellites that are about to leave their coverage area, which are transferred by neighboring control satellites, to its coverage area. This reduces the problem of blurred coverage boundaries or satellite omissions caused by satellite movement and improves the continuity of the on-orbit update process of satellite resource status information.

[0075] In some embodiments, the amount of resource status data required to be transmitted by each low-Earth orbit satellite is calculated based on historical information of each low-Earth orbit satellite, including: Determine the historical resource type and remaining historical resource quantity of each low-orbit satellite based on historical resource status information; Determine the historical mission priorities and execution schedules of each low-Earth orbit satellite based on historical mission information. Based on historical resource types, historical resource reserves, historical task priorities, and historical task execution progress, the data length and data frame format required for each low-orbit satellite to transmit data in the current update cycle are calculated. The data length and data frame format are used as the resource status data volume.

[0076] In this embodiment, historical resource type refers to the type of schedulable resources carried on the low-Earth orbit satellite, including but not limited to energy resource types (such as battery energy storage, solar panel power generation), communication resource types (such as transparent transponder bandwidth, regenerative processing payload processing capacity, solid-state memory capacity), computing resource types (such as onboard central processing unit computing power, digital signal processor load), attitude control resource types (such as momentum wheel remaining angular momentum, propellant remaining mass), etc.

[0077] Historical resource remaining quantity refers to the available remaining quantity of various historical resource types at the end of the previous update cycle, expressed in quantitative indicators such as remaining power percentage (%), available bandwidth in megahertz (MHz), and remaining storage capacity in gigabytes (GB).

[0078] Historical mission priority refers to the pre-assigned priority levels of various missions performed by low-Earth orbit satellites in the previous update cycle. This can be represented using a hierarchical coding system, such as urgent missions (priority level 1), important missions (priority level 2), routine missions (priority level 3), and low-priority missions (priority level 4). Mission priorities can be determined based on factors such as the importance of the service recipients, service quality requirements, and mission timeliness constraints. Higher priority missions indicate a need for stricter resource support and more frequent resource status monitoring, which may affect the calculation results of resource status data volume. For example, for low-Earth orbit satellites performing urgent missions, more detailed resource status parameter reporting is required to improve mission reliability.

[0079] Historical mission execution progress refers to the actual completion status of various tasks of low-orbit satellites in the previous update cycle, expressed as a percentage or status code, such as not started (0%), in progress (50%), completed (100%), abnormally aborted, etc.

[0080] Data length refers to the number of bits or bytes occupied by the resource status data that a low-Earth orbit (LEO) satellite needs to transmit to the control satellite in the current update cycle. Data frame format refers to the organization and encoding method of the resource status data, including the definition and length allocation of the frame header field, data field, and checksum field. The control satellite can determine the data length and data frame format of the data to be transmitted by each LEO satellite in the current update cycle by comprehensively considering historical resource types, historical resource availability, historical mission priorities, and historical mission execution progress, using a preset calculation model or lookup algorithm.

[0081] Based on the scale of status parameters corresponding to different historical resource types, combined with the consumption patterns and changes in resources by historical missions, the number of parameters, data bits, and information structure that may change in resource status information within the current update cycle can be estimated, thereby determining the overall data length required for transmission. The appropriate data frame format is determined based on the priority of different low-Earth orbit satellites and the historical mission execution progress. For example, for satellites in the midst of mission execution or with frequent mission switching, a larger estimated range of resource status changes is allocated, resulting in a longer data length to accommodate the changes; conversely, for satellites with idle missions or stable resource status, a smaller estimated range of changes is allocated, resulting in a shorter data length.

[0082] In some embodiments, historical resource type, historical resource remaining quantity, historical task priority, and historical task execution progress can be used as input variables, and data length suggestions and data frame formats can be output through a preset rule base or a trained neural network model.

[0083] In some embodiments, a resource status data lookup table can be pre-established, and the data length and data frame format of the data to be transmitted by each low-orbit satellite in the current update cycle can be calculated by looking up the table and interpolation.

[0084] In this embodiment, by determining the historical resource type and remaining amount of each low-orbit satellite based on historical resource status information, and by combining historical mission information to determine historical mission priority and execution progress, the prior historical information can be fully utilized to accurately reflect the resource usage patterns and mission execution status of low-orbit satellites. This allows the data length and data frame format to accurately reflect the actual update needs of each low-orbit satellite, thereby improving the accuracy of resource status data quantity measurement.

[0085] In some embodiments, determining a beam slot allocation strategy based on the amount of resource status data includes: Based on the data frame format, a unique corresponding communication beam is assigned to each low-Earth orbit satellite; Based on the data length, corresponding communication time slots are allocated to each low-Earth orbit satellite, and the order of communication time slots of each low-Earth orbit satellite is adjusted according to the historical mission priority of each low-Earth orbit satellite. The communication beams, communication time slots, and communication time slot order of each low-orbit satellite are used as the beam and time slot allocation strategy.

[0086] In this embodiment, the communication beam is a directional radio frequency beam formed by the inter-satellite link antenna of the control satellite, possessing specific physical parameters such as spatial pointing angle, beamwidth, carrier frequency, and polarization. Different data frame formats may correspond to different transmission reliability requirements and processing complexity. For example, extended data frames containing a large amount of diagnostic information require a more stable transmission link, while simplified data frames can tolerate a higher bit error rate. The control satellite can allocate a unique corresponding communication beam based on the data frame format characteristics of each low-Earth orbit satellite.

[0087] In some embodiments, communication beams with corresponding gain and anti-interference capabilities can be selected based on the complexity level and reliability requirements of the data frame format. Data frame formats with high complexity and high reliability requirements are allocated to beam resources with high gain, narrow beams, and low bit error rates, while data frame formats with low complexity and low reliability requirements can be allocated to beam resources with conventional gain. Considering the current orbital position and relative motion trend of each low-Earth orbit satellite, communication beams with spatial pointing angles can also be allocated to low-Earth orbit satellites to match the beam coverage with the satellite trajectory, thereby reducing the risk of frequent beam switching or link interruption caused by satellite movement.

[0088] In some embodiments, a data frame format-beam resource mapping table can be pre-established, and beam parameter combinations corresponding to various data frame formats can be predefined. After the data frame format is determined, a unique corresponding communication beam can be assigned to each low-orbit satellite by looking up the table.

[0089] A communication time slot refers to a dedicated transmission time period allocated to low-Earth orbit (LEO) satellites under a time-division multiple access (TDMA) system. The length of the communication time slot determines the upper limit of the amount of data that can be transmitted. Control satellites can allocate communication time slots that meet transmission requirements based on the data length calculations of each LEO satellite.

[0090] The control satellite can calculate the amount of effective data that can be transmitted per unit time slot based on the modulation and coding scheme of the current inter-satellite link, and then determine the communication time slot length that meets the data length requirements of each low-orbit satellite.

[0091] After the communication time slots are allocated, the control satellite can adjust the order of the communication time slots according to the historical mission priority of each low-Earth orbit satellite. For example, low-Earth orbit satellites with higher historical mission priority can be assigned to earlier communication time slots.

[0092] In this embodiment, by assigning a unique corresponding communication beam to each low-Earth orbit satellite according to the data frame format, signal interference between different low-Earth orbit satellites can be reduced, and the stability of inter-satellite communication can be improved. By assigning matching communication time slots to each low-Earth orbit satellite according to the data length, the time slot resources can be adapted to the actual transmission needs, improving the utilization efficiency of inter-satellite link resources. By adjusting the order of communication time slots in combination with the historical mission priority of each low-Earth orbit satellite, it can be ensured that satellites corresponding to high-priority missions complete the transmission of resource status information first, improving the efficiency of on-orbit updating of satellite resource status information.

[0093] In some embodiments, resource status information of each low-Earth orbit satellite is obtained according to a beam slot allocation strategy, including: According to the communication beams allocated in the beam slot allocation strategy, the communication beams of the control and management satellites are aligned with the corresponding low-Earth orbit satellites to establish communication links; Within the communication time slots defined by the beam time slot allocation strategy, resource status acquisition commands are sent to the corresponding low-Earth orbit satellites; Receive resource status information from each low-orbit satellite based on acquisition commands.

[0094] In this embodiment, the control satellite, based on the real-time orbital positions of each low-Earth orbit (LEO) satellite and the allocated communication beams, drives the antenna to adjust the beam direction so that the communication beams can cover the corresponding LEO satellites. After beam alignment, the control satellite and the LEO satellites complete a link handshake through a preset inter-satellite communication protocol to establish a two-way communication link.

[0095] The control satellite, following the allocated communication time slot sequence, sends resource status acquisition commands to the corresponding low-Earth orbit (LEO) satellites via established communication links within their dedicated communication time slots. These resource status acquisition commands may include information such as the LEO satellite identifier, a list of acquisition parameters, data transmission requirements, and acquisition time limits, instructing the LEO satellite to collect and upload its own resource status information according to preset requirements.

[0096] After receiving the resource status collection command sent by the control satellite, the low-orbit satellite collects its own current resource status information, encapsulates the collected resource status information according to the encoding method and data frame format required by the resource status collection command, and feeds back the encapsulated resource status information to the control satellite.

[0097] In this embodiment, by controlling the communication beam of the satellite to be aligned with the corresponding low-Earth orbit satellite according to the communication beam allocation strategy, the signal conflict and mutual interference of multiple satellites communicating simultaneously can be reduced. Resource status acquisition commands are sent within the allocated communication time slots, so that each low-Earth orbit satellite can respond within the preset time window, thereby reducing channel conflicts caused by concurrent communication of multiple satellites.

[0098] In some embodiments, a local satellite resource view within the coverage area is constructed based on the resource status information of each low-Earth orbit satellite, including: Using the current update cycle as the time node, obtain the orbital position information of each low-orbit satellite at the time node; By associating and mapping time points, orbital position information of each low-Earth orbit satellite, and resource status information of each low-Earth orbit satellite, a spatiotemporal status snapshot of the control satellite coverage area is formed, and the spatiotemporal status snapshot is used as a local satellite resource view.

[0099] In this embodiment, the control satellite uses the current update cycle time node as a reference. It can calculate the orbital position information of each low-Earth orbit (LEO) satellite at that time node based on the satellite ephemeris, or it can measure the signal transmission delay with the LEO satellite through inter-satellite ranging. Combined with the beam pointing angle, the relative position of the LEO satellite is calculated as its orbital position information. This orbital position information can include the LEO satellite's three-dimensional coordinates in the space-based resource coordinate system, orbital attitude parameters, and orbital velocity, characterizing the LEO satellite's spatial position and motion state at the current update cycle time node.

[0100] The management satellite can use time nodes as a unified index to bind the orbital position information of each LEO satellite with its resource status information. This ensures that the spatial position and resource status of the same LEO satellite correspond to the same time node. By integrating the associated data of time nodes, orbital position information, and resource status information of LEO satellites, a spatiotemporal state snapshot of LEO satellites within the management satellite's coverage area can be formed for the current update cycle. Alternatively, an index structure with LEO satellite identifiers as the primary key can be established, aggregating time nodes, orbital position information, and resource status information of each LEO satellite into the same data record to form a spatiotemporal state snapshot.

[0101] In this embodiment, the spatiotemporal state snapshot, i.e., the local satellite resource view, may include a view header (including time nodes, control satellite identifiers, etc.), a satellite record list (one record corresponding to each low-Earth orbit satellite, including satellite identifier, orbital position information, resource status information, etc.), and a view tail (including a view end identifier, optional digital signature or integrity verification fields, etc.). The local satellite resource view can clearly present the resource consumption and spatial distribution patterns of each low-Earth orbit satellite at a specific point in time, facilitating real-time monitoring and querying of space-based resource status within the coverage area by control satellites.

[0102] In this embodiment, by acquiring the orbital position information of each low-orbit satellite at the given time point, the on-orbit spatial position of each low-orbit satellite at the update time can be located. The time point, the orbital position information of each low-orbit satellite, and the resource status information of each low-orbit satellite are correlated and mapped to form a snapshot of the spatiotemporal status within the coverage area of ​​the control satellite. This allows the local satellite resource view to not only include the real-time resource status of low-orbit satellites, but also synchronously associate the on-orbit position with the update time, further improving the accuracy of on-orbit updates of space-based resources.

[0103] The on-orbit update and management method for space-based resources based on prior historical information provided in this application can be implemented by a space-based resource on-orbit update and management device based on prior historical information. This application uses the example of a space-based resource on-orbit update and management device based on prior historical information executing the method to illustrate the space-based resource on-orbit update and management device based on prior historical information provided in this application.

[0104] This application also provides a space-based resource on-orbit update and management device based on prior historical information.

[0105] like Figure 3 As shown, the space-based resource on-orbit update and management device based on prior historical information includes: The satellite control module 310 is used to acquire multiple low-orbit satellites that are within the coverage area of ​​the control satellites in the current update cycle; The control strategy determination module 320 is used to calculate the amount of resource status data that each low-orbit satellite needs to transmit based on the historical information of each low-orbit satellite. The historical information includes historical resource status information and historical mission information. The amount of resource status data is the change in the current resource status information of the low-orbit satellite compared to the historical resource status information. The module determines the beam slot allocation strategy based on the amount of resource status data and obtains the resource status information of each low-orbit satellite based on the beam slot allocation strategy. The resource view construction module 330 is used to construct a local satellite resource view within the coverage area based on the resource status information of each low-orbit satellite, and send synchronization information to the adjacent control satellites of the control satellite; the synchronization information includes the local satellite resource view and low-orbit satellites that will leave the coverage area of ​​the control satellite within a preset time period.

[0106] According to the space-based resource on-orbit update and management device based on prior historical information of this application, multiple low-orbit satellites within its coverage area are acquired through management satellites within the current update cycle. The required amount of resource status data to be transmitted is calculated based on the historical resource status information and historical mission information of each low-orbit satellite. Data transmission is only performed on the changes in resource status information compared to historical information, reducing the excessive communication pressure in full-volume transmission mode. A beam slot allocation strategy is determined based on this resource status data, and the resource status information of each low-orbit satellite is acquired, improving the utilization rate of inter-satellite link resources. A local satellite resource view is constructed based on the resource status information of each low-orbit satellite and synchronous information, including this local satellite resource view, is sent to adjacent management satellites. Inter-satellite collaboration updates a complete satellite network resource view, reducing the processing load of single-satellite resource views and achieving distributed collaborative processing. This enables autonomous on-orbit update and collaborative synchronization of satellite resource status information in a space-based environment independent of ground gateway stations, without waiting for low-orbit satellites to re-enter the network for updates. This reduces the limitations imposed by the distribution of ground gateway stations and national border coverage on information updates, improving the update efficiency and real-time performance of satellite resource status information.

[0107] In some embodiments, the satellite locking module 310 is further configured to: In response to the information update instructions periodically initiated by the control satellite, it receives information from the neighboring control satellites indicating low-orbit satellites that will leave the coverage area of ​​the neighboring control satellites within a preset time period; Based on the satellite ephemeris, low-Earth orbit (LEO) satellites that have left the coverage area of ​​the controlled satellites are deleted, and LEO satellites that will leave the coverage area of ​​adjacent controlled satellites within a preset time period are added to the coverage area of ​​the controlled satellites, resulting in multiple LEO satellites that are within the coverage area of ​​the controlled satellites in the current update cycle.

[0108] In some embodiments, the control strategy determination module 320 is further configured to: Determine the historical resource type and remaining historical resource quantity of each low-orbit satellite based on historical resource status information; Determine the historical mission priorities and execution schedules of each low-Earth orbit satellite based on historical mission information. Based on historical resource types, historical resource reserves, historical task priorities, and historical task execution progress, the data length and data frame format required for each low-orbit satellite to transmit data in the current update cycle are calculated. The data length and data frame format are used as the resource status data volume.

[0109] In some embodiments, the control strategy determination module 320 is further configured to: Based on the data frame format, a unique corresponding communication beam is assigned to each low-Earth orbit satellite; Based on the data length, corresponding communication time slots are allocated to each low-Earth orbit satellite, and the order of communication time slots of each low-Earth orbit satellite is adjusted according to the historical mission priority of each low-Earth orbit satellite. The communication beams, communication time slots, and communication time slot order of each low-orbit satellite are used as the beam and time slot allocation strategy.

[0110] In some embodiments, the control strategy determination module 320 is further configured to: According to the communication beams allocated in the beam slot allocation strategy, the communication beams of the control and management satellites are aligned with the corresponding low-Earth orbit satellites to establish communication links; Within the communication time slots defined by the beam time slot allocation strategy, resource status acquisition commands are sent to the corresponding low-Earth orbit satellites; Receive resource status information from each low-orbit satellite based on acquisition commands.

[0111] In some embodiments, the resource view building module 330 is further configured to: Using the current update cycle as the time node, obtain the orbital position information of each low-orbit satellite at the time node; By associating and mapping time points, orbital position information of each low-Earth orbit satellite, and resource status information of each low-Earth orbit satellite, a spatiotemporal status snapshot of the control satellite coverage area is formed, and the spatiotemporal status snapshot is used as a local satellite resource view.

[0112] In some embodiments, the satellite locking module 310 is further configured to: The low-orbit satellites that will leave the coverage area of ​​the controlled satellites within a preset time period are determined based on the satellite ephemeris.

[0113] The space-based resource on-orbit update and management device based on prior historical information in this application embodiment can be an electronic device or a component of an electronic device, such as an integrated circuit or a chip. The electronic device can be a satellite, such as a medium- or high-orbit satellite.

[0114] The space-based resource on-orbit update and management device based on prior historical information in this application embodiment can be a device with an operating system. This operating system can be a Microsoft (Windows) operating system, an Android operating system, an iOS operating system, or other possible operating systems; this application embodiment does not specifically limit it.

[0115] In some embodiments, this application also provides a satellite for performing the above-described method for on-orbit updating and management of space-based resources based on prior historical information.

[0116] In some embodiments, such as Figure 4As shown, this application embodiment also provides an electronic device 400, including a processor 401, a memory 402, and a computer program stored on the memory 402 and executable on the processor 401. When the program is executed by the processor 401, it implements the various processes of the above-described embodiment of the space-based resource on-orbit update and management method based on prior historical information, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0117] It should be noted that the electronic devices in the embodiments of this application include the aforementioned mobile electronic devices and non-mobile electronic devices.

[0118] This application also provides a non-transitory computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described embodiment of the space-based resource on-orbit update and management method based on prior historical information, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0119] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0120] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method for on-orbit updating and management of space-based resources based on prior historical information.

[0121] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0122] This application also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described embodiment of the space-based resource on-orbit update and management method based on prior historical information, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0123] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0124] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0125] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0126] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

[0127] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0128] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

Claims

1. A method for on-orbit updating and management of space-based resources based on prior historical information, characterized in that, include: The control satellite acquires multiple low-orbit satellites that are within the coverage area of ​​the control satellite in the current update cycle; The amount of resource status data that each low-Earth orbit satellite needs to transmit is calculated based on the historical information of each low-Earth orbit satellite; the historical information includes historical resource status information and historical mission information, and the amount of resource status data is the change in the current resource status information of the low-Earth orbit satellite compared to the historical resource status information. The beam slot allocation strategy is determined based on the amount of resource status data, and the resource status information of each low-Earth orbit satellite is obtained based on the beam slot allocation strategy. A local satellite resource view within the coverage area is constructed based on the resource status information of each low-orbit satellite, and synchronization information is sent to the adjacent control satellites of the control satellite; the synchronization information includes the local satellite resource view and low-orbit satellites that will leave the coverage area of ​​the control satellite within a preset time period.

2. The method according to claim 1, characterized in that, The acquisition of multiple low-Earth orbit satellites within the coverage area of ​​the controlled satellites in the current update cycle includes: In response to the information update command periodically initiated by the control satellite, receive information from the neighboring control satellites of the control satellite regarding low-orbit satellites that will leave the coverage area of ​​the neighboring control satellites within a preset time period; Based on the satellite ephemeris, low-orbit satellites that have left the coverage area of ​​the controlled satellite are deleted, and low-orbit satellites that will leave the coverage area of ​​adjacent controlled satellites within a preset time period are added to the coverage area of ​​the controlled satellite, resulting in multiple low-orbit satellites that are within the coverage area of ​​the controlled satellite in the current update cycle.

3. The method according to claim 1, characterized in that, The calculation of the amount of resource status data required to be transmitted by each low-Earth orbit satellite based on historical information includes: Based on the historical resource status information, determine the historical resource type and remaining historical resource quantity of each low-orbit satellite; The historical mission priority and execution progress of each low-Earth orbit satellite are determined based on the historical mission information. Based on the historical resource type, the remaining amount of historical resources, the historical task priority, and the historical task execution progress, the data length and data frame format of the data to be transmitted by each low-orbit satellite in the current update cycle are calculated. The data length and data frame format are used as the resource status data volume.

4. The method according to claim 3, characterized in that, The step of determining the beam slot allocation strategy based on the amount of resource status data includes: According to the data frame format, a unique corresponding communication beam is assigned to each low-Earth orbit satellite; Based on the data length, a corresponding communication time slot is allocated to each low-Earth orbit satellite, and the order of the communication time slots of each low-Earth orbit satellite is adjusted according to the historical mission priority of each low-Earth orbit satellite. The communication beams, communication time slots, and communication time slot order of each low-Earth orbit satellite are used as the beam and time slot allocation strategy.

5. The method according to claim 4, characterized in that, The step of obtaining resource status information for each low-Earth orbit satellite according to the beam slot allocation strategy includes: According to the communication beam allocated in the beam slot allocation strategy, the communication beam of the control and management satellite is aligned with the corresponding low-Earth orbit satellite to establish a communication link; Within the communication time slots defined by the beam time slot allocation strategy, a resource status acquisition command is sent to the corresponding low-Earth orbit satellite; Receive resource status information fed back by each low-orbit satellite based on the acquisition command.

6. The method according to claim 1, characterized in that, The construction of a local satellite resource view within the coverage area based on the resource status information of each low-Earth orbit satellite includes: Using the current update cycle as the time node, obtain the orbital position information of each low-orbit satellite at the time node; The time points, the orbital position information of each low-Earth orbit satellite, and the resource status information of each low-Earth orbit satellite are correlated and mapped to form a spatiotemporal status snapshot within the coverage area of ​​the controlled satellite, and the spatiotemporal status snapshot is used as the local satellite resource view.

7. The method according to claim 1, characterized in that, The method further includes: Based on the satellite ephemeris, determine the low-orbit satellites that will leave the coverage area of ​​the controlled satellites within a preset time period.

8. A space-based resource on-orbit update and management device based on prior historical information, characterized in that, include: The satellite control module is used to acquire multiple low-orbit satellites that are within the coverage area of ​​the controlled satellites in the current update cycle; The control strategy determination module is used to calculate the amount of resource status data that each low-Earth orbit satellite needs to transmit based on the historical information of each low-Earth orbit satellite; the historical information includes historical resource status information and historical mission information, and the amount of resource status data is the change in the current resource status information of the low-Earth orbit satellite compared with the historical resource status information; the module determines the beam slot allocation strategy based on the amount of resource status data, and obtains the resource status information of each low-Earth orbit satellite based on the beam slot allocation strategy; The resource view construction module is used to construct a local satellite resource view within the coverage area based on the resource status information of each low-orbit satellite, and send synchronization information to the adjacent control satellites of the control satellite; the synchronization information includes the local satellite resource view and low-orbit satellites that will leave the coverage area of ​​the control satellite within a preset time period.

9. A satellite, characterized in that, The satellite is used to perform the method as described in any one of claims 1-7.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-7.

Images