Satellite-borne software heterogeneous medium storage system and management method

By designing heterogeneous media storage systems on satellites, the problem of insufficient reliability of traditional satellite software management in high-radiation environments is solved, and the multi-level checksum switching of software versions is realized, and the reliability and flexibility of the satellite system is improved.

CN119668670APending Publication Date: 2025-03-21SHANGHAI SATELLITE ENG INST
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411618624.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-13
Publication Date
2025-03-21

AI Technical Summary

Technical Problem

Traditional satellite software management methods have insufficient reliability and low efficiency in high radiation environments, making it difficult to respond to software failures quickly, affecting the continuous operation of satellite systems.

Method used

A heterogeneous media storage system for satellite-based software is designed, including the Flash area of ​​the satellite-based computer, DRAM area, terminal Flash reconstruction area, terminal Flash golden area and terminal RAM operation area. Through multi-level checksum redundant configuration, the reliable storage and rapid switching of the software version are ensured.

Benefits of technology

Improves the reliability and flexibility of satellite software, ensuring rapid switching to the golden or historical version in the event of software failure, ensuring the normal operation of the satellite system and data integrity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119668670A_ABST
    Figure CN119668670A_ABST
Patent Text Reader

Abstract

The invention provides a satellite-borne software heterogeneous medium storage system and a management method. The satellite-borne software heterogeneous medium storage system comprises a satellite-borne computer Flash area, a satellite-borne computer DRAM area, a terminal Flash reconstruction area, a terminal Flash gold area and a terminal RAM operation area. The spaceborne computer DRAM region is used for acquiring and temporarily storing the latest reconstruction software version, and the spaceborne computer Flash region is used for storing golden versions and historical versions of all software; the terminal Flash reconfiguration area is used for storing a reconfiguration software version subjected to preliminary verification; the terminal RAM running area is used for running a currently activated software version; and the terminal Flash gold area is used for permanently storing a software gold version. According to the multi-version heterogeneous medium storage method for the satellite application program, the problem that in the prior art, software reliability and flexibility are insufficient can be effectively solved, and a powerful guarantee is provided for stable operation of a satellite communication system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of satellite on-orbit software management, and in particular to a satellite-borne software heterogeneous medium storage system and a management method. Background Art

[0002] With the increasing space exploration and satellite applications, the challenges faced by satellites in orbit are also increasing, especially in software management. Traditional software management methods have problems such as insufficient reliability and low efficiency when dealing with software upgrades and fault recovery in harsh space environments. In particular, software failures may occur in high-radiation environments, and it is necessary to be able to quickly switch to backup versions to ensure the continuous operation of satellite systems. Therefore, how to effectively store and manage software versions in order to quickly respond to various situations is a technical problem that needs to be solved urgently. Summary of the invention

[0003] In view of the defects in the prior art, the object of the present invention is to provide a satellite-borne software heterogeneous media storage system and management method.

[0004] According to the present invention, a satellite-borne software heterogeneous medium storage system includes: a satellite-borne computer Flash area, a satellite-borne computer DRAM area, a terminal Flash reconstruction area, a terminal Flash golden area, and a terminal RAM operation area;

[0005] The onboard computer DRAM area is used to obtain and temporarily store the latest reconstruction software version, and the reconstruction software version after preliminary verification is transmitted to the onboard computer Flash area or the terminal Flash reconstruction area; the onboard computer Flash area is used to store the golden version and historical versions of all software; the golden version is a verified version, which is used as the recovery point version;

[0006] The terminal Flash reconstruction area is used to store the reconstructed software version that has been preliminarily verified, and the reconstructed software version is input into the terminal RAM running area after being verified again; the terminal RAM running area is used to run the currently activated software version; the terminal Flash golden area is used to permanently store the golden version of the software. When an abnormality occurs to the currently running version of the terminal RAM running area, the golden version of the software in the terminal Flash golden area is input into the terminal RAM running area.

[0007] Preferably, the onboard computer Flash area and the onboard computer DRAM area adopt radiation protection treatment to resist the influence of cosmic rays and electromagnetic pulses; the terminal Flash area is set with redundant configuration and adopts ECC memory; the terminal RAM operation area adopts fast access technology.

[0008] Preferably, the golden version is a version that has been completely tested and verified on the ground, and is encrypted and uploaded to the Flash area of ​​the onboard computer via a dedicated communication link.

[0009] Preferably, the historical versions are stored in order in the Flash area of ​​the onboard computer according to the version number and update date, and each version is accompanied by a rollback instruction set.

