Service-Based Network Session Failover for Repository Outages

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing wireless communication systems face significant downtime due to repository and database interruptions, which current technologies fail to effectively mitigate, leading to prolonged network disruptions.

Innovation Solution

Implement a system and method that utilize a primary network component and backup network component, along with a primary and backup database, to maintain communication sessions and provide backup routing and configuration information, ensuring seamless operations even during interruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single repository and database are used to store routing and configuration information, then the system structure is simple, but the network experiences large periods of downtime when the repository or database is interrupted

Engineering Contradiction:

Improvenetwork availabilityVSAvoidsystem structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements local quality by allowing different network components to have different configurations - primary components use the primary repository/database while backup components use the backup repository/database. This enables the system to maintain operational quality even when one repository or database is interrupted, as components can switch to their respective backup counterparts without requiring complete system restructuring.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent applies preliminary action by pre-configuring both primary and backup repositories and databases before any interruption occurs. The backup infrastructure is established in advance with all necessary routing and configuration information, so that when an interruption happens, the system can immediately switch to the backup without delay for setup or configuration, thereby reducing downtime.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If backup network components and databases are implemented to prevent interruptions, then network reliability improves, but the system complexity increases

Engineering Contradiction:

Improverepository and database availabilityVSAvoidnumber of network components

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements copying by creating backup network components and databases that replicate the functionality and data of the primary components. These copies maintain synchronized routing and configuration information, enabling seamless failover when the primary system fails. The copying approach ensures that backup components are ready to immediately assume operational responsibilities without requiring complex real-time synchronization mechanisms during failure events.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent applies segmentation by dividing the single-point-of-failure repository/database system into segmented primary and backup infrastructure components. This segmentation isolates failures to specific segments (primary or backup), preventing cascading failures across the entire system. Each segment operates independently with its own repository and database, allowing the system to maintain partial or full functionality even when one segment is interrupted.

Inventive Principle:

Principle #1Segmentation

3Productivity

If the system waits for repository or database recovery before resuming operations, then data consistency is maintained, but productivity decreases due to prolonged downtime

Engineering Contradiction:

Improvenetwork operation continuityVSAvoiddowntime duration

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent implements continuity of useful action by enabling the network system to maintain operational continuity through backup components when primary components fail. Instead of halting operations to wait for repository or database recovery, the system continuously operates using backup infrastructure, ensuring that network services remain available. This approach maintains productivity by eliminating idle downtime while data consistency is preserved through synchronized backup configurations.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS12549433B2System and method to reduce network function interruptions in a service-based architecture

Publication Date: 2026.02.10 BOOST SUBSCRIBERCO LLC

AI summary

An apparatus is configured to communicate with multiple network components in a service-based architecture and comprises a memory and a processor. The memory stores multiple configuration commands. The processor is configured to generate a request to establish a communication session between a first network component, a second network component, and a third network component. The first network component exchanges connectivity signals with the second network component and the third network component. The second network component performs first plurality of session operations in response to the connectivity signals exchanged with the first network component. The second network component reports to the third network component that the first session operations are performed. The processor is further configured to, in response to determining that the communication session between the first network component and the second network component is lost, maintain the communication session between the first network component and the third network component.