A method and system for the automatic batch execution of multiple satellite payload missions

Abstract

This invention discloses a method and system for the batch automatic execution of multiple satellite payload tasks. The method includes: defining a unified task instruction format for different payloads; the satellite operations center computer receiving multiple task instructions from different payloads on the ground, sorting them by start time, and storing them in a cache; the satellite operations center computer comparing the start time and current time of each task instruction in the cache with the current time, and sending the task instructions to the payload slave computer via a CAN bus at a pre-set time; the payload slave computer receiving the task instructions, sorting them by start time, storing them in the cache, and executing the tasks directly or after merging and optimizing them according to a preset work sequence and time interval. This invention improves the automation level of satellites and enhances their usability and ease of use.

Description

Technical Field

[0001] This invention belongs to the field of automatic optimization and autonomous management technology for satellite on-orbit missions, and particularly relates to a method and system for the automatic batch execution of multiple satellite payload missions. Background Technology

[0002] Currently, small satellites typically consist of two main parts: the satellite platform and the payload. The satellite platform includes the satellite administration subsystem (responsible for overall onboard management and mission scheduling), the power supply and distribution subsystem (responsible for onboard energy), the attitude and orbit control subsystem (responsible for overall satellite attitude control and bias), the thermal control subsystem (responsible for overall satellite thermal management), and the telemetry, tracking, and command (TT&C) subsystem (responsible for satellite-to-ground telemetry and control links). The payload typically includes imaging payloads (such as high-resolution visible cameras, infrared cameras, and hyperspectral cameras responsible for imaging), data processing payloads (such as onboard real-time processors responsible for on-orbit data processing), and data transmission payloads (responsible for satellite-to-ground data transmission). With the increasing number of satellite payload devices, the rich and flexible operating modes bring new challenges to satellite design and applications.

[0003] For the automatic optimization and autonomous management of satellite on-orbit missions, the satellite service subsystem typically uses programmed control commands and relative time programmed control commands. The operation of on-board equipment in imaging and data transmission modes is numerous and complex. Traditional on-board missions require manual design of the workflow of each payload according to the payload's working time, and then generating programmed control commands and relative programmed control commands to be uploaded to the satellite for execution. This is not only inefficient but also prone to errors. It does not take into account the optimization of each payload and cannot maximize the satellite's effectiveness. Summary of the Invention

[0004] The technical problem solved by this invention is to overcome the shortcomings of the prior art and provide a method and system for the batch automatic execution of multiple satellite payload missions. During on-orbit operation, it is only necessary to upload information such as payload type, start time, imaging duration, and parameters of multiple missions. Each payload can drive the execution of a mission with only one data block. There is no need to pay attention to the instruction sequence of each mission and the instruction scheduling between multiple lower-level machines, which improves the automation level of the satellite and enhances its usability and ease of use.

[0005] The objective of this invention is achieved through the following technical solution: a method for the batch automatic execution of multiple satellite payload tasks, comprising: defining a unified task instruction format for different payloads; the satellite service center computer receiving multiple task instructions from different payloads on the ground, sorting them according to their start time and storing them in a cache; the satellite service center computer comparing the start time and current time of each task instruction from different payloads in the cache, and sending the task instructions to the payload slave computer via the CAN bus at a preset time; after receiving the task instructions, the payload slave computer sorts them according to their start time and stores them in a cache, and executes the tasks directly or after merging and optimizing them according to a preset working sequence and time interval.

[0006] In the above-mentioned method for the batch automatic execution of multiple satellite payload missions, the unified mission execution instruction format is that the effective data sent through the CAN bus is a 64-byte data block. Different payloads need to be designed to support this working mode of driving one imaging mission with one data block. The 64-byte data block must at least include the data header, mission number, mission mode, mission start time, duration, gain parameter, series parameter, TDI parameter, longitude, latitude, target pointing angle, solar altitude angle, and ground reflectivity.

