Satellite anti-single event effect task execution method and device, medium and equipment

Abstract

The invention discloses a satellite anti-single event effect task execution method and device, a medium and equipment, during the operation period of a satellite on an orbit, anomaly detection is performed on a target software program regularly according to monitoring parameters of the target software program, an anomaly detection result of the target software program is obtained, and when it is determined that the target software program is abnormal, the target software program is determined to be abnormal. The method comprises the steps of autonomously obtaining pre-stored version record data corresponding to a target software program from a preset specified storage medium, determining a software program of a historical version previously installed on a satellite according to the version record data, and returning the target software program to a software program of a previous version, the processing efficiency of abnormity occurring when a satellite runs on an orbit is improved, and then the safety of the satellite in the running process is improved.

Description

Technical Field

[0001] The present specification relates to the technical field of spacecraft space environment effect application, and in particular to a satellite anti-single particle effect mission execution method, device, medium and equipment. Background Art

[0002] With the development of aerospace technology, satellites play an increasingly critical role in many fields such as communication, navigation, remote sensing and scientific exploration. However, when satellites are operating in orbit, they will be affected by the complex and harsh space environment, such as the high-energy particles in cosmic rays. When the satellite's electronic equipment and software systems are affected by high-energy particles, single event effects (SEEs) may be triggered, resulting in internal memory bit flips and data corruption, which in turn affects the normal operation of key software used by the satellite (such as attitude control and signal processing software) and seriously affects the execution of satellite missions. For example, when the attitude control system of the satellite responsible for the attitude measurement and control of the satellite is abnormal, the attitude of the satellite may deviate, thereby affecting the satellite's pointing accuracy and stability. For another example, when the signal processing software responsible for signal modulation, demodulation, encoding and decoding is abnormal, it may cause communication interruption or data errors in the satellite, thereby affecting the execution of the satellite mission.

[0003] Normally, in order to avoid the impact of harsh space environment on the execution of satellite missions, the ground control center can monitor the satellite's operating status in real time based on telemetry data, so as to take timely measures when the satellite's operating status is abnormal, and remotely update and repair the satellite's software system. However, due to the communication delay and timeliness problems of ground telemetry and manual intervention, the efficiency of handling emergency anomalies of satellites is low.

[0004] Therefore, how to improve the efficiency of handling anomalies that occur when satellites are operating in orbit is an urgent problem to be solved. Summary of the invention

[0005] This specification provides a satellite anti-single-particle effect mission execution method, device, medium and equipment to partially solve the above-mentioned problems existing in the prior art.

[0006] This manual adopts the following technical solutions: This specification provides a method for executing a satellite anti-single event effect mission, including: Acquiring monitoring parameters of a target software program, wherein the monitoring parameters are used to reflect the running state of the target software program and the current state of hardware resources on which the target software program depends; According to the monitoring parameters, anomaly detection is performed on the target software program to obtain an anomaly detection result of the target software program, wherein the anomaly detection result is used to characterize whether the target software program has an anomaly; If it is determined that the target software program has an anomaly according to the anomaly detection result, obtaining the pre-stored version record data corresponding to the target software program from a preset designated storage medium; Determine, according to the version record data, a previous version of a historical software program that is adjacent to the target software program in update time as a fallback software program; The fallback software program is installed and run to perform task execution through the fallback software program.

[0007] Optionally, storing version record data corresponding to the target software program specifically includes: Receive data packet files sent by the ground terminal; Decrypting the data packet file to extract the software program to be installed, as well as version data and verification parameters of the software program to be installed from the data packet file, wherein the verification parameters are used to reflect whether there is an abnormality in the transmission process of the data packet file; The software program to be installed is verified according to the verification parameters to obtain a verification result, and when it is determined according to the verification result that there is no abnormality in the software program to be installed, the software program to be installed is installed, and the update time and version data of the software program to be installed are stored in the version record data corresponding to the software program to be installed.

