A method for automatically monitoring and capturing data requirements

Abstract

This application provides a method for automatically capturing data monitoring requirements, relating to the field of integrated avionics technology. This method utilizes an EXCEL -> XML -> BIN data conversion approach, with the conversion specifically implemented through a ground-side component that can load a database generation tool. This method provides a more user-friendly EXCEL protocol, offering more detailed prompts to the user. It solves the problems of simple TXT format database files failing to provide prompts for host users to fill in requirement information, easily leading to errors in database file entry, and hindering the management of multiple general-purpose processing modules.

Description

Technical Field

[0001] This invention relates to the field of integrated avionics technology, and in particular provides a method for automatically monitoring and capturing data requirements. Background Technology

[0002] The avionics core processing platform is a general-purpose processing platform sharing hardware and software resources, providing resources for data computation, data transmission, and data conversion for aircraft functions. Among these, the data monitoring function provides a data monitoring mechanism within the general-purpose processing module. This mechanism's input depends on the capture of monitoring data requirements. Currently, the conventional approach to capturing data monitoring requirements involves pre-writing relevant monitoring data information into a TXT format database file and loading configurable parameter information. The data monitoring software then parses and applies this database file. This approach has three problems: First, the TXT format database file cannot provide prompts to the user, the content presentation is not clear and intuitive, and it is prone to formatting issues. Second, different general-purpose processing modules need to maintain multiple different TXT database files, which can easily lead to confusion, is time-consuming and labor-intensive, and is not conducive to unified management. Third, when the host user enters invalid values, no error messages are provided, causing some errors to be discovered only when the data monitoring software is running, reducing the efficiency of requirement capture. Summary of the Invention

[0003] The purpose of this application is to address the shortcomings of existing database files in meeting the requirements for monitoring and capturing data.

[0004] To achieve the above objectives, the present invention adopts the following technical solution: a method for automatically capturing data monitoring requirements, used to capture input information of the automatic data monitoring mechanism of various general processing modules on the avionics core processing platform, the method comprising:

[0005] S1: Create an XSD file to define the schema of a loadable database XML file;

[0006] S2: Generate a loadable database XML template file based on the XSD file defined in S1;

[0007] S3: Based on the XSD file created by S1 and the XML template file generated by S2, define the configuration file EXCEL format for the loadable database generation tool and the user-oriented automatic monitoring data monitoring list EXCEL file format;

[0008] S4: Defines the loadable binary data (BIN) file format for data monitoring configuration;

[0009] S5: Define the loadable database configuration information for each general processing module according to the EXCEL format configuration file of the loadable database generation tool defined in S3;

[0010] S6: Define the loadable database automatic monitoring data monitoring list for each general processing module based on the user-oriented automatic monitoring data monitoring list EXCEL file format defined in S3;

[0011] S7: Based on the loadable database XML template file generated in S2, convert the loadable database configuration information defined in S5 and the loadable database automatic monitoring data monitoring list defined in S6 into a loadable database XML file;

[0012] S8: Generate a loadable binary data BIN file from the attribute values ​​in the loadable database XML file converted in S7, according to the loadable binary data BIN file format defined in S4. The generated loadable binary data BIN file is the input of the automatic data monitoring mechanism.

[0013] The automatic data monitoring requirement capture method provided by this invention also has the following technical feature: the XSD file includes element node information and attribute value range constraints from an XML file.

[0014] The automatic data monitoring requirement capture method provided by this invention also has the following technical features: the XML template file includes the database name, database version number, database ID, execution cycle of the data monitoring software, number of monitored data items, and monitoring data item information.

[0015] The automatic data monitoring demand capture method provided by this invention also has the following technical features: the monitoring data item information includes data item ID, partition ID to which the data item belongs, virtual address of the data item, size of the data item, and monitoring rate.

[0016] The automatic data monitoring requirement capture method provided by this invention also has the following technical features: the configuration file of the database generation tool can be loaded in EXCEL format, including the database name, database version information, database ID, and execution cycle information of the data monitoring software for each general processing module, wherein the information of each general processing module occupies a separate tab; the user-oriented automatic monitoring data monitoring list in EXCEL file format includes monitoring data item information in each general processing module, wherein the information of each general processing module occupies a separate tab.

[0017] The automatic data monitoring demand capture method provided by this invention also has the following technical features: the monitoring data item information in each general processing module includes data item ID, partition ID to which the data item belongs, virtual address of the data item, size of the data item, and monitoring rate.

[0018] The automatic data monitoring demand capture method provided by this invention also has the following technical feature: S7 includes:

[0019] S7.1: Convert the configuration file EXCEL of the loadable database generation tool and the user-oriented automatic monitoring data monitoring list EXCEL file into a loadable database procedure XML file;

[0020] S7.2: Use the XSD file created by S1 to validate the loadable database procedure XML file converted by S7.1. If the validation is successful, perform further validity checks on the loadable database procedure XML file. If the validation fails, report an error.

[0021] S7.3 checks whether the memory space of the automatic monitoring data is out of bounds. If it is not out of bounds, the loadable database procedure XML file is used as the loadable database XML file. If it is out of bounds, an error is reported.

