High-security software input and output configuration method based on functional module

Abstract

The invention discloses a high-security software input and output configuration method based on a functional module, belongs to the technical field of aviation airborne equipment communication software configuration, aims at solving the problems of code redundancy, low development efficiency and poor compatibility and expandability, and comprises the following steps: S1, integrating equipment communication parameters through a three-level hierarchical configuration file; s2, constructing an indexed data dictionary based on the unified configuration file; s3, realizing dynamic construction and analysis of communication data by using the index; the configuration file replaces more than 70% of communication code writing work, the period for adapting to new equipment is shortened to the day level from the week level, duplicate codes are reduced, the number of code lines is reduced, the maintenance labor cost is reduced, when a new protocol (such as CANopen) is expanded through the configuration file, bottom layer codes do not need to be modified, compatibility is improved, and the method is suitable for popularization and application. And communication parameters are visually presented through a configuration file, and the communication fault troubleshooting time is shortened from an hour level to a minute level in combination with an index tracking function of a data dictionary.

Description

Technical Field

[0001] This invention belongs to the field of communication software configuration technology for airborne equipment, and specifically relates to a high-security software input / output configuration method based on functional modules. Background Technology

[0002] Airborne communication systems are a critical component of aircraft safety, and the rationality and reliability of their communication software configuration are of paramount importance. Currently, the development of this field exhibits the following trends: Increased equipment diversity and complexity: With the continuous development of aviation technology, the types of airborne equipment are becoming increasingly diverse, and their functions are becoming more complex. Equipment from different manufacturers varies significantly in terms of communication protocols, speeds, addresses, and data formats, which poses a great challenge to the communication integration between devices. Traditional software configuration methods: Traditional airborne equipment communication software configuration typically involves defining the communication format and configuration of each device separately in the code. When faced with a large variety and number of devices, this approach generates a large amount of repetitive code, increasing the workload and complexity of software development, and is also prone to introducing errors, reducing development efficiency and software maintainability.

[0003] Lack of unified standards: The industry has not yet established a unified standard for airborne equipment communication configuration, resulting in poor software compatibility between different aircraft models or projects. When equipment on an aircraft is changed or upgraded, software developers often need to manually write a large amount of corresponding communication format-related code, which is not only time-consuming and labor-intensive, but also makes it difficult to ensure the consistency and accuracy of the code.

[0004] Existing airborne equipment communication software configuration technology has many shortcomings: 1. Code redundancy problem: Since the communication formats and configurations of different devices are defined separately in the code, there is a lot of duplicate code. This not only increases the amount of code, but also makes the code structure complex, difficult to understand and maintain. 2. Low development efficiency: When the equipment on the aircraft changes or needs to be adapted to different aircraft models, software developers need to manually write a large amount of communication format-related code, resulting in a long development cycle and low efficiency. 3. Poor compatibility and scalability: The lack of a unified configuration standard leads to poor software compatibility between different devices or aircraft models. At the same time, it is difficult to quickly expand and adapt when new devices are added or communication requirements change.

[0005] Therefore, a highly secure software input / output configuration method based on functional modules is needed to solve the problems of code redundancy, low development efficiency, and poor compatibility and scalability in existing technologies. Summary of the Invention

[0006] The purpose of this invention is to provide a highly secure software input / output configuration method based on functional modules to solve the problems mentioned in the background art.

[0007] To achieve the above objectives, the present invention provides the following technical solution: a high-security software input / output configuration method based on functional modules, comprising the following steps: S1. Configuration file collection and organization, including: S11. Create independent configuration files for each airborne device to record communication interface, protocol, rate, and address parameters. Ensure data accuracy through CRC check and manually verify the list to ensure completeness. S12. Organize the scattered configuration files into a three-level hierarchical structure according to the logical relationship that "a communication service contains multiple communication messages and a communication message contains multiple communication elements". S13. Through hierarchical association, multi-level configuration files are integrated into a unified file consistent with the binary format of communication data, which serves as the core configuration data source of the system. S2. Establish a data dictionary, including: S21. Parse the unified configuration file, extract the hierarchical relationship and parameters of communication services, messages, and elements, and generate index key-value pairs; S22. Construct a data dictionary based on index key values ​​to store the communication data format information corresponding to each level, and realize the fast mapping of "index → ​​data structure"; S3. Communication data construction and parsing, including: S31. Sending data: Determine the target service and message according to communication requirements, obtain the parameters of the corresponding elements through the data dictionary index, and assemble the data frame in binary format; S32. Receive data: For the received binary data frame, parse each element parameter through the data dictionary index to restore it into a recognizable communication message and service type.

[0008] It should be noted in the scheme that the three-level hierarchical structure mentioned in step S1 includes: Communication service layer: Defines the overall communication type for communication between multiple devices; Communication message layer: Subdivides specific communication messages under services; Data element layer: Each message is broken down into specific data elements.

