System for on-orbit service reconfiguration and update, start and end methods

Abstract

This invention belongs to the field of software-defined satellite technology, and specifically relates to a software architecture and update, startup, and shutdown method for on-orbit service reconfiguration. It designs an on-orbit service reconfiguration process based on framework software, an on-orbit operational status monitoring process, an on-orbit service reconfiguration testing and maintenance mode, an on-orbit component update mode, and an on-orbit operational fault or alarm mode. By loading, running, and stopping components through framework software, on-orbit reconfiguration of service capabilities is completed, which helps to achieve on-orbit updates of satellite functions and improves the flexibility and reliability of on-orbit service reconfiguration; at the same time, it reduces the dependencies between components, achieving service independence, communication independence, and security independence.

Description

Technical Field

[0001] This invention belongs to the field of software-defined satellite technology, and in particular relates to a system for on-orbit service reconfiguration and methods for updating, starting up and terminating it. Background Technology

[0002] Software-defined satellites utilize software technology to define the same satellite hardware, enabling the reconfiguration of payload functions or performance parameters. This allows for flexible on-orbit mission configuration and addresses the problem of traditional satellites becoming technologically outdated upon launch or before reaching their design lifespan, as their functions are largely fixed once launched and in orbit. Currently, software-defined satellites primarily borrow from software-defined radio technology in terrestrial communications to adjust satellite communication performance. This includes: beam reconfiguration through electronic tuning, beamforming, and beam skipping; dynamic adjustment of operating frequency bands and bandwidth through flexible filters and programmable channels; and dynamic adjustment of antenna gain within the coverage area through multi-port amplifiers. In summary, current software-defined satellite development focuses primarily on the communication satellite field, aiming to achieve on-orbit updates of the same function, but it does not yet support flexible switching between different types of functions. Summary of the Invention

[0003] The purpose of this invention is to address the problem that traditional satellites have essentially fixed functions after launch and orbit and cannot be updated in a timely manner, by providing a software architecture and methods for updating, starting, and terminating on-orbit services that are oriented towards reconfiguration.

[0004] To achieve the above objectives, the technical solution adopted by the present invention is as follows: A system for on-orbit service reconfiguration, comprising a platform layer, a control layer, and a component layer; The platform layer is used to initiate a power-on self-test and report self-test data to higher-level software; it also receives external component update commands, forwards the commands to the control layer, receives the results returned by the control layer, and reports them to higher-level software; it receives task run or stop commands from external software, checks component dependencies, sends the decomposed run or stop commands to the control layer, and receives the results returned by the control layer and reports them to higher-level software; it receives component status information returned by the control layer during component runtime and reports it to higher-level software; and after startup, it obtains the system hardware status and software running status, reports them periodically or reports them after receiving query commands from higher-level software. The control layer is used to receive component update instructions from the platform layer, load the corresponding components from the component layer according to the instruction information, execute the component update process, and return the results to the platform layer; it is also used to receive component run or stop instructions, execute the component run or stop commands according to the instruction information, and return the results to the platform layer; it is also used to periodically monitor the running status of each business component in the component layer, check the component watchdog status, and start the watchdog, and return the component status information to the platform layer. The component layer is used to load components from a specified location into memory by the control layer; it is also used to start or stop execution and to periodically reset the watchdog.

[0005] Furthermore, the system's component update method includes the following processes: (2.1) In standby mode, the platform layer receives update instructions and related parameters from external components and forwards the instructions and parameters to the control layer; (2.2) Back up old components in the control layer; (2.3) When the control layer completes the update according to the instructions and related parameters, it checks the component verification code. If the verification is correct, it loads and registers the component and calls the relevant test interface to perform the test. (2.4) If the test value is incorrect or the verification is incorrect, the corresponding component will be upgraded and rolled back, the update result will be logged, and the update failure will be reported to the platform layer; if the test value is correct and the verification is correct, the update verification will be successful, the component will be put into the database, the update result will be logged, and the update success will be reported to the platform layer. (2.5) The platform layer reports the results to the next level software.