[0008] Optionally, the verification parameters include: a digital signature value, a first key, and a digest algorithm parameter, wherein the digital signature value is obtained by encrypting the digest value corresponding to the software program to be installed by the ground terminal using a preset second key, and the digest algorithm parameter is used to characterize the algorithm used to determine the digest value corresponding to the software program to be installed and the format of the digest value; According to the verification parameters, the software program to be installed is verified to obtain a verification result, which specifically includes: Extracting a digest value of the software program to be installed according to the digest algorithm parameters to determine a reference digest value corresponding to the software program to be installed; and Decrypting the digital signature value according to the first key to obtain a decryption summary value corresponding to the software program to be installed; The software program to be installed is verified according to the reference digest value and the decrypted digest value to obtain a verification result, wherein if the reference digest value is consistent with the decrypted digest value, a verification result indicating that there is no abnormality in the software program to be installed can be obtained; if the reference digest value is inconsistent with the decrypted digest value, a verification result indicating that there is an abnormality in the software program to be installed can be obtained.

[0009] Optionally, if it is determined that the target software program has an anomaly according to the anomaly detection result, obtaining pre-stored version record data corresponding to the target software program from a preset designated storage medium specifically includes: If it is determined that the target software program has an abnormality according to the abnormality detection result, an abnormality impact range parameter is determined according to the monitoring parameter having the abnormality, and the abnormality impact range parameter is stored in a preset abnormality log file, wherein the abnormality impact range parameter is used to characterize at least one other software program affected by the monitoring parameter having the abnormality; and The pre-stored version record data corresponding to the target software program is obtained from a preset designated storage medium.

[0010] Optionally, installing and running the rollback software program to perform the task through the rollback software program specifically includes: Install and run the fallback software program, and determine a test task request that matches the fallback software program from preset test task requests as a target test task request; According to the target test task request, a functional test is performed on the rollback software program to obtain a functional test result of the rollback software program, wherein the functional test result is used to reflect whether the rollback software program has an abnormality; If it is determined according to the functional test result that there is no abnormality in the fallback software program, the task is executed through the fallback software program.

[0011] Optionally, the method further comprises: An exception report file is generated based on the exception detection result and the rollback software program, and the exception report file is sent to the ground end. The exception report file includes: at least one of the exception occurrence time, exception type, rollback result and version data of the rollback software program.

[0012] Optionally, the method further comprises: At every designated time interval, obtaining the verification parameter corresponding to each historical software program from the designated storage medium as a candidate verification parameter; For each historical software program, the historical software program is verified according to the candidate verification parameters corresponding to the historical software program, a verification result of the historical software program is obtained, and the verification result of the historical software program is saved.

[0013] This specification provides a satellite anti-single event effect task execution device, including: A first acquisition module, used for acquiring monitoring parameters of a target software program, wherein the monitoring parameters are used for reflecting the running state of the target software program and the current state of hardware resources on which the target software program depends; A detection module, used to perform anomaly detection on the target software program according to the monitoring parameters, and obtain an anomaly detection result of the target software program, wherein the anomaly detection result is used to indicate whether the target software program has an anomaly; A second acquisition module is used to acquire pre-stored version record data corresponding to the target software program from a preset designated storage medium if it is determined that the target software program has an abnormality according to the abnormality detection result; A determination module, configured to determine, based on the version record data, a previous version of a historical software program that is adjacent to the target software program in update time as a fallback software program; The execution module is used to install and run the rollback software program to perform tasks through the rollback software program.

[0014] This specification provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned satellite anti-single-particle effect task execution method is implemented.

[0015] This specification provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned satellite anti-single particle effect mission execution method when executing the program.

[0016] At least one of the above technical solutions adopted in this specification can achieve the following beneficial effects: In the satellite anti-single particle effect task execution method provided in this specification, first, the monitoring parameters of the target software program are obtained, where the monitoring parameters are used to reflect the running status of the target software program and the current status of the hardware resources on which the target software program depends. According to the monitoring parameters, an abnormality detection is performed on the target software program to obtain an abnormality detection result of the target software program. The abnormality detection result is used to characterize whether there is an abnormality in the target software program. If it is determined that the target software program has an abnormality according to the abnormality detection result, the version record data corresponding to the pre-stored target software program is obtained from a preset designated storage medium. According to the version record data, the previous version of the historical software program that is adjacent to the target software program in update time is determined as a fallback software program, and the fallback software program is installed and run to perform the task through the fallback software program.

