Satellite in-orbit software version number one-key downloading method and system

Abstract

The invention provides a one-key downloading method and system for a satellite on-orbit software version number. The one-key downloading method comprises the steps that S1, the version number of a standard format is set for satellite on-orbit software; s2, establishing a software version number database, and storing version numbers of all satellite software in standard formats, including current version number information and historical version number information; s3, setting an automatic version comparison mechanism, comparing the currently operated software version of the satellite with the latest version in the database, and updating the software and the software version number database in real time; s4, after a one-key downloading instruction is received, a version comparison mechanism is automatically executed, and the latest version number is downloaded to the ground; and S5, recording a log of downloading operation, and completing version number downloading. According to the method, the satellite software version number can be quickly and accurately transmitted through a one-key downloading method.

Description

Technical Field

[0001] The present invention relates to the field of on-orbit software management for satellites, and more specifically, to a method and system for one-key downloading of satellite on-orbit software version numbers. Background Art

[0002] With the continuous progress of satellite technology, the update and management of satellite on-orbit software have become crucial. Satellite software is not only responsible for controlling the routine operations of satellites, such as navigation, communication, and data collection, but also involves the ability to execute specific scientific tasks and respond to ground instructions in real time. However, in the prior art, the update process of satellite software often relies on manual operations and complex sequence steps, which are not only inefficient but also increase the risk of errors.

[0003] Chinese patent document with publication number CN117992111A discloses a method, system, and medium for version management of automotive software, which relates to the field of automotive software. The method includes constructing a software information management strategy, where the software information management strategy at least includes a version management strategy; automatically defining and storing software version information according to the software information management strategy; and automatically verifying the software version information through a connection bench test. This invention only manages the software version update, but does not further transmit the management result, nor compare the updated result again, affecting the accuracy and integrity of the version update management.

[0004] Chinese patent document with publication number CN117892309A discloses a method for version number standardization and a method for retrieving vulnerable version numbers based on homomorphic encryption, belonging to the field of information security technology. The version number standardization method of this invention is: the server maintains the longest historical version number length corresponding to each software, and performs complementary standardization processing on the upper and lower bounds of the version numbers in the server's vulnerability list according to the longest historical version number length. The vulnerable version number retrieval method of this invention includes: generating security parameters according to the encryption scheme, generating a public key and a private key from the security parameters; converting the version number into an order-preserving large integer and encrypting it to obtain a ciphertext, obtaining the corresponding decryption result based on the ciphertext operation method, and finally the client determines whether the local software version number is within the version number range of the server through the decryption result and performs vulnerability retrieval based on this information. To ensure the functional implementation during the vulnerability query and provide confidentiality services for the user side and the server side. The disadvantage of this invention is that the version number needs to be converted, and the process is too complex.

[0005] The failure of any software update may lead to mission delays, degradation of satellite performance, or even mission failure, resulting in huge economic losses and interruption of scientific research work. In addition, with the diversification and complexity of satellite missions, the frequency of software updates is increasing, which requires the update process to be efficient and reliable enough. Therefore, a method for quickly and accurately downloading the satellite software version number is needed. Summary of the Invention

[0006] Aiming at the defects in the prior art, the purpose of the present invention is to provide a one-key download method and system for the satellite on-orbit software version number.

[0007] A one-key download method for the satellite on-orbit software version number provided by the present invention includes:

[0008] Step S1: Set the version number in a standard format for the software on the satellite in orbit;

[0009] Step S2: Establish a software version number database to store the version numbers in the standard format of all satellite software, including: current version number information and historical version number information;

[0010] Step S3: Set an automated version comparison mechanism to compare the software version currently running on the satellite with the latest version in the database and update the software and the software version number database in real time;

[0011] Step S4: After receiving the one-key download instruction, automatically execute the version comparison mechanism and download the latest version number to the ground;

[0012] Step S5: Record the log of the download operation to complete the download of the version number.

[0013] Preferably, the step S1 includes:

[0014] Step S1.1: When the software code is updated and tested, perform the compilation and build process, and assign a unique version number to each compiled software;

[0015] Step S1.2: Standardize the version number to obtain the version number in the standard format; specifically, set the version number format, the first digit is the English prefix of the software, the second and third digits represent the main version number of the software, which is changed when the function module changes, and the fourth and fifth digits are the revision version numbers, which are changed when the satellite on-orbit software changes or is repaired.