[0007] In the above-mentioned method for automatically executing multiple satellite payload tasks in batches, the satellite service center computer refers to the satellite's central management computer, which communicates and manages with other lower-level computers on the satellite via the CAN bus.

[0008] In the above-mentioned method for the batch automatic execution of multiple satellite payload tasks, different payloads refer to various payloads configured on the satellite, which perform different imaging, data processing, or data transmission tasks; among them, different payloads include panchromatic camera a, infrared camera b, hyperspectral camera c, on-board processor d, and data transmission unit e.

[0009] In the above-mentioned method for the automatic batch execution of multiple satellite payload tasks, multiple task instructions refer to the m instructions corresponding to the same payload executing m batch tasks; for example, if the panchromatic camera a captures 3 targets, it corresponds to 3 task instructions; or multiple payloads execute batch tasks corresponding to x+y+z instructions; for example, if the panchromatic camera a captures 5 targets, the on-board processor c processes 3 of the targets, and the data transmission unit transmits 2 of the targets, it corresponds to 10 task instructions.

[0010] In the above-mentioned method for automatically executing multiple satellite payload tasks in batches, storing them in the cache after sorting by start time means that multiple 64-byte task instructions are stored in the cache of the satellite service center computer according to their task start time from smallest to largest.

[0011] In the above-mentioned method for the batch automatic execution of multiple satellite payload tasks, comparing the task start time and the current time one by one means that the satellite service center computer compares the task start time in UTC seconds contained in the task instruction with its own UTC seconds; the pre-set time refers to the agreed amount of time for a satellite service to send a task instruction. If the task start time in UTC seconds of this task instruction minus its own UTC seconds equals the amount of time for a satellite service to send a task instruction, then this task instruction is sent to the payload lower-level machine according to the payload identifier.

[0012] In the above-mentioned method for the batch automatic execution of multiple satellite payload tasks, the direct execution of tasks involves the payload lower-level machine receiving the task instruction, first determining whether the instruction format meets the 64-byte standard convention, and if so, extracting the valid information. When the task starts, it executes the predetermined actions according to the power-on, initialization, and execution process to complete the task.

[0013] In the above-mentioned method for automatically executing multiple satellite payload tasks in batches, the optimized task execution involves the payload lower-level computer receiving multiple task instructions and determining whether the multiple tasks can be completed in one power-on operation. If so, the tasks are merged and completed in one power-on operation, eliminating the need for repeated power-on and power-off operations.

[0014] A system for the batch automatic execution of multiple satellite payload tasks includes: a first module for defining a unified task instruction format for different payloads; a second module for receiving multiple task instructions from different payloads on the ground via a satellite operations center computer, sorting them by start time, and storing them in a cache; a third module for comparing the start time and current time of each task instruction in the cache with the current time via a CAN bus, and sending the task instructions to the payload slave device at a preset time; and a fourth module for the payload slave device to receive the task instructions, sort them by start time, store them in a cache, and execute the tasks directly or after merging and optimizing them according to a preset working sequence and time interval.

[0015] Compared with the prior art, the present invention has the following advantages:

[0016] This invention addresses the problems of numerous and complex operations of onboard equipment for satellite imaging and data transmission mode switching, as well as the low efficiency and error-prone design of programmable and relative programmable commands. It provides a method for the automatic execution of multiple satellite payload tasks. During on-orbit operation, only information such as payload type, start time, imaging duration, and parameters of multiple tasks needs to be uploaded. Each payload can drive the execution of a task with only one data block, eliminating the need to concern oneself with the command sequence of each task and the command scheduling between multiple lower-level machines. This improves the automation level of the satellite and enhances its usability and ease of use. Attached Figure Description

[0017] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0018] Figure 1 This is a flowchart of the implementation method for the batch automatic execution of satellite multi-payload tasks provided in the embodiments of the present invention. Detailed Implementation

[0019] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the disclosure to those skilled in the art. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0020] Figure 1 This is a flowchart illustrating the implementation method for the batch automatic execution of multiple satellite payload tasks provided in this embodiment of the invention. Figure 1 As shown, the method includes the following steps:

[0021] 1) Define a unified task instruction format for different loads. The instruction format should include the task number, load identifier, load start time, working duration, priority, working parameters and other parameters required for automatic task execution.

[0022] 2) The Star Service Center computer receives multiple mission instructions from different payloads on the ground, sorts them according to their start time, and stores them in a cache;

[0023] 3) The Star Service Center computer compares the start time and current time of each task instruction for different payloads in the cache, and sends the task instructions to the corresponding payload slave device via the CAN bus a certain time in advance.

[0024] 4) After receiving the task instruction, the lower-level payload computer sorts it according to the start time and stores it in the cache. It then executes the task directly or after merging and optimizing the tasks according to the pre-designed work sequence and time interval.

[0025] The unified task execution instruction format in step 1) refers to a 64-byte data block for valid data transmitted via the CAN bus. Different payloads need to be designed to support this working mode where one data block drives one imaging task. The 64-byte data block must at least include a data header, task number, task mode, task start time (UTC whole second), duration (seconds), gain parameters, level parameters, TDI parameters, longitude, latitude, target pointing angle, solar altitude angle, and ground reflectivity.

[0026] The satellite management center computer in step 2) refers to the satellite's central management computer, which communicates and manages with other lower-level computers on the satellite via the CAN bus.

[0027] The different payloads in step 2) refer to the various payloads configured on the satellite, which can perform different imaging, data processing, or data transmission tasks, such as panchromatic camera a, infrared camera b, hyperspectral camera c, on-board processor d, and data transmission unit e. This embodiment takes on-board high-resolution camera a, wide-field camera b, on-board real-time processor c, and data transmission unit d as examples.

[0028] In step 2), multiple task instructions refer to the m instructions corresponding to the same payload executing m batch tasks. For example, if panchromatic camera a captures 3 targets, there are 3 corresponding task instructions; or multiple payloads executing batch tasks correspond to (x+y+z) instructions. For example, if panchromatic camera a captures 5 targets, on-board processor c processes 3 of them, and data transmission unit transmits 2 of them, there are 10 corresponding task instructions. This embodiment uses the example of high-resolution camera a capturing 1 target, wide-field camera b capturing 1 target, on-board processor performing region extraction, and data transmission unit performing transmission.

[0029] Step 2) refers to storing multiple 64-byte task instructions in the cache according to their task start time (UTC whole second), from smallest to largest, in the cache of the space service center computer.

[0030] Step 3) involves comparing the task start time and the current time one by one. This means that the satellite service center computer compares the task start time (in UTC seconds) contained in the task instruction with its own UTC seconds. The "advance time" in step 3) refers to agreeing on a timeframe for a satellite service to send a task instruction, such as 60 seconds. If the task start time (in UTC seconds) of this instruction minus its own UTC seconds equals 60 seconds, then this task instruction is sent to the corresponding payload slave device according to the payload identifier.

[0031] Step 4) refers to the process of directly executing the task according to the pre-designed working sequence and time interval. After receiving the task instruction, the lower-level machine of the payload first determines whether the instruction format meets the standard convention of 64 bytes. If it does, it extracts the valid information and then executes the predetermined actions according to the internal process of power-on, initialization, and execution when the task starts, thus completing the task.

[0032] Step 4) refers to the process of merging and optimizing tasks. After receiving multiple task instructions, the lower-level payload determines whether the multiple tasks can be completed in one power-on operation. If so, the tasks are merged and completed in one power-on operation without repeated power-on and power-off operations.

[0033] Specifically, step 1): Define a unified task instruction format for different loads. The instruction format should include the task number, load identifier, load start time, working duration, priority, working parameters and other parameters required for automatic task execution.

[0034] The four payloads—high-resolution camera, infrared camera, real-time processor, and data transmission—are defined with a unified instruction format as shown below. While the formats may not be identical, the data block length must be the same, and all must include at least the task number, payload identifier, payload start time, duration, priority, and operating parameters required for automatic task execution.

