Anonymized Data Reassociation Using Split-Key Reidentification

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods do not provide a secure system or method for re-associating previously anonymized data with the data owner, particularly in scenarios where unauthorized third-parties must be prevented from accessing identity details while ensuring authorized reidentification based on legal or ethical reasons.

Innovation Solution

A method and system using cryptographic keys (k1, k2, k3) to securely associate and re-associate anonymized data with a data owner, involving a personal software application, service provider, and user identification data server, ensuring only authorized parties can reidentify the data owner.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Object-affected harmful factors

If data is deidentified to protect data owner privacy, then unauthorized access to identity details is prevented, but authorized reidentification capability is lost

Engineering Contradiction:

Improveunauthorized access to identity detailsVSAvoidauthorized reidentification capability

Core Design Contradiction:

Object-affected harmful factorsVSAdaptability or versatility

Solution Approach 1:

The system segments the identification mechanism into two separate components: a deidentification key (k2) that removes identity information and a reidentification key (k3) that restores it. These keys are stored in separate locations (service provider server and user identification data server respectively), allowing independent control over deidentification and reidentification operations without compromising security.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a user identification data server as an intermediary component that holds the reidentification key (k3) and mediates between the service provider server (holding deidentification key k2) and authorized recipients. This intermediary enables controlled reidentification only for authorized parties while maintaining privacy protection for unauthorized access.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If data is anonymised to prevent identity disclosure, then data privacy is improved, but data utility for authorized purposes deteriorates

Engineering Contradiction:

Improvedata privacy protectionVSAvoiddata utility for authorized purposes

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system implements dynamic state change in data identification: data can transition from identified state to deidentified state (for privacy protection) and subsequently to reidentified state (for authorized purposes). The identification status is not fixed but can be dynamically adjusted based on the operational context and authorization level, maintaining both privacy and utility.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent changes the identification parameter from direct name-based identification to cryptographic key-based identification. By transforming the identification mechanism from human-readable names to encrypted keys (k1, k2, k3), the system achieves both strong privacy protection and controlled reidentification capability through parameter transformation.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If cryptographic keys are distributed to multiple servers, then reidentification security is improved, but system complexity increases

Engineering Contradiction:

Improvereidentification securityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The cryptographic key management is segmented into three separate keys (k1, k2, k3) distributed across different servers and locations: k1 (private key) remains with the data owner, k2 (deidentification key) is stored at the service provider server, and k3 (reidentification key) is stored at the user identification data server. This segmentation distributes security responsibilities and reduces the risk of single point of failure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system creates multiple copies of identification information in different forms and locations: the deidentification key (k2) is copied to the service provider server for privacy protection operations, while the reidentification key (k3) is copied to the user identification data server for authorized restoration. These copies enable different operational modes while maintaining security through separation.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS20260057109A1Method and system for re-associating anonymised data with a data owner

Publication Date: 2026.02.26 MEDICEUS DADOS DE SAUDE SA

AI summary

A computer-implemented method for re-associating anonymised data with a data owner is described, wherein the data owner has an associated personal code. The method comprises the steps of accessing by a third-party computer the anonymised data stored in a service provider computer server and transferring a first form of the personal code from the third-party computer to the service provider computer server. The method further comprises matching the first form of the personal code with a second form of the personal code at the service provider computer server and transferring the second form of the personal code from the service provider computer server to a user identification data computer server. The method further comprises matching the second form of the personal code to a data owner identifier by the user identification data computer server.