[0017] It can be seen from the above method that by real-time monitoring of the running status of the target software program installed on the satellite, abnormal behaviors such as data anomalies, program crashes and performance degradation can be automatically detected. Once a software anomaly is detected, the control device can autonomously roll back to the previous normal software version to improve the efficiency of handling anomalies when the satellite is running in orbit. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of this specification and constitute a part of this specification. The illustrative embodiments and descriptions of this specification are used to explain this specification and do not constitute an improper limitation on this specification. In the drawings: Figure 1 A schematic diagram of a process for executing a satellite anti-single event effect mission provided in this specification; Figure 2 A schematic diagram of a satellite anti-single event effect mission execution device provided in this specification; Figure 3 A method corresponding to the Figure 1 Schematic diagram of electronic equipment. DETAILED DESCRIPTION

[0019] In order to make the purpose, technical solutions and advantages of this specification more clear, the technical solutions of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0020] At present, when a satellite is operating in orbit, high-energy particles of cosmic rays in the space environment may interact with semiconductor materials, causing charge accumulation, resulting in memory bit flips, data corruption, etc., which in turn may cause anomalies in the software program installed on the satellite itself, or anomalies in the application of the software program.

[0021] The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

[0022] Figure 1 The flowchart of a satellite anti-single-event effect task execution method provided in this specification includes the following steps: S101: Acquire monitoring parameters of a target software program, where the monitoring parameters are used to reflect the running status of the target software program and the current status of hardware resources on which the target software program depends.

[0023] In this specification, the satellite system can monitor the running status of each software program installed on the satellite in real time, so that when an abnormal software program is monitored, the abnormality can be handled in time, thereby improving the safety of the satellite.

[0024] Specifically, the satellite system can target each software program installed on the satellite and use the software program as the target software program, thereby obtaining monitoring parameters of the target software program and, when it is determined that the target software program has an abnormality based on the monitoring parameters of the target software program, promptly handle the abnormality so that the satellite can continue to execute the mission after the abnormality is handled.

[0025] The above-mentioned software programs can be determined according to actual needs, for example, software programs for satellite attitude control, software programs for satellite signal processing, software programs for image processing, etc.

[0026] The above monitoring parameters are used to reflect the running status of the target software program and the current status of the hardware resources that the target software program depends on. For example: the running time of the process corresponding to the target software program, the number of times the process corresponding to the target software program is started per unit time (such as the number of times the process corresponding to the target software program is started every 5 seconds, etc.), the memory usage rate and CPU usage rate of the target software program, etc.

[0027] In this specification, the execution subject used to implement the satellite anti-single particle effect task execution method can refer to a designated device such as a flight computer, an embedded device, etc. set in the satellite, or it can refer to devices such as a desktop computer, a server, etc. For the sake of ease of description, the satellite anti-single particle effect task execution method provided in this specification is described below by taking the control device as the execution subject as an example.

[0028] S102: Perform anomaly detection on the target software program according to the monitoring parameters to obtain an anomaly detection result of the target software program, wherein the anomaly detection result is used to indicate whether the target software program has an anomaly.

[0029] In this specification, the control device can determine, for each acquired monitoring parameter, an abnormality detection strategy that matches the monitoring parameter as the abnormality detection strategy corresponding to the monitoring parameter, and can perform abnormality detection on the monitoring parameter through the abnormality detection strategy corresponding to the monitoring parameter to obtain the abnormality detection result of the monitoring parameter, and then can determine the abnormality detection result of the target software program based on the abnormality detection result of each monitoring parameter.

[0030] The above anomaly detection result is used to characterize whether there is an anomaly in the target software program.

[0031] The above-mentioned anomaly detection strategy can be pre-set for different monitoring parameters. For example, if the monitoring parameter is the running time of the process corresponding to the target software program, the anomaly detection strategy for the monitoring parameter can be determined to compare the running time of the process corresponding to the target software program with the set running time threshold to determine whether the monitoring parameter is abnormal.

