A method for capturing interactive data monitoring requirements

Abstract

This application provides a method for interactive data monitoring requirement capture, relating to the field of integrated avionics technology, including: S1: defining a configuration file for the interactive requirement capture tool; S2: defining configuration information in the configuration file of the interactive requirement capture tool; S3: the user selects the current general processing module through an interactive interface; S4: the user selects the current request mode through an interactive interface and proceeds to subsequent steps according to the current request mode; S5: performing an interactive memory check; S6: performing an interactive memory snapshot; S7: generating and saving a request message detection file for the request data; S8: loading the message detection file; S9: sending the message data to the embedded data monitoring software. This method solves the problem that the current method of loading database files can only meet the monitoring of selected data, and supports the requirement capture of temporary data monitoring for running general processing modules.

Description

Technical Field

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

[0002] The input of the data monitoring mechanism inside the general processing module of the avionics core processing platform depends on the capture of monitoring data requirements. Currently, the method of loading database files can only achieve monitoring of some selected data (automatic monitoring scenario). However, for scenarios that require monitoring of temporary data during the operation of some general processing modules (interactive manual monitoring scenario), the method of loading and parsing fixed database files for requirement capture cannot meet the needs. Summary of the Invention

[0003] The purpose of this application is to solve the problem of demand capture in temporary data monitoring scenarios. This invention proposes a data interactive monitoring demand capture method.

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

[0005] S1: Define the configuration file for the interactive requirements capture tool, which is in EXCEL format;

[0006] S2: Define configuration information in the configuration file of the interactive requirements capture tool;

[0007] S3: Host users can select the current general processing module through the interactive interface;

[0008] S4: The host user selects the current request mode through the interactive interface. If the current request mode is interactive memory check mode, then proceed to S5; if the current request mode is interactive memory snapshot mode, then proceed to S6.

[0009] S5: Perform an interactive memory check. If the check result is correct, proceed to S7. If the check result is incorrect, report an error.

[0010] S6: Perform an interactive memory snapshot. If the check result is correct, proceed to S7. If the check result is incorrect, report an error.

[0011] S7: The interactive requirement capture tool generates and saves request message detection files for request data;

[0012] S8: The user selects the file path to load the request message detection file in the interactive requirement capture tool to load the file;

[0013] S9: The interactive requirement capture tool sends message data to the embedded data monitoring software via the AFDX network as input for processing temporary monitoring requests in the data monitoring requirement capture process.

[0014] The interactive data monitoring requirement capture method provided by this invention also has the following technical features: the configuration file includes application partition number information residing on each general processing module, virtual address range information of the application partition, monitoring rate range information, data size information range in interactive memory checks, and the size information of the largest memory block allowed to be monitored in interactive memory snapshots.

[0015] The data interactive monitoring demand capture method provided by the present invention also has the following technical feature, wherein step S5 includes:

[0016] S5.1: Host users fill in the partition number, virtual address, data size, and monitoring rate information of the currently requested data through the interactive interface;

[0017] S5.2: If not all the current request data has been added, repeat S5.1 to add all the request data to the request data queue. If the current request data has been added, proceed to step 5.3.

[0018] S5.3: The interactive requirement capture tool performs a validity check on the request data.

[0019] The data interactive monitoring demand capture method provided by this invention also has the following technical feature: S5.3 includes:

[0020] S5.3.1: Check whether the partition number, virtual address, data size, and monitoring rate information of the requested data added by the user are in the correct format.

[0021] If the partition number, virtual address, data size, and monitoring rate information of the requested data are in the correct format, proceed to S5.3.2;

[0022] An error will occur if the partition number, virtual address, data size, or monitoring rate information of the requested data is in the wrong format.

[0023] S5.3.2: Check whether the partition number, virtual address, data size, and monitoring rate information of the requested data added by the user conform to the range specified in the configuration file.

[0024] If the partition number, virtual address, data size, and monitoring rate information of the requested data meet the range specified in the configuration file, then proceed to S5.3.3;

[0025] An error will occur if the requested partition number, virtual address, data size, or monitoring rate information is out of range.

[0026] S5.3.3: Check whether the memory space of the requested data added by the user conforms to the address range specified in the configuration file.

[0027] If the memory space for the requested data does not exceed the bounds, proceed to S5.3.4;

[0028] An error will occur if the memory space for the requested data is out of bounds;

[0029] S5.3.4: Check if the total size of the detection entries added by the user exceeds the maximum allowed data size of the request message.

[0030] If the total size of the detected entries does not exceed the maximum allowed data size of the request message, proceed to S7;

[0031] An error will be reported if the total size of the detected entries exceeds the maximum allowed data size of the request message.

[0032] The data interactive monitoring demand capture method provided by the present invention also has the following technical feature: S6 includes:

[0033] S6.1: Host users fill in the partition number, virtual address, and data block size information of the currently requested data through the interactive interface;

[0034] S6.2: The interactive requirement capture tool performs a validity check on the request data.

[0035] The data interactive monitoring demand capture method provided by the present invention also has the following technical feature: S6.2 includes:

[0036] S6.2.1: Check whether the partition number, virtual address, and data block size information of the requested data added by the user are in the correct format.

[0037] If the partition number, virtual address, and data block size information of the requested data are in the correct format, proceed to S6.2.2;

[0038] An error will occur if the partition number, virtual address, or data block size information of the requested data is in an incorrect format;

[0039] S6.2.2: Check whether the partition number, virtual address, and data block size information of the requested data added by the user conform to the range specified in the configuration file.

[0040] If the partition number, virtual address, and data block size information of the requested data meet the range specified in the configuration file, then proceed to S6.2.3;

[0041] An error will occur if the requested partition number, virtual address, or data block size information is out of bounds.

[0042] S6.2.3: Check whether the memory space of the requested data added by the user conforms to the address range specified in the configuration file;

[0043] If the memory space for the requested data does not exceed the bounds, proceed to S6.2.4;

[0044] An error will occur if the memory space for the requested data is out of bounds;

[0045] S6.2.4: Check whether the total size of the detection entries added by the user exceeds the maximum allowed data size of the request message.

[0046] If the total size of the detected entries does not exceed the maximum allowed data size of the request message, proceed to S7;

[0047] An error will be reported if the total size of the detected entries exceeds the maximum allowed data size of the request message.

[0048] The interactive monitoring requirement capture method provided by this invention also has the following technical feature: the method further includes a function to capture data when monitoring requirements need to be changed.

[0049] If the required request message detection file exists locally, repeat S8-S9;

[0050] If the required request message detection file does not exist locally, repeat steps S3-S9.

[0051] Beneficial effects

[0052] This invention proposes a demand capture method for temporary data monitoring during the runtime of a general processing module (interactive manual monitoring scenario). It solves the problem that the current method of using database file loading can only monitor some selected data (automatic monitoring scenario). Furthermore, based on the size of the monitored data, it more comprehensively considers demand capture under two interactive monitoring scenarios (interactive memory check mode and interactive memory snapshot mode), providing support for capturing continuous data with the maximum memory capacity when monitoring resources are limited.

[0053] The interactive data monitoring requirement capture method provided by this invention offers an EXCEL protocol for monitoring temporary data during the runtime of general processing modules. This protocol takes into account more comprehensive information, such as the application partition number information, application partition address range information, and monitoring rate range information residing on each general processing module. Storing this information in the tool's configuration file can not only greatly reduce the amount of code, but also eliminate the need to change the device's software function modules when device functions or usage scenarios change. Developers can achieve their goals by modifying the attribute definitions of the configuration file, making it easier for developers to maintain the configuration file. Attached Figure Description

[0054] 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.

[0055] Figure 1 This is a schematic diagram of the overall architecture of the data interactive monitoring requirement capture method provided in the embodiments of the present invention;

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

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] Interactive manual monitoring, designed to meet real-time monitoring needs, involves sending real-time monitoring request commands to the running general processing module. The data monitoring software then performs data monitoring based on these commands. The optimized data monitoring request capture scheme proposes a method for handling ad-hoc monitoring requests, implemented through a ground-based interactive request capture tool. This tool provides a user-friendly interface for inputting request items and transmits the generated message data to the embedded data monitoring software via the AFDX network.

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

[0063] S1: Define the configuration file for the interactive requirements capture tool, which is in EXCEL format;

[0064] S2: Define configuration information in the configuration file of the interactive requirements capture tool;

[0065] S3: Host users can select the current general processing module through the interactive interface;

[0066] S4: The host user selects the current request mode through the interactive interface. If the current request mode is interactive memory check mode, then proceed to S5; if the current request mode is interactive memory snapshot mode, then proceed to S6.

[0067] S5: Perform an interactive memory check. If the check result is correct, proceed to S7. If the check result is incorrect, report an error.

[0068] S6: Perform an interactive memory snapshot. If the check result is correct, proceed to S7. If the check result is incorrect, report an error.

[0069] S7: The interactive requirement capture tool generates and saves request message detection files for request data;

[0070] S8: The user selects the file path to load the request message detection file in the interactive requirement capture tool to load the file;

[0071] S9: The interactive requirement capture tool sends message data to the embedded data monitoring software via the AFDX network as input for processing temporary monitoring requests in the data monitoring requirement capture process.

