On-orbit reconstruction method and system for high-capacity software of low-orbit satellite

Abstract

The invention provides a low-orbit satellite high-capacity software on-orbit reconstruction method and system, and belongs to the field of satellite on-orbit reconstruction, and the method comprises the steps: S1, carrying out the batch and framing processing of an ultra-large-capacity reconstruction packet on the ground; s2, the satellite-borne management software verifies and writes the information service unit DRAM temporary area; s3, the satellite-borne management software carries out continuity verification on the current batch of reconstruction files in the DRAM temporary area, a result is downloaded to the ground, and the ground carries out supplementary injection of an error-missing packet according to telemetering; s4, the spaceborne management software writes the reconstructed file which is verified to be normal into a FLASH buffer area; s5, the satellite-borne management software forwards the complete reconstruction files to a terminal reconstruction unit in batches; and S6, after the terminal reconfiguration unit operates the reconfiguration version for a period of time, the spaceborne management software writes the reconfiguration file into the FLASH solidification area according to a ground instruction, and the reconfiguration file is used as a backspacing version. According to the method, the problem of on-orbit reconstruction of ultra-large-capacity software is solved, and the reconstruction efficiency of the satellite in the controllable arc section is improved.

Description

Technical Field

[0001] The present invention belongs to the field of satellite on-orbit reconstruction, and in particular, relates to a method and system for on-orbit reconstruction of large-capacity software of a low-orbit satellite. Background Art

[0002] Low-orbit satellites refer to artificial satellites that operate in orbits below 2,000 kilometers from the earth's surface. They have the advantages of wide coverage, short transmission delay, and low cost, and are widely used in communications, navigation, remote sensing, and other fields. With the continuous improvement of the functions and performance of low-orbit satellites, the software they carry is becoming more and more complex and large, and needs to be updated and maintained on-orbit to adapt to the ever-changing needs. However, the on-orbit reconstruction of low-orbit satellites faces many challenges, such as the limited controllable arc segment of communication between satellites and ground tracking and control stations, unstable communication links, and other problems, which lead to low reconstruction efficiency, high risk of reconstruction failure, and poor software reliability after reconstruction. For ultra-large-capacity reconstruction files, such as the reconstruction file capacity of the V7 series FPGA, can reach 200MB. Due to the limited controllable arc segment of low-orbit satellites, the average communication time with the ground is only 7-8 minutes per orbit. Ultra-large-capacity reconstruction files must be uploaded in batches. If the reconstruction files uploaded in batches are abnormal, they need to be re-uploaded, which greatly reduces the efficiency of on-orbit reconstruction. On the other hand, due to the limited cache space of the information service unit, it is difficult to process the large-capacity reconstruction package in the same way as the small-capacity reconstruction package is cached in the DRAM temporary area and then directly forwarded to the terminal reconstruction unit. If the reconstruction file does not run properly, it will take too long to re-upload the reconstruction package from the ground, which will directly affect the normal operation of the terminal and even threaten the health of the satellite. Therefore, an effective solution must be proposed to achieve a reconstruction method for efficient uploading of large-capacity reconstruction packages, processing and forwarding by the information service unit.

[0003] The existing methods for large-capacity satellite software reconstruction mainly include the following: one is to split the reconstruction file into multiple small files, upload them to the satellite's memory in batches, and then splice and verify them on the satellite's terminal reconstruction unit, and finally replace the original software. The disadvantage of this method is that for ultra-large-capacity software reconstruction packages, when there are many small files that need to be split, the redundancy of the software and hardware equipment for processing the reconstruction package on the entire satellite will be significantly increased, wasting resources. If a small file is lost or damaged, the entire reconstruction file will be unusable and need to be re-uploaded, increasing the cost and risk of reconstruction.

