Service-Based Database Failover for Continuous Network Repository Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies fail to provide reliable solutions to reduce or prevent repository and database interruptions in wireless communication systems, leading to significant downtime and disruptions in network operations.
Innovation Solution
The system and method integrate a network component performing a Network Repository Function (NRF) with a backup component and a database with a backup database, enabling automatic establishment of backup communication sessions and access to backup routing and configuration information in case of interruptions, thereby minimizing downtime.
Engineering Contradictions & Design Principles
Engineering 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
Solution Approach 1:
The patent implements local quality by allowing different network components to have different levels of data storage capability. Specifically, some network components store routing and configuration information locally in their own databases, while others rely on the central repository. This differentiation enables components to continue operating with locally stored information when the central repository or database is interrupted, thereby improving network reliability without requiring complete system redundancy
Solution Approach 2:
The patent applies segmentation by dividing the centralized repository and database system into multiple distributed database instances across different network components. Each database instance stores a subset or copy of the routing and configuration information, allowing the system to segment the failure impact. When one repository or database is interrupted, other segments remain operational, preventing complete network downtime while maintaining a relatively simple overall architecture
2Reliability
If backup components and databases are implemented to prevent interruptions, then network availability is improved, but the system complexity increases
Solution Approach 1:
The patent implements copying by creating duplicate copies of the repository and database across multiple network components. Specifically, backup repositories and backup databases are established that contain copies of the routing and configuration information. When the primary repository or database is interrupted, network components can automatically switch to accessing the copied data in the backup systems, ensuring continuous operation. This copying approach provides reliable failover while keeping the backup system structure relatively simple by using identical data formats and structures
Solution Approach 2:
The patent applies preliminary action by pre-configuring backup repositories and databases with routing and configuration information before interruptions occur. The backup systems are established in advance and continuously updated with current network data, so that when a failure occurs, the switch to backup components can happen immediately without requiring data reconstruction or system reconfiguration. This preliminary preparation reduces the complexity of the failover process while ensuring high reliability
Data Source
AI summary
An apparatus is communicatively coupled to a plurality of databases 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 in which a network component accesses a first database and a second database based at least in part upon a configuration command of the configuration commands. The network component exchanges connectivity signals with the first database and the second database. The first database provides database operations in response to the connectivity signals exchanged with the network component. The first database reports to the second database that the database operations are provided. The processor is further configured to, in response to determining that the communication session between the network component and the first database is lost, maintain the communication session to access the second database.