5G Hybrid Routing With Active-Standby Cluster Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional routing systems in next-generation networks like 5G face challenges in managing distinct deployment scenarios and functionalities of nodes, leading to data flow disruptions and inefficiencies, particularly when nodes are down or unavailable.
Innovation Solution
A system and method that enables hybrid routing by using a controller to manage PLMN clusters, determining active and inactive endpoints, and routing requests through secondary clusters when primary endpoints are inactive, while facilitating load balancing and traffic monitoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional routing systems are used in 5G networks, then network simplicity is maintained, but data transmission reliability deteriorates when nodes are down or unavailable
Solution Approach 1:
The system performs preliminary actions by pre-establishing backup routing paths and identifying alternative nodes before primary nodes fail. The controller proactively discovers and stores alternative routing information, so when a node goes down, the system can immediately switch to pre-planned backup paths without complex real-time calculations, thus improving reliability while managing complexity.
Solution Approach 2:
The controller acts as an intermediary between source and destination nodes, managing the complexity of hybrid routing centrally. It monitors node status, determines whether to use primary or alternative paths, and makes routing decisions based on node availability. This central mediation simplifies the overall system by consolidating routing intelligence in one component rather than distributing complex logic across all nodes.
2Reliability
If hybrid routing with primary and alternative paths is implemented, then data transmission reliability is improved, but routing decision complexity increases
Solution Approach 1:
The system pre-identifies and stores alternative routing paths and candidate nodes before they are needed. By performing discovery and path planning in advance, the system avoids complex real-time decision-making when failures occur, reducing the operational complexity of managing hybrid routing while maintaining high reliability through pre-prepared backup paths.
Solution Approach 2:
The routing system incorporates self-service mechanisms where the controller automatically monitors node status, detects failures, and switches to alternative paths without human intervention. The system self-manages the complexity of hybrid routing through automated status determination and path selection, reducing the burden of manual routing management while ensuring communication continuity.
3Productivity
If multiple PLMN clusters are pre-mapped for routing, then data path optimization is improved, but network configuration complexity increases
Solution Approach 1:
The system pre-maps multiple PLMN clusters and establishes alternative routing paths in advance, creating a prepared network topology that enables rapid path selection. By configuring multiple potential paths beforehand, the system optimizes data transmission efficiency when failures occur, as the controller can immediately select from pre-established paths without complex real-time configuration, thus improving productivity while managing configuration complexity through advance planning.
Data Source
AI summary
The present disclosure pertains to a system that enables hybrid routing with active and standby instances. A request from sites apart from Nagpur site is obtained at 702, and that from Nagpur site is obtained at 706. Then, it is checked at 704, whether any endpoint is active. If so, the request is transmitted to primary cluster 710. However, if no endpoint is active, then at 708, it is checked whether the request is from the Nagpur. If so, then it is checked again, at 712, whether any endpoint is active. However, in case it is found, at the 708, the request is not from Nagpur, then it is fed to Nagpur DR cluster 720. Further, at the 712, if any endpoint is active, then the request is transmitted to Nagpur active cluster 730, but, if no endpoint is active, then the request is fed to DR for Nagpur 740.