Key Cache Manager Table for Multi-Locality Security Chip Coherency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In conventional hardware security architectures, key cache managers from different localities do not communicate, leading to coherency issues when sharing cryptographic key storage resources, resulting in incorrect key usage and limited access to security chip features.
Innovation Solution
A method that allows key cache managers to load and save restoration data for application keys, enabling recognition of key removal and restoration, as well as eviction of keys without affecting other localities, through a flowchart-based process that includes encryption, decryption, and storage management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If key cache managers from different localities share the key storage without communication, then access to security chip features is limited, but if they communicate and coordinate, then coherency problems occur due to mutual distrust
Solution Approach 1:
The patent introduces a key cache manager table as an intermediary data structure that mediates between multiple key cache managers from different localities. This table stores metadata about keys including their locality origin, allowing key cache managers to query and coordinate access without direct communication, thus enabling shared access while maintaining coherency through centralized tracking
Solution Approach 2:
The system implements feedback mechanisms where key cache managers query the key cache manager table to check the status and locality information of keys before access. This feedback loop ensures that key cache managers are aware of keys evicted by other localities and can restore them appropriately, maintaining coherency while enabling versatile access
2Device complexity
If key cache managers operate independently without tracking evictions, then device complexity is reduced, but key coherency problems arise when keys are evicted by other localities
Solution Approach 1:
The patent creates a copy of key metadata (including locality information) in the key cache manager table whenever a key is loaded into the key storage. This copy allows key cache managers to independently track and detect evictions without direct communication, maintaining coherency while keeping the system architecture simple and independent
3Speed
If the key storage is filled with keys from one locality, then that locality's applications have fast access, but keys from other localities cannot be loaded
Solution Approach 1:
The patent implements dynamic key cache management where the key cache manager table is updated in real-time as keys are loaded, evicted, or restored. This dynamic tracking allows the system to adaptively manage keys from multiple localities, switching between local and remote keys based on current needs while maintaining fast access through the locality-optimized key storage
Data Source
AI summary
A method for a plurality of key cache managers for a plurality of localities to share cryptographic key storage resources of a security chip, includes: loading an application key into the key storage; and saving a restoration data for the application key by a key cache manager, where the restoration data can be used by the key cache manager to re-load the application key into the key storage if the application key is evicted from the key storage by another key cache manager. The method allows each of a plurality of key cache managers to recognize that its key had been removed from the security chip and to restore its key. The method also allows each key cache manager to evict or destroy any key currently loaded on the security chip without affecting the functionality of other localities.