[0072] In the above embodiments, when the size of a single data item does not exceed the capacity of a single message transmission, an interactive memory check mode is used. This mode checks data once or periodically (depending on the monitoring rate). When the monitored data exceeds the capacity of a single message transmission, an interactive memory snapshot mode is used. This mode checks data once, and each monitoring request can only monitor one large block of memory data. The interactive memory snapshot mode has a higher priority than the interactive memory check mode, ensuring that the data monitoring software can capture continuous data of the maximum memory capacity when processing both types of requests simultaneously.

[0073] In some embodiments, the configuration file includes application partition number information residing on each general processing module, virtual address range information of the application partition, monitoring rate range information, data size information range in interactive memory checks, and the size information of the largest memory block allowed to be monitored in interactive memory snapshots.

[0074] In some embodiments, S5 includes:

[0075] S5.1: Host users fill in the partition number, virtual address, data size, and monitoring rate information of the currently requested data through the interactive interface;

[0076] S5.2: If not all the current request data has been added, repeat S5.1 to add all the request data to the request data queue. If the current request data has been added, proceed to step 5.3.

[0077] S5.3: The interactive requirement capture tool performs a validity check on the request data.

[0078] In some embodiments, S5.3 includes:

[0079] S5.3.1: Check whether the partition number, virtual address, data size, and monitoring rate information of the requested data added by the user are in the correct format.

[0080] If the partition number, virtual address, data size, and monitoring rate information of the requested data are in the correct format, proceed to S5.3.2;

[0081] If the partition number, virtual address, data size, or monitoring rate information of the requested data is in an incorrect format, the tool should provide the user with a prompt in the user information prompt bar and generate an error log.

[0082] S5.3.2: Check whether the partition number, virtual address, data size, and monitoring rate information of the requested data added by the user conform to the range specified in the configuration file.

[0083] If the partition number, virtual address, data size, and monitoring rate information of the requested data meet the range specified in the configuration file, then proceed to S5.3.3;

[0084] If the requested data partition number, virtual address, data size, or monitoring rate information exceeds the specified range, the tool should provide the user with a prompt in the user information prompt bar and generate an error log.

[0085] S5.3.3: Check whether the memory space (virtual address + size) of the requested data added by the user conforms to the address range specified in the configuration file.

[0086] If the memory space (virtual address + size) of the requested data does not exceed the bounds, then proceed to S5.3.4;

[0087] If the memory space (virtual address + size) of the requested data 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;

[0088] S5.3.4: Check if the total size of the detection entries added by the user exceeds the maximum allowed data size of the request message.

[0089] If the total size of the detected entries does not exceed the maximum allowed data size of the request message, proceed to S7;

[0090] If the total size of the detected entries exceeds the maximum allowed data size of the request message, the tool should provide the user with a prompt in the user information bar and generate an error log.

[0091] In some embodiments, S6 includes:

[0092] S6.1: Host users fill in the partition number, virtual address, and data block size information of the currently requested data through the interactive interface;

[0093] S6.2: The interactive requirement capture tool performs a validity check on the request data.

[0094] In some embodiments, S6.2 includes:

[0095] S6.2.1: Check whether the partition number, virtual address, and data block size information of the requested data added by the user are in the correct format.

[0096] If the partition number, virtual address, and data block size information of the requested data are in the correct format, proceed to S6.2.2;

[0097] If the partition number, virtual address, or data block size information of the requested data is in an incorrect format, the tool should provide the user with a prompt in the user information prompt bar and generate an error log.

[0098] S6.2.2: Check whether the partition number, virtual address, and data block size information of the requested data added by the user conform to the range specified in the configuration file.

[0099] If the partition number, virtual address, and data block size information of the requested data meet the range specified in the configuration file, then proceed to S6.2.3;

[0100] If the requested data partition number, virtual address, or data block size information exceeds the range, the tool should provide the user with a prompt in the user information prompt bar and generate an error log message.

[0101] S6.2.3: Check whether the memory space (virtual address + data block size) of the requested data added by the user conforms to the address range specified in the configuration file;

[0102] If the memory space (virtual address + data block size) of the requested data does not exceed the bounds, then proceed to S6.2.4;

[0103] If the memory space (virtual address + data block size) of the requested data 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;

[0104] S6.2.4: Check whether the total size of the detection entries added by the user exceeds the maximum allowed data size of the request message.

[0105] If the total size of the detected entries does not exceed the maximum allowed data size of the request message, proceed to S7;

[0106] If the total size of the detected entries exceeds the maximum allowed data size of the request message, the tool should provide the user with a prompt in the user information bar and generate an error log.

[0107] In some embodiments, the method further includes options for situations where monitoring requirements need to be changed.

[0108] If the required request message detection file exists locally, repeat S8-S9;

[0109] If the required request message detection file does not exist locally, repeat steps S3-S9.