[0010] A method for managing heterogeneous media storage of onboard software provided by the present invention includes:

[0011] Onboard software reconstruction steps: The ground control center remotely reconstructs the software data packet, which is verified in the onboard computer DRAM area and the terminal Flash reconstruction area respectively, and then forwarded to the terminal RAM operation area;

[0012] The steps of storing the historical version of the onboard software are as follows: the ground control center sends a reconstructed software data packet transfer instruction to store the reconstructed software version in the onboard computer DRAM into the onboard computer Flash;

[0013] Onboard software startup version selection steps: If the software in the terminal RAM running area runs normally, the reconstructed software version in the terminal Flash reconstruction area is solidified as the running version at the next startup; otherwise, the golden software version is used as the running version at the next startup;

[0014] Onboard software version rollback steps: The ground control center sends a command to restore the historical version of the software, and transfers the historical software version stored in the onboard computer Flash area to the onboard computer DRAM area for verification and the terminal Flash reconstruction area for verification in sequence. After passing the verification, the software data package is transferred to the terminal RAM running area for execution.

[0015] Preferably, the onboard software reconstruction step includes the following sub-steps:

[0016] Step S21: The ground control center reconstructs the software data packet through remote control, and the satellite receives the data and stores it in the DRAM area of ​​the onboard computer;

[0017] Step S22: The ground control center sends a reconstructed software data packet verification instruction to verify the software data packet stored in the DRAM area of ​​the onboard computer;

[0018] Step S23: When the verification result of the software data packet in the DRAM area of ​​the onboard computer is abnormal, an error log is recorded and reported to the ground control center, and the ground control center resends the missing error data packet until the verification is normal;

[0019] Step S24: When the verification result of the software data packet in the DRAM area of ​​the onboard computer is normal, the ground control center forwards the reconstructed software version in the DRAM of the onboard computer to the Flash reconstruction area of ​​the operation terminal through instructions;

[0020] Step S25: Perform a global check on the terminal Flash reconstruction area. If the check fails, the ground control center controls the onboard computer to resend the missing data packet through remote control commands.

[0021] Step S26: If the global verification of the terminal Flash reconstruction area is normal, the ground control center transfers the software data package of the terminal Flash reconstruction area to the terminal RAM running area through instructions, and the terminal RAM running area starts the reconstructed version software.

[0022] Preferably, the onboard software historical version storage step includes the following sub-steps:

[0023] Step S31: The ground control center reconstructs the software data packet through remote control, and the satellite receives the data and stores it in the DRAM area of ​​the onboard computer;

[0024] Step S32: The ground control center sends a reconstructed software data packet verification instruction to verify the software data packet stored in the DRAM area of ​​the onboard computer;

[0025] Step S33: If the software data packet verification result is abnormal, the ground control center resends the missing data packet until the verification is normal;

[0026] Step S34: If the software data packet verification result is normal, the ground control center may send a reconstructed software data packet transfer instruction to store the reconstructed software version in the onboard computer DRAM into the onboard computer Flash.

[0027] Preferably, the onboard software startup version selection step includes the following sub-steps:

[0028] Step S41, the ground control center sends a reconstruction version verification instruction, transfers the software data package of the terminal Flash reconstruction area to the terminal RAM running area, and the terminal RAM running area verifies the reconstruction software version;

[0029] Step S42, if the software in the terminal RAM running area runs normally, the ground sends a start-up software version reconstruction instruction to solidify the reconstruction software version in the terminal Flash reconstruction area, and automatically runs the reconstruction software version at the next startup;

[0030] Step S43, if the software in the terminal RAM running area runs abnormally, the ground sends a command to start the golden version to run the golden software version in the terminal Flash golden area, and the ground performs fault contingency plan processing at the same time.

[0031] Preferably, the onboard software version rollback step includes the following sub-steps:

[0032] Step S51: The ground control center sends a historical software version recovery instruction to transfer the historical software version stored in the onboard computer Flash area to the onboard computer DRAM area;

[0033] Step S52: The ground control center sends a reconstructed software data packet verification instruction to verify the software data packet stored in the DRAM area of ​​the onboard computer;

[0034] Step S53: when the verification result of the software data packet in the DRAM area of ​​the onboard computer is abnormal, the Flash area of ​​the onboard computer re-transfers the missing data packet until the verification is normal;

[0035] Step S54: When the verification result of the software data package in the DRAM area of ​​the onboard computer is normal, the ground control center transfers the reconstructed software version in the DRAM of the onboard computer to the reconstruction area of ​​the terminal Flash through an instruction;