[0004] The other method is to compress the reconstructed file into a smaller file, upload it to the satellite's memory at one time, then decompress and verify it on the satellite, and finally replace the original software. The disadvantage of this method is that the compression and decompression process consumes the satellite's computing resources and power, and the compression rate is affected by the content and structure of the reconstructed file. It cannot guarantee that the compressed file can be uploaded within the limited communication time window, which also increases the difficulty and uncertainty of reconstruction.

[0005] Therefore, the existing on-orbit reconstruction method of low-orbit satellite software still has problems such as low efficiency, poor reliability, and poor maintainability. Especially for ultra-large capacity software, these problems are more prominent. There is an urgent need for a new on-orbit reconstruction method of low-orbit satellite software to improve the ability and effect of on-orbit update and maintenance of low-orbit satellite software. Summary of the invention

[0006] In view of the defects in the prior art, the purpose of the present invention is to provide a method and system for on-orbit reconstruction of large-capacity software of low-orbit satellites.

[0007] According to the present invention, a method for reconfiguring large-capacity software on a low-orbit satellite on-orbit includes:

[0008] Step S1: The ground subpackaging software processes the ultra-large capacity software reconstruction package into batches and frames into ultra-large capacity reconstruction files, and then uploads the ultra-large capacity reconstruction files to the satellite in batches through the ground measurement and control channel;

[0009] Step S2: The onboard management software verifies the contents of the ultra-large capacity reconstruction files uploaded in batches, and writes them into the temporary DRAM area of ​​the information service unit after the verification is normal;

[0010] Step S3: The onboard management software performs continuity check on the current batch of ultra-large capacity reconstruction files in the temporary DRAM area of ​​the information service unit, and transmits the check result to the ground in the form of telemetry, and the ground performs supplementary annotation of missing error packets based on the telemetry;

[0011] Step S4: the onboard management software writes the current batch of ultra-large capacity reconstruction files that have been verified to be normal in the temporary area of ​​the information service unit DRAM into the FLASH buffer;

[0012] Step S5: The onboard management software forwards the complete ultra-large capacity reconstruction files in the FLASH buffer of the information service unit to the terminal reconstruction unit in batches;

[0013] Step S6: After the terminal reconstruction unit runs the reconstructed version normally for a period of time, the onboard management software writes the reconstructed file in the FLASH buffer of the information service unit into the FLASH solidification area according to the ground command, and uses it as a fallback version.

[0014] Preferably, the batch processing in step S1 includes:

[0015] Before the reconstruction process begins, the ground subpacketization software splits the ultra-large capacity reconstruction package into several reconstructed remote control packages of equal length according to the length of the remote control package. The number of batches marked on the reconstruction package is calculated based on the total byte length of the remote control package, with X MB as a batch. X MB is the maximum capacity of the DRAM storage area of ​​the onboard reconstruction package. The number of batches is the integer of the result of dividing the capacity of the ultra-large capacity reconstruction package by X and adding 1.

[0016] The framing process in step S1 includes: framing each reconstructed packet according to the format of the above-mentioned frame.

[0017] Preferably, the betting method in step S1 is:

[0018] At the beginning of the reconstruction process, the ground first sends an injection number instruction to the information service unit; the instruction content includes: the reconstruction object, the total number of reconstructed packages uploaded this time, and the number of batches to be injected; the ultra-large capacity reconstruction packages that have been split and framed by the ground subpackaging software are injected in batches through the ground injection channel in batch order, and after being received by the transponder, they are transmitted to the information service unit through the channel gateway.

[0019] Preferably, in step S2, the onboard management software verifies the contents of the first batch of reconstruction packets, verifies the packet length and the correctness of the verification information, and writes the reconstructed packets that pass the verification into the temporary DRAM area of ​​the information service unit.

[0020] Preferably, in step S3, after the first batch of reconstruction packages are filled and verified, the onboard management software performs continuity verification on the reconstruction packages in the temporary DRAM area of ​​the information service unit, verifies the number and sequence number of the missing packets in the reconstruction packages, and transmits the verification results to the ground in the form of telemetry, and the ground fills in the missing packets based on the telemetry information.

