Data packaging method based on avionics core processing platform

Abstract

The data packaging method based on the avionics core processing platform of the present invention classifies and packages the data to be loaded according to certain data format requirements, thereby improving the efficiency of software maintenance, loading and management and enhancing the safety of avionics equipment. First, different loadable software aircraft parts are formed according to whether each software item is related to the device location. Secondly, multiple raw data with dependencies are packaged or combined into a separate binary configuration file or database, and a specific operation configuration table in a specific loadable software aircraft part is generated for the avionics core processing platform; then, a loadable item header is added to all executable files or configuration files to be loaded through a data file generation tool to generate a loadable item; then, a support file is generated for all loadable items through a support file generation tool, so that the information contained in the loadable software aircraft part is conveniently processed uniformly during the loading process, and the performance is high.

Description

Technical Field

[0001] The present invention belongs to the technical field of data loadable for avionics equipment, and in particular relates to a data packaging method based on an avionics core processing platform. Background Art

[0002] As a highly centralized processing system used in a wide variety of passenger aircraft, the avionics core processing platform (ACP) is increasingly recognized for its high reliability, high security, and ease of maintenance. Numerous data items reside on the avionics devices within the ACP, including platform-level software operating systems, resident applications, configuration data, and databases. With the widespread adoption of ACPs, the number of data items residing on them is increasing. The lack of effective data packaging methods and tools has led to inconvenience in loading and maintenance operations, resulting in reduced onboard data transmission efficiency. Summary of the Invention

[0003] In view of this, the data packaging method based on the avionics core processing platform of the present invention packages the data to be loaded according to certain data format requirements, which is used to solve the problem of chaotic data item configuration of avionics equipment, improve the efficiency of software maintenance, management and loading, and enhance the safety of avionics equipment.

[0004] A method for data packaging based on an avionics core processing platform is suitable for loading data of an airborne avionics system, wherein the avionics system runs multiple types of software and is provided with multiple avionics devices. The method comprises:

[0005] Step 1: Classify software-loadable aircraft parts to form multiple software sets. Each software set is split based on whether it is related to the location of the avionics equipment. Multiple data sets applicable to the avionics equipment are generated by default. Each data set serves as a software-loadable aircraft part. The data sets include a first data set, multiple second data sets, and a third data set. The data sets serve as input to a tool set. The tool set is used to package the data loaded by the avionics equipment and write data rules into each data set:

[0006] Step 2: executing a data integration tool process, wherein all the second data sets are used to generate a specific operation configuration table through the data integration tool, and the data integration tool is used to connect the operating system configuration, end system configuration, storage configuration, and file system configuration provided by the user and applicable to the specified avionics device into a binary file;

[0007] Step 3: executing a data file generation tool process, wherein a plurality of software in a data package is encapsulated;

[0008] Step 4: Execute the support file generation tool process to describe the packaged data packet and form a description file in a predetermined format;

[0009] Step 5: Execute the header file generation tool, wherein the support file description file executes the header file generation tool to generate a header file, which is used for a quick or brief description of the data included in the data set during the avionics equipment data loading process, and for determining a quick judgment of the content loaded by the avionics equipment.

[0010] First, the present invention forms different loadable software aircraft parts according to whether each software item is related to the device location, namely general loadable software aircraft parts, specific loadable software aircraft parts and configuration list loadable software aircraft parts.

[0011] Common loadable software aircraft components: Contains software and minimum configuration data common to all locations to support avionics equipment in various locations. Even if the location of the equipment changes, the software on it will continue to operate normally.

[0012] Specific loadable software aircraft parts: Contains only software items for specific avionics equipment, including the equipment's partition loading mapping table and specific operation configuration table;

[0013] Configuration List (CLS): This list contains configuration items for all avionics equipment in the avionics core processing platform. This list defines configuration items by listing all common CLS and individual CLS components, along with their part numbers, for use in configuration checks.

[0014] Secondly, loadable software aircraft parts are generated by executing the following tools, including:

[0015] (1) Data integration tools