[0032] For another example: if the monitoring parameter is the number of times the process corresponding to the target software program is started per unit time, the anomaly detection strategy for the monitoring parameter can be determined as determining whether the number of times the process corresponding to the target software program is started per unit time exceeds a preset threshold value for the number of starts. If so, it can be determined that the monitoring parameter is abnormal.

[0033] The above-mentioned method of determining the abnormality detection result of the target software program based on the abnormality detection result of each monitoring parameter can be: if, based on the abnormality detection result of each monitoring parameter, it is determined that at least one monitoring parameter among the monitoring parameters of the target software program is abnormal, then it can be determined that the target software program is abnormal.

[0034] S103: If it is determined that the target software program has an abnormality according to the abnormality detection result, then the pre-stored version record data corresponding to the target software program is obtained from a preset designated storage medium.

[0035] Furthermore, if the control device determines that an abnormality exists in the target software program based on the abnormality detection result, the control device may obtain the pre-stored version record data corresponding to the target software program from a preset designated storage medium.

[0036] The above-mentioned designated storage medium may refer to a memory capable of resisting damage to electronic equipment caused by high-energy particles in the space environment, for example, a memory with radiation resistance made of high-purity silicon material.

[0037] Another example is a memory device manufactured using deep submicron technology, which has a smaller device size and a lower probability of single event effects.

[0038] Another example is a memory that uses a redundant design and has a high fault tolerance capability.

[0039] The above-mentioned version record data may be version data, update time, etc. of different versions of software programs historically installed on the satellite.

[0040] It should be noted that the above-mentioned version record data can be recorded and saved in a designated storage medium by the control device each time it receives a new software program to be installed. For ease of understanding, the entire process of installing the software program on the satellite is described in detail below.

[0041] Specifically, when the ground end needs to upload a software program to the satellite, it can take the software program to be installed in the satellite as the software program to be installed, and assign a unique version number to the software program to be installed, for example: algorithm software: CAL_V1.0, CAL_V1.1, CAL_V1.2, etc.

[0042] Furthermore, the ground terminal can use a preset digest algorithm to extract the digest value of the software program to be installed to determine the digest value corresponding to the software program to be installed. For example, the above-mentioned digest algorithm can be the national commercial cryptographic algorithm (SM3 Cryptographic Hash Algorithm, SM3). At this time, the ground terminal can use SM3 to perform hash calculation on the software program to be installed to obtain the digest value corresponding to the software program to be installed.

[0043] Furthermore, the ground end can use a preset first key to encrypt the summary value corresponding to the software program to be installed, generate a digital signature value of the software program to be installed, and package the software program to be installed (the executable file or binary code of the software program to be installed), version data of the software program to be installed, the digital signature value of the software program to be installed, the preset second key, and the summary algorithm parameters into a data packet file, and send the data packet file to the control device.

[0044] Among them, in order to improve the security of data packet files during transmission, the ground end can also use a specified encryption algorithm (such as a symmetric encryption algorithm) to encrypt the data packet before sending the data packet file to the control device to obtain an encrypted data packet file, and share the encryption key used in the encryption process with the control device in advance through a secure key distribution mechanism, and then the encrypted data packet file can be sent to the control device.

[0045] In addition, in order to prevent data in the data packet file from being damaged during transmission, the ground terminal can also add an error check code (such as a 32-bit cyclic redundancy check code (32-bit Cyclic Redundancy Check, CRC32)) to the data packet file, so that the control device can perform integrity check on the received data packet file according to the error check code after receiving the data packet file.

[0046] In this specification, after receiving the data packet file sent by the ground terminal, the control device can perform a preliminary integrity check on the received data packet file according to the error check code in the data packet file.

[0047] Furthermore, the control device can decrypt the received data packet file according to the received encryption key to extract the software program to be installed, as well as the version data and verification parameters of the software program to be installed from the received data packet file. The verification parameters here are used to reflect whether there are any abnormalities in the transmission process of the data packet file. The verification parameters here may include: a digital signature value, a first key, and a digest algorithm parameter. The digest algorithm parameter here is used to characterize the algorithm used to determine the digest value corresponding to the software program to be installed and the format of the digest value.

