Distributed Database Private Data Encryption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies face challenges in securely exchanging and processing private data between devices, particularly in centralized systems that may compromise user privacy and security, especially in IoT environments where hacks are prevalent.

Innovation Solution

A method involving network-enabled devices that use public-key cryptography and a distributed database system to encrypt and share private data, with metadata for access permissions and time validation, ensuring secure data exchange without relying on centralized service providers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If centralized servers are used for data processing, then service functionality is improved, but user privacy and security are compromised

Engineering Contradiction:
Improveservice functionalityVSAvoiduser privacy and security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the centralized server architecture into distributed network-enabled devices that each process data locally. Instead of one central authority holding all data, the system divides data processing across multiple independent nodes, each capable of autonomous operation. This segmentation eliminates the single point of failure and privacy violation inherent in centralized systems while maintaining service functionality through distributed collaboration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces cryptographic intermediaries (public-key infrastructure, homomorphic encryption, zero-knowledge proofs) that enable secure data exchange without direct trust between parties. These cryptographic mediators allow devices to verify data integrity and authenticate each other without exposing private information, resolving the trust deficit in centralized systems while enabling versatile service functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If decentralized distributed systems are used, then security and privacy are improved, but system complexity increases

Engineering Contradiction:
Improvesecurity and privacyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates universal cryptographic protocols and standardized data structures that work across diverse network-enabled devices regardless of their specific functionality. By establishing a common framework for encryption, authentication, and data exchange that can be applied universally across different device types and services, the system reduces the complexity burden that would otherwise arise from customizing security implementations for each individual device or service.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent transforms complex security requirements into manageable parameters through cryptographic abstraction. Instead of dealing with complex trust relationships and security policies directly, the system converts these into standardized cryptographic parameters (keys, certificates, encryption schemes) that can be automatically managed by software agents. This parameter transformation simplifies the deployment and maintenance of decentralized security while maintaining high reliability.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If public-key cryptography is implemented, then data security is improved, but computational overhead increases

Engineering Contradiction:
Improvedata securityVSAvoidcomputational overhead
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial cryptography selectively rather than encrypting all data uniformly. Critical private information receives full cryptographic protection through homomorphic encryption and zero-knowledge proofs, while less sensitive metadata or public information uses lighter authentication mechanisms. This partial application of cryptographic intensity reduces overall computational overhead while maintaining necessary security levels for protecting private data.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent performs cryptographic key generation, exchange, and verification in advance during device registration and connection establishment phases. By setting up cryptographic credentials and establishing trusted channels before actual data processing occurs, the system minimizes the computational burden during time-critical data operations. The heavy cryptographic lifting is done preliminarily when security can be enforced without real-time performance constraints.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3662403B1Private data processing
Publication Date: 2023.11.08 VISA INTERNATIONAL SERVICE ASSOCIATION
  • EP3662403B1 patent drawingFigure 1
  • EP3662403B1 patent drawingFigure 2A
  • EP3662403B1 patent drawingFigure 2B

AI summary

A method includes storing, in one or more databases amongst a plurality of databases by one or more nodes in a distributed database system, data for one or more of network-enabled devices. The data for each network-enabled device includes encrypted private data, and metadata associated with the private data. The metadata may include permissions data, time period validation data, and encryption parameters. In addition, the method may include locating the encrypted first private data and determining using first permissions data associated with the encrypted first private data and using the second network-enabled device identifier if the second network-enabled device is authorized to access the first private data. The method includes providing the first private data to the second network-enabled device. The second network-enabled device obtains and decrypts the encrypted first private data to obtain the first private data.