[0021] Preferably, in step S4, after all reconstruction packets are verified to be normal, the onboard management software writes the first batch of reconstruction packets in the temporary DRAM area of ​​the information service unit into the FLASH buffer;

[0022] After receiving the reconstruction package and verifying the normal telemetry, the ground continues to send the next batch of reconstruction packages until all reconstruction packages are uploaded in batches and a complete reconstruction file is stored in the FLASH buffer.

[0023] Preferably, in step S5, the onboard management software first forwards the complete reconstruction file from the information service unit FLASH buffer to the terminal reconstruction unit in the reconstruction package format required by the ground transmission instruction in batch order;

[0024] The content of the ground-based instruction includes: reconstruction object, reconstruction packet forwarding format, and time interval of reconstruction packet forwarding terminal.

[0025] Preferably, in step S6, after the terminal reconstruction unit runs the reconstructed version normally for a period of time, the ground sends an instruction, and the onboard management software writes the reconstructed file in the FLASH buffer of the information service unit into the FLASH solidification area in batch order according to the ground instruction, and uses it as a fallback version.

[0026] Preferably, in step S6, when the terminal reconstruction unit needs to restore to the previous version of the reconstruction file, the ground sends an instruction, and the instruction content includes: reconstruction object, reconstruction packet forwarding format, and time interval of the reconstruction packet forwarding terminal;

[0027] The onboard management software forwards the reconstruction files in the FLASH hardening area of ​​the information service unit to the terminal reconstruction unit in batch order according to the ground instructions.

[0028] A low-orbit satellite large-capacity software on-orbit reconstruction system, comprising:

[0029] Module M1: The ground subpackaging software batches and frames the ultra-large capacity software reconstruction packages into ultra-large capacity reconstruction files, and then uploads the ultra-large capacity reconstruction files to the satellite in batches through the ground measurement and control channel;

[0030] Module M2: The onboard management software verifies the contents of the large-capacity reconstruction files uploaded in batches, and writes them into the temporary DRAM area of ​​the information service unit after the verification is normal;

[0031] Module M3: The onboard management software performs continuity verification on the current batch of ultra-large capacity reconstruction files in the temporary DRAM area of ​​the information service unit, and transmits the verification results to the ground in the form of telemetry. The ground then supplements the missing error packets based on the telemetry.

[0032] Module M4: The onboard management software writes the current batch of ultra-large capacity reconstruction files that have been verified to be normal in the temporary area of ​​the DRAM of the information service unit into the FLASH buffer;

[0033] Module M5: The onboard management software forwards the complete ultra-large capacity reconstruction files in the FLASH buffer of the information service unit to the terminal reconstruction unit in batches;

[0034] Module M6: After the terminal reconstruction unit runs the reconstruction version normally for a period of time, the onboard management software writes the reconstruction file in the FLASH buffer of the information service unit into the FLASH solidification area according to the ground command, which is used as a fallback version.

[0035] Compared with the prior art, the present invention has the following beneficial effects:

[0036] 1. By solving the problem of on-orbit reconstruction of ultra-large-capacity software, the rate correlation between the ground injection segment and the on-board forwarding segment is decoupled, and the efficiency of satellite reconstruction within the controllable arc segment is improved;

[0037] 2. By using ground-based packaging software to process large-capacity software reconstruction packages in batches and frames, hundreds of reconstruction files from different terminals are processed in a unified format, which significantly improves the efficiency of file construction on the ground and improves the convenience and reliability of verification, forwarding, and storage of reconstruction packages by onboard management software;

[0038] 3. By using the coordinated work of the information service unit DRAM temporary area and the FLASH buffer, the reconstruction package is transferred and processed between different memories, realizing batch verification and temporary storage of ultra-large capacity reconstruction packages, ensuring the integrity and correctness of the reconstruction file while improving the efficiency of reconstructed package injection. When the verification is abnormal, the missing package can be reissued according to the specified address to avoid re-injection, which will cause the reconstruction time to be too long and affect normal work;