[0048] Among them, if the control device determines that there is an integrity abnormality in the data packet file based on the error check code in the data packet file, or an error occurs when decrypting the received data packet file according to the received encryption key, a warning message can be sent to the ground terminal.

[0049] Of course, if the control device uses the received encryption key to obtain the version data and verification parameters of the software program to be installed, the control device can verify the software program to be installed according to the verification parameters to obtain a verification result, and if it is determined that there is no abnormality in the software program to be installed according to the verification result, the control device will install the software program to be installed, and store the update time and version data of the software program to be installed in the version record data corresponding to the software program to be installed (the version record data corresponding to the software program to be installed here may include version data of historical software programs of the same type as the software program to be installed but with a different version).

[0050] Specifically, the control device can determine the digest algorithm used by the ground terminal when calculating the digest value corresponding to the software program to be installed, and the format of the digest value corresponding to the software program to be installed, according to the digest algorithm parameters, and then recalculate the digest value corresponding to the software program to be installed extracted from the received data packet file according to the determined digest algorithm and the determined digest value format as a reference digest value. And, according to the first key in the data packet file, the digital signature value in the data packet file is decrypted to obtain the decrypted digest value corresponding to the software program to be installed.

[0051] Furthermore, the control device may verify the software program to be installed according to the calculated reference digest value and the decrypted digest value to obtain a verification result.

[0052] Among them, if the calculated reference digest value is consistent with the decrypted digest value, a verification result can be obtained that there is no abnormality in the software program to be installed. At this time, the control device can install the software program to be installed, and store the update time and version data of the software program to be installed in the version record data corresponding to the software program to be installed.

[0053] If the calculated reference digest value is inconsistent with the decrypted digest value, a verification result indicating that an abnormality exists in the software program to be installed can be obtained. At this time, the control device can send an alarm message to the ground terminal and re-acquire the data packet file from the ground terminal.

[0054] It should be noted that since the above-mentioned designated storage medium with radiation resistance constructed using special technology is often small, in actual application scenarios, the software program to be installed can be stored in the designated storage medium. Preferably, the software program to be installed can also be installed in other storage media, and the version record data and verification parameters of the software program to be installed can be saved in the designated storage medium.

[0055] In addition, in this specification, the control device may perform permission verification on each software program installation operation, and may only execute the software program installation operation after determining that the software program installation operation meets the preset authorization conditions.

[0056] It is worth mentioning that in order to improve the security of data transmission between the ground end and the satellite, an automatic repeat request mechanism (ARQ) can be used when the ground end and the satellite are transmitting data. When an abnormality is detected during the data transmission process, the data can be resent until the data is correctly received and a confirmation signal is received from the receiver.

[0057] S104: Determine, according to the version record data, a previous version of a historical software program that is adjacent to the target software program in update time as a fallback software program.

[0058] S105: Install and run the rollback software program to perform the task through the rollback software program.

[0059] In this specification, after obtaining the version record data corresponding to the target software program, the control device can determine, based on the obtained version record data, the previous version of the historical software program that is adjacent to the target software program in update time as the fallback software program, and then obtain the verification parameters of the fallback software program from the specified storage medium, and verify the fallback software program through the above method, so as to install and run the fallback software program after determining that there is no abnormality in the fallback software program, so as to execute the task through the fallback software program, and save the executed rollback operation and the version data of the currently running fallback software program to the preset version management log.

[0060] Specifically, the control device can install and run the fallback software program, and determine a test task request that matches the fallback software program from the preset test task requests as the target test task request, and then perform a functional test on the fallback software program according to the target test task request to obtain a functional test result of the fallback software program, wherein the functional test result here is used to reflect whether there is an abnormality in the fallback software program.

[0061] Furthermore, if the control device determines that there is no abnormality in the fallback software program based on the functional test results, the task is executed through the fallback software program, and during the process of executing the task through the fallback software program, the running status of the fallback software program continues to be monitored, so that when an abnormality is detected in the fallback software program again, the abnormality is recorded and an alarm message is sent to the ground end.

[0062] In addition, while executing the task through the fallback software program, the control device can also generate an exception report file based on the exception detection results of the target software program and the fallback software program, and send the exception report file to the ground end. The exception report file here includes: at least one of the exception occurrence time, exception type, fallback result and version data of the fallback software program.