[0036] Step S55: Perform a global check on the terminal Flash reconstruction area. If the check fails, the onboard computer Flash area re-transfers the missing data packet.

[0037] Step S56: If the global verification of the terminal Flash reconstruction area is normal, the ground control center transfers the software data package of the terminal Flash reconstruction area to the terminal RAM running area through instructions, and the terminal RAM running area starts the historical version software.

[0038] Preferably, when the software version in the terminal RAM running area fails, the onboard computer will automatically switch to the most recent stable historical version and attempt to restart; if the automatic rollback fails, the ground control center will manually select any historical version in the onboard computer Flash area for recovery operation.

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

[0040] 1. The present invention opens up five different storage spaces on the satellite. The division allows different versions of software and data to be effectively managed and stored. The multiple storage spaces on the satellite can be used to perform multi-level verification of the reconstructed data, which increases the reliability of software reconstruction and ensures the integrity and availability of the data.

[0041] 2. The software on the satellite can roll back to the historical version according to ground instructions, which improves the flexibility of the on-board software and makes it easy to switch and manage different versions of the software.

[0042] 3. The golden version of the software is always stored on the satellite. Even if the software fails to load or reconstruct, the golden version can still be reloaded and started, which improves the reliability of the on-board software and ensures the normal operation of the satellite.

[0043] 4. The multi-version heterogeneous media storage method for satellite applications proposed in the present invention can effectively solve the problems of insufficient software reliability and flexibility in the prior art, and provide a strong guarantee for the stable operation of the satellite communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] 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:

[0045] Figure 1 A schematic diagram of a heterogeneous medium storage system for onboard software is provided for the present invention;

[0046] Figure 2 A flowchart of the onboard software reconstruction process provided by an embodiment of the present invention;

[0047] Figure 3 A flowchart of the onboard software history version storage process provided by an embodiment of the present invention;

[0048] Figure 4 A flowchart for selecting a startup version of the onboard software provided by an embodiment of the present invention;

[0049] Figure 5 A flowchart of the onboard software historical version rollback process provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0050] 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.

[0051] The present invention discloses a satellite-borne software heterogeneous medium storage system, referring to Figure 1 As shown, five heterogeneous media storage spaces are divided on the satellite to store different versions and data of satellite software, namely, the onboard computer Flash area, the onboard computer DRAM area, the terminal Flash reconstruction area, the terminal Flash golden area, and the terminal RAM running area.

[0052] Among them, the onboard computer Flash area is used to store the golden version and historical versions of all software. This area has a high radiation protection capability to ensure long-term stable storage. The onboard computer DRAM area is used to temporarily store the latest reconstructed software version. This area is easy to access and update quickly, but may require more frequent verification and updates in a radiation environment. The terminal Flash reconstruction area is used to store the reconstructed software version that has undergone preliminary verification. This area provides a transitional storage solution for temporary storage before the software version is fully verified. The terminal Flash golden area is used to permanently store the fully verified golden version of the software as the most reliable recovery point. The terminal RAM running area is used to run the currently activated software version, whether it is the latest reconstructed version or the historical version to which it has rolled back.

[0053] In a preferred embodiment, the onboard computer Flash area and DRAM area are specially treated with radiation protection to resist the influence of cosmic rays and electromagnetic pulses. The terminal Flash area improves the data protection level through redundant configuration and uses ECC (Error-Correcting Code) memory to reduce the error rate. The terminal RAM operation area uses fast access technology and has transient error detection and recovery capabilities.

[0054] There are three types of software versions in this solution: The golden version is confirmed by the development team after multiple rounds of testing and verification on the ground, and is encrypted and uploaded to the Flash area of ​​the onboard computer via a dedicated communication link. The historical versions are stored in the Flash area of ​​the onboard computer in order according to the version number and update date, and each version is accompanied by a rollback instruction set. The reconstructed version is first run and tested in the simulation environment of the ground control center and uploaded through the backend.

[0055] The present invention also discloses a management method for heterogeneous medium storage of satellite-borne software, comprising:

[0056] Onboard software reconstruction steps: The ground control center remotely reconstructs the software data packet, which is verified in the onboard computer DRAM area and the terminal Flash reconstruction area respectively, and then forwarded to the terminal RAM operation area;

[0057] The steps of storing the historical version of the onboard software are as follows: the ground control center sends a reconstructed software data packet transfer instruction to store the reconstructed software version in the onboard computer DRAM into the onboard computer Flash;

