A method for loading backup of platform data in an integrated processing platform

Abstract

The application provides a method for processing platform data loading backup, and belongs to the technical field of airborne embedded integrated modular architecture, and specifically comprises the following steps: classifying module data loading file types; defining software data loading files which have important influence on hardware operation as first-type files, and storing the first-type files in a module local FLASH for backup; defining software data loading files which have no influence on hardware operation as second-type files, and storing the backup of the second-type files in a large-capacity storage; and when a FLASH writing operation fault occurs in the second-type files, using the second-type file data stored in the large-capacity storage to perform FLASH recovery. Through the processing scheme, the integrated processing platform data loading efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of airborne embedded integrated modular architecture, and in particular to a method for loading and backing up data on an integrated processing platform. Background Technology

[0002] The integrated processing platform based on IMA provides shared computing resources for multiple aircraft functions, supporting the hosting of multiple aircraft function applications. Therefore, online upgrades involve a wide variety of file types and a large number of files, making the processing complex. Online data loading involves multiple devices being upgraded simultaneously, but asynchronous upgrade steps lead to errors in locally stored data, and there is a lack of monitoring interfaces. Summary of the Invention

[0003] In view of this, this application provides a method for data loading and backup of an integrated processing platform, which solves the problems of a large number of data loading modules, a variety of file types, many on-device devices, and asynchronous data loading that is prone to human error. It provides data backup support for multiple upgrade operations and backup recovery support for loading anomalies, thereby improving the data loading efficiency of the integrated processing platform.

[0004] The method for loading and backing up data on a comprehensive processing platform provided in this application adopts the following technical solution:

[0005] A method for loading and backing up data on a comprehensive processing platform includes the following steps:

[0006] Classify module data loading file types: Software data loading files that have a significant impact on hardware operation are defined as Class I files, and Class I files are stored in the module's local FLASH memory as backups. Software data loading files that have no impact on hardware operation are defined as Class II files, and backups of Class II files are stored in a large-capacity storage device.

[0007] If a FLASH write operation failure occurs in the second type of file, the data of the second type of file stored in a large-capacity memory is used for FLASH recovery.

[0008] Optionally, the first type of files includes bootloaders, core driver software, operating systems, and loading software.

[0009] Optionally, the second type of files includes resident applications and configuration files.

[0010] Optionally, backups of the second type of files are stored on a large-capacity electronic disk storage device: the received data is loaded onto the electronic disk, and after the data is received, it is written to the FLASH. If the FLASH write operation fails, the file data stored on the electronic disk is used for FLASH recovery.

[0011] Optionally, the data loading and backup process includes: saving all received loadable data files to an electronic disk as a backup of the loaded data, and then performing corresponding operations on all data files, backing up the first type of files in the module to the FLASH using the module's local FLASH storage backup method.

[0012] Optionally, during the loading process of the second type of file data, it is synchronously loaded into the data management center of the integrated processing platform as a data backup. When the FLASH write operation fails, the backup file is loaded through the data management center of the integrated processing platform via the distributed file system to restore the FLASH.

[0013] Optionally, the data loading backup includes the following steps:

[0014] All received loadable data files are first saved to the local file system;

[0015] The received file is sent to the data management center of the integrated processing platform as a backup of the loaded data and saved there.

[0016] Read data files received from the local file system and perform corresponding operations;

[0017] The first type of files in the module are backed up to the FLASH memory using the module's local FLASH storage backup method.

[0018] In summary, this application includes the following beneficial technical effects:

[0019] This application addresses the challenges of a large number of data loading modules and file types on an integrated processing platform, as well as the numerous onboard devices and the potential for data loading to be asynchronous and subject to human error. It proposes a categorized data backup mechanism that provides data backup support for multiple upgrade operations and backup recovery support for loading anomalies, thereby improving the data loading efficiency of the integrated processing platform. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 Flowchart for loading backup data for this application. Detailed Implementation

[0022] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0023] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. This application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, in the absence of conflict, the following embodiments and features in the embodiments can be combined with each other. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0024] It should be noted that various aspects of embodiments within the scope of the appended claims are described below. It will be apparent that the aspects described herein can be embodied in a wide variety of forms, and any particular structure and / or function described herein is merely illustrative. Based on this application, those skilled in the art will understand that one aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement the device and / or practice the method. Additionally, this device and / or method can be implemented using structures and / or functionalities other than one or more of the aspects set forth herein.

[0025] It should also be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. The drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0026] Furthermore, specific details are provided in the following description to facilitate a thorough understanding of the examples. However, those skilled in the art will understand that the described aspects can be practiced without these specific details.

[0027] This application provides a method for loading and backing up data on a comprehensive processing platform.

[0028] A method for loading and backing up data on a comprehensive processing platform includes the following steps:

[0029] Classify module data loading files by type: Software data loading files that have a significant impact on hardware operation are defined as Class I files, and Class I files are stored in the module's local FLASH memory as backups. Software data loading files that have no impact on hardware operation are defined as Class II files, and backups of Class II files are stored in a large-capacity storage device.

[0030] If a FLASH write operation failure occurs in the second type of file, the data of the second type of file stored in a large-capacity memory is used for FLASH recovery.

[0031] The first type of file includes programs such as bootloaders, core driver software, operating systems, and loading software.

[0032] The second type of files includes resident applications and configuration files, among other files.

[0033] The first type of file uses local FLASH storage backup in the module for data recovery in case of abnormal situations.

[0034] The second type of file backup is carried out separately according to the device module storage design:

[0035] In one embodiment, the device has a large-capacity electronic disk storage:

[0036] The second type of file backup is stored on a large-capacity electronic disk storage device: the received data is loaded onto the electronic disk, and after the data is received, it is written to the FLASH. If the FLASH write operation fails, the file data stored on the electronic disk is used to restore the FLASH.

[0037] like Figure 1 As shown, the data loading and backup process includes: saving all received loadable data files to an electronic disk as a backup of the loaded data; performing corresponding operations on all data files, such as writing to FLASH and changing directories; and backing up the first type of files in the module to FLASH using the module's local FLASH storage backup method.

[0038] In one embodiment, the device does not have a large-capacity electronic disk storage.

[0039] During the loading process of the second type of file data, it is synchronously loaded into the data management center of the integrated processing platform as a data backup. When the FLASH write operation fails, the backup file is loaded through the data management center of the integrated processing platform via the distributed file system to restore the FLASH.

[0040] The data loading and backup process includes the following steps:

[0041] All received loadable data files are first saved to the local file system;

[0042] The received file is sent to the data management center of the integrated processing platform as a backup of the loaded data and saved there.

[0043] Read data files received from the local file system and perform corresponding operations, such as writing to FLASH and changing directories;

[0044] The first type of files in the module are backed up to the FLASH memory using the module's local FLASH storage backup method.

[0045] This application addresses the challenges of a large number of data loading modules and file types on an integrated processing platform, as well as the numerous onboard devices and the potential for data loading to be asynchronous and subject to human error. It proposes a categorized data backup mechanism that provides data backup support for multiple upgrade operations and backup recovery support for loading anomalies, thereby improving the data loading efficiency of the integrated processing platform.

[0046] In one embodiment, a method for loading and backing up data on a comprehensive processing platform is provided.

[0047] The integrated processing platform based on IMA provides common computing resources for multiple aircraft functions, and consists of various functional modules of different types:

[0048] General Processing Module (CPM): Provides general processing resources, but does not have a large-capacity electronic disk storage design;

[0049] General Purpose I / O Module (GPIO): Provides general purpose I / O processing resources and features a large-capacity electronic disk storage design.

[0050] Large Capacity Storage Module (MMM): Provides ultra-large capacity storage resources. The module has an electronic disk large capacity storage design and serves as the data management center of the integrated processing platform, backing up and saving the data loaded by all modules.

[0051] Signal Processing Module (SPM): Provides general signal processing resources, but does not have a large-capacity electronic disk storage design.

[0052] Image Processing Module (GPM): Provides general image processing resources, but does not have a large-capacity electronic disk storage design.

[0053] The data loading process for the CPM module is as follows:

[0054] Step 1: CPM saves the received loadable data file to the local file system.

[0055] Step 2: CPM sends the received file to the integrated processing platform data management center through the network file system, performs data backup, and saves it to the integrated processing platform data management center;

[0056] Step 3: CPM reads the received data files from the local file system and performs corresponding operations, such as writing to FLASH and changing directories.

[0057] Step 4: CPM backs up the module bootloader, operating system, and data loading function to the FLASH memory using the module's local FLASH storage backup method.

[0058] The data loading and backup process for SPM and GPM is the same as that for CPM.

[0059] The GPIO module data loading process is as follows:

[0060] Step 1: GPIO saves the received loadable data file to the module's electronic disk mass storage for data backup.

[0061] Step 2: GPIO performs corresponding operations on the received data file, such as writing to FLASH or changing the directory.

[0062] Step 3: GPIO backs up the module bootloader, operating system, and data loading function to the FLASH memory using the module's local FLASH storage backup method.

[0063] The MMM data loading and backup process is the same as GPIO.

[0064] 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. A method for loading and backing up data on a comprehensive processing platform, characterized in that, Includes the following steps: Classify module data loading file types: Software data loading files that have a significant impact on hardware operation are defined as Class I files, and Class I files are stored in the module's local FLASH memory as backups. Software data loading files that have no impact on hardware operation are defined as Class II files, and backups of Class II files are stored in a large-capacity storage device. If a FLASH write operation failure occurs in the second type of file, the data of the second type of file stored in a large-capacity memory is used for FLASH recovery. The first type of file includes bootloaders, core driver software, operating systems, and loading software; The backup of the second type of file is stored on a large-capacity electronic disk storage device: the received data is loaded and saved on the electronic disk. After the data is received, it is written to the FLASH. If the FLASH write operation fails, the file data stored on the electronic disk is used to restore the FLASH. During the loading process of the second type of file data, it is synchronously loaded into the data management center of the integrated processing platform as a data backup. When the FLASH write operation fails, the backup file is loaded through the data management center of the integrated processing platform via the distributed file system to restore the FLASH.

2. The method for loading and backing up data on a comprehensive processing platform according to claim 1, characterized in that, The second type of file includes resident applications and configuration files.

3. The method for loading and backing up data on a comprehensive processing platform according to claim 1, characterized in that, The data loading and backup process includes: saving all received loadable data files to an electronic disk as a backup of the loaded data; then performing corresponding operations on all data files; and backing up the first type of files in the module to the FLASH memory using the module's local FLASH storage backup method.

4. The method for loading and backing up data on a comprehensive processing platform according to claim 1, characterized in that, The data loading and backup process includes the following steps: All received loadable data files are first saved to the local file system; The received file is sent to the data management center of the integrated processing platform as a backup of the loaded data and saved there. Read data files received from the local file system and perform corresponding operations; The first type of files in the module are backed up to the FLASH memory using the module's local FLASH storage backup method.

Images