[0063] It should be noted that the control device can also obtain the verification parameters corresponding to each historical software program from the specified storage medium at every specified time interval as alternative verification parameters, and then verify each historical software program according to the alternative verification parameters corresponding to the historical software program to obtain the verification result of the historical software program, and save the verification result of the historical software program, so that when executing the rollback operation, it can determine whether the historical software program has any abnormality based on the verification result of the historical software program, and when it is determined that the historical software program does not have any abnormality, the historical software program can be installed and run as a rollback software program.

[0064] It is worth noting that in actual application scenarios, when a monitoring parameter of a target software program is abnormal, in addition to affecting the operation of the target software program itself, it may also affect the operation of other software programs. For example, when the monitoring parameter of the control software program installed on the satellite for controlling the sensor to collect image data is abnormal, it may cause the software program installed on the satellite for image processing to also be abnormal.

[0065] Based on this, when the control device determines that there is an abnormality in the target software program based on the abnormality detection result, it can also determine the abnormality impact range parameters based on the monitoring parameters with the abnormality, and store the abnormality impact range parameters in a preset abnormality log file. The abnormality impact range parameters here are used to characterize at least one other software program affected by the monitoring parameters with the abnormality.

[0066] Furthermore, when the control device installs the fallback software program and runs it to perform tasks through the fallback software program, it can also determine, based on the above-mentioned abnormal impact range parameters, at least one other software program affected by the abnormal monitoring parameters as a supplementary abnormal software program, and perform abnormality detection on the supplementary abnormal software program so that when it is determined that the supplementary abnormal software program has an abnormality, the rollback operation for the supplementary abnormal software program can be executed in a timely manner.

[0067] It can be seen from the above method that the control device can automatically detect abnormal behaviors such as data anomalies, program crashes and performance degradation by monitoring the running status of software such as attitude control and signal processing installed on the satellite in real time. Once a software anomaly is detected, the control device can autonomously roll back to the previous normal software version and perform signature verification during the rollback process to ensure the integrity and credibility of the version.

[0068] The above are one or more implementation methods of satellite anti-single-particle effect task execution methods of this specification. Based on the same idea, this specification also provides a corresponding satellite anti-single-particle effect task execution device, such as Figure 2 shown.

[0069] Figure 2 A schematic diagram of a satellite anti-single event effect mission execution device provided for this specification includes: A first acquisition module 201, used for acquiring monitoring parameters of a target software program, wherein the monitoring parameters are used for reflecting the running state of the target software program and the current state of hardware resources on which the target software program depends; A detection module 202, configured to perform anomaly detection on the target software program according to the monitoring parameters, and obtain an anomaly detection result of the target software program, wherein the anomaly detection result is used to indicate whether the target software program has an anomaly; The second acquisition module 203 is used to acquire the pre-stored version record data corresponding to the target software program from a preset designated storage medium if it is determined that the target software program has an abnormality according to the abnormality detection result; A determination module 204 is used to determine, based on the version record data, a previous version of a historical software program that is adjacent to the target software program in update time as a fallback software program; The execution module 205 is used to install and run the rollback software program to perform the task through the rollback software program.

[0070] Optionally, the device further includes: a storage module 206; The storage module 206 is specifically used to receive a data packet file sent by the ground end; decrypt the data packet file to extract the software program to be installed, as well as the version data and verification parameters of the software program to be installed from the data packet file, and the verification parameters are used to reflect whether there is an abnormality in the transmission process of the data packet file; verify the software program to be installed according to the verification parameters to obtain a verification result, and when it is determined that there is no abnormality in the software program to be installed according to the verification result, install the software program to be installed, and store the update time and version data of the software program to be installed in the version record data corresponding to the software program to be installed.