[0058] Onboard software startup version selection steps: If the software in the terminal RAM running area runs normally, the reconstructed software version in the terminal Flash reconstruction area is solidified as the running version at the next startup; otherwise, the golden software version is used as the running version at the next startup;

[0059] Onboard software version rollback steps: The ground control center sends a command to restore the historical version of the software, and transfers the historical software version stored in the onboard computer Flash area to the onboard computer DRAM area for verification and the terminal Flash reconstruction area for verification in sequence. After passing the verification, the software data package is transferred to the terminal RAM running area for execution.

[0060] Reference Figure 2 As shown, the onboard software reconstruction step includes the following sub-steps:

[0061] Step S21: The ground control center reconstructs the software data packet through remote control, and the satellite receives the data and stores it in the DRAM area of ​​the onboard computer;

[0062] Specifically, after the ground control center develops a new version of the software, it first conducts a comprehensive test in a simulated environment. The software data packets that pass the test are encrypted and then securely uploaded to the satellite's onboard computer DRAM area via remote control signals.

[0063] Step S22: The ground control center sends a reconstructed software data packet verification instruction to verify the software data packet stored in the DRAM area of ​​the onboard computer; the verification algorithm includes but is not limited to CRC, SHA or MD5.

[0064] Step S23: When the verification result of the software data packet in the DRAM area of ​​the onboard computer is abnormal, an error log is recorded and reported to the ground control center, and the ground control center resends the missing error data packet until the verification is normal;

[0065] Step S24: When the verification result of the software data packet in the DRAM area of ​​the onboard computer is normal, the ground control center forwards the reconstructed software version in the DRAM of the onboard computer to the Flash reconstruction area of ​​the operation terminal through instructions;

[0066] Step S25: After the reconstructed software version is migrated to the terminal Flash reconstruction area, a global check is performed on the terminal Flash reconstruction area. If the check fails, the ground control center controls the onboard computer to resend the missing data packet through remote control commands.

[0067] Step S26: If the global verification of the terminal Flash reconstruction area is normal, the ground control center transfers the software data package of the terminal Flash reconstruction area to the terminal RAM running area through instructions, and the terminal RAM running area starts the reconstructed version software.

[0068] Reference Figure 3 As shown, the onboard software historical version storage step includes the following sub-steps:

[0069] Step S31: The ground control center reconstructs the software data packet through remote control, and the satellite receives the data and stores it in the DRAM area of ​​the onboard computer;

[0070] Step S32: The ground control center sends a reconstructed software data packet verification instruction to verify the software data packet stored in the DRAM area of ​​the onboard computer;

[0071] Step S33: If the software data packet verification result is abnormal, the ground control center resends the missing data packet until the verification is normal;

[0072] Step S34: If the software data packet verification result is normal, the ground control center may send a reconstructed software data packet transfer instruction to store the reconstructed software version in the onboard computer DRAM into the onboard computer Flash.

[0073] Each backup operation will be recorded in the satellite log and the ground control center will be notified simultaneously. The onboard computer Flash area will automatically maintain the version chain to ensure that the latest backup will not overwrite important historical versions.

[0074] Reference Figure 4 As shown, the onboard software startup version selection step includes the following sub-steps:

[0075] Step S41, when the global verification of the terminal Flash reconstruction area is normal, the ground control center sends a reconstruction version verification instruction, transfers the software data package of the terminal Flash reconstruction area to the terminal RAM running area, and the terminal RAM running area verifies the reconstruction software version;

[0076] After the software version in the terminal Flash reconstruction area is migrated, the onboard computer will perform a series of global checks to ensure data integrity and software reliability. The checks include but are not limited to software signature verification, integrity check, and compatibility test. After the check passes, the ground control center issues a start command, and the terminal RAM operation area will start the new software version and start running.

[0077] Step S42: If the software in the terminal RAM operation area runs normally, the ground sends a command to start the reconstruction software version, solidifies the reconstruction software version in the terminal Flash reconstruction area, and automatically runs the reconstruction software version at the next startup;

[0078] Step S43, if the software in the terminal RAM running area runs abnormally, the ground will send a command to start the golden version to run the golden software version in the terminal Flash golden area, and the ground will perform fault contingency plan processing at the same time.

[0079] If a problem occurs during any calibration or startup phase, the system will automatically roll back to the previous step or restore to the golden version and report it to the ground control center.

[0080] Reference Figure 5 As shown, the onboard software version rollback step includes the following sub-steps:

[0081] Step S51: The onboard computer Flash area stores historical software versions. When the satellite needs to roll back to the historical version, the ground control center sends a historical software version recovery instruction to transfer the historical software version stored in the onboard computer Flash area to the onboard computer DRAM area.

[0082] Step S52: The ground control center sends a reconstructed software data packet verification instruction to verify the software data packet stored in the DRAM area of ​​the onboard computer;

[0083] Step S53: when the verification result of the software data packet in the DRAM area of ​​the onboard computer is abnormal, the Flash area of ​​the onboard computer re-transfers the missing data packet until the verification is normal;

[0084] Step S54: When the verification result of the software data package in the DRAM area of ​​the onboard computer is normal, the ground control center transfers the reconstructed software version in the DRAM of the onboard computer to the reconstruction area of ​​the terminal Flash through an instruction;

[0085] Step S55: After the reconstructed software version is migrated to the terminal Flash reconstruction area, a global check is performed on the terminal Flash reconstruction area. If the check result fails, the onboard computer Flash area re-transfers the missing data packet.

[0086] Step S56: The global verification of the terminal Flash reconstruction area is normal, and the ground control center transfers the software data package of the terminal Flash reconstruction area to the terminal RAM running area through instructions, and the terminal RAM running area starts the historical version software.

[0087] Once the software version running on orbit fails, the onboard computer will automatically switch to the most recent stable historical version and try to restart. If the automatic rollback fails, the ground control center can intervene remotely and manually select any historical version in the Flash area for recovery. Under the remote command of the ground control center, the selected historical version will be loaded into the DRAM area and restarted, and the terminal RAM operation area will switch to this version to run.

[0088] The monitoring system on the satellite will detect the software running status and storage media condition in real time, and any abnormalities will be reported immediately. The ground control center will regularly perform telemetry checks on the storage media to evaluate its performance and integrity and perform maintenance operations as needed. All operations and changes will be recorded in the satellite's non-volatile storage for future analysis and auditing.

[0089] 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.

[0090] 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 spaceborne software heterogeneous media storage system, characterized in that: include: Onboard computer Flash area, onboard computer DRAM area, terminal Flash reconstruction area, terminal Flash golden area, terminal RAM operation area; The onboard computer DRAM area is used to obtain and temporarily store the latest reconstruction software version, and the reconstruction software version after preliminary verification is transmitted to the onboard computer Flash area or the terminal Flash reconstruction area; the onboard computer Flash area is used to store the golden version and historical versions of all software; the golden version is a verified version, which is used as the recovery point version; The terminal Flash reconstruction area is used to store the reconstructed software version that has been preliminarily verified, and the reconstructed software version is input into the terminal RAM running area after being verified again; the terminal RAM running area is used to run the currently activated software version; the terminal Flash golden area is used to permanently store the golden version of the software. When an abnormality occurs to the currently running version of the terminal RAM running area, the golden version of the software in the terminal Flash golden area is input into the terminal RAM running area.

2. The onboard software heterogeneous media storage system according to claim 1, characterized in that: The onboard computer Flash area and the onboard computer DRAM area adopt radiation protection treatment to resist the influence of cosmic rays and electromagnetic pulses; the terminal Flash area is set with redundant configuration and adopts ECC memory; the terminal RAM operation area adopts fast access technology.

3. The onboard software heterogeneous media storage system according to claim 1, characterized in that: The golden version is the version that has been completely tested and verified on the ground, and is uploaded to the Flash area of ​​the onboard computer through a dedicated communication link.

4. The onboard software heterogeneous media storage system according to claim 1, characterized in that: The historical versions are stored in order in the Flash area of ​​the onboard computer according to the version number and update date, and each version is accompanied by a rollback instruction set.

5. A method for managing heterogeneous media storage of onboard software, based on the onboard software heterogeneous media storage system according to any one of claims 1 to 4, characterized in that: include: Onboard software reconstruction steps: The ground control center remotely reconstructs the software data packet, which is verified in the onboard computer DRAM area and the terminal Flash reconstruction area respectively, and then forwarded to the terminal RAM operation area; The steps of storing the historical version of the onboard software are as follows: the ground control center sends a reconstructed software data packet transfer instruction to store the reconstructed software version in the onboard computer DRAM into the onboard computer Flash; Onboard software startup version selection steps: If the software in the terminal RAM running area runs normally, the reconstructed software version in the terminal Flash reconstruction area is solidified as the running version at the next startup; otherwise, the golden software version is used as the running version at the next startup; Onboard software version rollback steps: The ground control center sends a command to restore the historical version of the software, and transfers the historical software version stored in the onboard computer Flash area to the onboard computer DRAM area for verification and the terminal Flash reconstruction area for verification in sequence. After passing the verification, the software data package is transferred to the terminal RAM running area for execution.

