IDL Code Generation With Dynamic Memory and Safety Rule Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing interface definition languages (IDL) lack support for dynamic memory allocation and fail to adequately address safety-critical scenarios, leading to potential data overflow or inefficient memory usage, and lack clear mapping to high-level safety standards.
Innovation Solution
Implement dynamic memory allocation for data types/interfaces in IDL files and convert high-level safety standards into low-level rules using machine learning, ensuring compliance through a verification process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If static memory allocation is used in IDL data types, then memory usage is predictable and efficient, but data overflow may occur and data precision may be truncated
Solution Approach 1:
The patent introduces dynamic memory allocation capabilities into IDL data types, allowing the memory size to be adjusted at runtime based on actual data requirements. This resolves the contradiction by making the previously static memory allocation dynamic, thereby preventing data overflow and precision truncation while maintaining reliability in safety-critical applications.
Solution Approach 2:
The patent changes the memory allocation parameter from fixed to variable, enabling the system to adapt memory size according to actual needs. This parameter change allows the IDL to handle cases where data precision requirements vary, resolving the contradiction between reliable data handling and memory allocation flexibility.
2Reliability
If high static memory allocation is set to prevent overflow, then data precision is maintained, but memory efficiency decreases and too much memory is consumed
Solution Approach 1:
By implementing dynamic memory allocation in IDL, the system can allocate exactly the amount of memory needed for each data type at runtime. This eliminates the need to over-allocate memory statically, thereby maintaining data precision while optimizing memory consumption and preventing waste.
Solution Approach 2:
The memory allocation parameter transitions from a fixed high value to a dynamic value that adjusts based on actual data requirements. This resolves the contradiction by allowing the system to maintain sufficient memory for precision when needed, while consuming minimal memory when not required.
3Extent of automation
If low-level verification rules are used for IDL files, then verification can be performed, but the rules do not clearly map to high-level safety standards
Solution Approach 1:
The patent introduces an intermediary layer that translates high-level safety standards into verification rules for IDL files. This intermediary enables automatic verification while maintaining clear traceability to safety standards, resolving the contradiction between automation capability and ease of mapping to safety requirements.
Solution Approach 2:
The system performs preliminary translation of safety standards into verification rules before the actual verification process. This preliminary action ensures that the verification can be automated while the mapping to safety standards remains clear and understandable, as the translation is done in advance in a systematic manner.
Data Source
AI summary
Provided are a system, apparatus, and method for generating codes. The method may include, receiving an interface definition language (IDL) file and a high-level rule file; converting the high-level rule file into a low-level rule file; determining whether the IDL file complies with the low-level rule file; and based on determining that the IDL file complies with the low-level rule file, generating code based on the IDL file.