[0016] The purpose of the data integration tool is to combine multiple separate binary files into a single loadable configuration or database file that can be accessed by the avionics core processing platform as a single entity. The tool uses the specific operational configuration tables within a specific loadable software aircraft component as an example. These specific operational configuration tables are the operating system configuration, end system configuration, storage configuration, and file system configuration. These configuration binaries are tightly coupled: the arinc653 port defined in the operating system configuration must match the COM port in the end system configuration, and the partitions defined in the operating system configuration must match the partitions in the specified storage and file system configurations. The tool concatenates these dependent binary files into a single file.

[0017] (2) Data File Generation Tool: This tool generates and verifies loadable items for avionics devices on the avionics core processing platform by adding a LIH to the original binary file. The LIH includes loadable item attributes, software and hardware information, binary file size, and CRC. When the loadable item is loaded, the LIH is stored in the avionics device and used to generate configuration reports.

[0018] (3) Support file generation tools

[0019] Part of the information in the support file is in the header file and part is in the data file. The data file generation tool concentrates this data in one file so that the avionics equipment can process the information uniformly when loading data, such as compatibility verification.

[0020] (4) Header file generation tool

[0021] The header file is used by the avionics core processing platform to confirm the data files and supporting files to be loaded during the data loading process.

[0022] The technical beneficial effects of the present invention are:

[0023] By determining whether the data items in the avionics equipment are related to the equipment location, general loadable software aircraft parts, specific loadable software aircraft parts and configuration list loadable software aircraft parts are formed, which can effectively improve the efficiency of configuration management. The data integration tool combines a set of interdependent binary configuration files or databases into a single file to reduce the number of loadable items, thereby reducing the number of compatibility checks. Secondly, in order to align the memory with the sector boundary, the size of all loadable items must be rounded to the sector with the closest size. Each loadable item stored has a large amount of memory waste. By merging files, the storage efficiency of the avionics equipment can be improved. The loadable item header generated by the data file generation tool is used by the avionics core processing platform to identify the information of the current loadable item and generate a configuration report. When a new loadable software aircraft part needs to be created, its LIH can be used to directly create a new support file. The support file generation tool and the header file generation tool provide compatibility verification support for the avionics core processing platform when loading data, thereby improving the security of the avionics equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0025] Figure 1 This is the overall architecture diagram of the toolset;

[0026] Figure 2 A classification diagram of aircraft parts that can be loaded with software;

[0027] Figure 3 To support file format diagram;

[0028] Figure 4 This is the header file format diagram. DETAILED DESCRIPTION

[0029] The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0030] The following describes the embodiments of the present disclosure through specific examples, and those skilled in the art can easily understand other advantages and effects of the present disclosure from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments. The present disclosure can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present disclosure. 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 the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.

[0031] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein can be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on this disclosure, it should be understood by those skilled in the art that an 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 described herein can be used to implement an apparatus and / or practice a method. In addition, other structures and / or functionalities other than one or more of the aspects described herein can be used to implement this apparatus and / or practice this method.

[0032] like Figures 1 to 4 The data packaging method based on the avionics core processing platform is suitable for loading data of an airborne avionics system that runs multiple types of software and is equipped with multiple avionics devices. The method includes:

[0033] Step 1: Classify the "loadable software aircraft parts" to form multiple software sets, split each software according to whether it is related to the location of the avionics equipment, and preset multiple data sets applicable to the avionics equipment, each data set as a "loadable software aircraft part"; the data sets include a first data set, multiple second data sets and a third data set. The data sets serve as inputs to the tool set, which is used to package the data loaded by the avionics equipment and put data rules into each data set. Specifically,

[0034] Step 1.1: Store the software applicable to the universal position of all avionics equipment in the first data set. That is, any software in the first data set is loaded by the avionics equipment of the universal position;

[0035] Step 1.2: Each avionics device corresponds to a device loading mapping table and a specific operation configuration table. According to the names of the device loading mapping table and the specific operation configuration table (the name includes the location and name of the corresponding avionics device), the device loading mapping table and the specific operation configuration table are stored in a second data set that matches the name. (A name is pre-assigned to the second data set. If the names of the two tables are the same, the name is stored.)

[0036] Step 1.3: The third data set is used to count and store the names of the first data set and all second data sets to form a configuration list. That is, the configuration list in the third data set stores all names; the configuration list is applicable to the loading of all avionics equipment.