6. The method for managing heterogeneous media storage of onboard software according to claim 5, characterized in that: The onboard software reconstruction step includes the following sub-steps: Step S21: The ground control center reconstructs the software data packet through remote control, and the satellite receives the data and stores it in the DRAM area of ​​the onboard computer; Step S22: The ground control center sends a reconstructed software data packet verification instruction to verify the software data packet stored in the DRAM area of ​​the onboard computer; Step S23: When the verification result of the software data packet in the DRAM area of ​​the onboard computer is abnormal, an error log is recorded and reported to the ground control center, and the ground control center resends the missing error data packet until the verification is normal; Step S24: When the verification result of the software data packet in the DRAM area of ​​the onboard computer is normal, the ground control center forwards the reconstructed software version in the DRAM of the onboard computer to the Flash reconstruction area of ​​the operation terminal through instructions; Step S25: Perform a global check on the terminal Flash reconstruction area. If the check fails, the ground control center controls the onboard computer to resend the missing data packet through remote control commands. Step S26: If the global verification of the terminal Flash reconstruction area is normal, the ground control center transfers the software data package of the terminal Flash reconstruction area to the terminal RAM running area through instructions, and the terminal RAM running area starts the reconstructed version software.

7. The method for managing heterogeneous media storage of onboard software according to claim 5, characterized in that: The onboard software historical version storage step includes the following sub-steps: Step S31: The ground control center reconstructs the software data packet through remote control, and the satellite receives the data and stores it in the DRAM area of ​​the onboard computer; Step S32: The ground control center sends a reconstructed software data packet verification instruction to verify the software data packet stored in the DRAM area of ​​the onboard computer; Step S33: If the software data packet verification result is abnormal, the ground control center resends the missing data packet until the verification is normal; Step S34: If the software data packet verification result is normal, the ground control center may send a reconstructed software data packet transfer instruction to store the reconstructed software version in the onboard computer DRAM into the onboard computer Flash.

8. The method for managing heterogeneous media storage of onboard software according to claim 5, characterized in that: The onboard software startup version selection step includes the following sub-steps: Step S41, the ground control center sends a reconstruction version verification instruction, transfers the software data package of the terminal Flash reconstruction area to the terminal RAM running area, and the terminal RAM running area verifies the reconstruction software version; Step S42, if the software in the terminal RAM running area runs normally, the ground sends a command to start the reconstruction software version, solidifies the reconstruction software version in the terminal Flash reconstruction area, and automatically runs the reconstruction software version at the next startup; Step S43, if the software in the terminal RAM running area runs abnormally, the ground sends a command to start the golden version to run the golden software version in the terminal Flash golden area, and the ground performs fault contingency plan processing at the same time.

9. The method for managing heterogeneous media storage of onboard software according to claim 5, characterized in that: The onboard software version rollback step includes the following sub-steps: Step S51: The ground control center sends a historical software version recovery instruction to transfer the historical software version stored in the onboard computer Flash area to the onboard computer DRAM area; Step S52: The ground control center sends a reconstructed software data packet verification instruction to verify the software data packet stored in the DRAM area of ​​the onboard computer; Step S53: when the verification result of the software data packet in the DRAM area of ​​the onboard computer is abnormal, the Flash area of ​​the onboard computer re-transfers the missing data packet until the verification is normal; Step S54: When the verification result of the software data package in the DRAM area of ​​the onboard computer is normal, the ground control center transfers the reconstructed software version in the DRAM of the onboard computer to the reconstruction area of ​​the terminal Flash through an instruction; Step S55: Perform a global check on the terminal Flash reconstruction area. If the check fails, the onboard computer Flash area re-transfers the missing data packet. Step S56: If the global verification of the terminal Flash reconstruction area is normal, the ground control center transfers the software data package of the terminal Flash reconstruction area to the terminal RAM running area through instructions, and the terminal RAM running area starts the historical version software.

10. The method for managing heterogeneous media storage of onboard software according to claim 5, characterized in that: When the software version in the terminal RAM running area fails, the onboard computer will automatically switch to the most recent stable historical version and attempt to restart; if the automatic rollback fails, the ground control center will manually select any historical version in the onboard computer Flash area for recovery.