Federated Database Routing for Restricted Data Privacy

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Data privacy laws restrict the processing and storage of certain data outside specific countries, hindering the implementation of Globally Integrated Enterprise strategies that require global data processing without restrictions, particularly in Europe where customer data can only be transferred outside the EU/EEA with explicit consent.

Innovation Solution

A system and method for processing restricted-access data using a centralized database for non-restricted data and local systems with federated databases to provide a unified view, ensuring compliance with local data privacy laws by routing requests based on user associations and storing restricted data locally, thus preventing its storage in centralized databases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is stored in a centralized database for global processing, then data accessibility and global integration are improved, but compliance with local data privacy laws deteriorates

Engineering Contradiction:

Improveglobal data processing capabilityVSAvoidcompliance with data privacy laws

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The database system is segmented into multiple distributed data centers across different geographical regions, each operating autonomously while being part of the global system. This allows data to be processed globally through the distributed network while remaining physically located in compliant jurisdictions, thus maintaining both global integration and legal compliance.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A distributed coordination layer acts as an intermediary between global processing requirements and local data storage constraints. This coordination mechanism enables queries and processing operations to span multiple data centers while ensuring data remains stored in legally compliant locations, mediating between global accessibility needs and local privacy law requirements.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If restricted-access data is stored locally in separate databases, then data privacy compliance is improved, but system complexity and data integration difficulty worsen

Engineering Contradiction:

Improvedata privacy complianceVSAvoiddistributed database system complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The distributed data center architecture provides universal functionality by implementing a standardized framework that simultaneously handles data storage, privacy compliance, global processing, and coordination across multiple locations. This multi-functional system reduces overall complexity compared to implementing separate specialized systems for each function.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

All data centers in the distributed system follow homogeneous architectural patterns, data models, and access protocols. This uniformity across distributed locations simplifies integration and reduces system complexity, making the distributed system as manageable as a centralized system while maintaining data locality for compliance.

Inventive Principle:

Principle #33Homogeneity

3Reliability

If multiple user IDs and APIs are required to access different databases, then data security and access control are improved, but ease of operation and user convenience deteriorate

Engineering Contradiction:

Improveaccess control securityVSAvoiduser access convenience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system implements a universal authentication and access control mechanism that works across all distributed data centers through a common interface. Users authenticate once and gain appropriate access to relevant data across the distributed system, eliminating the need for multiple user IDs and APIs while maintaining security through centralized access policies.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Multiple access control mechanisms and authentication systems across different data centers are merged into a unified access control framework. This consolidation maintains the security benefits of access control while providing users with a single, convenient interface to access their data across the entire distributed system.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS9317697B2Processing of restricted access data

Publication Date: 2016.04.19 FINJAN BLUE INC

AI summary

Embodiments related to processing of restricted-access data. An aspect includes receiving a request for data from a user by a storage system infrastructure comprising a centralized database that stores non-restricted access data and a local system that stores restricted-access data associated with a first set of areas or entities and comprising a federated database for providing a federated view, wherein the requested data comprises restricted-access first data and non-restricted access second data. Another aspect includes based on an association of the user, routing, by a routing entity, the request to the local system. Another aspect includes receiving the request at the at least one federated database of the local system. Another aspect includes retrieving from the federated database the restricted-access first data and the non-restricted access second data. Another aspect includes displaying the federated view comprising the restricted-access first data and the non-restricted access second data to the user.