Spacecraft payload system function reconstruction method, software architecture and hardware platform architecture

Abstract

The application discloses a kind of aerospace load system function reconfiguration method, software architecture and hardware platform architecture, wherein the method comprises: reconfiguration preparation: establish software and hardware resource model library and resource management system, and form virtual system based on several virtual components in software and hardware resource model library;Reconfiguration implementation: the process of task function work is established based on the reconfigurable configuration file of virtual system, including information collection and reconfiguration execution;Running monitoring: the running state of each device in aerospace load system is monitored online in real time, and running state condition is uploaded according to preset frequency;Dynamic reconfiguration: based on task change condition, software and hardware resources are scheduled again according to preset reconfiguration strategy, to realize the self-adapting reorganization of software and hardware resources.The application can solve the current situation of traditional one set of equipment one function, the system has reconfigurable, scalable, upgradeable capacity, can satisfy different load task application demand, realize one star multi-use, one star multi-ability.

Description

Technical Field

[0001] This invention relates to the field of software-defined radio technology, and in particular to a method for reconfiguring the functions of an aerospace payload system, its software architecture, and its hardware platform architecture. Background Technology

[0002] Traditional space payload systems are designed for specific missions, with fixed process algorithms and logic. Mission functions are tightly coupled with physical equipment, and the payload's functional performance is singular and specific, unable to achieve flexible configuration. Within its validity period, the payload system's software and hardware lack the ability to expand, upgrade, and grow, failing to meet different mission application requirements and adapt to ever-increasing differentiated needs. This necessitates the continuous launch of more advanced space payload systems to meet evolving application demands, significantly increasing development costs and time. Summary of the Invention

[0003] To address the aforementioned issues, this invention proposes a method for reconfiguring the functions of a space payload system, along with its software and hardware platform architecture. It employs an open hardware architecture based on "plug and play" and an open software architecture based on "software-defined radio." Through a plug-in-based software reloading method, the system payload functions are reconfigured and upgraded, forming an open, universal, and sustainably iteratively upgradeable integrated space electronic information experimental platform. This decouples mission functions from physical equipment, achieves multi-functionality of a single satellite through dynamic software reconfiguration, and supports continuous iterative upgrades of the entire payload system as technology advances to meet evolving application needs.

[0004] The technical solution adopted in this invention is as follows:

[0005] A method for reconfiguring the function of a space payload system, comprising:

[0006] Restructuring preparation: Establish a software and hardware resource model library and a resource management system, and form a virtual system based on several virtual components in the software and hardware resource model library;

[0007] Reconstruction Implementation: The process of establishing task functions based on the reconstructable configuration file of the virtual system, including information collection and reconstruction execution;

[0008] Operation monitoring: After the reconstruction is completed, the operation status of each device in the space payload system is monitored online in real time, and the operation status is uploaded at a preset frequency;

[0009] Dynamic reconfiguration: Based on changes in tasks, hardware and software resources are rescheduled according to a preset reconfiguration strategy to achieve adaptive reorganization of hardware and software resources.

[0010] Furthermore, the reconstruction preparation includes:

[0011] Application component development: Application components are generated using a unified development environment wizard, and interface code is automatically generated through an integration wizard to meet unified interface specification requirements. Different application components add business functions under a unified framework to form a functional component resource library.

[0012] Software component import: Manage the import of functional components, frameworks, and application software into the library;

[0013] Hardware resource abstraction: All information of actual hardware devices is collected into a hardware information database and managed and maintained in units of virtual hardware. The virtual hardware is a collection of all parameter attributes corresponding to the actual hardware devices.

[0014] Blueprint creation: Based on the application mode and hardware resources, establish software and hardware resource configuration relationships for different modes; after completing the construction of the resource configuration relationship topology, configure components for the selected hardware according to task requirements.

[0015] Furthermore, the hardware resource abstraction includes:

[0016] Collect hardware resource and software resource deployment diagrams and version information reported by various application processing software to form a hardware resource mapping diagram;

[0017] Hardware resource coding is performed on all system resources based on hardware information to establish a hardware view.

[0018] Furthermore, the refactoring execution in the refactoring implementation includes:

[0019] Based on the reconfigurable configuration file, the real hardware system is set to the preset working mode, the connection relationship is configured, and the hardware system platform is built.

[0020] According to the configuration file, the required functional software is deployed to the corresponding processing platform according to the deployment relationship, and then started to run.

[0021] Furthermore, the operational status monitoring includes:

[0022] Hardware resource status monitoring: Deploy reconstruction agent software in the hardware resources to collect hardware resource information and aggregate the information to the reconstruction management software; the reconstruction management software monitors the entire system resources and issues alarms when new hardware resources are added or when resources malfunction.

[0023] Software runtime status monitoring: During real-time operation, the operation of software resources is monitored to understand the resource load and detect anomalies.

[0024] Furthermore, the dynamic reconfiguration includes:

[0025] Work mode switching: Reselect the existing work mode and perform the aforementioned reconstruction.

[0026] Work mode adjustment: First, perform dynamic process design and dynamic software assembly, and then carry out the aforementioned reconstruction implementation.

[0027] Furthermore, the dynamic process design includes monitoring system hardware resources and execution status, formulating application software integration plans based on task changes, and forming blueprint files; the dynamic software assembly includes reading software resources, assembling, deploying and loading dynamic software, and storing the resulting blueprint files in a database.

[0028] A space payload system software architecture, comprising:

[0029] The application service layer is configured to implement various business functions of the aerospace payload system and support business function expansion; through service analysis, the target service is decomposed into a set of application objects combined in a preset order, and the application objects are configured to jointly complete the required service;

[0030] The application object layer is configured to perform application object services, including wireless modulated signal reception, signal detection and parameter estimation, and visual image decoding; each application object in the application object layer comprises one or more basic functional units.

[0031] The basic component service layer is configured to provide communication between application deployment to hardware platforms and components, track changes in aerospace payload systems, and shield differences between different hardware platforms.

[0032] The hardware platform layer is configured with a standard bus and programmable architecture, mapping the basic functional units of the application objects to a general-purpose hardware platform.

[0033] Furthermore, the dynamic deployment and reconfiguration of system software includes: based on the reconfigurable resource pool, adopting a service-oriented software architecture based on a software bus, and carrying out software integration development and application in the form of core framework + software bus + functional components.

[0034] A space payload system hardware platform architecture, comprising:

[0035] The integrated aperture module is configured to achieve multi-beam coverage and arbitrary shape beam generation, supporting simultaneous operation of multiple functions and multiple modes;

[0036] The integrated channel module is configured to amplify, switch, and transmit digital optical signals between the integrated aperture module, integrated processing module, and integrated application module, forming a core switching network.

[0037] The integrated processing and application module is configured to perform digital signal processing with multiple tasks by dynamically deploying different task function software components;

[0038] The integrated management and control module is configured to enable telemetry monitoring of the space payload system and management and scheduling of mission functions.

[0039] The beneficial effects of this invention are as follows:

[0040] The proposed aerospace payload system functional reconfiguration method, software architecture, and hardware platform architecture can solve the problem of the traditional single-function system. The system is reconfigurable, scalable, and upgradeable, meeting the application requirements of different payload missions and achieving multi-purpose and multi-functionality from a single satellite. By utilizing software-defined system functions, the software is plug-and-play, achieving the goals of improving system performance and reducing costs. Attached Figure Description

[0041] Figure 1 This is a flowchart of the aerospace payload system functional reconfiguration method according to Embodiment 1 of the present invention.

[0042] Figure 2 This is a schematic diagram of the open integrated payload hardware platform architecture of Embodiment 2 of the present invention.

[0043] Figure 3 This is a schematic diagram of the layered architecture of Embodiment 3 of the present invention.

[0044] Figure 4 This is a schematic diagram of the software refactoring architecture of Embodiment 3 of the present invention.

[0045] Figure 5 This is a schematic diagram of the system architecture of Embodiment 4 of the present invention.

[0046] Figure 6 This is a configuration diagram of the integrated processing and application hardware platform modules of Embodiment 4 of the present invention. Detailed Implementation

[0047] To provide a clearer understanding of the technical features, objectives, and effects of the present invention, specific embodiments are now described. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention; that is, the described embodiments are only a part of the embodiments of the invention, not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0048] Example 1

[0049] like Figure 1 As shown, this embodiment provides a method for reconfiguring the function of a space payload system, including the following steps:

[0050] Restructuring preparation: Establish a software and hardware resource model library and a resource management system, and form a virtual system based on several virtual components in the software and hardware resource model library;

[0051] Refactoring Implementation: The process of establishing task functions based on the refactorable configuration file of the virtual system, including information collection and refactoring execution;

[0052] Operation monitoring: After the reconstruction is completed, the operation status of each device in the space payload system is monitored online in real time, and the operation status is uploaded at a preset frequency;

