Distributed Registry for Secure User Data Transmission

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data security solutions, such as blockchain technology, fail to ensure user consent and data confidentiality during personal data transmission between parties, as they do not support anonymity and do not allow for the removal of records, making it difficult to revoke consent and protect user data privacy.

Innovation Solution

A method and system using a distributed registry, where each interaction stage is recorded, including user consent, using hashes and digital signatures to ensure secure data transmission, allowing for the verification of consent and confidentiality through a blockchain-based database, enabling secure data exchange while maintaining user control over their personal data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If blockchain technology is used to record data transmission, then the reliability and traceability of data transmission is improved, but the ability to ensure user anonymity and revoke consent deteriorates

Engineering Contradiction:
Improvereliability of data transmission recordingVSAvoiduser anonymity and consent revocation capability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system segments the data transmission process into distinct stages (consent obtaining, data transmission, data processing) and records each stage separately in the distributed registry. This allows selective verification of specific transmission events while maintaining user anonymity through hash-based identification rather than direct personal data storage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism using hash functions and distributed registry that mediates between the need for reliable recording and user anonymity. The hash-based records serve as intermediaries that verify transmission events without exposing sensitive personal data, and the distributed registry acts as a neutral mediator that both parties can trust.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a distributed registry records all interaction stages, then the lawfulness and user control over data is improved, but the complexity of the system increases

Engineering Contradiction:
Improvelawfulness of data transmissionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by obtaining user consent and registering it in the distributed registry before actual data transmission occurs. This preliminary recording of consent intentions allows for simplified verification during transmission, as the consent framework is already established and stored, reducing the complexity of real-time verification.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The distributed registry provides feedback mechanisms that allow parties to verify the lawfulness of data transmission by checking recorded consent and transmission events. This feedback loop enables automated verification without requiring complex manual verification processes, as the registry continuously provides verifiable records of consent and transmission status.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11258771B2Systems and methods for sending user data from a trusted party to a third party using a distributed registry
Publication Date: 2022.02.22 AO KASPERSKY LAB
  • US11258771B2 patent drawing
  • US11258771B2 patent drawing
  • US11258771B2 patent drawing

AI summary

Disclosed herein are systems and method for securely sending user data. In an exemplary aspect, a trusted party device may receive a request for user data and a first hash of the request stored in a distributed registry. In response to verifying that the first hash matches a hash of the request as calculated by the trusted party device, the trusted party device may generate and transmit both a confirmation request to send the user data and a second hash of the confirmation request to an authorized user device. The trusted party device may receive, from the authorized user device, both a confirmation message and a third hash of the confirmation message stored in the distributed registry. In response to verifying that the third hash matches a hash of the confirmation message as calculated by the trusted party device, the trusted party device may send the requested user data.