[0016] Preferably, the step S3 includes:

[0017] Step S3.1: Set up an automated version comparison mechanism. According to the version number in the standard format, compare the version number of the software currently running on the satellite with the latest version number in the database digit by digit starting from the first digit. When the comparison result shows no difference, it means there is no version update. If there is a difference in the comparison result, it means there is a version update;

[0018] Step S3.2: When a version update is detected, trigger the execution of the comparison automatically to compare the software information corresponding to the version numbers before and after the update;

[0019] Step S3.3: Process the comparison result. If the comparison results are the same, continue to run the current version of the software and update the software version number database; if the comparison results are different, stop the operation of the current version of the software, perform software update and software version number database update, and record the historical version number information and the current running version number information at the same time;

[0020] Among them, the software update and software version number database update include: updating the software to the latest status version and running the software; storing the latest software version number in the software version number database.

[0021] Preferably, the said step S4 includes:

[0022] Step S4.1: Send a one-key download instruction to the satellite software, and download the version number of the updated version to the ground through the automated version comparison mechanism;

[0023] Step S4.2: Set up security verification during the download process to verify the version number;

[0024] Step S4.3: Set up a status feedback mechanism to feedback the download progress and results in real time, including information such as success, failure or need for intervention.

[0025] Preferably, the said step S5 includes:

[0026] The content of the log includes: the timestamp of the operation, the identity of the operator who executed the operation, and the downloaded software version number.

[0027] According to a one-key download system for satellite on-orbit software version numbers provided by the present invention, it includes:

[0028] Module M1: Set the version number in the standard format for the software on the satellite in orbit;

[0029] Module M2: Establish a software version number database to store all the version numbers in the standard format of the satellite software, including: current version number information and historical version number information;

[0030] Module M3: Set up an automated version comparison mechanism to compare the software version currently running on the satellite with the latest version in the database and update the software and the software version number database in real time;

[0031] Module M4: After receiving the one-key download instruction, automatically execute the version comparison mechanism and download the latest version number to the ground;

[0032] Module M5: Record the log of the download operation to complete the download of the version number.

[0033] Preferably, the module M1 includes:

[0034] Module M1.1: When the software code is updated and tested, perform the compilation and build process, and assign a unique version number to each compiled software;

[0035] Module M1.2: Standardize the version number to obtain the version number in the standard format; specifically, set the version number format, the first digit is the English prefix of the software, the second and third digits represent the main version number of the software, which is changed when the function module changes, and the fourth and fifth digits are the revision version number, which is changed when the satellite on-orbit software changes or is repaired.

[0036] Preferably, the module M3 includes:

[0037] Module M3.1: Set up an automated version comparison mechanism. According to the version number in the standard format, compare the software version number currently running on the satellite with the latest version number in the database digit by digit from the first digit. When the comparison results are the same, there is no version update. If the comparison results are different, there is a version update;

[0038] Module M3.2: When a version update is detected, automatically trigger the execution of the comparison and compare the software information corresponding to the version numbers before and after the update;

[0039] Module M3.3: Process the comparison results. If the comparison results are the same, continue to run the current version of the software and update the software version number database; if the comparison results are different, stop the operation of the current version of the software, perform software update and software version number database update, and record the historical version number information and the current running version number information at the same time;

[0040] Among them, the software update and the software version number database update include: updating the software to the latest state version and running the software; storing the latest software version number in the software version number database.

[0041] Preferably, the module M4 includes:

[0042] Module M4.1: Send a one - key download instruction to the satellite software, and transfer the version number of the updated version to the ground through an automated version comparison mechanism.

[0043] Module M4.2: During the download process, set up security verification to verify the version number.

[0044] Module M4.3: Set up a status feedback mechanism to provide real - time feedback on the download progress and results, including information on success, failure, or the need for intervention.

[0045] Preferably, the module M5 includes:

[0046] The content of the log includes: the timestamp of the operation, the identity of the operator who performed the operation, and the software version number being downloaded.

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

[0048] 1. The present invention has established a standardized version number naming rule, which helps to simplify version tracking and management, and at the same time improves the efficiency of software development and maintenance.

[0049] 2. By establishing a centralized software version number database, the present invention not only stores the current version number information but also records the historical version number information, providing a reliable centralized data source for software version tracking and auditing.

