Secure Database Linkage via Homomorphic Encryption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for securely linking datasets containing sensitive information, such as financial or medical records, face challenges in maintaining privacy and compliance with regulations, as they often require divulging personal information or relying on trusted third parties with access to sensitive data.

Innovation Solution

A method and system for secure linkage of databases using public and private key pairs, specifically employing probabilistic encryption techniques like additive homomorphic encryption and Pallier cryptosystems, allowing encrypted comparison results to be decrypted without revealing personal information, and utilizing a semi-trusted key holder to manage key pairs and perform secure comparisons.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional secure linkage methods are used to protect privacy, then personal information remains protected, but the ability to determine matching records between datasets is compromised or requires trusted third parties

Engineering Contradiction:
Improveprivacy protectionVSAvoidmatching record determination
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary mechanism using public-key cryptography where encrypted data can be compared without revealing the underlying personal information. The encryption scheme acts as a mediator that enables matching record determination while maintaining privacy protection, eliminating the need for trusted third parties to access sensitive data.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transforms the data representation by encrypting personal information before comparison. By changing the parameter state from plaintext to encrypted form, the system enables matching operations on encrypted data, thereby maintaining privacy while allowing record linkage functionality.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If encrypted data is used to protect sensitive information, then privacy is maintained, but computational complexity and resource requirements increase

Engineering Contradiction:
Improvedata securityVSAvoidcomputational resources
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the computational workload by distributing encryption and decryption operations between different parties. The first party encrypts their data using public keys, the second party performs comparisons on encrypted data, and results are decrypted by the appropriate party. This segmentation reduces the computational burden on any single system while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses public keys as copies that can be freely distributed for encryption purposes without compromising security. The public key acts as a non-sensitive copy that enables the encryption function, while the private key remains protected. This copying mechanism reduces complexity by eliminating the need for secure key distribution channels.

Inventive Principle:
Principle #26Copying

3Reliability

If complete encryption is applied to all data fields, then maximum privacy protection is achieved, but the ability to perform efficient comparisons and matching is reduced

Engineering Contradiction:
Improveprivacy protectionVSAvoidmatching efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies encryption selectively rather than uniformly to all data. The system identifies and encrypts only the specific data fields that require privacy protection for matching purposes, while leaving other fields in their original form. This local application of encryption maintains privacy where needed while preserving matching efficiency.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements partial encryption of data fields rather than complete encryption of all data. By encrypting only the necessary identifying fields used for matching while leaving other fields unencrypted or differently processed, the system achieves sufficient privacy protection without sacrificing matching efficiency.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9503432B2Secure linkage of databases
Publication Date: 2016.11.22 PRIVACY ANALYTICS
  • US9503432B2 patent drawing
  • US9503432B2 patent drawing
  • US9503432B2 patent drawing

AI summary

A secure linkage between databases allows records of an individual in a first database to be linked to records of the same individual in a second database without disclosing or providing personal information outside of either database or system responsible for controlling access to the respective databases. As such, records of individuals may be securely linked together without compromising privacy or security of the databases.