Region-Restricted Data Storage Routing for Low-Latency Queries

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage systems face challenges in managing data resources with region restrictions, leading to increased latency and inefficiency when querying data resources stored across multiple geographical regions.

Innovation Solution

A server system with a manager function that stores a list of geographical regions where data can be stored, based on region-restrictions, and routes query requests to the correct storage centers, ensuring compliance with data location restrictions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data resources are stored across multiple storage centres in different geographical regions, then storage capacity and availability are improved, but query latency increases due to the need to fan out requests to multiple locations

Engineering Contradiction:
Improvestorage capacityVSAvoidquery latency
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The manager function pre-determines and stores the geographical region where each data resource is located before query requests are made. This preliminary indexing allows the system to directly route queries to the correct storage centre without fan-out, reducing query latency while maintaining distributed storage capacity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The manager function acts as an intermediary between query requests and storage centres. It receives query requests, uses pre-stored region information to determine the correct storage centre, and routes requests accordingly, eliminating the need for clients to fan out requests to multiple storage centres

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data resources with region restrictions are stored only in specific geographical regions, then compliance with region restrictions is ensured, but system complexity increases due to the need to track and manage regional constraints

Engineering Contradiction:
Improvecompliance with region restrictionsVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The manager function serves multiple purposes: it manages the list of geographical regions, determines appropriate storage locations for incoming data resources based on region restrictions, and routes query requests to correct storage centres. This multi-functionality reduces the need for separate specialized components, managing complexity while ensuring compliance

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

3Device complexity

If query requests are routed directly to storage centres without centralized management, then system simplicity is maintained, but efficiency decreases due to inability to honor region-restrictions effectively

Engineering Contradiction:
Improvesystem simplicityVSAvoidquery efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The manager function is introduced as a lightweight intermediary that maintains a simple list of geographical regions and uses it to route queries efficiently. This adds minimal complexity while dramatically improving productivity by ensuring queries are routed directly to the correct storage centre without fan-out

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12368777B2Managing data resources
Publication Date: 2025.07.22 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12368777B2 patent drawing
  • US12368777B2 patent drawing

AI summary

A method comprising: storing, in a database, a list of geographical regions in which the party consents to their data being stored; receiving a request to store data of the party, wherein at least one of the data has a region-restriction that restricts the regions in which that data can be stored; determining, based on a respective region-restriction of a respective one of the data, in which of the list of regions the respective data can be stored; storing the data, wherein each respective data is stored in at least one respective storage centre associated with one of the regions according to the determination; storing, in the database, a list comprising a pointer to each respective stored data, wherein the pointer identifies the respective storage centre; receiving a request to retrieve a respective stored data; and using the pointer to route the request to the respective storage centre.