[0053] Dynamic reconfiguration: Based on changes in tasks, hardware and software resources are rescheduled according to a preset reconfiguration strategy to achieve adaptive reorganization of hardware and software resources.

[0054] (1) Restructuring preparation

[0055] The resources prepared for refactoring include reconfigurable hardware and software resources. All resources are defined and described using standard models, and then installed as virtual components into the model library of the refactoring management software for unified management. The resource library is managed by establishing a resource management system, which includes component registration, information publishing, security management, and operation and maintenance. After establishing a hardware and software resource model library in the system resource library, a collection of available resources for the entire system is formed. These resources provide different functions, performance characteristics, and interfaces. Because a standard model is used, these resources can be combined and linked according to certain strategies to form a complete system and perform specific functions. The process of building a virtual system involves selecting appropriate components from the hardware and software resource model library (knowledge base) to form the virtual system.

[0056] Preferably, the reconstruction preparation includes the following steps:

[0057] Application component development: Application components are generated using a unified development environment wizard, and interface code is automatically generated through an integration wizard to meet unified interface specification requirements. Different application components add business functions under a unified framework to form a functional component resource library.

[0058] Software component import: Manage the import of functional components, frameworks, and application software into the library.

[0059] Hardware resource abstraction: All information of the actual hardware device is collected into the hardware information database and managed and maintained in units of virtual hardware. Virtual hardware is a collection of all parameters and attributes corresponding to the actual hardware device.

[0060] Blueprint creation: Based on the application mode and hardware resources, establish software and hardware resource configuration relationships for different modes; after completing the construction of the resource configuration relationship topology, configure components for the selected hardware according to task requirements.

[0061] More preferably, in hardware resource abstraction, the main hardware information that the system needs to maintain includes device type, device name, device number, peripheral interfaces, and hardware interconnection information between processors. Hardware management provides operations such as inputting, updating, and deleting this information at the virtual hardware level. Accurate hardware information can provide reliable data support for hardware-software mapping. A resource organization structure diagram is established by user-created resource information. During real-time operation, hardware resource and software resource deployment diagrams and version information reported by various application processing software can be collected to form a hardware resource mapping diagram. The refactoring management software establishes a hardware view by collecting hardware information. Based on the system composition, the hardware view encodes all system resources into hardware resources. System hardware resources include PowerPC processors, FPGA processors, AD converters, and DA converters.

[0062] (2) Restructuring Implementation

[0063] The refactoring implementation mainly includes two parts: information collection and refactoring execution. Preferably, the refactoring execution includes two aspects: first, setting the actual hardware system to a predetermined working mode according to the refactorable configuration file, configuring its connection relationships, and building the hardware system platform; second, deploying the required functional software to the corresponding processing platform according to the configuration file and starting its operation. After the above two steps, a complete system including hardware and software is established and can work normally.

[0064] (3) Operation status monitoring

[0065] Operational status monitoring involves online real-time monitoring of all devices in the system during normal operation after the refactoring operation is completed. This monitoring is achieved by health management software residing on each device reporting its operational status to the refactoring management software at regular intervals. This can identify potential problems in the system and guide the system to make adjustments and contingency plans in a timely manner.

[0066] Preferably, the operational status monitoring includes:

[0067] Hardware resource status monitoring: Deploy reconstruction agent software in hardware resources to collect hardware resource information and aggregate the information to reconstruction management software; the reconstruction management software monitors the entire system resources and issues alarms when new hardware resources are added or when resources malfunction.

[0068] Software operation status monitoring: During real-time operation, the system software resource operation status is monitored to understand the resource operation load and anomaly monitoring, so as to facilitate the reallocation of system resources.

[0069] (4) Dynamic Reconfiguration

[0070] Dynamic reconfiguration is a process in which the system re-schedules software and hardware resources and redesigns system processes based on changes in the task during task execution, according to certain reconfiguration strategies. This enables the system's software and hardware resources to "adaptively reorganize," allowing the system's capabilities to change with the task.

[0071] If an existing working mode is selected again, the task requirements can be fulfilled by directly and dynamically refactoring it; if a new mode needs to be designed dynamically, the main steps include:

[0072] Dynamic process design: Monitor system hardware resources and execution status, and formulate application software integration plans based on task changes, forming blueprint documents;

[0073] Dynamic software assembly: Read software resources, perform dynamic software assembly, realize software deployment and loading, and put the resulting blueprint files into the library.

