Security Module Memory Utilization via Native Code Garbage Collection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing security modules struggle with efficient memory utilization when code is written in languages other than Java, as they cannot be deleted or reused, leading to suboptimal memory management.
Innovation Solution
A dynamic storage device with a processor that detects native codes, links them to a Java storage area, allocates segments, and manages them like Java packages, allowing for garbage collection and resizing of memory space, even for codes written in languages other than Java.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If native codes are stored in a separate first storage area, then code organization is simplified and access is easier, but memory utilization is inefficient and space cannot be reused
Solution Approach 1:
The patent merges the first storage area (native code storage) with the second storage area (Java package storage) by making the first storage area a part of the second storage area through address linking. This allows the heap manager to manage both native codes and Java packages uniformly, enabling effective memory utilization and garbage collection for native codes while maintaining organized access.
2Quantity of substance
If Java packages are managed with garbage collection and dynamic resizing, then memory utilization is optimized, but native codes cannot benefit from these memory management features
Solution Approach 1:
The patent makes the heap manager universal by enabling it to manage both Java packages and native codes. Native codes are allocated from the heap like Java packages, and the heap manager can perform garbage collection on native codes when their associated Java packages are deleted. This allows dynamic resizing and reusability of memory space for both code types.
3Adaptability or versatility
If codes written in languages other than Java are used, then programming flexibility increases, but memory cannot be dynamically managed or reused
Solution Approach 1:
The patent introduces an intermediary mechanism where native codes (written in languages other than Java) are allocated from the Java heap through the heap manager. The heap manager acts as an intermediary that tracks native code locations, manages their memory allocation, and enables garbage collection. This allows flexible programming with native codes while maintaining dynamic memory management and reusability through the heap manager's coordination.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
A security module and method for optimum memory utilization is disclosed. According to an embodiment of the present invention, a security module for optimum memory utilization, said security module comprises: a dynamic storage device including a first storage area storing one or more native codes and a second storage area storing one or more Java packages, and a processor being operationally coupled to the dynamic storage device configured to: detect presence of the one or more native codes in the first storage area, form the detected one or more native codes in the first storage area as a part of the second storage area, and manage the one or more native codes like the Java packages in the second storage area.