[0071] Optionally, the verification parameters include: a digital signature value, a first key, and a digest algorithm parameter, wherein the digital signature value is obtained by encrypting the digest value corresponding to the software program to be installed by the ground terminal using a preset second key, and the digest algorithm parameter is used to characterize the algorithm used to determine the digest value corresponding to the software program to be installed and the format of the digest value; The storage module 206 is specifically used to extract the digest value of the software program to be installed according to the digest algorithm parameters to determine the reference digest value corresponding to the software program to be installed; and, according to the first key, decrypt the digital signature value to obtain the decrypted digest value corresponding to the software program to be installed; verify the software program to be installed according to the reference digest value and the decrypted digest value to obtain a verification result, wherein if the reference digest value is consistent with the decrypted digest value, a verification result indicating that there is no abnormality in the software program to be installed can be obtained, and if the reference digest value is inconsistent with the decrypted digest value, a verification result indicating that there is an abnormality in the software program to be installed can be obtained.

[0072] Optionally, the second acquisition module 203 is specifically used to, if it is determined that the target software program has an abnormality based on the abnormality detection result, determine an abnormality impact range parameter based on the monitoring parameter with the abnormality, and store the abnormality impact range parameter in a preset abnormality log file, wherein the abnormality impact range parameter is used to characterize at least one other software program affected by the monitoring parameter with the abnormality; and obtain the pre-stored version record data corresponding to the target software program from a preset designated storage medium.

[0073] Optionally, the execution module 205 is specifically used to install and run the fallback software program, and determine a test task request that matches the fallback software program from the preset test task requests as a target test task request; according to the target test task request, perform a functional test on the fallback software program to obtain a functional test result of the fallback software program, and the functional test result is used to reflect whether there is an abnormality in the fallback software program; if it is determined according to the functional test result that there is no abnormality in the fallback software program, then the task is executed through the fallback software program.

[0074] Optionally, the execution module 205 is specifically used to generate an exception report file based on the exception detection result and the fallback software program, and send the exception report file to the ground end, and the exception report file includes: the exception occurrence time, the exception type, the fallback result and at least one of the version data of the fallback software program.

[0075] Optionally, the execution module 205 is specifically used to obtain the verification parameters corresponding to each historical software program from the specified storage medium at every specified time interval as alternative verification parameters; for each historical software program, verify the historical software program according to the alternative verification parameters corresponding to the historical software program, obtain the verification result of the historical software program, and save the verification result of the historical software program.

[0076] This specification also provides a computer-readable storage medium, which stores a computer program, which can be used to execute the above Figure 1 A satellite anti-single-particle effect mission execution method is provided.

[0077] This manual also provides Figure 3 The one shown corresponds to Figure 1 A schematic diagram of the electronic device. Figure 3 As mentioned above, at the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include other hardware required for the business. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it to achieve the above Figure 1 Of course, in addition to the software implementation, this specification does not exclude other implementations, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0078] For the improvement of a technology, it can be clearly distinguished whether it is a hardware improvement (for example, improvement of the circuit structure of diodes, transistors, switches, etc.) or a software improvement (improvement of the method flow). However, with the development of technology, many improvements of the method flow today can be regarded as direct improvements of the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented with a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming themselves, without having to ask chip manufacturers to design and make dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0079] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0080] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0081] For the convenience of description, the above device is described by dividing it into various units according to its functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0082] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0083] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0084] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0085] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0086] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0087] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0088] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0089] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0090] It should be understood by those skilled in the art that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, this specification may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0091] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0092] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0093] The above description is only an embodiment of the present specification and is not intended to limit the present specification. For those skilled in the art, the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of the claims of the present specification.

Claims

1. A satellite anti-single event effect mission execution method, characterized in that: include: Acquiring monitoring parameters of a target software program, wherein the monitoring parameters are used to reflect the running state of the target software program and the current state of hardware resources on which the target software program depends; According to the monitoring parameters, anomaly detection is performed on the target software program to obtain an anomaly detection result of the target software program, wherein the anomaly detection result is used to characterize whether the target software program has an anomaly; If it is determined that the target software program has an anomaly according to the anomaly detection result, obtaining the pre-stored version record data corresponding to the target software program from a preset designated storage medium; Determine, according to the version record data, a previous version of a historical software program that is adjacent to the target software program in update time as a fallback software program; The fallback software program is installed and run to perform task execution through the fallback software program.

