Airborne software packaging management method and device
By separating and containerizing the source code of airborne software, the problem of tight coupling between airborne software and operating system is solved, enabling flexible software development and rapid deployment and upgrade capabilities.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- XIAN AIRCRAFT DESIGN INST OF AVIATION IND OF CHINA
- Filing Date
- 2025-12-31
- Publication Date
- 2026-04-28
AI Technical Summary
Airborne application software is tightly coupled with the operating system, making it difficult to achieve distributed deployment, combination and reuse. It lacks independent development and deployment capabilities and is difficult to support dynamic configuration and rapid maintenance and upgrades.
By separating functions at the source code level, extracting application source code, system source code, and driver source code, creating system management images and resource images, and generating container image configuration files and deployment view configuration files, unified scheduling and management of containers can be achieved.
It enables flexible reconfiguration and rapid deployment of airborne software, supports portability to different hardware environments, and provides a flexible software development model and rapid dynamic reconfiguration and version upgrade capabilities.
Smart Images
Figure CN121934854A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of airborne software technology, and specifically relates to an airborne software packaging and management method and apparatus. Background Technology
[0002] Conventional airborne application software is tightly coupled with the operating system, and there is no unified interface protocol to encapsulate different software functional units as services. Therefore, it is difficult to eliminate differences in hardware platforms, operating systems and programming languages, difficult to carry out distributed deployment, combination and reuse, difficult to enable airborne systems to have independent development and deployment capabilities, and difficult to support dynamic configuration, reconstruction, rapid maintenance and upgrades. Summary of the Invention
[0003] The purpose of this application is to provide an airborne software packaging management method and apparatus to solve or mitigate at least one of the problems in the prior art.
[0004] The technical solution of this application is: an airborne software packaging and management method and apparatus, comprising:
[0005] Step S10: Obtain the airborne software source code, separate the airborne software source code according to function, and extract the application source code, system-level source code, and driver source code required for containerization.
[0006] Step S20: Establish a system management image based on the extracted system-level source code, and establish a system resource image based on the target machine processor information, system-level source code, and driver source code;
[0007] Step S30: Construct a container application source file set based on the application source code, system management image, and system resource image;
[0008] Step S40: Create container image configuration files and container deployment view configuration files based on the container application source file set;
[0009] Step S50: Generate an application image based on the container image configuration file and an application package based on the container deployment view configuration file. Instantiate the application image to generate a container application and / or generate a container application through the application package. Deploy or run the container application to achieve unified scheduling and management of containers.
[0010] Preferably, the extracted application source code includes:
[0011] The application functions in the airborne software source code are separated to form the application function software source code. If the application function software source code also includes management functions, then these are separated to form the application management function software source code.
[0012] Separate the input / output functions from the airborne software source code that are not related to the operating system and hardware resources to form the input / output function software source code;
[0013] Based on the containerization encapsulation requirements, the source code of the organization application function software, input / output function software, and application management function software was rewritten to form the application source code.
[0014] Preferably, the extracted system-level source code includes:
[0015] The system-level scheduling management function was separated from the airborne software source code to form the system-level scheduling function software source code;
[0016] Separate the operating system-level input / output interface functions from the airborne software source code to form system-level input / output function software source code.
[0017] Preferably, the extracted driver source code is:
[0018] Separate the hardware drivers from the onboard software source code to form the driver function software source code.
[0019] Preferably, the process of building a system management image based on the extracted system-level source code is as follows:
[0020] 1) If the system-level scheduling function software source code uses a static scheduling table for time-sharing and partitioned scheduling with spatial and temporal isolation, then a static management container image is formed;
[0021] 2) If the system-level scheduling function software source code uses priority and task preemption scheduling algorithms, then a dynamically managed container image is formed.
[0022] Preferably, the process of establishing a system resource image based on the target machine processor information, system-level source code, and driver source code is as follows:
[0023] Based on the target machine processor information, system-level input / output function software source code, and driver function software source code, a target machine processor system resource image, a system-level input / output function system resource image, and a driver function system resource image are generated respectively.
[0024] Preferably, the container image configuration file consists of container operating system information, the runtime environment required for application operation, application installation and deployment scripts, and application start and stop commands;
[0025] The container deployment view configuration file consists of container image, replica set, resource allocation, port mapping, file mapping, real-time / non-real-time settings, application name, access policy, and storage policy.
[0026] In addition, this application also provides an airborne software packaging and management device, comprising:
[0027] The source code extraction module is used to obtain the airborne software source code, separate the airborne software source code according to function, and extract the application source code, system-level source code and driver source code required for containerization.
[0028] The image generation module is used to create a system management image based on the extracted system-level source code, and to create a system resource image based on the target machine processor information, system-level source code, and driver source code.
[0029] The container application source file set construction module is used to construct a container application source file set based on the application source code, system management image, and system resource image.
[0030] The configuration file generation module creates container image configuration files and container deployment view configuration files based on the container application source file set.
[0031] The application generation module generates application images based on container image configuration files and application packages based on container deployment view configuration files. It instantiates application images to generate container applications and / or generates container applications from application packages, deploys or runs container applications, and achieves unified scheduling and management of containers.
[0032] The airborne software packaging and management method of this application has the following advantages:
[0033] 1) When containerizing airborne software, this invention independently extracts application functions, input / output functions, and application management functions, effectively supporting the flexible reconfiguration of airborne software application functions. It also independently extracts system-level scheduling and management functions, system-level input / output functions, and hardware drivers, and independently encapsulates them as system management images and system resource images. This effectively decouples the dependencies between the application layer and the system layer, making the operation of airborne application software more flexible and enabling portability in different hardware resource environments.
[0034] 2) This invention establishes independent container image configuration files and container deployment view configuration files, which generate application images and application packages, providing two methods for instantiating, deploying, and running container applications, making the software development model more flexible.
[0035] 3) Based on the different scheduling and management methods of airborne software, this invention designs static management container images and dynamic management container images, and performs unified encapsulation and management of these two types of images, which satisfies the time-space isolation of the static scheduling table method and the integrated unified management of priority and task preemption scheduling.
[0036] 4) This invention designs a component repository at the system layer of the target machine. Container applications deployed and running at the application layer are generated by this repository through the instantiation of images and application packages, which strongly supports the rapid deployment and dynamic reconstruction of onboard software, as well as the flexible upgrade and rollback of software versions. Attached Figure Description
[0037] To more clearly illustrate the technical solutions provided in this application, the accompanying drawings will be briefly described below. Obviously, the drawings described below are merely some embodiments of this application.
[0038] Figure 1 This is a schematic diagram of the airborne software packaging and management method of this application.
[0039] Figure 2 This is a schematic diagram of the airborne software packaging process of this application.
[0040] Figure 3 This is a schematic diagram of the airborne software packaging and management device of this application. Detailed Implementation
[0041] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be described in more detail below with reference to the accompanying drawings.
[0042] To overcome the problems raised in the background introduction, this application provides an airborne software packaging and management method and apparatus, which extracts and containerizes airborne software according to its functions at the source code level to form container applications, facilitating unified scheduling, management, deployment and operation of such applications.
[0043] like Figure 1 As shown, the airborne software packaging management method of this application includes the following steps:
[0044] Step S10: Obtain the airborne software source code, separate the airborne software source code according to function, and extract the application source code, system-level source code, and driver source code required for containerization.
[0045] like Figure 2 As shown, the application source code extracted in this application includes:
[0046] 1) Separate the application functions from the airborne software source code to form the application function software source code (AP_FUNC);
[0047] If the application function software source code (AP_FUNC) also includes management function software, then it is separated to form the application management function software source code (AP_MNG).
[0048] 2) Separate the input / output functions in the airborne software source code that are not related to the operating system and hardware resources to form the input / output function software source code (AP_IO);
[0049] Based on containerization requirements, the source code of the organization application function software (AP_FUNC), input / output function software (AP_IO), and application management function software (AP_MNG) is rewritten to form the application source code (AP_SOURCE_CODE).
[0050] The system-level source code extracted in this application includes:
[0051] 3) Separate the system-level scheduling and management functions from the airborne software source code to form the system-level scheduling function software source code (SYS_MNG);
[0052] 4) Separate the operating system-level input / output interface functions from the airborne software source code to form the system-level input / output function software source code (SYS_IO).
[0053] The driver source code extracted in this application is:
[0054] 6) Separate the hardware drivers from the airborne software source code to form the driver function software source code (HW_DRV).
[0055] Step S20: Establish a system management image based on the extracted system-level source code, and establish a system resource image based on the target machine processor information, system-level source code, and driver source code.
[0056] The process of building a system management image based on the extracted system-level source code is as follows:
[0057] 1) If the system-level scheduling function software source code (SYS_MNG) uses a static scheduling table for time-sharing and partitioned scheduling with spatial and temporal isolation, then a static management container image (SMNG_IMAGE) is formed.
[0058] 2) If the system-level scheduling function software source code SYS_MNG uses a priority and task preemption scheduling algorithm, then a dynamically managed container image (DMNG_IMAGE) is formed.
[0059] The process of creating a system resource image based on the target machine processor information, system-level source code, and driver source code is as follows:
[0060] Based on the target machine processor information, the system-level input / output function software source code (SYS_IO), and the driver function software source code (HW_DRV), a target machine processor system resource image (CPU_IMAGE), a system-level input / output function system resource image (SYS_IO_IMAGE), and a driver function system resource image (HW_DRV_IMAGE) are generated respectively.
[0061] Step S30: Construct a container application source file set (AP_CONTAINER_FILE_SET) containing the application source code (AP_SOURCE_CODE), the statically managed container image (SMNG_IMAGE), the dynamically managed container image (DMNG_IMAGE), the target machine processor system resource image (CPU_IMAGE), the system-level input / output function system resource image (SYS_IO_IMAGE), and the driver function system resource image (HW_DRV_IMAGE).
[0062] Step S40: Based on the container application source file set (AP_CONTAINER_FILE_SET), create the container image configuration file (DKR_FILE) and the container deployment view configuration file (CHART_FILE).
[0063] The container image configuration file (DKR_FILE) consists of container operating system information, the runtime environment required for application operation, application installation and deployment scripts, and application start and stop commands.
[0064] The container deployment view configuration file (CHART_FILE) consists of container image, replica set, resource allocation, port mapping, file mapping, real-time / non-real-time settings, application name, access policy, and storage policy.
[0065] Step S50: Generate an application image (AP_IMAGE) based on the container image configuration file (DKR_FILE) and an application package (AP_PKG) based on the container deployment view configuration file (CHART_FILE). Instantiate the application image (AP_IMAGE) to generate a container application (AP_CONTAINER) and / or generate a container application (AP_CONTAINER) through the application package (AP_PKG). Deploy or run the container application (AP_CONTAINER) to achieve unified scheduling and management of containers.
[0066] The airborne software packaging and management method of this application has the following advantages:
[0067] 1) When containerizing airborne software, this invention independently extracts application functions, input / output functions, and application management functions, effectively supporting the flexible reconfiguration of airborne software application functions. It also independently extracts system-level scheduling and management functions, system-level input / output functions, and hardware drivers, and independently encapsulates them as system management images and system resource images. This effectively decouples the dependencies between the application layer and the system layer, making the operation of airborne application software more flexible and enabling portability in different hardware resource environments.
[0068] 2) This invention establishes independent container image configuration files and container deployment view configuration files, which generate application images and application packages, providing two methods for instantiating, deploying, and running container applications, making the software development model more flexible.
[0069] 3) Based on the different scheduling and management methods of airborne software, this invention designs static management container images and dynamic management container images, and performs unified encapsulation and management of these two types of images, which satisfies the time-space isolation of the static scheduling table method and the integrated unified management of priority and task preemption scheduling.
[0070] 4) This invention designs a component repository at the system layer of the target machine. Container applications deployed and running at the application layer are generated by this repository through the instantiation of images and application packages, which strongly supports the rapid deployment and dynamic reconstruction of onboard software, as well as the flexible upgrade and rollback of software versions.
[0071] Based on this, such as Figure 3 This application also provides an airborne software packaging and management device, the device 100 comprising:
[0072] The source code extraction module 101 is used to obtain the airborne software source code, separate the airborne software source code according to function, and extract the application source code, system-level source code and driver source code required for containerization.
[0073] The image generation module 102 is used to create a system management image based on the extracted system-level source code, and to create a system resource image based on the target machine processor information, system-level source code, and driver source code.
[0074] The container application source file set construction module 103 is used to construct a container application source file set based on the application source code, system management image, and system resource image.
[0075] The configuration file generation module 104 creates container image configuration files and container deployment view configuration files based on the container application source file set.
[0076] The application generation module 105 generates an application image based on the container image configuration file and an application package based on the container deployment view configuration file. It instantiates the application image to generate a container application and / or generates a container application through the application package, and deploys or runs the container application to achieve unified scheduling and management of containers.
[0077] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. An airborne software packaging and management method, characterized in that, include: Step S10: Obtain the airborne software source code, separate the airborne software source code according to function, and extract the application source code, system-level source code, and driver source code required for containerization. Step S20: Establish a system management image based on the extracted system-level source code, and establish a system resource image based on the target machine processor information, system-level source code, and driver source code; Step S30: Construct a container application source file set based on the application source code, system management image, and system resource image; Step S40: Create container image configuration files and container deployment view configuration files based on the container application source file set; Step S50: Generate an application image based on the container image configuration file and an application package based on the container deployment view configuration file. Instantiate the application image to generate a container application and / or generate a container application through the application package. Deploy or run the container application to achieve unified scheduling and management of containers.
2. The airborne software packaging management method as described in claim 1, characterized in that, The extracted application source code includes: The application functions in the airborne software source code are separated to form the application function software source code. If the application function software source code also includes management functions, then these are separated to form the application management function software source code. Separate the input / output functions from the airborne software source code that are not related to the operating system and hardware resources to form the input / output function software source code; Based on the containerization encapsulation requirements, the source code of the organization application function software, input / output function software, and application management function software was rewritten to form the application source code.
3. The airborne software packaging and management method as described in claim 2, characterized in that, The extracted system-level source code includes: The system-level scheduling management function was separated from the airborne software source code to form the system-level scheduling function software source code; Separate the operating system-level input / output interface functions from the airborne software source code to form system-level input / output function software source code.
4. The airborne software packaging and management method as described in claim 3, characterized in that, The extracted driver source code is: Separate the hardware drivers from the onboard software source code to form the driver function software source code.
5. The airborne software packaging and management method as described in claim 4, characterized in that, The process of building a system management image based on the extracted system-level source code is as follows: 1) If the system-level scheduling function software source code uses a static scheduling table for time-sharing and partitioned scheduling with spatial and temporal isolation, then a static management container image is formed; 2) If the system-level scheduling function software source code uses priority and task preemption scheduling algorithms, then a dynamically managed container image is formed.
6. The airborne software packaging and management method as described in claim 5, characterized in that, The process of creating a system resource image based on the target machine processor information, system-level source code, and driver source code is as follows: Based on the target machine processor information, system-level input / output function software source code, and driver function software source code, a target machine processor system resource image, a system-level input / output function system resource image, and a driver function system resource image are generated respectively.
7. The airborne software packaging and management method as described in claim 6, characterized in that, The container image configuration file consists of container operating system information, the runtime environment required for application operation, application installation and deployment scripts, and application start and stop commands. The container deployment view configuration file consists of container image, replica set, resource allocation, port mapping, file mapping, real-time / non-real-time settings, application name, access policy, and storage policy.
8. An airborne software packaging and management device, characterized in that, include: The source code extraction module is used to obtain the airborne software source code, separate the airborne software source code according to function, and extract the application source code, system-level source code and driver source code required for containerization. The image generation module is used to create a system management image based on the extracted system-level source code, and to create a system resource image based on the target machine processor information, system-level source code, and driver source code. The container application source file set construction module is used to construct a container application source file set based on the application source code, system management image, and system resource image. The configuration file generation module creates container image configuration files and container deployment view configuration files based on the container application source file set. The application generation module generates application images based on container image configuration files and application packages based on container deployment view configuration files. It instantiates application images to generate container applications and / or generates container applications from application packages, deploys or runs container applications, and achieves unified scheduling and management of containers.