[0050] 3. The security verification performed during the download process of the present invention ensures the integrity of the software version and the reliability of the source, thereby improving the security of the entire system.

[0051] 4. The present invention automatically records detailed logs of all download operations, including time, operator, and version number information, providing important data support for post - event auditing and troubleshooting.

[0052] 5. The current in - memory download function is complex to implement, requiring the inversion of the address mapping of the software in the hardware, with a long preparation time and wasting TT&C resources. The present invention can directly specify the software download through a one - key download instruction, shielding the hardware address inversion, which can speed up the in - memory download time and improve the on - orbit troubleshooting efficiency. Brief Description of the Drawings

[0053] By reading the detailed description of the non - restrictive embodiments with reference to the following drawings, other features, objectives, and advantages of the present invention will become more apparent:

[0054] Figure 1 It is a flowchart of the one - key download method for the satellite on - orbit software version number of the present invention;

[0055] Figure 2Schematic diagram of the one - key download method for the satellite - on - orbit software version number in Embodiment 1 of the present invention. Detailed implementation manners

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

[0057] A one - key download method for the satellite - on - orbit software version number provided by the present invention includes:

[0058] Step S1: Set a version number in a standard format for the satellite - on - orbit software;

[0059] Step S2: Establish a software version number database to store all the version numbers of the satellite software in the standard format, including: current version number information and historical version number information;

[0060] Step S3: Set an automated version comparison mechanism to compare the currently running software version of the satellite with the latest version in the database and update the software and the software version number database in real - time;

[0061] Step S4: After receiving the one - key download instruction, automatically execute the version comparison mechanism and download the latest version number to the ground;

[0062] Step S5: Record the log of the download operation to complete the version number download.

[0063] Specifically, the step S1 includes:

[0064] Step S1.1: When the software code is updated and tested, perform the compilation and build process, and assign a unique version number to each compiled software;

[0065] Step S1.2: Standardize the version number to obtain a version number in the standard format; specifically, set the version number format, the first digit is the English prefix of the software, the second and third digits represent the main version number of the software, which is changed when the function module changes, and the fourth and fifth digits are the revision version numbers, which are changed when the satellite - on - orbit software changes or is repaired.

[0066] Specifically, the step S3 includes:

[0067] Step S3.1: Set up an automated version comparison mechanism. According to the version number in the standard format, compare the software version number of the currently running satellite with the latest version number in the database digit by digit starting from the first digit. When the comparison results show no difference, it means there is no version update. If there are differences in the comparison results, it means there is a version update;

[0068] Step S3.2: When a version update is detected, automatically trigger the execution of the comparison to compare the software information corresponding to the version numbers before and after the update;

[0069] Step S3.3: Process the comparison results. If the comparison results are the same, continue to run the current version of the software and update the software version number database; if the comparison results are different, stop the operation of the current version of the software, perform software update and software version number database update, and record the historical version number information and the currently running version number information for telemetry downlink;

[0070] Among them, the software update and software version number database update include: updating the software to the latest status version and running the software; storing the latest software version number in the software version number database.

[0071] Specifically, the said step S4 includes:

[0072] Step S4.1: Send a one-key downlink instruction to the satellite software. The satellite, through the automated version comparison mechanism, downlinks the version number of the updated version to the ground;

[0073] Step S4.2: Set up security verification during the downlink process to verify the version number;

[0074] Step S4.3: Set up a status feedback mechanism to real-time feedback the downlink progress and results, including information on success, failure, or the need for intervention.

[0075] The operating and storage environments of space software are harsh, such as single-particle upset in storage and damage to the storage area. To ensure the correct update of on-orbit software, the ground uses tools to compare the information of the two versions. When the comparison results are the same, run the latest version; when the results are different, roll back the software version to the previous version to ensure that the software is always in a controllable version state;

[0076] Specifically, the ground compares the received version with the local version. When the comparison results are the same, the ground runs the latest version; when the results are different, roll back the software version to the previous version to ensure that the software is always in a controllable version state.

[0077] Specifically, the said step S5 includes:

[0078] The content of the log includes: the timestamp of the operation, the identity of the operator who performed the operation, and the downlinked software version number.

[0079] Example 1

[0080] Refer to Figure 2 As shown, for a method of one-key downloading of the satellite on-orbit software version number described in this embodiment, the generation method includes the following steps:

[0081] Step 1: During the development of satellite on-orbit software, whenever the software code is updated and tested, a compilation and build process will be carried out, and the compiled software will be assigned a unique version number;

[0082] In the embodiment of the present invention, the satellite on-orbit software refers to the on-board software running on the satellite, such as attitude control software, image processing software, etc. During the software development process, each commit or snapshot is associated with a version number to track the iterative process of the software. Whenever the software code is updated and tested, a compilation and build process will be carried out to generate an executable file or firmware suitable for the satellite environment. The compiled software will be assigned a unique version number, which corresponds to a specific commit in the source code library, ensuring that the exact code changes can be traced back.

[0083] Step 2: Standardize the standard format of the satellite on-orbit software version number;

[0084] In the embodiment of the present invention, the version number format is V-R1-1.0. The first digit is the English prefix of the software, and the second and third digits represent the main version number of the software. When there are major changes in the functional modules, such as changes in the functional structure of the software, for example, adding new modules, evolving functions, integrating new technologies, etc., changes are made. The fourth and fifth digits are the revision version numbers. When there are minor changes or Bug fixes in the satellite on-orbit software, such as fixing software or upgrading software content, for example, interface improvement, software update, enhanced security performance, etc., but the functions of the software itself are not changed, changes are made. Exemplarily, V-R2-2.1 indicates that the software has been upgraded to the second generation version 2.1.

[0085] Step 3: Establish a centralized software version number database.

[0086] In the embodiment of the present invention, establishing a centralized software version number database not only stores the currently running software version number, but also records all historical version numbers and their related information, such as release dates, change logs, and metadata of related builds. This database can be accessed through a web service to support fast query and version tracking.

[0087] Step 4: Design an automated version comparison mechanism for comparing the currently running software version of the satellite with the latest version in the database;

[0088] In the embodiments of the present invention, the automated version comparison mechanism runs regularly or under specific triggering conditions to compare the current software version on the satellite with the latest version recorded in the database. Once a version inconsistency is detected, the system will automatically mark it.

[0089] Step 5: Implement the one - click download instruction function. When the operator initiates a download request, the system automatically performs a version comparison and downloads the latest software version number.

[0090] In the embodiments of the present invention, a one - click download function is set. The operator can simply click a button through the user interface to initiate a software update request. The system will automatically perform a version comparison, confirm the update requirement, and start the download process. The on - board software has the function of downloading the memory of a certain address segment. The measurement and control personnel send a memory download instruction to download the main partition code to the ground, and use a comparison tool to compare the information of the two versions.

[0091] Step 6: During the download process, the system performs a security check to ensure that the downloaded software version number has not been tampered with and the source is reliable.

[0092] In the embodiments of the present invention, during the download process, the system performs multi - level security checks, including but not limited to file integrity checks, digital signature verification, and source authentication. These measures ensure that the downloaded software version number has not been manually tampered with and the source is authorized.

[0093] Step 7: The system provides a status feedback mechanism to real - time feedback the download progress and results to the operator, including information such as success, failure, or the need for intervention.

[0094] In the embodiments of the present invention, the status feedback mechanism provides detailed download status information to the operator in real - time. This includes the start of the download, the transfer rate, the amount of data transferred, the estimated remaining time, and the final download result, ensuring that the operator has a full understanding of the entire process.

[0095] Step 8: The system automatically records the logs of all download operations, including the time, the operator, and the version number information of the downloaded software, for post - event auditing and troubleshooting.

[0096] In the embodiments of the present invention, the system automatically records detailed logs of all download operations, including the timestamp of the operation, the identity information of the operator, the software version number of the download, and the result of the operation. These log information is crucial for post - event auditing, performance analysis, and troubleshooting, and helps to improve the transparency and maintainability of the system.

[0097] Specifically, the software code is compiled and built to assign a unique version number; a centralized database is established to record the current and historical version number information of the software; an automated version comparison mechanism is designed to identify the differences between the currently running version of the satellite and the latest version in the database, and to implement the one-key download instruction function, automatically execute the comparison and download the latest version; during the download process, the system performs security verification to ensure the integrity and source reliability of the software; at the same time, a real-time status feedback mechanism is provided to report the download progress and results to the operator. Finally, the system automatically records the detailed logs of all download operations for post-event auditing and troubleshooting. The entire process improves the efficiency and reliability of satellite software management through automation and strict security measures