2. The method according to claim 1, characterized in that Storing version record data corresponding to the target software program, specifically including: Receive data packet files sent by the ground terminal; Decrypting the data packet file to extract the software program to be installed, as well as version data and verification parameters of the software program to be installed from the data packet file, wherein the verification parameters are used to reflect whether there is an abnormality in the transmission process of the data packet file; The software program to be installed is verified according to the verification parameters to obtain a verification result, and when it is determined according to the verification result that there is no abnormality in the software program to be installed, the software program to be installed is installed, and the update time and version data of the software program to be installed are stored in the version record data corresponding to the software program to be installed.

3. The method according to claim 2, characterized in that The verification parameters include: a digital signature value, a first key, and a digest algorithm parameter, wherein the digital signature value is obtained by encrypting the digest value corresponding to the software program to be installed by the ground terminal using a preset second key, and the digest algorithm parameter is used to characterize the algorithm used to determine the digest value corresponding to the software program to be installed and the format of the digest value; According to the verification parameters, the software program to be installed is verified to obtain a verification result, which specifically includes: Extracting a digest value of the software program to be installed according to the digest algorithm parameters to determine a reference digest value corresponding to the software program to be installed; and Decrypting the digital signature value according to the first key to obtain a decryption summary value corresponding to the software program to be installed; The software program to be installed is verified according to the reference digest value and the decrypted digest value to obtain a verification result, wherein if the reference digest value is consistent with the decrypted digest value, a verification result indicating that there is no abnormality in the software program to be installed can be obtained; if the reference digest value is inconsistent with the decrypted digest value, a verification result indicating that there is an abnormality in the software program to be installed can be obtained.

4. The method according to claim 1, characterized in that If it is determined that the target software program has an abnormality according to the abnormality detection result, obtaining the pre-stored version record data corresponding to the target software program from a preset designated storage medium, specifically including: If it is determined that the target software program has an abnormality according to the abnormality detection result, an abnormality impact range parameter is determined according to the monitoring parameter having the abnormality, and the abnormality impact range parameter is stored in a preset abnormality log file, wherein the abnormality impact range parameter is used to characterize at least one other software program affected by the monitoring parameter having the abnormality; and The pre-stored version record data corresponding to the target software program is obtained from a preset designated storage medium.

5. The method according to claim 1, characterized in that Installing and running the rollback software program to perform the task through the rollback software program specifically includes: Install and run the fallback software program, and determine a test task request that matches the fallback software program from preset test task requests as a target test task request; According to the target test task request, a functional test is performed on the rollback software program to obtain a functional test result of the rollback software program, wherein the functional test result is used to reflect whether the rollback software program has an abnormality; If it is determined according to the functional test result that there is no abnormality in the fallback software program, the task is executed through the fallback software program.

6. The method according to claim 1, characterized in that The method further comprises: An exception report file is generated based on the exception detection result and the rollback software program, and the exception report file is sent to the ground end. The exception report file includes: at least one of the exception occurrence time, exception type, rollback result and version data of the rollback software program.

7. The method according to claim 1, characterized in that The method further comprises: At every designated time interval, obtaining the verification parameter corresponding to each historical software program from the designated storage medium as a candidate verification parameter; For each historical software program, the historical software program is verified according to the candidate verification parameters corresponding to the historical software program, a verification result of the historical software program is obtained, and the verification result of the historical software program is saved.

8. A satellite anti-single event effect mission execution device, characterized in that: include: A first acquisition module, used for acquiring monitoring parameters of a target software program, wherein the monitoring parameters are used for reflecting the running state of the target software program and the current state of hardware resources on which the target software program depends; A detection module, used to perform anomaly detection on the target software program according to the monitoring parameters, and obtain an anomaly detection result of the target software program, wherein the anomaly detection result is used to indicate whether the target software program has an anomaly; A second acquisition module is used to acquire pre-stored version record data corresponding to the target software program from a preset designated storage medium if it is determined that the target software program has an abnormality according to the abnormality detection result; A determination module, configured to determine, based on the version record data, a previous version of a historical software program that is adjacent to the target software program in update time as a fallback software program; The execution module is used to install and run the rollback software program to perform tasks through the rollback software program.

9. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of claims 1 to 7 is implemented.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method described in any one of claims 1 to 7 is implemented.

Images