[0074] Example 2

[0075] This embodiment is based on embodiment 1:

[0076] like Figure 2 As shown, this embodiment provides an open, integrated payload hardware platform architecture, including:

[0077] The integrated aperture module is configured to achieve multi-beam coverage and arbitrary shape beam generation, supporting simultaneous operation of multiple functions and multiple modes;

[0078] The integrated channel module is configured to amplify, switch, and transmit digital optical signals between the integrated aperture module, integrated processing module, and integrated application module, forming a core switching network.

[0079] The integrated processing and application module is configured to perform digital signal processing with multiple tasks by dynamically deploying different task function software components;

[0080] The integrated management and control module is configured to enable telemetry monitoring of the space payload system and management and scheduling of mission functions.

[0081] The open integrated payload hardware platform of this embodiment adopts a generalized, modular, and standardized design. Based on microsystem array technology, high-speed transmission and switching technology, and high-performance computing technology, it supports scalable design, with subsystems and modules that are plug-and-play. It supports on-orbit replacement, performance upgrades, and other requirements, forming an open, general-purpose, and continuously iteratively upgradeable aerospace electronic information integrated test platform.

[0082] Example 3

[0083] This embodiment is based on embodiment 2:

[0084] Based on the operating environment provided by the open integrated payload hardware platform in Embodiment 2, this embodiment proposes a software-defined function design concept. The software adopts a hierarchical structure and componentization technology, establishes a unified interface specification and development integration standard, and realizes dynamic configuration of hardware platform functions through software reconfiguration capabilities. Functional software is mapped and deployed to different hardware nodes of the hardware platform, and the logical relationship between integrated processing and application systems is re-established to form the system topology. The software reconfiguration enhances the flexibility and scalability of the payload system.

[0085] This system features an open hardware and software architecture, capable of adapting to various application services and upgraded software and hardware applications. The software employs a layered architecture, implementing control, management, and application at each layer of the system. The system's layered architecture, such as... Figure 3 As shown.

[0086] The software system architecture is divided into four layers: application service layer, application object layer, basic component service layer, and hardware platform layer. Each layer defines a unified structure and provides standard drivers or application programming interfaces to achieve interoperability.

[0087] (1) The application service layer first performs service analysis, decomposing specific services into a set of application objects (components) combined in a certain order. These objects can work together to complete the required service. The application service layer implements various business functions of the system and supports the expansion of business functions.

[0088] (2) The application object layer can be wireless modulation signal reception, signal detection and parameter estimation, visual image decoding, etc. Each application object can be composed of one or more basic functional units.

[0089] (3) The basic component service layer provides a consistent method for application deployment to hardware platforms and communication between components, and can track system changes while also shielding the differences between different hardware platforms.

[0090] (4) The hardware platform layer adopts a standard bus and programmable architecture. Each basic functional unit is mapped to a general-purpose hardware platform and its function is performed by the corresponding hardware unit, involving FPGA, DSP and GPP computing nodes.

[0091] The software system operates according to a layered structure, enabling communication between application objects through a unified interface. Communication between application objects and services is handled by middleware, which implements a software bus to support data transmission between various software components and modular design of functional components, functioning similarly to a computer system's hardware bus. Application components are created as software plug-ins according to the bus specification, allowing them to run simply by plugging them into the bus, achieving plug-and-play technology. Simultaneously, application components interoperate and communicate with each other through the middleware, unrestricted by operating systems or application programming languages, enhancing the flexibility of application services and ultimately enabling the automatic composition and dynamic deployment of software tasks.

[0092] Dynamic deployment and refactoring, based on a refactorable resource pool, employs a service-oriented software architecture grounded in a software bus, integrating, developing, and applying software in the form of a "core framework + software bus + functional components." System software refactoring architecture, such as... Figure 4 As shown.

[0093] Based on the system's application functions, the system software mainly comprises two layers of software libraries: the VxWorks platform and the FPGA / DSP platform. Different component libraries at different levels implement different functions such as resource scheduling, real-time processing, and analysis algorithms. Components are registered and incorporated into the software resource library for unified management. Different components are assembled according to the system application to achieve different application functions and resource scheduling. The core framework assembles components, while the refactoring management and refactoring agent software dynamically adds and unloads components. A software bus facilitates data interaction between components and software. Based on the system resource allocation principles, different application software is formed through the assembly and execution of different components and incorporated into the library. By loading these application software, the system's functions are refactored, resulting in a comprehensive processing system with diverse functionalities.

