Method for non-invasive updating of spacecraft on-orbit mission flow based on hardware virtualization
Patent Information
- Application Number
- CN202611018134.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-09
- Publication Date
- 2026-10-09
AI Technical Summary
[0003]当在轨发生飞行故障需修复或飞行任务需升级时，现有技术通过局部在轨编程方式直接对飞行软件中涉及飞行任务流程的软件代码进行修改，或通过全局在轨编程方式直接替换整个飞行软件二进制码，过程复杂、实施难度大、风险较高
[0012]本发明通过构建虚拟嵌入式系统将飞行任务流程与飞行软件基础框架隔离，将飞行任务流程（二进制文件）存储于数据库中，执行飞行任务流程时将飞行任务流程（二进制文件）加载到虚拟嵌入式系统中，通过虚拟嵌入式系统实现飞行任务流程（二进制文件）与飞行软件基础框架的交互；而对飞行任务流程的更新升级、增加只针对数据库，不涉及飞行软件基础框架，降低过程复杂度、实施难度、风险；
Smart Images
Figure CN122884512A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the management of spacecraft on-orbit flight mission processes under limited resources, and particularly to a non-invasive update method for spacecraft on-orbit flight mission processes based on hardware virtualization. Background Technology
[0002] Space missions are high-risk missions, requiring significant upfront research and development investment and high reliability during on-orbit operation. On-orbit computers are exposed to the extreme temperatures, radiation, and ionization of space, necessitating the selection of radiation-hardened hardware. Typically, this means that only low-frequency processors and small-capacity memory can be used to build the hardware platform.
[0003] When a flight malfunction occurs in orbit and needs repair or the flight mission needs to be upgraded, existing technologies either modify the software code related to the flight mission process directly through local on-orbit programming or replace the entire flight software binary code directly through global on-orbit programming. This process is complex, difficult to implement, and carries high risks.
[0004] Therefore, how to achieve on-orbit upgrades of spacecraft flight mission procedures without changing the flight software framework under limited resources has become an urgent problem to be solved. Summary of the Invention
[0005] The purpose of this invention is to provide a non-invasive update method for spacecraft on-orbit flight mission processes based on hardware virtualization. This method constructs a virtual embedded system (virtual hardware) based on a digital RISCV instruction set, which isolates the flight mission processes from the basic flight software framework, enabling on-orbit replacement, upgrades, and additions of flight mission processes without involving changes to the basic flight software framework.
[0006] To achieve the above objectives, this invention provides a non-invasive update method for spacecraft on-orbit flight mission procedures based on hardware virtualization. It constructs a virtual embedded system based on a digital RISC-CV instruction set to isolate the flight mission procedures from the basic flight software framework. A flight mission procedure database is set up to store the flight mission procedures. When executing a flight mission procedure, the procedure is loaded into the virtual embedded system, enabling interaction between the flight mission procedures and the basic flight software framework. On-orbit updates, upgrades, and additions to the flight mission procedures are achieved by updating the flight mission procedure database.
[0007] The above-mentioned non-invasive update method for spacecraft on-orbit flight mission processes based on hardware virtualization includes: (1) constructing a virtual embedded system based on the digital RISCV instruction set on the spacecraft embedded processor with limited resources, constructing an information interaction interface between the virtual embedded system and the spacecraft flight software, and realizing spacecraft status acquisition and control output; (2) for each flight mission process, implementing flight mission process coding through high-level language programming, and compiling it into an independently executable binary file described by RISCV instructions through an automated toolchain; setting up a flight mission process database to store the binary files of each flight mission process; (3) when executing the flight mission process, the virtual embedded system reads the binary file of the flight mission process, parses the binary machine instructions, and realizes the timing and logic control of the flight mission process through the binary machine instruction parsing process; (4) when the executed flight mission process needs to collect data or output data to the outside, the ECALL instruction in the RISCV instruction set completes the callback of the input and output interface in the basic framework code of the flight software.
[0008] The above-mentioned non-invasive update method for spacecraft on-orbit flight mission process based on hardware virtualization includes the following steps: In step (2), the automated toolchain encapsulates feature identification information at the beginning of the generated bin file and adds CRC check information at the end of the file; In step (3), before parsing the binary machine instructions, the feature identification information encapsulated at the beginning of the binary file and the CRC check information added at the end are first verified.
[0009] The above-mentioned non-invasive update method for spacecraft on-orbit flight mission processes based on hardware virtualization also includes: (5) when multiple flight mission processes need to run in parallel, constructing multiple virtual embedded systems, each virtual embedded system reading a binary file of a flight mission process; (6) designing a flight mission process lookup table to support the addition, modification, lookup, and cancellation of flight mission processes.
[0010] The above-mentioned non-invasive update method for spacecraft on-orbit flight mission processes based on hardware virtualization includes step (6) as follows: when the on-orbit flight mission process needs to be updated, the binary file of the original flight mission process in the flight mission process database is replaced by the flight mission process lookup table; when a new on-orbit flight mission process needs to be added, the binary file of the new on-orbit flight mission process is injected into the reserved space of the flight mission process database, and the flight mission process lookup table is updated at the same time; the binary file of a certain on-orbit flight mission process is viewed by the flight mission process lookup table through the telemetry downlink method; and the on-orbit flight mission process is discarded by setting the valid flag of the flight mission process to invalid.
[0011] Compared with the prior art, the beneficial technical effects of the present invention are:
[0012] This invention isolates the flight mission process from the basic flight software framework by constructing a virtual embedded system. The flight mission process (binary file) is stored in a database. When the flight mission process is executed, the flight mission process (binary file) is loaded into the virtual embedded system, and the interaction between the flight mission process (binary file) and the basic flight software framework is realized through the virtual embedded system. Updates and upgrades to the flight mission process only involve the database and do not involve the basic flight software framework, thus reducing process complexity, implementation difficulty, and risk.
[0013] This invention has been successfully applied to multiple spacecraft, achieving flexible upgrades to on-orbit flight mission procedures. The upgrade process has no impact on the basic framework of the spacecraft's flight software, and the spacecraft's flight software remains in a highly reliable operating state. It solves the problem of on-orbit updates, upgrades, and additions to flight mission procedures without involving changes to the flight software framework. Attached Figure Description
[0014] Figure 1 This is a block diagram of a non-invasive update method for spacecraft on-orbit flight missions based on hardware virtualization, according to an embodiment of the present invention.
[0015] Figure 2 This is a schematic diagram of the flight mission process lookup table and multiple virtual embedded systems in an embodiment of the present invention. Detailed Implementation
[0016] Figure 1 The diagram shown is a block diagram of a non-invasive update method for spacecraft on-orbit flight missions based on hardware virtualization, according to an embodiment of the present invention.
[0017] like Figure 1 The non-invasive update method for spacecraft on-orbit flight mission processes based on hardware virtualization in this embodiment includes:
[0018] (1) On a spacecraft embedded processor with limited resources, a virtual embedded system (virtual hardware) based on the digital RISCV instruction set is constructed, and an information interaction interface between the virtual embedded system and the spacecraft flight software is constructed to realize the spacecraft status acquisition and control output.
[0019] The virtual embedded system (virtual hardware) forms a container structure to hold the executed flight mission process;
[0020] (2) For each flight mission process, the flight mission process is encoded by programming in high-level languages such as C and C++, and compiled into an independent executable binary file described by RISCV instructions through an automated toolchain; a flight mission process database is set up to store the binary files of each flight mission process.
[0021] In this embodiment, the automated toolchain further encapsulates feature identification information at the beginning of the generated bin file and adds CRC check information at the end of the file for data verification, thereby improving system reliability; the compilation tool uses the mature GCC compiler.
[0022] (3) When executing the flight mission process, the virtual embedded system reads the binary file of the flight mission process, parses the binary machine instructions, and realizes the timing and logic control of the flight mission process through the binary machine instruction parsing process;
[0023] Before parsing binary machine instructions, the characteristic identification information encapsulated in the header of the binary file and the CRC check information added at the tail are first verified.
[0024] When the flight mission process is not executed, it is stored in the flight mission process database. When it is executed, it is loaded into the virtual embedded system (virtual hardware) and integrated into the basic framework of the flight software through the virtual embedded system (virtual hardware).
[0025] (4) When the flight mission process needs to collect data or output data to the outside world, the ECALL instruction in the RISCV instruction set completes the callback of the input and output interface in the basic framework code of the flight software. The function number is placed in register r10 of the virtual embedded system, and if there are call parameters, they are stored in registers a0~a7.
[0026] (5) When multiple flight mission processes need to run in parallel, multiple virtual embedded systems are constructed. Each virtual embedded system reads a binary file of a flight mission process, such as... Figure 2 ;
[0027] (6) For example Figure 2 Design a flight mission process lookup table to support adding, modifying, querying, deleting (or scrapping) flight mission processes.
[0028] When the on-orbit flight mission process needs to be updated, the binary file of the original flight mission process in the flight mission process database is replaced by the flight mission process lookup table.
[0029] When a new on-orbit flight mission procedure needs to be added, the binary file of the new on-orbit flight mission procedure is injected into the reserved space of the flight mission procedure database, and the flight mission procedure lookup table is updated at the same time.
[0030] By using telemetry downlink and looking up the flight mission process table, you can view the binary file of a specific on-orbit flight mission process.
[0031] By setting the valid flag of the flight mission process to invalid, the on-orbit flight mission process is discarded.
[0032] The flight mission flow lookup table reflects the mapping relationship between flight mission flow and storage address.
[0033] This invention isolates the flight mission process from the basic flight software framework by constructing a virtual embedded system. The flight mission process (binary file) is stored in a database. When executing the flight mission process, the flight mission process (binary file) is loaded into the virtual embedded system, enabling interaction between the flight mission process (binary file) and the basic flight software framework. Updates and additions to the flight mission process only affect the database and do not involve the basic flight software framework, reducing process complexity, implementation difficulty, and risk. This invention solves the problem of on-orbit updates, upgrades, and additions to the flight mission process without involving changes to the flight software framework.
Claims
1. A non-invasive update method for spacecraft on-orbit flight mission processes based on hardware virtualization, characterized in that, A virtual embedded system based on the digital RISC-CV instruction set is constructed to isolate the flight mission process from the basic flight software framework; a flight mission process database is set up to store the flight mission processes; when the flight mission process is executed, it is loaded into the virtual embedded system, and the interaction between the flight mission process and the basic flight software framework is realized through the virtual embedded system; on-orbit updates, upgrades, and additions to the flight mission process are achieved by updating the flight mission process database.
2. The non-invasive update method for spacecraft on-orbit flight mission procedures based on hardware virtualization as described in claim 1, characterized in that, include: (1) On a spacecraft embedded processor with limited resources, a virtual embedded system based on the digital RISCV instruction set is constructed, and an information interaction interface between the virtual embedded system and the spacecraft flight software is constructed to realize the spacecraft status acquisition and control output. (2) For each flight mission process, the flight mission process is encoded by high-level language programming and compiled into an independent executable binary file described by RISCV instructions through an automated toolchain; a flight mission process database is set up to store the binary files of each flight mission process; (3) When executing the flight mission process, the virtual embedded system reads the binary file of the flight mission process, parses the binary machine instructions, and realizes the timing and logic control of the flight mission process through the binary machine instruction parsing process; (4) When the flight mission process needs to collect data or output data to the outside world, the ECALL instruction in the RISCV instruction set completes the callback of the input and output interface in the basic framework code of the flight software.
3. The non-invasive update method for spacecraft on-orbit flight mission procedures based on hardware virtualization as described in claim 2, characterized in that, In step (2), the automated toolchain also encapsulates feature identification information at the beginning of the generated bin file and adds CRC check information at the end of the file.
4. The non-invasive update method for spacecraft on-orbit flight mission procedures based on hardware virtualization as described in claim 3, characterized in that, In step (3), before parsing the binary machine instructions, the feature identification information encapsulated in the header of the binary file and the CRC check information added to the tail are first verified.
5. The non-invasive update method for spacecraft on-orbit flight mission procedures based on hardware virtualization as described in claim 2, characterized in that, In step (2), the compilation tool used is the mature GCC compiler.
6. The non-invasive update method for spacecraft on-orbit flight mission procedures based on hardware virtualization as described in claim 2, characterized in that, The method further includes: (5) When multiple flight mission processes need to run in parallel, multiple virtual embedded systems are constructed, and each virtual embedded system reads a binary file of a flight mission process.
7. The non-invasive update method for spacecraft on-orbit flight mission procedures based on hardware virtualization as described in claim 2, characterized in that, The method further includes: (6) Design a flight mission process lookup table to support the addition, modification, lookup and cancellation of flight mission processes.
8. The non-invasive update method for spacecraft on-orbit flight mission procedures based on hardware virtualization as described in claim 7, characterized in that, Step (6) includes: When the on-orbit flight mission process needs to be updated, the binary file of the original flight mission process in the flight mission process database is replaced by the flight mission process lookup table. When a new on-orbit flight mission procedure needs to be added, the binary file of the new on-orbit flight mission procedure is injected into the reserved space of the flight mission procedure database, and the flight mission procedure lookup table is updated at the same time. By using telemetry downlink and looking up the flight mission process table, you can view the binary file of a specific on-orbit flight mission process. By setting the valid flag of the flight mission process to invalid, the on-orbit flight mission process can be discarded.