DNS Domain Failover Using Backup Data Center Replicas

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud service providers face challenges in seamlessly integrating separate identity management systems for IaaS and SaaS/PaaS services, leading to unsatisfactory customer experiences and obstacles in service interactions, and there are inefficiencies in data center failover processes that cause significant delays in user transfer during data center unavailability.

Innovation Solution

Implementing an integrated identity management platform that transparently combines IAM and IDCS systems, and utilizing DNS addresses to automatically redirect users to backup data centers with replicated domains for faster failover, minimizing service disruption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If legacy approaches of transferring a user to another data center are used, then service availability is maintained, but the transfer time is significant and causes service disruption

Engineering Contradiction:
Improveservice availabilityVSAvoidtransfer time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-establishing backup data centers with replicated domains before any failure occurs. When a data center becomes unavailable, the system can immediately redirect users to the pre-prepared backup data center, eliminating the time-consuming transfer process of legacy approaches while maintaining service availability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses an intermediary mechanism in the form of a unified DNS-based address that abstracts the underlying data center location. This intermediary address automatically resolves to the appropriate data center (primary or backup), enabling seamless user redirection without requiring users to be explicitly transferred, thus reducing transfer time while maintaining reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If separate identity management systems (IAM and IDCS) are used for IaaS and SaaS/PaaS services, then service specialization is achieved, but integration complexity increases and customer experience deteriorates

Engineering Contradiction:
Improveservice specializationVSAvoidsystem integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges separate identity management systems (IAM for IaaS and IDCS for SaaS/PaaS) into a unified identity management platform. This consolidation maintains the specialized functionality of each system while eliminating integration complexity, allowing seamless cross-service authentication and improving customer experience without sacrificing service specialization.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal identity management platform that can handle authentication and authorization across multiple service types (IaaS, SaaS, PaaS) through a single system. This multi-functional approach replaces multiple specialized systems, reducing integration complexity while maintaining adaptability to different service requirements.

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

Data Source

PatentUS12468609B2Failover of domains
Publication Date: 2025.11.11 ORACLE INT CORP
  • US12468609B2 patent drawing
  • US12468609B2 patent drawing
  • US12468609B2 patent drawing

AI summary

An approach of performing data center failover using an address that indicates a backup data center. The address includes common names indicating a data center with a domain and a backup datacenter with a replica of the domain. A cloud service provider can receive the address, establish a connection with an available data center, and failover to the backup data center if the data center with the connection becomes unavailable.