[0094] Software refactoring primarily involves the refactoring of FPGA, DSP platform software, and RxWorks platform software. For the FPGA software platform, pre-installed software versions with different operating modes are used, and different FPGA functional software is loaded according to different task requirements to achieve software refactoring and meet diverse functional needs. The embedded software refactoring function of the DSP platform is more flexible and can be implemented using a layered structure.

[0095] The process of implementing functional reconfigurability is divided into four stages: reconfiguration preparation, reconfiguration implementation, operation monitoring, and dynamic reconfiguration. For specific implementation process, refer to the aerospace payload system functional reconfiguration method in Example 1.

[0096] Example 4

[0097] This embodiment is based on embodiment 3:

[0098] This embodiment adopts an open and reconfigurable architecture, and the specific implementation of the system architecture is as follows: Figure 5 As shown. The application service layer is the application component layer of the waveform, which implements various business functions of the system and supports the expansion of business functions. The basic component service layer includes basic framework services, embedded operating system, drivers, and board support packages. The hardware platform layer provides computing nodes such as FPGA, DSP, GPP, and CPU, and standard buses include Ethernet bus, CAN bus, RS422 bus, SRIO bus, and LVDS bus, providing standard interface communication capabilities for the system.

[0099] An open, reconfigurable architecture achieves multiple functional tasks through software reconfiguration on a single integrated hardware platform. The hardware processing and application hardware platform are modularly designed, enabling plug-and-play capabilities for both hardware and software. The system also features on-orbit hardware and software upgrade capabilities, with configurations such as... Figure 6 As shown, it includes 10 general signal processing modules of type I, 6 general signal processing modules of type II, 8 general signal processing modules, 2 switching modules, 1 IO module, 1 system control module, 1 system time control module, 2 wavelength division multiplexing / demultiplexing modules, and 2 power supply modules.

[0100] The Type I general-purpose signal processing module consists of two XC7VX690T FPGAs and one DSP6678, with the DSP6678 externally connected to a 64-bit 512MB DDR3 memory. Each chip is simultaneously connected to a primary / backup RapidIO network via a switching chip. The FPGA's GTH high-speed interface provides a high-speed digital fiber optic interface via an opto-optical-to-electrical conversion daughter card. The two FPGAs exchange data via two 6X 7.5Gbps GTH high-speed serial buses and 80 pairs of LVDS buses, providing data transmission capabilities of greater than 80Gbps and 20Gbps respectively. The FPGA and DSP chip are connected via a Link link.

[0101] The general-purpose signal processing module consists of four DSP6678 chips, each connected to a primary / backup RapidIO network via a switching chip, with both primary and backup networks operating on a 1-way 4X configuration. Each DSP6678 is paired with an external 8GB 64-bit DDR3 memory module.

[0102] Based on the system task requirements, analyze the resources of each processing stage of the system, and explain the dynamic reconfiguration deployment under two typical working conditions.

[0103] Operating Condition 1: Function 1 calls array 1. In this condition, the integrated processing and application subsystem receives multiple AD signals from array 1. Among them, 6 Type I FPGA modules complete signal preprocessing, 5 Type II FPGA modules complete signal processing, 2 Type I FPGA modules and 1 Type II FPGA module complete information fusion, the DSP module completes information processing, and the CPU and FPGA modules complete the implementation of Function 1.

[0104] Operating Condition 2: Function 2 calls array 2. In this condition, the integrated processing and application subsystem receives the AD signal from array 2. Four Type I FPGA modules complete signal preprocessing, five Type II FPGA modules complete digital beamforming, two Type I FPGA modules and one Type II FPGA module complete information fusion, the DSP module completes parameter measurement, and the CPU and FPGA modules implement Function 2.

[0105] Relying on a reconfigurable integrated processing and application hardware platform, the processing platform software version is reconfigured based on onboard blueprint files or ground-based injection, achieving multi-functional application goals and realizing multiple uses and capabilities for a single satellite. Based on the object information injected from the ground, the onboard knowledge base is updated. The system architecture can quickly load algorithms based on relevant algorithms and prior knowledge injected from the ground, thereby improving capabilities. In this embodiment, the system reconfiguration time is less than 30 seconds, and the reconfiguration success rate can reach 99.00%.

[0106] It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

Claims

