Homomorphic Encryption for Secure Database Query Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems struggle to securely process mixed data containing both secure and insecure operations without compromising security, especially when using homomorphic cryptography on numerical values in digital computing, as they fail to maintain privacy and security during query operations.

Innovation Solution

A computer-implemented method and system that secures user-generated queries on a client-side to generate encrypted queries, allowing operations on mixed data without revealing recognizable terms to the server, using homomorphic cryptography to perform queries on encrypted data while maintaining security and privacy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If homomorphic cryptography is used to encrypt data before storing on the server, then data security and privacy are improved, but query processing complexity and computational overhead increase

Engineering Contradiction:
Improvedata securityVSAvoidquery processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-processing data during the upload phase. Specifically, the client encrypts data using homomorphic encryption before transmitting to the server, and the server pre-processes this encrypted data into encrypted indexes and encrypted data structures. This preliminary encryption and indexing work eliminates the need for complex real-time decryption and re-encryption operations during query processing, thereby reducing query processing complexity while maintaining data security.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces encrypted indexes as an intermediary mechanism between the encrypted data and query operations. These encrypted indexes serve as a mediator that enables the server to perform search operations on encrypted data without decrypting it. The encrypted indexes act as a bridge that translates query requirements into operations that can be performed on encrypted data structures, thereby simplifying the overall query processing complexity while preserving data security through homomorphic encryption.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If all data is encrypted to maintain security, then data privacy is improved, but query performance and processing speed deteriorate

Engineering Contradiction:
Improvedata privacyVSAvoidquery performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies segmentation by dividing data into different encryption categories based on sensitivity levels. Critical sensitive data is encrypted using homomorphic encryption, while less sensitive data may use lighter encryption or remain in plaintext form. This selective encryption approach ensures that only the necessary portions of data undergo computationally intensive encryption operations, thereby maintaining data privacy for sensitive information while preserving query performance for non-sensitive data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent employs parameter changes by adjusting encryption strength and type based on data sensitivity parameters. Different encryption algorithms and key lengths are applied depending on the sensitivity classification of the data. This parameter-based approach allows the system to optimize the balance between security and performance by using stronger encryption only where necessary, thereby maintaining data privacy for sensitive information while minimizing the impact on query performance.

Inventive Principle:
Principle #35Parameter changes

3Object-affected harmful factors

If encrypted data is stored on the server, then security against unauthorized access is improved, but the server's ability to perform operations on the data without decryption is lost

Engineering Contradiction:
Improveunauthorized access protectionVSAvoidserver operation capability
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The patent replaces the traditional mechanical approach of decrypting data for processing with cryptographic mathematics operations. Instead of decrypting encrypted data to perform operations, the system uses homomorphic encryption properties that allow mathematical operations to be performed directly on ciphertexts. The server performs cryptographic computations (such as polynomial multiplications and modular arithmetic) on encrypted data without ever decrypting it, thereby maintaining unauthorized access protection while enabling server-side operations through substitution of cryptographic operations for traditional data processing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent changes the operational parameters of the server from plaintext data manipulation to cryptographic computation. The server operates in the encrypted domain, performing operations based on cryptographic parameters and protocols rather than direct data manipulation. This parameter change enables the server to perform useful operations on encrypted data while maintaining security, as the server's operational capability is transformed to work with ciphertexts and cryptographic primitives rather than plaintext data.

Inventive Principle:
Principle #35Parameter changes

4Adaptability or versatility

If mixed secure and insecure data is processed together, then data utility and versatility are improved, but security risks and vulnerability increase

Engineering Contradiction:
Improvedata utilityVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies local quality by assigning different security levels and encryption types to different portions of the data based on their sensitivity characteristics. Within the same database system, highly sensitive data fields are encrypted with strong homomorphic encryption, while less sensitive fields may use lighter encryption or remain in plaintext. This local differentiation of security quality allows the system to process mixed secure and insecure data together, improving data utility and versatility while maintaining appropriate security protections for each data type based on its specific security requirements.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9313179B1Mixing secure and insecure data and operations at server database
Publication Date: 2016.04.12 GOOGLE LLC
  • US9313179B1 patent drawing
  • US9313179B1 patent drawing
  • US9313179B1 patent drawing

AI summary

Processing a query, includes, at a client, receiving a user-generated query having a plurality of recognizable terms, securing the user-generated query to generate an encrypted query, so that the plurality of recognizable terms generated by the user-generated query cannot be determined by a server, transmitting the encrypted query to the server, to perform the query on encrypted data comprising a mix of regular data and secure data previously provided by the client, wherein at least one of selection criteria of the query and identities of selected records of the query result cannot be determined by the server, and interpreting a result of the query provided by the server, and providing an output of the query to the user having the plurality of recognizable terms.