[0035] Table 1 High-resolution camera imaging command data block

[0036]

[0037]

[0038] Table 2 Wide-field camera imaging command data block

[0039]

[0040]

[0041] Table 3 Real-Time Processor Task Instruction Data Block

[0042]

[0043] Table 4 Data Transmission Task Instruction Data Block

[0044]

[0045]

[0046]

[0047] Step 2): This embodiment takes the simultaneous shooting by a high-resolution camera and a wide-field camera starting at 12:30:00 on February 15, 2023, and the onboard task of extracting a 6km*6km area from the high-resolution camera as an example. The instructions on the ground are shown in the table below:

[0048] Table 5 Different Lower-Level Machine Instructions

[0049]

[0050] After these instructions are transmitted from the ground to the satellite, the satellite's mission center computer stores them in chronological order of start time, with data transmission first, followed by high-resolution cameras and real-time processors, and wide-field cameras last.

[0051] Step 3: The Star Service Center computer compares the start time and current time of each task instruction from different payloads in the cache, and sends the task instruction to the corresponding payload slave device via the CAN bus a certain time in advance.

[0052] In this embodiment, the data transmission instruction is sent to the corresponding lower-level machine 60 seconds in advance. When the time reaches 12:28:50 on 2023 / 2 / 15, the satellite host sends the 5th data transmission instruction to the data transmission unit. When the time reaches 12:29:00 on 2023 / 2 / 15, the satellite host sends the 1st instruction to the high-resolution camera, the 4th instruction to the real-time processor at 12:29:01, and the 3rd instruction to the wide-field camera at 12:29:02.

[0053] Step 4: After receiving the task instructions, the lower-level payload computer sorts them according to the start time and stores them in the cache. It then executes the tasks directly or after merging and optimizing them according to the pre-designed work sequence and time interval.

[0054] In this example, after receiving the instruction, the lower-level machine of the high-resolution camera will set the status according to the parameters in the data block, then power on the imaging unit to execute the shooting and output;

[0055] After receiving the instruction, the lower-level machine of the wide-field camera will set the status according to the parameters in the data block, and then power on the imaging unit to execute the shooting and output;

[0056] After receiving the instruction, the real-time processor sets its status according to the parameters in the data block, then powers on and waits for high-resolution camera data input. Afterward, it performs 6km x 6km region extraction based on information from the auxiliary data.

[0057] After receiving the instruction, the data transmission unit will set parameters such as file number, storage status, compression ratio, and rate according to the parameters in the data block, and then power on to execute data recording.

[0058] This embodiment also provides a system for the batch automatic execution of multiple satellite payload tasks. The system includes: a first module for defining a unified task instruction format for different payloads; and a second module for receiving multiple task instructions from different payloads on the ground through the satellite service center computer, sorting them according to their start time, and storing them in a cache.

[0059] The third module is used to compare the start time and current time of multiple task instructions for different payloads in the cache through the computer at the space service center, and send the task instructions to the payload lower-level machine via the CAN bus at a preset time. The fourth module is used to store the task instructions in the cache after the payload lower-level machine receives the task instructions according to the start time, and execute the tasks directly or after merging and optimizing them according to the preset working sequence and time interval.

[0060] This embodiment enables automatic execution of multiple payload tasks at the designated time. During on-orbit operation, it is only necessary to upload information such as payload type, start time, imaging duration, and parameters for multiple tasks. Each payload can drive a task with just one data block, eliminating the need to focus on the instruction sequence for each task and the instruction scheduling between multiple lower-level machines. This improves the automation level of the satellite and enhances its usability and ease of use.

[0061] Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make possible changes and modifications to the technical solutions of the present invention by utilizing the methods and techniques disclosed above without departing from the spirit and scope of the present invention. Therefore, any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solutions of the present invention shall fall within the protection scope of the technical solutions of the present invention.

Claims

