Memory Device Certificate Validation for Scalable Key Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing memory systems face inefficiencies and security challenges due to static public key storage, leading to increased latency, resource overhead, and limited flexibility in establishing trusted connections with new devices.
Innovation Solution
Implement a validation procedure at a server level to authenticate intermediary devices using public-private key pairs, generating certificates signed by the server's private key, and sharing these certificates with memory devices to establish trusted connections without storing public keys within the memory device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If public keys are stored within the memory device, then authentication can be performed locally, but the memory device becomes overloaded with key management operations and storage requirements
Solution Approach 1:
The patent extracts the public key storage function from the memory device and relocates it to the server. The server stores the public keys and issues certificates to authorized devices, while the memory device only stores a reference to the server's public key for validation. This extraction eliminates the need for the memory device to manage multiple public keys locally, reducing its operational complexity while maintaining authentication capability.
Solution Approach 2:
The patent introduces a server as an intermediary between the memory device and authenticated devices. The server acts as a mediator that handles public key storage, device authentication, and certificate issuance. This intermediary absorbs the complexity of key management operations, allowing the memory device to maintain simple local validation functionality without bearing the burden of managing multiple public keys.
2Adaptability or versatility
If multiple public keys are stored in the memory device for different devices, then more devices can be authenticated, but the memory device experiences increased resource overhead and latency
Solution Approach 1:
The patent extracts the storage of multiple public keys from the memory device and relocates this function to the server. The server maintains a database of public keys for multiple authenticated devices, while the memory device only stores a single reference to the server's public key. This extraction enables the system to authenticate multiple devices without increasing the memory device's storage requirements or validation latency.
Solution Approach 2:
The patent moves the key management function from the local dimension (memory device) to the remote dimension (server). By storing public keys in a different dimension (server database rather than local memory), the system achieves the ability to authenticate multiple devices without imposing the associated resource overhead and latency on the memory device. Validation operations are shifted to occur at the server dimension.
3Reliability
If the memory device validates all data requests locally, then security is maintained, but the memory device is overloaded with validation operations
Solution Approach 1:
The patent introduces a server as an intermediary that handles the bulk of validation operations. The server receives data requests, validates them against stored public keys and certificates, and returns validation results to the memory device. This intermediary absorbs the productivity burden of validation operations, allowing the memory device to maintain security through simple reference validation without being overloaded by complex validation processing.
Solution Approach 2:
The server performs self-service validation by maintaining its own database of public keys and certificates, and by autonomously validating data requests before they reach the memory device. This self-service capability at the server level reduces the validation operation throughput requirements on the memory device, as the server handles validation independently rather than requiring the memory device to process each validation request locally.
Data Source
AI summary
Methods, systems, and devices for sharing keys with authorized users are described. In some cases, the first device may transmit, to the server, a request for a certificate for the first device to communicate with a memory device. The server may generate the certificate using a first private key of a first public-private key pair. The first device may receive the certificate and generate a content message that is signed by a second private key of a second public-private key pair. In some cases, the memory device may receive the content message and the certificate and validate the certificate using a first public key of the first public-private key pair. In such cases, the first device may establish a connection with the memory device in response to the memory device validating the certificate.