[0009] It is worth noting that the index key values ​​of the data dictionary in step S2 correspond one-to-one with the hierarchy of communication services, messages, and elements, and the index query response time is ≤1ms.

[0010] It should be further noted that when changing equipment, only the configuration file level parameters need to be modified, and there is no need to adjust the code logic.

[0011] As a preferred implementation method, a unified configuration file is used to establish a data dictionary, and an indexing mechanism is used to achieve fast query functionality.

[0012] As a preferred implementation, the data dictionary adopts a static index structure, and the query time for high-frequency messages is less than 1ms.

[0013] Compared with the prior art, the high-security software input / output configuration method based on functional modules provided by the present invention has at least the following beneficial effects: (1) This invention separates parameter definitions through a three-level configuration file of "service → message → element". When a device changes, only the configuration file at the corresponding level needs to be modified (such as adding a communication service or message for a new device), without touching the code logic. For example, when adding a satellite communication device, only the communication service and message definition of the device need to be added to the configuration file, and the data dictionary index is automatically updated, improving development efficiency by more than 70%.

[0014] (2) This invention uses a unique index to associate the hierarchical structure of the configuration file, enabling millisecond-level queries of "requirements → parameters". For example, when parsing complex flight status data, the data dictionary can simultaneously retrieve communication element parameters from multiple devices, ensuring that the data frame parsing accuracy reaches 99.9%, which is more than 30% higher than the traditional method.

[0015] (3) The configuration file of this invention replaces more than 70% of the communication code writing work, shortens the cycle of adapting to new devices from weekly to daily, reduces duplicate code by 90%, reduces the number of lines of code by 60%, and reduces maintenance manpower costs by more than 50%. At the same time, it supports plug-and-play device access. When extending new protocols (such as CANopen) through the configuration file, there is no need to modify the underlying code, and the compatibility is improved to more than 95%. The communication parameters are visualized through the configuration file. Combined with the indexing and tracking function of the data dictionary, the communication fault diagnosis time is shortened from hours to minutes. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating a high-security software input / output configuration method based on functional modules according to the present invention. Detailed Implementation

[0017] The present invention will be further described below with reference to embodiments.

[0018] Please see Figure 1 This invention provides a high-security software input / output configuration method based on functional modules, comprising the following steps: S1. Configuration file collection and organization, including: S11. Create independent configuration files for each airborne device to record communication interface, protocol, rate, and address parameters. Ensure data accuracy through CRC check and manually verify the list to ensure completeness. S12. Organize the scattered configuration files into a three-level hierarchical structure according to the logical relationship that "a communication service contains multiple communication messages and a communication message contains multiple communication elements". S13. Through hierarchical association, multi-level configuration files are integrated into a unified file consistent with the binary format of communication data, which serves as the core configuration data source of the system. S2. Establish a data dictionary, including: S21. Parse the unified configuration file, extract the hierarchical relationship and parameters of communication services, messages, and elements, and generate index key-value pairs; S22. Construct a data dictionary based on index key values ​​to store the communication data format information corresponding to each level, and realize the fast mapping of "index → ​​data structure"; S3. Communication data construction and parsing, including: S31. Sending data: Determine the target service and message according to communication requirements, obtain the parameters of the corresponding elements through the data dictionary index, and assemble the data frame in binary format; S32. Receive data: For the received binary data frame, parse each element parameter through the data dictionary index to restore it into a recognizable communication message and service type.

[0019] Furthermore, it is worth specifying that the three-level hierarchical structure mentioned in step S1 includes: Communication service layer: Defines the overall communication type for communication between multiple devices; Communication message layer: Subdivides specific communication messages under services; Data element layer: Each message is broken down into specific data elements.

[0020] The specific syntax for the above three-level hierarchical flowchart is shown below: graph TD A [Configuration File Module] --> B [Communication Service Layer] A --> C [Communication Message Layer] A --> D [Communication Element Layer] B -->C C -->D E [Data Dictionary Module] --> F [Index Mechanism] F -->B F -->C F -->D The configuration file module integrates device communication parameters through a three-level hierarchical structure, while the data dictionary module associates each level through indexes, enabling fast querying and data interaction.

[0021] Specifically, the syntax for the communication data processing flowchart is as follows: flowchart LR User requirements --> G [Determine communication service / message] G --> H [Data dictionary index query] H --> I{Send / Receive} I -->|Send| J [Construct binary data frame] I -->|Receive| K[parse binary data frame] J -->L [Device Communication Interface] L --> M [Target Device] M --> N [Return Data] N -->K K --> O [Output parsing result] User requests trigger data dictionary queries, construct or parse data frames based on the communication direction, and complete the interaction through the device interface.

[0022] Furthermore, it is worth noting that the index key values ​​of the data dictionary mentioned in step S2 correspond one-to-one with the hierarchy of communication services, messages, and elements, and the index query response time is ≤1ms.

[0023] Further as Figure 1 As shown, it is worth noting that when changing equipment, only the configuration file level parameters need to be modified, and there is no need to adjust the code logic.