[0006] Furthermore, the system's task startup and termination methods include the following processes: (3.1) In standby mode, the platform layer receives external task execution instructions and related parameters, checks component dependencies according to the instructions, and sorts the components. (3.2) The platform layer commands the control layer to perform initialization operations on each component in the order of components, including loading, registration and confirmation of version number; after initialization, the control layer commands the corresponding components to start in the order of components, and commands the control layer to start the watchdog, and records the component start time. If an error occurs in the process, the platform layer returns the execution result error to the upper-level software, and the process ends. (3.3) During task execution, the control layer periodically detects the memory and computing resources occupied by the component, periodically checks the watchdog status, and if the watchdog is not reset, it reports the component error to the platform layer and restarts the watchdog; after the component starts, the watchdog status is reset periodically. (3.4) After receiving the task termination instruction, the platform layer commands the control layer to stop the running components in reverse order of component startup, and then unregisters the components and releases the resources occupied by the software during runtime. If all terminations are successful, the task termination success result is returned to the upper level software; otherwise, the task termination failure result is returned to the upper level software.

[0007] The beneficial effects of this invention are as follows: The on-orbit service reconfiguration method based on framework software proposed in this invention fully considers the flexibility of on-orbit reconfiguration for different types of services. It can update different types of services for on-orbit reconfiguration through the integration of frameworks and components. Through the exception rollback mechanism in the component update process, it avoids the impact of component update failure on the original service operation during on-orbit service reconfiguration. The use of framework software to achieve loose coupling between components effectively reduces the dependency between components, thereby achieving service independence, communication independence, and security independence. When one component in the system malfunctions, other components will not be affected by its malfunction. Through different components loading, unloading, instantiating, and deinstantiating themselves, it achieves self-management of component resource consumption, avoids system anomalies caused by improper handling by other components, and improves the reliability of the entire system. Attached Figure Description

[0008] Figure 1 This is a schematic diagram of the system of the present invention.

[0009] Figure 2 The business process diagram is reconstructed for this invention.

[0010] Figure 3 This is a schematic diagram of the dynamic integration of the components of the present invention. Detailed Implementation

[0011] The present invention will now be further described with reference to examples and accompanying drawings.

[0012] This invention proposes a system and its update, startup, and termination methods for on-orbit service reconfiguration. It fully considers the flexibility of on-orbit reconfiguration for different types of services, achieving various on-orbit reconfigurations through a microkernel integration framework and plug-and-play components. The framework software effectively reduces dependencies between components, thereby achieving service independence, communication independence, and security independence. When one component malfunctions, other components are not affected. Each component performs its own loading, unloading, instantiation, and deinstantiation, adhering to self-management of resources and avoiding anomalies caused by improper handling by other components, thus improving the overall system reliability. The specific implementation is as follows: Example 1, as Figure 1 As shown.

[0013] A system for on-orbit service reconfiguration, characterized in that it includes a platform layer, a control layer, and a component layer; The platform layer is used to initiate a power-on self-test and report self-test data to higher-level software; it also receives external component update commands, forwards the commands to the control layer, receives the results returned by the control layer, and reports them to higher-level software; it receives task run or stop commands from external software, checks component dependencies, sends the decomposed run or stop commands to the control layer, and receives the results returned by the control layer and reports them to higher-level software; it receives component status information returned by the control layer during component runtime and reports it to higher-level software; and after startup, it obtains the system hardware status and software running status, reports them periodically or reports them after receiving query commands from higher-level software. The control layer is used to receive component update instructions from the platform layer, load the corresponding components from the component layer according to the instruction information, execute the component update process, and return the results to the platform layer; it is also used to receive component run or stop instructions, execute the component run or stop commands according to the instruction information, and return the results to the platform layer; it is also used to periodically monitor the running status of each business component in the component layer, check the component watchdog status, and start the watchdog, and return the component status information to the platform layer. The component layer is used to load components from a specified location into memory by the control layer; it is also used to start or stop execution and to periodically reset the watchdog.

[0014] Example 2, a system component update method, includes the following process: (2.1) In standby mode, the platform layer receives update instructions and related parameters from external components and forwards the instructions and parameters to the control layer; (2.2) Back up old components in the control layer; (2.3) When the control layer completes the update according to the instructions and related parameters, it checks the component verification code. If the verification is correct, it loads and registers the component and calls the relevant test interface to perform the test. (2.4) If the test value is incorrect or the verification is incorrect, the corresponding component will be upgraded and rolled back, the update result will be logged, and the update failure will be reported to the platform layer; if the test value is correct and the verification is correct, the update verification will be successful, the component will be put into the database, the update result will be logged, and the update success will be reported to the platform layer. (2.5) The platform layer reports the results to the next level software.