[0037] By classifying all software that can be loaded into avionics equipment, the number of times the software is loaded can be reduced by merging the software, thereby improving the efficiency of the use of avionics equipment.

[0038] Step 2: Execute the data integration tool process, wherein all second data sets are used to generate a specific operation configuration table through the data integration tool. The data integration tool is used to connect the operating system configuration, end system configuration, storage configuration, and file system configuration provided by the user and applicable to the specified avionics equipment into a binary file, such as by traversing the operating system configuration, end system configuration, storage configuration, and file system configuration to generate a binary file. Preferably,

[0039] The binary file is parsed to determine whether the various parts of the binary file connection are correct. The binary file generated by parsing calculates the correctness of the CRC values ​​of the operating system configuration, end system configuration, storage configuration and file system configuration. If correct, a data integration tool result report is generated. If incorrect, the tool will report an error message and the user will re-enter the information.

[0040] Step 3: Execute the data file generation tool process to encapsulate several software in a data package. Specifically,

[0041] Step 3.1 The data set obtains the "data file description file" through human-computer interaction. The format of the "data file description file" is XML and includes a main node corresponding to the XML format. The main node includes the LoadItem loadable item. The attributes of the main node are the name, ID, part number and type of the loadable item; the sub-node SW software information. The attributes of this sub-node include the software version information; the sub-node HW hardware information. The attributes of this sub-node include the cabinet number, version, cabinet location and module location of the target avionics equipment to load the data file; the sub-node DataFile binary file. The attributes of this sub-node include href, which is a variable link to the storage location of the binary file;

[0042] Step 3.2: The binary file and description file serve as input to the data file generation tool. The data file is generated by the data file generation tool. The data file is used to load data for all avionics equipment. The data file generation tool parses the data file description file to obtain the software's loadable item attributes and hardware and software information, as well as the binary file size and CRC value. These are then added to the 1024 bytes of the binary file header. The 1024 bytes of the binary file header serve as the loadable item header data (LIH). The loadable item header data (LIH) is used by the avionics equipment to quickly identify the loadable item.

[0043] Furthermore, verification is required, such as parsing all attributes in the XML description file in step 3 and comparing them with all attributes in the generated LIH. If correct, a verification report is generated, including whether each attribute is verified successfully. If incorrect, the tool will report an error message and the user will re-enter the information.

[0044] Step 4: Execute the support file generation tool process to describe the packaged data package and form a description file in a predetermined format. All "data file description files" serve as inputs to the support file generation tool. The support file generation tool is used to generate support files. The format of the support files is XML. The specific content of the XML format includes the main node SupportFile support file. The attributes of the main node are the name, ID and part number of the aircraft parts that can be loaded with the software this time, as well as the name, ID and part number of the support file itself; the child node include, the attributes of the child node include href, which links the description file of the data file as a variable to the storage location of the data file description file. If there are multiple data files in this loading, multiple corresponding child nodes are introduced. For example, the binary support file format generated by parsing the description file of the support file and traversing the data files and the description files of the data files contained in the file is as follows: Figure 3 shown.

[0045] Step 4.2: Parse all attributes in the data file description file and the support file description file, and compare them with all attributes in the generated binary support file. If they are correct, generate a verification report, including whether each attribute is verified successfully. If not, the tool will report an error message and the user will re-enter the information.

[0046] Step 5: Execute the header file generation tool process, where the header file is a binary file and supports the file description file to execute the header file generation tool to generate the header file. The header file is used to quickly or briefly describe the data included in the data set during the avionics equipment data loading process, and to quickly determine the content loaded by the avionics equipment. Specifically,

[0047] Step 5.1: The support file description file in step 4 is used as input to the header file generation tool. The binary file of the header file is generated by parsing the nodes and attributes of the support file description file;

[0048] Step 5.2: The binary format of the header file is as follows Figure 4 As shown;

[0049] Step 5.3: Parse all nodes and attributes in the support file description file in step 5.1, compare them with all attributes in the generated header file, and generate a verification report, including whether each attribute is verified successfully. If any attribute has an error, the header file generation tool will fail to execute.