[0024] Configuration files replace more than 70% of communication code writing, shorten the adaptation cycle for new devices from weeks to days, reduce duplicate code by 90%, reduce the number of lines of code by 60%, and reduce maintenance manpower costs by more than 50%.

[0025] The configuration file visually presents communication parameters, and combined with the indexing and tracing function of the data dictionary, the time for troubleshooting communication faults is reduced from hours to minutes. It supports plug-and-play device access, and when extending new protocols (such as CANopen) through the configuration file, no modification to the underlying code is required, improving compatibility to over 95%.

[0026] Furthermore, this invention addresses the issue that existing solutions using file systems to store configuration files are suitable for lightweight scenarios but have low query efficiency under large data volumes. It introduces an embedded database (such as SQLite) to store configuration data and utilizes database indexes to optimize query performance, making it suitable for multi-device communication scenarios on complex models. However, this requires additional development of a database interface, increasing system resource consumption (approximately 5%–10% memory overhead).

[0027] Furthermore, this invention addresses the problem that existing solutions based on static indexes are suitable for fixed configuration scenarios. By employing dynamic data structures such as hash tables or skip lists, it improves the query speed of high-frequency communication messages (average query time reduced from 10ms to less than 1ms). However, dynamic indexes have higher maintenance complexity and may introduce additional consistency issues.

[0028] Furthermore, this invention addresses the issue of existing technical solutions relying on standardized processes for manually verifying the integrity of configuration files. It develops an automated verification tool that scans configuration files based on preset rules (such as mandatory field checks and value range validation) and generates an integrity report. This can reduce manual verification time from 2 hours per device to 5 minutes per device, but requires development costs.

[0029] In summary: This invention separates parameter definitions through a three-level configuration file structure of "service → message → element". When a device changes, only the corresponding level of the configuration file needs to be modified (such as the communication service or message of a new device), without touching the code logic. This invention uses a unique index to associate the configuration file hierarchy, enabling millisecond-level queries of "requirement → parameter". This invention's configuration file replaces more than 70% of the communication code writing work, shortening the adaptation cycle for new devices from weeks to days, reducing duplicate code by 90%, reducing the number of lines of code by 60%, and lowering maintenance manpower costs by more than 50%. It also supports plug-and-play device access. When extending new protocols (such as CANopen) through the configuration file, no modification to the underlying code is required, improving compatibility to over 95%. Furthermore, the communication parameters are visualized through the configuration file, and combined with the indexing and tracking function of the data dictionary, the communication fault troubleshooting time is shortened from hours to minutes.

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

[0031] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A highly secure software input / output configuration method based on functional modules, characterized in that: Includes the following steps: S1. Configuration file collection and organization, including: S11. Create independent configuration files for each airborne device to record communication interface, protocol, rate, and address parameters. Ensure data accuracy through CRC check and manually verify the list to ensure completeness. S12. Organize the scattered configuration files into a three-level hierarchical structure according to the logical relationship that "a communication service contains multiple communication messages and a communication message contains multiple communication elements". S13. Through hierarchical association, multi-level configuration files are integrated into a unified file consistent with the binary format of communication data, which serves as the core configuration data source of the system. S2. Establish a data dictionary, including: S21. Parse the unified configuration file, extract the hierarchical relationship and parameters of communication services, messages, and elements, and generate index key-value pairs; S22. Construct a data dictionary based on index key values ​​to store the communication data format information corresponding to each level, and realize the fast mapping of "index → ​​data structure"; S3. Communication data construction and parsing, including: S31. Sending data: Determine the target service and message according to communication requirements, obtain the parameters of the corresponding elements through the data dictionary index, and assemble the data frame in binary format; S32. Receive data: For the received binary data frame, parse each element parameter through the data dictionary index to restore it into a recognizable communication message and service type.

2. The high-security software input / output configuration method based on functional modules according to claim 1, characterized in that: The three-level hierarchical structure mentioned in step S1 includes: Communication service layer: Defines the overall communication type for communication between multiple devices; Communication message layer: Subdivides specific communication messages under services; Data element layer: Each message is broken down into specific data elements.

3. The high-security software input / output configuration method based on functional modules according to claim 1, characterized in that: In step S2, the index key values ​​of the data dictionary correspond one-to-one with the hierarchy of communication services, messages, and elements, and the index query response time is ≤1ms.

4. The high-security software input / output configuration method based on functional modules according to claim 1, characterized in that: When changing equipment, only the configuration file level parameters need to be modified; no adjustment to the code logic is required.

5. The high-security software input / output configuration method based on functional modules according to claim 1, characterized in that: A unified configuration file is used to establish a data dictionary, and an indexing mechanism is employed to enable fast query functionality.

6. The high-security software input / output configuration method based on functional modules according to claim 1, characterized in that: The data dictionary uses a static index structure, and the query time for high-frequency messages is less than 1ms.

Images