1. A method for automatically executing multiple satellite payload tasks in batches, characterized in that... include: Define a unified task instruction format for different loads; The satellite mission center's computer receives multiple mission instructions from different payloads on the ground, sorts them according to their start time, and stores them in a cache. The Star Service Center computer compares the start time and current time of each task instruction from different payloads in the cache, and sends the task instructions to the payload slave computer via the CAN bus at a pre-set time. After receiving the task instructions, the lower-level payload computer sorts them according to the start time and stores them in the cache. It then executes the tasks directly or after merging and optimizing them according to the preset working sequence and time interval.

2. The method for automatically executing multiple satellite payload tasks in batches according to claim 1, characterized in that: The unified task execution instruction format is a 64-byte data block of valid data sent via the CAN bus. Different payloads need to be designed to support this working mode of driving an imaging task with one data block. The 64-byte data block must include at least the data header, task number, task mode, task start time, duration, gain parameter, level parameter, TDI parameter, longitude, latitude, target pointing angle, solar altitude angle, and ground reflectivity.

3. The method for automatically executing multiple satellite payload tasks in batches according to claim 1, characterized in that: The satellite management center computer refers to the central management computer of the satellite, which communicates and manages with other lower-level computers on the satellite via the CAN bus.

4. The method for automatically executing multiple satellite payload tasks in batches according to claim 1, characterized in that: Different payloads refer to the various payloads configured on the satellite that perform different imaging, data processing, or data transmission tasks; among them, different payloads include panchromatic camera a, infrared camera b, hyperspectral camera c, on-board processor d, and data transmission unit e.

5. The method for automatically executing multiple satellite payload tasks in batches according to claim 1, characterized in that: Multiple task instructions refer to the m instructions corresponding to the same payload executing m batch tasks; for example, if the panchromatic camera a captures 3 targets, then there are 3 task instructions; or multiple payloads executing batch tasks correspond to x+y+z instructions; for example, if the panchromatic camera a captures 5 targets, the on-board processor c processes 3 of them, and the data transmission unit transmits 2 of them, then there are 10 task instructions.

6. The method for automatically executing multiple satellite payload tasks in batches according to claim 1, characterized in that: Sort by start time and store in cache means that multiple 64-byte task instructions are stored in the cache of the space agency computer according to their start time, from smallest to largest.

7. The method for automatically executing multiple satellite payload tasks in batches according to claim 1, characterized in that: Comparing the task start time and the current time one by one means that the Star Service Center computer compares the task start time in UTC seconds contained in the task instruction with its own UTC seconds. The pre-set time refers to the agreed time for a satellite to send a task instruction. If the time of the task start time in UTC seconds minus the time of the task instruction itself in UTC seconds equals the time for a satellite to send a task instruction, then this task instruction is sent to the payload lower-level machine according to the payload identifier.

8. The method for automatically executing multiple satellite payload tasks in batches according to claim 1, characterized in that: When the lower-level device receives the task instruction, it first determines whether the instruction format meets the 64-byte standard convention. If it does, it extracts the valid information and then performs the predetermined actions according to the power-on, initialization, and execution process to complete the task.

9. The method for automatically executing multiple satellite payload tasks in batches according to claim 1, characterized in that: After merging and optimizing, the lower-level payload receives multiple task instructions and determines whether the multiple tasks can be completed in one power-on operation. If so, the tasks are merged and completed in one power-on operation, eliminating the need for repeated power-on and power-off operations.

10. A system for automatically executing multiple satellite payload missions in batches, characterized in that... include: The first module is used to define a unified task instruction format for different payloads; The second module is used to receive multiple mission instructions from different payloads injected on the ground through the computer of the satellite service center, and store them in the cache after sorting them according to the start time. The third module is used to compare the start time and current time of multiple task instructions for different payloads in the cache through the Star Service Center computer, and send the task instructions to the payload lower-level machine through the CAN bus at a preset time. The fourth module is used to receive task instructions from the payload lower-level machine, sort them according to the start time, store them in the cache, and execute the tasks directly or after merging and optimizing them according to the preset working sequence and time interval.

Images