[0015] Example 3, as Figure 2 , 3 As shown.

[0016] The system's task startup and termination methods include the following procedures: (3.1) In standby mode, the platform layer receives external task execution instructions and related parameters, checks component dependencies according to the instructions, and sorts the components. (3.2) The platform layer commands the control layer to perform initialization operations on each component in the order of components, including loading, registration and confirmation of version number; after initialization, the control layer commands the corresponding components to start in the order of components, and commands the control layer to start the watchdog, and records the component start time. If an error occurs in the process, the platform layer returns the execution result error to the upper-level software, and the process ends. (3.3) During task execution, the control layer periodically detects the memory and computing resources occupied by the component, periodically checks the watchdog status, and if the watchdog is not reset, it reports the component error to the platform layer and restarts the watchdog; after the component starts, the watchdog status is reset periodically. (3.4) After receiving the task termination instruction, the platform layer commands the control layer to stop the running components in reverse order of component startup, and then unregisters the components and releases the resources occupied by the software during runtime. If all terminations are successful, the task termination success result is returned to the upper level software; otherwise, the task termination failure result is returned to the upper level software.

Claims

1. A system for on-orbit service reconfiguration, characterized in that, It includes the platform layer, the control layer, and the component layer; The platform layer is used to initiate a power-on self-test and report self-test data to higher-level software; it also receives external component update commands, forwards the commands to the control layer, receives the results returned by the control layer, and reports them to higher-level software; it receives task run or stop commands from external software, checks component dependencies, sends the decomposed run or stop commands to the control layer, and receives the results returned by the control layer and reports them to higher-level software; it receives component status information returned by the control layer during component runtime and reports it to higher-level software; and after startup, it obtains the system hardware status and software running status, reports them periodically or reports them after receiving query commands from higher-level software. The control layer is used to receive component update instructions from the platform layer, load the corresponding components from the component layer according to the instruction information, execute the component update process, and return the results to the platform layer; it is also used to receive component run or stop instructions, execute the component run or stop commands according to the instruction information, and return the results to the platform layer; it is also used to periodically monitor the running status of each business component in the component layer, check the component watchdog status, and start the watchdog, and return the component status information to the platform layer. The component layer is used by the controlled layer to load components from a specified location into memory. It is also used to start or stop execution and to reset the watchdog timer at regular intervals.

2. The system for on-orbit service reconfiguration according to claim 1, characterized in that, The system's component update method includes the following processes: (2.1) In standby mode, the platform layer receives update instructions and related parameters from external components and forwards the instructions and parameters to the control layer; (2.2) Back up old components in the control layer; (2.3) When the control layer completes the update according to the instructions and related parameters, it checks the component verification code. If the verification is correct, it loads and registers the component and calls the relevant test interface to perform the test. (2.4) If the test value is incorrect or the verification is incorrect, the corresponding component will be upgraded and rolled back, the update result will be logged, and the update failure will be reported to the platform layer; if the test value is correct and the verification is correct, the update verification will be successful, the component will be put into the database, the update result will be logged, and the update success will be reported to the platform layer. (2.5) The platform layer reports the results to the next level software.

3. A system for on-orbit service reconfiguration according to claim 1, characterized in that, The system's task startup and termination methods include the following procedures: (3.1) In standby mode, the platform layer receives external task execution instructions and related parameters, checks component dependencies according to the instructions, and sorts the components. (3.2) The platform layer commands the control layer to perform initialization operations on each component in the order of components, including loading, registration and confirmation of version number; after initialization, the control layer commands the corresponding components to start in the order of components, and commands the control layer to start the watchdog, and records the component start time. If an error occurs in the process, the platform layer returns the execution result error to the upper-level software, and the process ends. (3.3) During task execution, the control layer periodically detects the memory and computing resources occupied by the component, periodically checks the watchdog status, and if the watchdog is not reset, it reports the component error to the platform layer and restarts the watchdog; after the component starts, the watchdog status is reset periodically. (3.4) After receiving the task termination instruction, the platform layer commands the control layer to stop the running components in reverse order of component startup, and then unregisters the components to release the resources occupied by the software during runtime. If all terminations are successful, return a successful termination result to the parent software; otherwise, return a failed termination result to the parent software.

Images