Layered Database Backup for Telecom Read Availability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing cellular network data repositories face challenges in achieving extremely high read availability (99.99999%) due to inflexible and difficult-to-implement customized configurations, making it hard to scale and upgrade.

Innovation Solution

A high read availability system utilizing a layered database architecture with a primary, hot backup, and tepid backup database, asynchronously replicating data across logically linked yet physically separate layers, ensuring data availability through a novel backup scheme that leverages standard SQL servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If customized repository solutions are used to meet 99.99999% read availability, then reliability is improved, but device complexity and difficulty of implementation increase

Engineering Contradiction:

Improveread availabilityVSAvoidcustom configuration complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The database system is segmented into multiple independent instances distributed across different sites, each capable of operating autonomously. This segmentation allows the system to achieve high read availability through redundancy without requiring complex custom configurations, as each segment can fail independently without affecting others.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Standard SQL servers are used instead of customized repository solutions, making the system more universal and easier to implement. The same standard database technology serves multiple functions (primary database, hot backup, tepid backup) across different sites, reducing configuration complexity while maintaining 99.99999% read availability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If customized repository solutions are used to meet 99.99999% read availability, then reliability is improved, but ease of manufacture and implementation deteriorates

Engineering Contradiction:

Improveread availabilityVSAvoidimplementation ease

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

Multiple copies of the database are created and distributed across different sites, with each copy being a standard SQL server instance. This copying approach maintains high read availability through redundancy while simplifying implementation, as standard database technologies can be deployed without custom programming or configuration.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system changes the operational parameters by using asynchronous replication and multiple backup tiers (hot backup, tepid backup) with standard SQL servers. This allows achieving 99.99999% read availability through parameter configuration rather than custom implementation, improving ease of manufacture and deployment.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If large data repositories are customized to meet 99.99999% read availability, then reliability is improved, but adaptability and scalability deteriorate

Engineering Contradiction:

Improveread availabilityVSAvoidflexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The database architecture is made dynamic by allowing flexible deployment configurations across multiple sites with different replication strategies. The system can adapt to various operational scenarios (single site failure, multi-site failure, maintenance operations) while maintaining high read availability, improving both reliability and adaptability.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system adds a spatial dimension by distributing database instances across multiple physical sites, and a temporal dimension through asynchronous replication and multiple backup tiers. This dimensional expansion allows the system to achieve high read availability without sacrificing adaptability, as the distributed architecture can accommodate various deployment scenarios.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS20260056843A1Providing extremely high read availability in a telecommunication environment

Publication Date: 2026.02.26 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

The present disclosure generally relates to providing extremely high read availability for data repositories within a telecommunication network. Systems described herein implement a novel architecture and backup scheme in connection with non-customized data servers to provide at least 99.99999% read availability within a telecommunication network. In one or more examples, the novel architecture includes a primary database and hot backup database that mirrors the primary database. Additionally, the novel architecture further includes a tepid backup database that stores asynchronous snapshot replications of the primary database that are sent to the tepid backup database out-of-band. In the event of a cascading failure that affects the primary database and the hot backup database, the best snapshot replication stored by the tepid backup database is initialized to service a read request that would otherwise have failed.