Trusted Device Key Access for Zero-Knowledge Encrypted Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage systems face vulnerabilities in protecting sensitive information due to the risk of unauthorized access and hacking, especially in cloud-based environments, where traditional encryption techniques rely on centralized servers that can be compromised, leading to potential data breaches and loss of user control over who accesses their private information.

Innovation Solution

A decentralized 'zero-knowledge' data management network where data is encrypted by a user's device using its own public key, stored encrypted on a server, and accessed by a trusted device with a recipient-specific rekeying process, ensuring only intended recipients can decrypt the data without the server ever seeing the raw sensitive information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If data is stored on centralized servers, then data accessibility and convenience are improved, but security and vulnerability to unauthorized access deteriorate

Engineering Contradiction:
Improvedata accessibilityVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts the decryption capability from the server by implementing client-side decryption. The server only stores encrypted data and provides decryption instructions, but the actual decryption occurs on the user's device. This separation removes the security vulnerability of centralized storage while maintaining accessibility through distributed client-side processing.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces encrypted data as an intermediary between the server and the user. Instead of direct access to plaintext data, all data interactions go through encryption/decryption layers. The server handles encrypted data, transmission occurs in encrypted form, and decryption happens client-side, creating multiple protective barriers against unauthorized access.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If traditional encryption techniques are used with centralized servers, then data storage efficiency is improved, but vulnerability to hacking and data breaches increases

Engineering Contradiction:
Improvestorage efficiencyVSAvoidhacking vulnerability
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent implements self-service encryption where each user's device independently encrypts and decrypts their own data using their private keys. The server does not need to manage encryption keys or perform decryption operations. This distributes the security burden to individual users while maintaining efficient centralized storage of encrypted data.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent changes the encryption parameter from server-managed symmetric encryption to client-managed asymmetric encryption. By using public-private key pairs where the private key never leaves the user's device, the system maintains storage efficiency while fundamentally changing the security model to resist hacking attempts.

Inventive Principle:
Principle #35Parameter changes

3Quantity of substance

If cloud-based data storage is implemented, then data transmission and storage capacity are improved, but the number of vulnerable data handling locations increases

Engineering Contradiction:
Improvestorage capacityVSAvoidvulnerability points
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent segments the data security function across multiple independent locations (user devices) rather than concentrating it on the server. Each user's private key and decryption capability reside on their own device, creating many small, independent security zones instead of one large vulnerable target. This maintains cloud storage capacity while distributing security responsibilities.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20260031975A1Storing encrypted data for access by a trusted device
Publication Date: 2026.01.29 JOURNEY AI
  • US20260031975A1 patent drawing
  • US20260031975A1 patent drawing
  • US20260031975A1 patent drawing

AI summary

In one embodiment, a method herein may comprise: receiving, at a first device, an encrypted private key of a second device encrypted using a public key of the first device, wherein the second device encrypted data into encrypted data using a public key of the second device and stored the encrypted data on a storage server; and decrypting, by the first device, a private key of the second device from the encrypted private key using a private key of the first device; and accessing, by the first device, the encrypted data on the storage server by utilizing the private key of the second device.