[0110] 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 interactive data monitoring requirements, used to capture input information from the interactive data monitoring mechanisms of various general processing modules on an avionics core processing platform, characterized in that, The method includes: S1: Define the configuration file for the interactive requirements capture tool, which is in EXCEL format; S2: Define configuration information in the configuration file of the interactive requirements capture tool; S3: Host users select the current general processing module through the interactive interface; S4: The host user selects the current request mode through the interactive interface. If the current request mode is interactive memory check mode, then proceed to S5; if the current request mode is interactive memory snapshot mode, then proceed to S6. S5: Perform an interactive memory check. If the check is successful, proceed to S7; otherwise, report an error. S5 includes: S5.1: Host users fill in the partition number, virtual address, data size, and monitoring rate information of the currently requested data through the interactive interface; S5.2: If not all the current request data has been added, repeat S5.1 to add all the request data to the request data queue. If the current request data has been added, proceed to step 5.

3. S5.3: The interactive requirement capture tool performs a validity check on the request data; S6: Perform an interactive memory snapshot. If the check result is correct, proceed to S7; otherwise, report an error. S6 includes: S6.1: Host users fill in the partition number, virtual address, and data block size information of the currently requested data through the interactive interface; S6.2: The interactive requirement capture tool performs a validity check on the request data; S7: The interactive requirement capture tool generates and saves request message detection files for request data; S8: The user selects the file path to load the request message detection file in the interactive requirement capture tool to load the file; S9: The interactive requirement capture tool sends the generated message data to the embedded data monitoring software via the AFDX network as input for processing temporary monitoring requests in the data monitoring requirement capture process.

2. The data interactive monitoring demand capture method according to claim 1, characterized in that, The configuration file includes application partition number information residing on each general processing module, virtual address range information of the application partition, monitoring rate range information, data size information range in interactive memory checks, and the size information of the maximum memory block that can be monitored in interactive memory snapshots.

3. The data interactive monitoring demand capture method according to claim 1, characterized in that, S5.3 includes: S5.3.1: Check whether the partition number, virtual address, data size, and monitoring rate information of the requested data added by the user are in the correct format. If the partition number, virtual address, data size, and monitoring rate information of the requested data are in the correct format, proceed to S5.3.2; An error will occur if the partition number, virtual address, data size, or monitoring rate information of the requested data is in the wrong format. S5.3.2: Check whether the partition number, virtual address, data size, and monitoring rate information of the requested data added by the user conform to the range specified in the configuration file. If the partition number, virtual address, data size, and monitoring rate information of the requested data meet the range specified in the configuration file, then proceed to S5.3.3; An error will occur if the requested partition number, virtual address, data size, or monitoring rate information is outside the specified range. S5.3.3: Check whether the memory space of the requested data added by the user conforms to the address range specified in the configuration file. If the memory space for the requested data does not exceed the bounds, proceed to S5.3.4; An error will occur if the memory space for the requested data is out of bounds; S5.3.4: Check if the total size of the detection entries added by the user exceeds the maximum allowed data size of the request message. If the total size of the detected entries does not exceed the maximum allowed data size of the request message, proceed to S7; An error will be reported if the total size of the detected entries exceeds the maximum allowed data size of the request message.

4. The data interactive monitoring demand capture method according to claim 1, characterized in that, S6.2 includes: S6.2.1: Check whether the partition number, virtual address, and data block size information of the requested data added by the user are in the correct format. If the partition number, virtual address, and data block size information of the requested data are in the correct format, proceed to S6.2.2; An error will occur if the partition number, virtual address, or data block size information of the requested data is in an incorrect format; S6.2.2: Check whether the partition number, virtual address, and data block size information of the requested data added by the user conform to the range specified in the configuration file. If the partition number, virtual address, and data block size information of the requested data meet the range specified in the configuration file, then proceed to S6.2.3; An error will occur if the requested partition number, virtual address, or data block size information is out of bounds. S6.2.3: Check whether the memory space of the requested data added by the user conforms to the address range specified in the configuration file; If the memory space for the requested data does not exceed the bounds, proceed to S6.2.4; An error will occur if the memory space for the requested data is out of bounds; S6.2.4: Check whether the total size of the detection entries added by the user exceeds the maximum allowed data size of the request message. If the total size of the detected entries does not exceed the maximum allowed data size of the request message, proceed to S7; An error will be reported if the total size of the detected entries exceeds the maximum allowed data size of the request message.

5. The data interactive monitoring demand capture method according to claim 1, characterized in that, The method also includes options for situations where monitoring requirements need to be changed. If the required request message detection file exists locally, repeat S8-S9; If the required request message detection file does not exist locally, repeat steps S3-S9.

Images