[0039] 4. By adopting the collaborative work of FLASH buffer and FLASH solidification area, the backup and recovery of reconstructed files are realized, the rollback and recoverability of reconstructed files are improved, and the stability and flexibility of the reconstructed software are guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0041] Figure 1 This is a schematic diagram of the ultra-large capacity software reconstruction method for low-orbit satellites;

[0042] Figure 2 It is the workflow diagram of ground subcontracting software;

[0043] Figure 3 Reconstructed the workflow diagram for the onboard management software;

[0044] Figure 4 This is the workflow diagram for version rollback of onboard management software. DETAILED DESCRIPTION

[0045] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0046] The present application discloses a method for reconstructing large-capacity software on a low-orbit satellite on-orbit, the method comprising: ground subpackaging software, satellite management software, an information service unit storage module and a terminal reconstruction unit, wherein the information service unit storage module comprises a DRAM temporary area, a FLASH buffer area and a FLASH solidification area. The ground subpackaging software performs batch and frame processing on the ultra-large-capacity software to be reconstructed, and the satellite management software in the FLASH solidification area first verifies the large-capacity reconstruction files uploaded in batches, and writes the reconstruction files from the DRAM temporary area to the FLASH buffer area for temporary storage after the single batch verification is normal; after all batches are uploaded, the management software forwards the complete reconstruction files in the FLASH buffer area to the terminal reconstruction unit at a terminal-specific transmission rate; after the terminal reconstruction unit receives the reconstruction and operates normally, the satellite management software writes the complete reconstruction files in the FLASH buffer area of ​​the information service unit into the FLASH solidification area, which is used as a fallback version of the terminal reconstruction unit, without the need for re-uploading on the ground.

[0047] Figure 1 Schematic diagram of the ultra-large capacity software reconstruction method for low-orbit satellites of this application, such as Figure 1 As shown, the reconstruction method of the low-orbit satellite ultra-large capacity software of the present invention includes the following parts:

[0048] Embodiment 1:

[0049] Step S1: The ground subpackaging software processes the large-capacity software reconstruction package in batches and frames it, and then injects it to the satellite through the ground measurement and control channel;

[0050] Before the reconstruction process begins, the ground subpacketization software will split the ultra-large capacity reconstruction package according to the length of the remote control package, and split it into several reconstructed remote control packages of equal length. According to the total byte length of the remote control package, the number of batches of the reconstruction package is calculated with X MB as a batch. X MB is generally the maximum capacity of the DRAM storage area of ​​the reconstruction package on the satellite. For example, if the capacity of the ultra-large capacity reconstruction package is Y MB, the number of batches is the integer of Y divided by X plus 1. Finally, each reconstruction package is framed according to the format of the frame noted above.

[0051] At the beginning of the reconstruction process, the ground sends a note number instruction to the information service unit, which includes the reconstruction object, the total number of reconstructed packages uploaded this time, and the number of batches uploaded. Then, the ultra-large capacity reconstruction packages that have been split and framed by the ground subpackaging software are uploaded in batches through the ground upload channel in batch order, and after being received by the transponder, they are transmitted to the information service unit through the channel gateway.

[0052] Step S2: The onboard management software verifies the contents of the ultra-large capacity reconstruction files uploaded in batches, and writes them into the temporary DRAM area of ​​the information service unit after the verification is normal;

[0053] The onboard management software verifies the contents of the first batch of reconstruction packets, verifies the packet length, and the correctness of the verification information, and writes the reconstruction packets that pass the verification into the temporary DRAM area of ​​the information service unit.

[0054] Step S3: The onboard management software performs continuity check on the current batch of reconstruction files in the temporary DRAM area of ​​the information service unit, and transmits the check result to the ground in the form of telemetry, and the ground performs supplementary annotation of missing error packets based on the telemetry;

