Cloud Datacenter Selection via Sovereignty-Aware Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Cloud computing networks face challenges in supporting data sovereignty policies, as existing routing techniques like Anycast and multicast are not configured to determine routing decisions based on data sovereignty requirements or geographic locations of network servers, leading to potential non-compliance when handling sensitive data.

Innovation Solution

Implementing techniques within the cloud computing network to identify client data sovereignty requirements and redirect requests to geographically compliant datacenters, allowing servers to compare their location with client policies and migrate sessions to compliant datacenters if necessary, ensuring compliance while maintaining performance and reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If Anycast routing technique is used to route client requests to the nearest datacenter, then network performance and load balancing are improved, but data sovereignty compliance cannot be ensured

Engineering Contradiction:

Improvenetwork performanceVSAvoiddata sovereignty compliance

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

The patent introduces DNS servers as intermediary components that mediate between client requests and datacenters. These DNS servers receive client requests, determine the appropriate datacenter based on both geographic proximity and data sovereignty requirements, and route requests accordingly. This intermediary layer resolves the contradiction by adding a decision-making step that considers both performance and compliance factors.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements dynamic routing where the selected datacenter changes based on real-time conditions including client location, data sovereignty requirements, and datacenter capacity. The system dynamically adjusts routing decisions rather than using static geographic-based routing, allowing it to adapt to different compliance requirements while maintaining performance optimization.

Inventive Principle:

Principle #15Dynamics

2Productivity

If datacenters are geographically distributed to improve service performance, then network efficiency is enhanced, but ability to comply with jurisdictional data sovereignty policies deteriorates

Engineering Contradiction:

Improveservice performanceVSAvoiddata sovereignty policy compliance

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the cloud service network into multiple geographically distributed datacenters, each capable of providing services independently. This segmentation allows the system to maintain high performance through geographic distribution while enabling compliance with different data sovereignty policies by routing requests to appropriate segmented locations based on client requirements.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent makes the datacenter network universal by designing it to serve multiple functions: geographic proximity optimization, data sovereignty compliance, and load balancing. The same distributed infrastructure supports both performance goals and compliance requirements through intelligent routing, making the system adaptable to different policy requirements without sacrificing performance.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Loss of time

If routing decisions are based solely on geographic proximity, then network latency is reduced, but compliance with client-specific geographic restrictions cannot be determined

Engineering Contradiction:

Improvenetwork latencyVSAvoidgeographic restriction compliance

Core Design Contradiction:

Loss of timeVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements preliminary action by having DNS servers determine compliance requirements before routing requests to datacenters. The system预先 identifies data sovereignty requirements and uses this information to pre-determine appropriate datacenter selections, ensuring compliance is checked before the request is fulfilled, thus preventing latency issues from compliance violations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent incorporates feedback mechanisms where DNS servers continuously monitor client locations, data sovereignty requirements, and datacenter statuses. This feedback loop allows the system to adjust routing decisions in real-time, balancing latency optimization with compliance requirements by using updated information about client geographic restrictions and datacenter capabilities.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS11799948B2Cloud service datacenter selection based on data sovereignty policies

Publication Date: 2023.10.24 CISCO TECHNOLOGY INC

AI summary

Cloud services are provided by a distributed network including a number of geographically distributed datacenters, to client devices in accordance with data sovereignty requirements. A server within the distributed network may receive a service request and determine whether it complies with the data sovereignty requirements of the client. When the geographic location of the server does not comply with the client's data sovereignty requirements, the server may determine and transmit back to the client device a set of alternative datacenters within the distributed network that comply with the client's data sovereignty requirements. The client device may use network probes to select an alternative datacenter, and the cloud service request of the client device may be migrated from the server to the selected datacenter.