[0098] The present invention also provides a one-key download system for the on-orbit software version number of a satellite. The one-key download system for the on-orbit software version number of a satellite can be implemented by executing the process steps of the one-key download method for the on-orbit software version number of a satellite. That is, those skilled in the art can understand the one-key download method for the on-orbit software version number of a satellite as a preferred implementation manner of the one-key download system for the on-orbit software version number of a satellite

[0099] A one-key download system for the on-orbit software version number of a satellite according to the present invention includes: Module M1: Set a version number in a standard format for the software on orbit of the satellite; Module M2: Establish a software version number database to store the version numbers in the standard format of all satellite software, including: current version number information and historical version number information; Module M3: Set an automated version comparison mechanism to compare the currently running software version of the satellite with the latest version in the database and update the software and the software version number database in real time; Module M4: After receiving the one-key download instruction, automatically execute the version comparison mechanism and download the latest version number to the ground; Module M5: Record the log of the download operation to complete the download of the version number

[0100] Specifically, Module M1 includes: Module M1.1: When the software code is updated and tested, perform the compilation and build process, and assign a unique version number to each compiled software; Module M1.2: Standardize the version number to obtain a version number in a standard format. Specifically, set the version number format, the first digit is the English prefix of the software, the second and third digits represent the main version number of the software, which is changed when the function module changes, and the fourth and fifth digits are the revision version numbers, which are changed when the on-orbit software of the satellite changes or is repaired

[0101] Specifically, the module M3 includes: Module M3.1: Set an automated version comparison mechanism. According to the version number in the standard format, compare the version number of the software currently running on the satellite with the latest version number in the database bit by bit starting from the first digit. When the comparison result shows no difference, it means there is no version update. If there is a difference in the comparison result, it means there is a version update. Module M3.2: When a version update is detected, automatically trigger the execution of the comparison to compare the software information corresponding to the version numbers before and after the update. Module M3.3: Process the comparison result. If the comparison results are the same, continue to run the current version of the software and update the software version number database. If the comparison results are different, stop the operation of the current version of the software, perform software update and software version number database update, and record the historical version number information and the currently running version number information at the same time. Among them, the software update and software version number database update include: Update the software to the latest status version and run the software; Store the latest software version number in the software version number database.

[0102] Specifically, the module M4 includes: Module M4.1: Send a one-key download instruction to the satellite software, and download the version number of the updated version to the ground through an automated version comparison mechanism. Module M4.2: Set a security check during the download process to check the version number. Module M4.3: Set a status feedback mechanism to real-time feedback the download progress and results, including information such as success, failure, or the need for intervention.

[0103] Specifically, the content of the log included in the module M5 includes: the timestamp of the operation, the identity of the operator who executed the operation, and the software version number downloaded.

[0104] Those skilled in the art know that in addition to implementing the system and its various devices, modules, and units provided by the present invention in the form of pure computer-readable program code, the method steps can be logically programmed to enable the system and its various devices, modules, and units provided by the present invention to be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers, etc. to achieve the same functions. Therefore, the system and its various devices, modules, and units provided by the present invention can be regarded as a kind of hardware component, and the devices, modules, and units included therein for implementing various functions can also be regarded as the structure within the hardware component; the devices, modules, and units for implementing various functions can also be regarded as both software modules for implementing the method and the structure within the hardware component.

[0105] The specific embodiments of the present invention have been described above. 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. Without conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. A one-key download method for satellite on-orbit software version numbers, characterized in that, Including: Step S1: Set a version number in a standard format for the software on the satellite in orbit. Step S2: Establish a software version number database to store the version numbers of all satellite software in the standard format, including: current version number information and historical version number information. Step S3: Set up an automated version comparison mechanism to compare the software version currently running on the satellite with the latest version in the database, and update the software and the software version number database in real time. Step S4: After receiving the one-key download instruction, automatically execute the version comparison mechanism and download the latest version number to the ground. Step S5: Record the log of the download operation to complete the download of the version number.

2. The one-key download method for the satellite on-orbit software version number according to claim 1, characterized in that The said Step S1 includes: Step S1.1: When the software code is updated and tested, perform the compilation and build process, and assign a unique version number to each compiled software. Step S1.2: Standardize the version number to obtain the version number in the standard format. Specifically, set the version number format. The first digit is the English prefix of the software, the second and third digits represent the major version number of the software, which is changed when the function module changes. The fourth and fifth digits are the revision version numbers, which are changed when the software on the satellite in orbit changes or is repaired.