[0055] After the first batch of reconstruction packets are filled and verified, the onboard management software performs continuity verification on the reconstruction packets in the temporary DRAM area of ​​the information service unit, verifies the number and sequence number of the missing packets in the reconstruction packets, and transmits the verification results to the ground in the form of telemetry. The ground then fills in the missing packets based on the telemetry information.

[0056] Step S4: the onboard management software writes the current batch reconstruction file that has been verified to be normal in the temporary area of ​​the DRAM of the information service unit into the FLASH buffer;

[0057] After all the reconstruction packets are verified to be normal, the onboard management software writes the first batch of reconstruction packets in the temporary area of ​​the DRAM of the information service unit into the FLASH buffer;

[0058] After receiving the reconstruction package and verifying the normal telemetry, the ground continues to send the next batch of reconstruction packages, and so on, until all reconstruction packages are uploaded in batches. At this time, the FLASH buffer contains a complete reconstruction file.

[0059] Step S5: The onboard management software forwards the complete reconstruction files in the FLASH buffer of the information service unit to the terminal reconstruction unit in batches;

[0060] The ground sends a command, which includes the reconstruction object, the reconstruction packet forwarding format, and the time interval of the reconstruction packet forwarding terminal. Then the onboard management software first forwards the complete reconstruction file from the information service unit FLASH buffer to the terminal reconstruction unit in the reconstruction packet format required by the command in batch order;

[0061] Step S6: After the terminal reconstruction unit runs the reconstructed version normally for a period of time, the onboard management software writes the reconstructed file in the FLASH buffer of the information service unit into the FLASH solidification area according to the ground command, and uses it as a fallback version.

[0062] After the terminal reconstruction unit runs the reconstruction version normally for a period of time, the ground sends a command, and the onboard management software writes the reconstruction file in the FLASH buffer of the information service unit into the FLASH hardening area in batch order according to the ground command, which is used as a fallback version;

[0063] When the terminal reconstruction unit needs to be restored to the previous version of the reconstruction file, the ground sends a command, which includes the reconstruction object, the reconstruction packet forwarding format, and the time interval for the reconstruction packet forwarding terminal. The onboard management software forwards the reconstruction file in the FLASH solidification area of ​​the information service unit to the terminal reconstruction unit in batch order according to the ground command.

[0064] Embodiment 2:

[0065] Figure 2 This is a workflow diagram of the ground subcontracting software based on Example 1 of the present application. As shown in the figure, the workflow of the ground subcontracting software includes:

[0066] The ground subcontracting software reads the reconstruction file and calculates the capacity of the reconstruction file;

[0067] If it is a software reconstruction file with super large capacity, the ground subcontracting software will calculate the number of batches based on the reconstruction file capacity. If it is a software reconstruction file with small capacity, the reconstruction file will be directly split into reconstruction packages;

[0068] The ground subpackaging software splits the ultra-large capacity software reconstruction file according to the remote control package format shown in the following table. Each reconstruction package of a satellite contains a 6-byte leading header and a 946-byte data field, where the 2-byte batch number in the data field is used to characterize the batch of the current reconstruction package;

[0069] Table 1 Remote Control Packet Format

[0070]

[0071] The ground subcontracting software divides the reconstructed packages into batches, with 16384 (214) packages as one batch, and fills the batch number into the data field;

[0072] The ground packetization software adds a frame header and CRC check to each reconstructed packet to complete the framing of the upper frame.

[0073] Embodiment 3:

[0074] Figure 3 This is a reconfiguration workflow diagram of the onboard management software of the present application based on Example 1. As shown in the figure, the reconfiguration workflow of the onboard management software includes:

[0075] When the onboard management software receives the reconstruction package, it will perform content verification on each reconstruction package. If the verification passes, the reconstruction package will be cached in the temporary DRAM area of ​​the information service unit. If the verification fails, the reconstruction package will not be received.

[0076] After receiving a batch of reconstruction packages, the onboard management software verifies the integrity and continuity of the reconstruction packages. If there are any missing packages, the telemetry is fed back to the ground, and the ground makes up the package according to the telemetry information until the current batch of reconstruction packages passes the verification.