[0050] The above are only specific embodiments of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A method for data packaging based on an avionics core processing platform, suitable for loading data into an airborne avionics system, wherein the avionics system runs multiple types of software and is equipped with multiple avionics devices, characterized in that: The method comprises, Step 1: Classify the software-loadable aircraft parts to form multiple software sets, and classify each software set according to whether it is related to the location of the avionics equipment; A plurality of data sets applicable to avionics equipment are generated by default. Each of the data sets is used as a software-loadable aircraft component. The data sets include a first data set, a plurality of second data sets, and a third data set. The data sets serve as inputs to a tool set. The tool set is capable of packaging the data loaded by the avionics equipment and writing data rules to each data set. The rules for writing data to each data set include: Step 1.1: Store the software applicable to the common location of all avionics equipment in the first data set; Step 1.2: Each avionics device corresponds to a device loading mapping table and a specific operation configuration table. According to the names of the device loading mapping table and the specific operation configuration table, the device loading mapping table and the specific operation configuration table are stored in a second data set that matches the names; Step 1.3: The third data set is used to count the names and storage of the first data set and all the second data sets to form a configuration list; Step 2: executing a data integration tool process, wherein all the second data sets are used to generate a specific operation configuration table through the data integration tool, and the data integration tool is used to connect the operating system configuration, end system configuration, storage configuration, and file system configuration provided by the user and applicable to the specified avionics device into a binary file; Step 3: executing a data file generation tool process, wherein a plurality of software in a data package is encapsulated; Step 4: Execute the support file generation tool process to describe the packaged data packet and form a description file in a predetermined format; Step 5: Execute the header file generation tool, wherein the header file generation tool is supported by the file description file to generate a header file. The header file is used for a quick or brief description of the data included in the data set during the avionics equipment data loading process, and to quickly determine the content loaded by the avionics equipment.

2. The method according to claim 1, characterized in that The binary file in step 2 is parsed to determine whether the various parts of the binary file connection are correct. The binary file generated by parsing is used to calculate the correctness of the CRC values ​​of the operating system configuration, end system configuration, storage configuration and file system configuration. If correct, a data integration tool result report is generated. If incorrect, the tool will report an error message and the user will re-enter the information.

3. The method according to claim 2, characterized in that Step 3 includes, In step 3.1, the data set obtains a data file description file through human-computer interaction. The data file description file is in XML format and includes a main node corresponding to the XML format. The main node includes a LoadItem loadable item. The attributes of the main node are the name, ID, item number and type of the loadable item. 3.2 The binary file and description file are used as inputs of a data file generation tool, which generates a data file for data loading of all avionics equipment. The data file generation tool parses the data file description file to sequentially derive the software's add-in item attributes and hardware and software information, as well as the binary file's size and CRC value, and adds them to the 1024 bytes of the binary file header. The 1024 bytes of the binary file header serve as the add-in item header data LIH, which is used by avionics equipment to quickly identify add-ins.

4. The method according to claim 3, characterized in that Parse all the attributes in the XML description file in step 3 and compare them with all the attributes in the generated LIH. If they are correct, generate a verification report, including whether each attribute is verified successfully. If they are incorrect, the tool will report an error message and the user will re-enter the information.

5. The method according to claim 4, characterized in that Step 4 includes: all the data file description files are used as inputs of a support file generation tool, the support file generation tool is used to generate a support file, and the format of the support file is XML format; Parse all attributes in the data file description file and the support file description file, and compare them with all attributes in the generated binary support file. If they are correct, generate a verification report, including whether each attribute is verified successfully. If not, the tool will report an error message and the user will re-enter the information.

6. The method according to claim 5, characterized in that Step 5 includes, Step 5.1: The support file description file in step 4 is used as input to the header file generation tool. The binary file of the header file is generated by parsing the nodes and attributes of the support file description file; Step 5.2: Setting the binary format of the header file; Step 5.3: Parse all nodes and attributes in the support file description file in step 5.1, compare them with all attributes in the generated header file, and generate a verification report, including whether each attribute is verified successfully. If any attribute has an error, the header file generation tool will fail to execute.

Images