Oracle-Aided Encryption Protocol for Compact FHE Data Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Fully homomorphic encryption (FHE) significantly increases data size and storage requirements, making it impractical for large data lakes and cloud-based analytics, and existing methods do not efficiently address this issue.
Innovation Solution
Implement an Oracle-aided protocol that initially encrypts data using symmetric encryption (e.g., AES) for long-term storage and converts it to FHE encryption only when needed, utilizing a privacy-preserving auxiliary server (Oracle) to re-encrypt the data without revealing its contents.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If fully homomorphic encryption is applied to encrypt data for cloud storage and computation, then data security and privacy are improved, but data size increases by approximately 1000 times and storage resources are substantially increased
Solution Approach 1:
The patent segments the data lifecycle into distinct phases: initial symmetric encryption for storage, and selective FHE conversion for computation. This segmentation allows each encryption method to be applied only where needed, avoiding the 1000x size increase during long-term storage while maintaining security benefits when computation is required.
Solution Approach 2:
The patent applies preliminary symmetric encryption (AES) to data before storage, creating a compact encrypted form that uses minimal storage space. This preliminary action prepares the data for secure storage without the overhead of FHE, and only converts to FHE when computation is needed, preventing premature size expansion.
2Reliability
If fully homomorphic encryption is applied to enable cloud-based computations on encrypted data, then data privacy during computation is improved, but memory storage resources are substantially increased
Solution Approach 1:
The patent implements a dynamic encryption strategy where the encryption type changes based on operational requirements. Data stored in symmetric encryption format transitions to FHE format only when computation operations are needed. This dynamic approach optimizes memory usage by maintaining compact storage during idle periods while enabling privacy-preserving computation when required.
Solution Approach 2:
The patent changes the encryption parameter state from symmetric encryption to FHE encryption based on computational needs. This parameter change allows the system to toggle between compact storage mode and computation-ready mode, optimizing the balance between storage efficiency and computational privacy protection.
3Adaptability or versatility
If fully homomorphic encryption is applied to large data lakes for analytics, then secure cloud-based analytics are enabled, but the increased data size becomes impractical for storage
Solution Approach 1:
The patent extracts the FHE conversion step from the general data storage process and applies it selectively only to data subsets that require cloud-based analytics. This extraction prevents the unnecessary FHE conversion of entire data lakes, avoiding the 1000x size increase for data that will not be processed in the cloud.
Solution Approach 2:
The patent creates a universal data format that can serve multiple functions: symmetric encryption for cost-effective long-term storage and FHE encryption for secure cloud analytics. This multi-functionality allows the same data to be stored efficiently and then converted when needed, making large data lakes practical for both storage and secure analytics.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Systems and methods that may implement an Oracle-aided protocol for producing and using FHE encrypted data. The systems and methods may initially encrypt and store input data in one encrypted form that is not performed using FHE, which does not substantially increase the size of the data and storage resources required to store the encrypted data. In accordance with the Oracle-aided protocol, the encrypted data is re-encrypted as FHE encrypted data when FHE encrypted data is required.