[0077] The onboard management software writes the verified reconstruction packages from the information service unit DRAM temporary area into the FLASH buffer, and then waits for the next batch of reconstruction packages to pass the verification before continuing to write into the FLASH buffer until the complete reconstruction file is written;

[0078] The onboard management software receives the command sent from the ground, and the command content includes the reconstruction object, the reconstruction packet forwarding format, and the time interval of the reconstruction packet forwarding terminal. The reconstruction object is the terminal to be reconstructed this time, the reconstruction packet forwarding format includes the reconstruction packet format and the application data format, and the time interval of the reconstruction packet forwarding terminal is the time interval between the end of the previous packet and the header of the next packet. The onboard management software forwards the reconstruction files in the FLASH buffer of the information service unit to the terminal in batch order according to the ground command.

[0079] Embodiment 4:

[0080] Figure 4 This is a version rollback workflow diagram of the onboard management software based on Example 1 of the present application. As shown in the figure, the version rollback workflow of the onboard management software includes:

[0081] The onboard management software receives the reconstruction package storage instruction sent by the ground. The instruction content includes the file number corresponding to the current reconstruction file, and the file number maps the storage area address in the FLASH solidification area corresponding to the file. The onboard management software writes the reconstruction package from the FLASH buffer of the information service unit to the corresponding storage area in the FLASH solidification area in batch order until the complete reconstruction file is written;

[0082] The onboard management software receives the version rollback instruction sent from the ground. The instruction content includes the reconstruction object, the reconstruction packet forwarding format, and the time interval for reconstructing the packet forwarding terminal. The reconstruction object is the terminal to be reconstructed this time. The reconstruction packet forwarding format includes the reconstruction packet format and the application data format. The time interval for reconstructing the packet forwarding terminal is the time interval between the end of the previous packet and the header of the next packet. The onboard management software forwards the reconstruction files in the FLASH buffer of the information service unit to the terminal in batch order according to the ground instruction.

[0083] In the embodiment of the present invention, ground packet sub-software is used to process the ultra-large capacity software reconstruction package in batches and in frames, and the reconstruction files of different terminal reconstruction units can be processed in a unified format, which significantly improves the efficiency of reconstructing files on the ground and enhances the convenience and reliability of the satellite management software in verifying, forwarding, and storing reconstruction packages. The information service unit DRAM temporary area and FLASH buffer zone work in coordination to achieve batch verification and temporary storage of ultra-large capacity reconstruction packages, which can ensure the integrity and correctness of the reconstruction files while improving the efficiency of reconstructing package upload. When the verification is abnormal, the missing error package can also be reissued according to the specified address to avoid re-uploading, which causes the reconstruction time to be too long and affects the normal satellite operation. Through the coordinated work of the FLASH buffer zone and the FLASH solidification area, the backup and recovery of the reconstruction file is achieved, the reversibility and recoverability of the reconstruction file are improved, and the stability and flexibility of the reconstructed software are guaranteed.

[0084] The present invention also provides a low-orbit satellite large-capacity software on-orbit reconstruction system, which can be implemented by executing the process steps of the low-orbit satellite large-capacity software on-orbit reconstruction method, that is, those skilled in the art can understand the low-orbit satellite large-capacity software on-orbit reconstruction method as a preferred implementation of the low-orbit satellite large-capacity software on-orbit reconstruction system.

[0085] A low-orbit satellite large-capacity software on-orbit reconstruction system, comprising:

[0086] Module M1: The ground subpackaging software batches and frames the ultra-large capacity software reconstruction packages into ultra-large capacity reconstruction files, and then uploads the ultra-large capacity reconstruction files to the satellite in batches through the ground measurement and control channel;

[0087] Module M2: The onboard management software verifies the contents of the large-capacity reconstruction files uploaded in batches, and writes them into the temporary DRAM area of ​​the information service unit after the verification is normal;