[0022] Beneficial effects

[0023] The automatic data monitoring requirement capture method provided by this invention provides an XML template file protocol, whose XSD verification function ensures the correctness of the parameters of the loadable database file. This solves the problem that simple txt database files cannot detect errors in time when host users fill in invalid information, resulting in some errors being discovered only when the data monitoring software is running, thus reducing the efficiency of requirement capture.

[0024] The automatic data monitoring and demand capture method provided by this invention proposes a loadable database generation mechanism that is more convenient for host users. It provides a more user-friendly EXCEL protocol, gives users more detailed prompts, and solves the problem that simple txt format database files cannot provide host users with prompts for filling in demand information, which easily leads to errors in filling in the database file.

[0025] The automatic data monitoring and requirement capture method provided by this invention maintains the loadable database configuration information of all general processing modules in a single configuration file (EXCEL). This not only significantly reduces the amount of code but also eliminates the need to modify the device's software modules when device functions or usage scenarios change. Developers can achieve their goals simply by modifying the attribute definitions in the configuration file, facilitating the maintenance of the loadable database. Furthermore, each general processing module has a separate tab for easy filling by host users, solving the problem of multiple different TXT configuration files required for different general processing modules, which can easily lead to confusion, time-consuming and labor-intensive processes, and hinder unified management of configuration information.

[0026] The automatic data monitoring requirement capture method provided by this invention maintains the automatic monitoring data monitoring list of all general processing modules in a user-facing Excel file. Each general processing module has a separate tab, which is convenient for host users to fill in. This solves the problem that different general processing modules require multiple different txt database files, which can easily cause confusion, is time-consuming and labor-intensive, and is not conducive to the unified management of requirement information.

[0027] This invention proposes a format definition for a data monitoring loadable database. This format architecture has strong universality and is easy to extend to the format definition process of other airborne software databases. Attached Figure Description

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

[0029] Figure 1 This is a schematic diagram of the overall architecture of the automatic data monitoring demand capture method provided in this embodiment of the invention;

[0030] Figure 2 This is a flowchart of the automatic data monitoring requirement capture method provided in an embodiment of the present invention. Detailed Implementation

[0031] The present application will be further described in detail below with reference to the accompanying drawings and embodiments. However, it should be noted that these embodiments are not intended to limit the present application. Equivalent transformations or substitutions in function, method, or structure made by those skilled in the art based on these embodiments are all within the protection scope of the present application.

[0032] In the description of the embodiments of this application, it should be understood that the terms "center", "longitudinal", "lateral", "up", "down", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings. They are only for the convenience of describing the creation of this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the creation of this application.

[0033] Furthermore, the terms "first," "second," "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0034] The terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to fixed connections, detachable connections, or integral connections; they can refer to mechanical connections or electrical connections; they can refer to direct connections or indirect connections through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art can understand the specific meaning of these terms in this application based on the specific circumstances.

[0035] Automatic monitoring involves predefining data items to be monitored in a loadable database. The data monitoring software then performs data monitoring based on the loaded monitoring information. The loadable binary FIDO database includes configurable parameters required for the normal operation of the automatic monitoring function, as well as a list of monitoring data. The data monitoring requirement capture optimization scheme proposes a more user-friendly and robust loadable binary FIDO database generation process, namely, an EXCEL-->XML-->BIN data conversion method. The data conversion is specifically implemented through the loadable database generation tool on the ground-side component.

[0036] like Figure 1-2 As shown, a method for capturing automatic data monitoring requirements is provided, used to capture input information from the automatic data monitoring mechanisms of various general processing modules on the avionics core processing platform. The method includes:

[0037] S1: Create an XSD file to define the schema of a loadable database XML file. The XSD file defines the schema of the XML file and constrains the range of values ​​for element attributes in the XML file.

[0038] S2: Generate a loadable database XML template file based on the XSD file defined in S1;

[0039] S3: Based on the XSD file created by S1 and the XML template file generated by S2, define the configuration file EXCEL format for the loadable database generation tool and the user-oriented automatic monitoring data monitoring list EXCEL file format;

[0040] S4: Define the loadable binary data BIN file format for data monitoring configuration. The loadable binary data BIN file format is defined as shown in Table 1.

[0041] Table 1 shows the loadable binary data (BIN) file formats.

[0042]

[0043]

[0044]

[0045] S5: Define the loadable database configuration information for each general processing module according to the EXCEL format configuration file of the loadable database generation tool defined in S3;

[0046] S6: Define the loadable database automatic monitoring data monitoring list for each general processing module based on the user-oriented automatic monitoring data monitoring list EXCEL file format defined in S3;

[0047] S7: Based on the loadable database XML template file generated in S2, convert the loadable database configuration information defined in S5 and the loadable database automatic monitoring data monitoring list defined in S6 into a loadable database XML file;

[0048] S8: Generate a loadable binary data BIN file from the attribute values ​​in the loadable database XML file converted in S7, according to the loadable binary data BIN file format defined in S4. The generated loadable binary data BIN file is the input of the automatic data monitoring mechanism.

