Centralized Data Access System for Distributed Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed computing systems, accessing and deleting user data is complex due to each service operating autonomously with different data storage and processing formats, making it difficult for central systems to manage user data access and deletion requests efficiently, especially under regulatory requirements like GDPR and CCPA.

Innovation Solution

A distributed service provider system with a front-end tool allows users to request data access and deletion through a single interface, using asynchronous API-based messaging to interact with multiple service systems, and employs security questions for identity verification, ensuring secure and timely handling of personal data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If distributed services store and process user data autonomously with different formats, then service independence and flexibility are improved, but data access and deletion management complexity increases

Engineering Contradiction:
Improveservice independenceVSAvoiddata access management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a centralized data access and deletion system that acts as an intermediary between users and distributed services. This system receives user requests, translates them into service-specific queries, and aggregates results from multiple autonomous services, thereby simplifying management while preserving service independence.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal data access interface that can handle multiple types of user requests (access, deletion, verification) across different services through a single system. This multi-functional approach allows the centralized system to manage diverse data operations without requiring separate mechanisms for each service.

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

2Adaptability or versatility

If each service stores user data in different formats and processes, then service autonomy is improved, but determining which service stores user data becomes difficult

Engineering Contradiction:
Improveservice autonomyVSAvoiddata location detection
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a feedback mechanism where the centralized data access system queries each distributed service about stored user data and collects responses. This feedback loop enables the system to build a comprehensive view of data locations across services without compromising their autonomous storage formats or processes.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The centralized system serves as an intermediary that translates user data location queries into service-specific detection requests and aggregates the results. This mediator approach allows detection of data across autonomous services while preserving their independent operations and data formats.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If deletion requests must be processed by each service individually, then data accuracy in deletion is improved, but processing time and operational complexity increase

Engineering Contradiction:
Improvedeletion accuracyVSAvoiddeletion processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by first identifying all services that store user data before initiating deletion operations. This pre-detection phase allows the system to prepare coordinated deletion requests to multiple services simultaneously, reducing overall processing time while ensuring accurate deletion from each service that holds the data.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent establishes continuous monitoring and communication channels with distributed services, allowing deletion requests to be propagated and executed across services in a coordinated manner. This continuous action framework enables parallel processing of deletion operations while maintaining accuracy through centralized coordination.

Inventive Principle:
Principle #20Continuity of useful action

4Productivity

If a centralized system manages data access across distributed services, then user data access efficiency is improved, but system complexity and communication overhead increase

Engineering Contradiction:
Improvedata access efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a centralized data access system as an intermediary layer between users and distributed services. This mediator consolidates communication with multiple services into a single interface, improving user access efficiency while managing system complexity through standardized interaction protocols with each service.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The centralized system provides universal data access functionality that handles multiple user requests across different services through a unified interface. This multi-functional approach improves efficiency by eliminating the need for users to interact with each service individually, while the system manages internal complexity through automated request routing and result aggregation.

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

Data Source

PatentUS12189811B2Systems and methods for augmentation of user data during data access and deletion in distributed service systems
Publication Date: 2025.01.07 STRIPE LLC
  • US12189811B2 patent drawing
  • US12189811B2 patent drawing
  • US12189811B2 patent drawing

AI summary

A method and apparatus for a distributed service provider augmenting user data during data access and deletion is described. The method may include monitoring a plurality of user data returned by service system responses to requests for user data associated with a user identifier. The method may further include building an additional user data search query using a subset of user data from the monitored plurality of user data returned by the service system responses to the initial requests for user data. Furthermore, the method can include executing the additional user data search query at each of the plurality of service systems to identify additional user data stored by one or more of the plurality of service systems, wherein the identified additional data is not associated with the user identifier.