[0088] Module M3: The onboard management software performs continuity verification on the current batch of ultra-large capacity reconstruction files in the temporary DRAM area of ​​the information service unit, and transmits the verification results to the ground in the form of telemetry. The ground then supplements the missing error packets based on the telemetry.

[0089] Module M4: The onboard management software writes the current batch of ultra-large capacity reconstruction files that have been verified to be normal in the temporary area of ​​the DRAM of the information service unit into the FLASH buffer;

[0090] Module M5: The onboard management software forwards the complete ultra-large capacity reconstruction files in the FLASH buffer of the information service unit to the terminal reconstruction unit in batches;

[0091] Module M6: After the terminal reconstruction unit runs the reconstruction version normally for a period of time, the onboard management software writes the reconstruction file in the FLASH buffer of the information service unit into the FLASH solidification area according to the ground command and uses it as a fallback version.

[0092] Those skilled in the art know that, in addition to realizing the system and its various devices, modules, and units provided by the present invention in a purely computer-readable program code, it is entirely possible to realize the same functions in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system and its various devices, modules, and units provided by the present invention can be considered as a hardware component, and the devices, modules, and units included therein for realizing various functions can also be regarded as structures within the hardware component; the devices, modules, and units for realizing various functions can also be regarded as both software modules for realizing the method and structures within the hardware component.

[0093] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. A method for on-orbit reconstruction of large-capacity software of a low-orbit satellite, characterized in that: include: Step S1: The ground subpackaging software processes the ultra-large capacity software reconstruction package into batches and frames into ultra-large capacity reconstruction files, and then uploads the ultra-large capacity reconstruction files to the satellite in batches through the ground measurement and control channel; Step S2: The onboard management software verifies the contents of the ultra-large capacity reconstruction files uploaded in batches, and writes them into the temporary DRAM area of ​​the information service unit after the verification is normal; Step S3: The onboard management software performs continuity check on the current batch of ultra-large capacity reconstruction files in the temporary DRAM area of ​​the information service unit, and transmits the check result to the ground in the form of telemetry, and the ground performs supplementary annotation of missing error packets based on the telemetry; Step S4: the onboard management software writes the current batch of ultra-large capacity reconstruction files that have been verified to be normal in the temporary area of ​​the information service unit DRAM into the FLASH buffer; Step S5: The onboard management software forwards the complete ultra-large capacity reconstruction files in the FLASH buffer of the information service unit to the terminal reconstruction unit in batches; Step S6: After the terminal reconstruction unit runs the reconstructed version normally for a period of time, the onboard management software writes the reconstructed file in the FLASH buffer of the information service unit into the FLASH solidification area according to the ground command, and uses it as a fallback version.

2. The method for on-orbit reconstruction of large-capacity software for low-orbit satellites according to claim 1, characterized in that: The batch processing in step S1 includes: Before the reconstruction process begins, the ground subpacketization software splits the ultra-large capacity reconstruction package into several reconstructed remote control packages of equal length according to the length of the remote control package. The number of batches marked on the reconstruction package is calculated based on the total byte length of the remote control package, with X MB as a batch. X MB is the maximum capacity of the DRAM storage area of ​​the onboard reconstruction package. The number of batches is the integer of the result of dividing the capacity of the ultra-large capacity reconstruction package by X and adding 1. The framing process in step S1 includes: framing each reconstructed packet according to the format of the above-mentioned frame.

3. The method for on-orbit reconstruction of large-capacity software for low-orbit satellites according to claim 1, characterized in that: The betting method described in step S1 is: At the beginning of the reconstruction process, the ground first sends an injection number instruction to the information service unit; the instruction content includes: the reconstruction object, the total number of reconstructed packages uploaded this time, and the number of batches to be injected; the ultra-large capacity reconstruction packages that have been split and framed by the ground subpackaging software are injected in batches through the ground injection channel in batch order, and after being received by the transponder, they are transmitted to the information service unit through the channel gateway.