[0049] In some embodiments, the XSD file includes element node information and attribute value range constraints from the XML file.

[0050] In some embodiments, the XML template file includes the database name, database version number, database ID, execution cycle of the data monitoring software, number of monitored data items, and monitoring data item information.

[0051] In some embodiments, the monitoring data item information includes the data item ID, the partition ID to which the data item belongs, the virtual address of the data item, the size of the data item, and the monitoring rate.

[0052] In some embodiments, the configuration file EXCEL format of the loadable database generation tool includes the loadable database name, database version information, database ID, and execution cycle information of the data monitoring software for each general processing module, wherein the information of each general processing module occupies a separate tab.

[0053] The user-oriented automatic monitoring data monitoring list EXCEL file format includes monitoring data item information from each general processing module, with each general processing module's information occupying a separate tab.

[0054] In some embodiments, the monitoring data item information in each general processing module includes the data item ID, the partition ID to which the data item belongs, the virtual address of the data item, the size of the data item, and the monitoring rate.

[0055] In some embodiments, S7 includes:

[0056] S7.1: Convert the configuration file EXCEL of the loadable database generation tool and the user-oriented automatic monitoring data monitoring list EXCEL file into a loadable database procedure XML file;

[0057] S7.2: Use the XSD file created in S1 to validate the loadable database procedure XML file converted in S7.1. If the validation is successful, proceed to S7.3 to perform further validity checks on the loadable database procedure XML file. If the validation fails, the tool should provide the user with a prompt in the user information bar and generate an error log.

[0058] S7.3 Checks whether the memory space (virtual address + size) of the automatic monitoring data exceeds the limit. If it does not exceed the limit, the loadable database procedure XML file is used as the loadable database XML file. If it exceeds the limit, the tool should provide the user with a prompt message in the user information prompt bar and generate an error log message.

[0059] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the protection scope of this application. The above description is merely a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of this application, and these improvements and modifications should also be considered within the protection scope of this application.

Claims

1. A method for capturing automatic data monitoring requirements, used to capture input information from the automatic data monitoring mechanisms of various general processing modules on an avionics core processing platform, characterized in that, The method includes: S1: Create an XSD file to define the schema of a loadable database XML file; S2: Generate a loadable database XML template file based on the XSD file defined in S1; S3: Based on the XSD file created by S1 and the XML template file generated by S2, define the configuration file EXCEL format for the loadable database generation tool and the user-oriented automatic monitoring data monitoring list EXCEL file format; S4: Defines the loadable binary data (BIN) file format for data monitoring configuration; S5: Define the loadable database configuration information for each general processing module according to the EXCEL format configuration file of the loadable database generation tool defined in S3; S6: Define the loadable database automatic monitoring data monitoring list for each general processing module based on the user-oriented automatic monitoring data monitoring list EXCEL file format defined in S3; S7: Based on the loadable database XML template file generated in S2, convert the loadable database configuration information defined in S5 and the loadable database automatic monitoring data monitoring list defined in S6 into a loadable database XML file; S8: Generate a loadable binary data BIN file from the attribute values ​​in the loadable database XML file converted in S7, according to the loadable binary data BIN file format defined in S4. The generated loadable binary data BIN file is the input of the automatic data monitoring mechanism.

2. The automatic data monitoring demand capture method according to claim 1, characterized in that, The XSD file includes element node information and attribute value range constraints from the XML file.

3. The automatic data monitoring demand capture method according to claim 1, characterized in that, The XML template file contains the database name, database version number, database ID, execution cycle of the data monitoring software, number of monitored data items, and monitoring data item information.

4. The automatic data monitoring demand capture method according to claim 3, characterized in that, The monitoring data item information includes the data item ID, the partition ID to which the data item belongs, the virtual address of the data item, the size of the data item, and the monitoring rate.

5. The automatic data monitoring demand capture method according to claim 1, characterized in that, The configuration file for the loadable database generation tool, in EXCEL format, includes the name of the database to be loaded by each general processing module, database version information, database ID, and execution cycle information of the data monitoring software. The information for each general processing module occupies a separate tab. The user-facing automatic monitoring data monitoring list, in EXCEL file format, includes monitoring data item information from each general processing module. The information for each general processing module occupies a separate tab.

6. The automatic data monitoring demand capture method according to claim 5, characterized in that, The monitoring data item information in each general processing module includes the data item ID, the partition ID to which the data item belongs, the virtual address of the data item, the size of the data item, and the monitoring rate.

7. The automatic data monitoring demand capture method according to claim 1, characterized in that, S7 includes: S7.1: Convert the configuration file EXCEL of the loadable database generation tool and the user-oriented automatic monitoring data monitoring list EXCEL file into a loadable database procedure XML file; S7.2: Use the XSD file created by S1 to validate the loadable database procedure XML file converted by S7.

1. If the validation is successful, perform further validity checks on the loadable database procedure XML file. If the validation fails, report an error. S7.3 checks whether the memory space of the automatic monitoring data is out of bounds. If it is not out of bounds, the loadable database procedure XML file is used as the loadable database XML file. If it is out of bounds, an error is reported.

Images