1. A method for reconfiguring a function of a space payload system, characterized by, include: Restructuring preparation: Establish a software and hardware resource model library and a resource management system, and form a virtual system based on several virtual components in the software and hardware resource model library; Reconstruction Implementation: The process of establishing task functions based on the reconstructable configuration file of the virtual system, including information collection and reconstruction execution; Operation monitoring: After the reconstruction is completed, the operation status of each device in the space payload system is monitored online in real time, and the operation status is uploaded at a preset frequency; Dynamic reconfiguration: Based on changes in tasks, hardware and software resources are rescheduled according to a preset reconfiguration strategy to achieve adaptive reorganization of hardware and software resources; The reconstruction preparation includes: Application component development: Application components are generated using a unified development environment wizard, and interface code is automatically generated through an integration wizard to meet unified interface specification requirements. Different application components add business functions under a unified framework to form a functional component resource library. Software component import: Manage the import of functional components, frameworks, and application software into the library; Hardware resource abstraction: All information of actual hardware devices is collected into a hardware information database and managed and maintained in units of virtual hardware. The virtual hardware is a collection of all parameter attributes corresponding to the actual hardware devices. Blueprint creation: Based on the application mode and hardware resources, establish software and hardware resource configuration relationships for different modes; after completing the construction of the resource configuration relationship topology, configure components for the selected hardware according to task requirements; The hardware resource abstraction includes: Collect hardware resource and software resource deployment diagrams and version information reported by various application processing software to form a hardware resource mapping diagram; Hardware resource coding is performed on all system resources based on hardware information to establish a hardware view.

2. The space payload system functional reconfiguration method of claim 1, wherein, The refactoring execution in the refactoring implementation includes: Based on the reconfigurable configuration file, the real hardware system is set to the preset working mode, the connection relationship is configured, and the hardware system platform is built. According to the configuration file, the required functional software is deployed to the corresponding processing platform according to the deployment relationship, and then started to run.

3. The space payload system functional reconfiguration method of claim 1, wherein, The operational status monitoring includes: Hardware resource status monitoring: Deploy reconstruction agent software in the hardware resources to collect hardware resource information and aggregate the information to the reconstruction management software; the reconstruction management software monitors the entire system resources and issues alarms when new hardware resources are added or when resources malfunction. Software runtime status monitoring: During real-time operation, the operation of software resources is monitored to understand the resource load and detect anomalies.

4. The space payload system functional reconfiguration method of claim 1, wherein, The dynamic reconfiguration includes: Work mode switching: Reselect the existing work mode and perform the aforementioned reconstruction. Work mode adjustment: First, perform dynamic process design and dynamic software assembly, and then carry out the aforementioned reconstruction implementation.

5. The space payload system functional reconfiguration method of claim 4, wherein, The dynamic process design includes monitoring system hardware resources and execution status, formulating application software integration plans based on task changes, and forming blueprint files; the dynamic software assembly includes reading software resources, assembling, deploying and loading dynamic software, and storing the resulting blueprint files in a database.

6. A space payload system, which applies the space payload system function reconfiguration method according to any one of claims 1 to 5, characterized by, include: The application service layer is configured to implement various business functions of the aerospace payload system and support the expansion of business functions; The target service is decomposed into a set of application objects combined in a preset order through service analysis. The application objects are configured to jointly complete the required service. The application object layer is configured to perform application object services, including wireless modulated signal reception, signal detection and parameter estimation, and visual image decoding; each application object in the application object layer comprises one or more basic functional units. The basic component service layer is configured to provide communication between application deployment to hardware platforms and components, track changes in aerospace payload systems, and shield differences between different hardware platforms. The hardware platform layer is configured with a standard bus and programmable architecture, mapping the basic functional units of the application objects to a general-purpose hardware platform.

7. The space payload system according to claim 6, characterized in that, Dynamic deployment and reconfiguration of system software includes: based on a reconfigurable resource pool, adopting a service-oriented software architecture based on a software bus, and integrating and developing software in the form of a core framework + software bus + functional components.

8. A space payload system, employing the space payload system functional reconfiguration method according to any one of claims 1-5, characterized in that, include: The integrated aperture module is configured to achieve multi-beam coverage and arbitrary shape beam generation, supporting simultaneous operation of multiple functions and multiple modes; The integrated channel module is configured to amplify, switch, and transmit digital optical signals between the integrated aperture module, integrated processing module, and integrated application module, forming a core switching network. The integrated processing and application module is configured to perform digital signal processing with multiple tasks by dynamically deploying different task function software components; The integrated management and control module is configured to enable telemetry monitoring of the space payload system and management and scheduling of mission functions.

Images