4. The method for on-orbit reconstruction of large-capacity software for low-orbit satellites according to claim 1, characterized in that: In step S2, the onboard management software verifies the contents of the first batch of reconstruction packets, verifies the packet length and the correctness of the verification information, and writes the reconstruction packets that pass the verification into the temporary DRAM area of ​​the information service unit.

5. The method for on-orbit reconstruction of large-capacity software for low-orbit satellites according to claim 1, characterized in that: In step S3, after the first batch of reconstruction packets are filled and verified, the onboard management software performs continuity verification on the reconstruction packets in the temporary DRAM area of ​​the information service unit, verifies the number and sequence number of the missing packets in the reconstruction packets, and transmits the verification results to the ground in the form of telemetry. The ground then fills in the missing packets based on the telemetry information.

6. The method for on-orbit reconstruction of large-capacity software for low-orbit satellites according to claim 1, characterized in that: In step S4, after all reconstruction packets are verified to be normal, the onboard management software writes the first batch of reconstruction packets in the temporary DRAM area of ​​the information service unit into the FLASH buffer; After receiving the reconstruction package and verifying the normal telemetry, the ground continues to send the next batch of reconstruction packages until all reconstruction packages are uploaded in batches and a complete reconstruction file is stored in the FLASH buffer.

7. The method for on-orbit reconstruction of large-capacity software for low-orbit satellites according to claim 1, characterized in that: In step S5, the onboard management software first forwards the complete reconstruction file from the information service unit FLASH buffer to the terminal reconstruction unit in the reconstruction package format required by the ground transmission instruction according to the batch order; The content of the ground-based instruction includes: reconstruction object, reconstruction packet forwarding format, and time interval of reconstruction packet forwarding terminal.

8. The method for on-orbit reconstruction of large-capacity software for low-orbit satellites according to claim 1, characterized in that: In step S6, after the terminal reconstruction unit runs the reconstructed version normally for a period of time, the ground sends an instruction, and the onboard management software writes the reconstructed file in the FLASH buffer of the information service unit into the FLASH solidification area in batch order according to the ground instruction, which is used as a fallback version.

9. The method for on-orbit reconstruction of large-capacity software for low-orbit satellites according to claim 1, characterized in that: In step S6, when the terminal reconstruction unit needs to restore to the previous version of the reconstruction file, the ground sends an instruction, and the instruction content includes: reconstruction object, reconstruction packet forwarding format, and reconstruction packet forwarding terminal time interval; The onboard management software forwards the reconstruction files in the FLASH hardening area of ​​the information service unit to the terminal reconstruction unit in batch order according to the ground instructions.

10. A low-orbit satellite large-capacity software on-orbit reconstruction system, characterized in that: include: Module M1: The ground subpackaging software batches and frames the ultra-large capacity software reconstruction packages into ultra-large capacity reconstruction files, and then uploads the ultra-large capacity reconstruction files to the satellite in batches through the ground measurement and control channel; Module M2: The onboard management software verifies the contents of the large-capacity reconstruction files uploaded in batches, and writes them into the temporary DRAM area of ​​the information service unit after the verification is normal; Module M3: The onboard management software performs continuity verification on the current batch of ultra-large capacity reconstruction files in the temporary DRAM area of ​​the information service unit, and transmits the verification results to the ground in the form of telemetry. The ground then supplements the missing error packets based on the telemetry. Module M4: The onboard management software writes the current batch of ultra-large capacity reconstruction files that have been verified to be normal in the temporary area of ​​the DRAM of the information service unit into the FLASH buffer; Module M5: The onboard management software forwards the complete ultra-large capacity reconstruction files in the FLASH buffer of the information service unit to the terminal reconstruction unit in batches; Module M6: After the terminal reconstruction unit runs the reconstruction version normally for a period of time, the onboard management software writes the reconstruction file in the FLASH buffer of the information service unit into the FLASH solidification area according to the ground command and uses it as a fallback version.

Images