3. The one-key download method for the satellite on-orbit software version number according to claim 1, characterized in that, The said Step S3 includes: Step S3.1: Set up an automated version comparison mechanism. According to the version number in the standard format, compare the version number of the software currently running on the satellite with the latest version number in the database digit by digit starting from the first digit. When the comparison result has no difference, there is no version update. If the comparison result has a difference, there is a version update. Step S3.2: When it is detected that there is a version update, automatically trigger the execution of the comparison, and compare the software information corresponding to the version numbers before and after the update. Step S3.3: Process the comparison result. If the comparison results are the same, continue to run the current version of the software and update the software version number database. If the comparison results are different, stop the operation of the current version of the software, perform software update and software version number database update, and record the historical version number information and the currently running version number information at the same time. Among them, the software update and software version number database update include: update the software to the latest state version and run the software; store the latest software version number in the software version number database.

4. The one-key download method for the satellite on-orbit software version number according to claim 1, characterized in that The said Step S4 includes: Step S4.1: Send a one-key download instruction to the satellite software, and download the version number of the updated version to the ground through the automated version comparison mechanism. Step S4.2: Set up a security verification during the download process to verify the version number. Step S4.3: Set up a status feedback mechanism to feedback the download progress and results in real time, including information such as success, failure or need for intervention.

5. The one-key downlink method for the satellite on-orbit software version number according to claim 1, wherein The said Step S5 includes: The content of the log includes: the timestamp of the operation, the identity of the operator who performed the operation, and the software version number downloaded.

6. A one-key downlink system for satellite on-orbit software version numbers, characterized in that, Including: Module M1: Set a version number in a standard format for the software on the satellite in orbit. Module M2: Establish a software version number database to store the version numbers of all satellite software in the standard format, including: current version number information and historical version number information. Module M3: Set up an automated version comparison mechanism to compare the software version currently running on the satellite with the latest version in the database and update the software and the software version number database in real time; Module M4: After receiving the one-key download instruction, automatically execute the version comparison mechanism and download the latest version number to the ground; Module M5: Record the log of the download operation to complete the download of the version number.

7. The one-key download system for the satellite on-orbit software version number according to claim 6, characterized in that, The said module M1 includes: Module M1.1: When the software code is updated and tested, perform the compilation and build process, and assign a unique version number to each compiled software; Module M1.2: Standardize the version number to obtain the version number in the standard format; specifically, set the version number format, the first digit is the English prefix of the software, the second and third digits represent the main version number of the software, which is changed when the functional module changes, and the fourth and fifth digits are the revision version numbers, which are changed when the on-orbit software of the satellite changes or is repaired.

8. The one-key downlink system for the satellite on-orbit software version number according to claim 6, characterized in that, The said module M3 includes: Module M3.1: Set up an automated version comparison mechanism. According to the version number in the standard format, compare the software version number currently running on the satellite with the latest version number in the database digit by digit starting from the first digit. When the comparison result shows no difference, it means there is no version update. If the comparison result shows a difference, it means there is a version update; Module M3.2: When it is detected that there is a version update, automatically trigger the execution of the comparison to compare the software information corresponding to the version numbers before and after the update; Module M3.3: Process the comparison result. If the comparison result is the same, continue to run the current version of the software and update the software version number database; if the comparison result is different, stop the operation of the current version of the software, perform software update and software version number database update, and record the historical version number information and the currently running version number information at the same time; Among them, the software update and the software version number database update include: updating the software to the latest status version and running the software; storing the latest software version number in the software version number database.

9. The one-key downlink system for the satellite on-orbit software version number according to claim 6, characterized in that The said module M4 includes: Module M4.1: Send a one-key download instruction to the satellite software, and download the version number of the updated version to the ground through the automated version comparison mechanism; Module M4.2: Set up a security verification during the download process to verify the version number; Module M4.3: Set up a status feedback mechanism to feedback the download progress and results in real time, including information such as success, failure or the need for intervention.

10. The one-key download system for the satellite on-orbit software version number according to claim 6, characterized in that The said module M5 includes: The content of the log includes: the timestamp of the operation, the identity of the operator who executed the operation, and the software version number downloaded.

Images