gNB-DU Multi-Connection Architecture for 5G Resilience
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing architecture for gNB-DU apparatuses, where each gNB-DU is connected to only one gNB-CU, leads to significant service disruptions when the connected gNB-CU fails, affecting all users under its coverage.
Innovation Solution
Implementing a method where the gNB-DU apparatus communicates with multiple gNB-CU-CP apparatuses, allowing for failover and load balancing. This includes detecting failures of primary gNB-CU-CPs and seamlessly switching to backup gNB-CU-CPs within the gNB-CU-CP pool or using backup gNB-CU-CPs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a gNB-DU is connected to only one gNB-CU, then the device complexity is reduced and ease of operation is improved, but the reliability deteriorates because all gNB-DUs enter out of service state when the connected gNB-CU fails
Solution Approach 1:
Multiple gNB-CU-CP apparatuses are merged into a pooled architecture where they collectively serve multiple gNB-DUs. The gNB-DU maintains connections to multiple gNB-CU-CPs simultaneously, combining their resources to provide redundant service coverage and ensure continuity when one gNB-CU-CP fails.
Solution Approach 2:
The system changes the connection parameter from single-gNB-CU to multiple-gNB-CU-CP connections. By modifying the connection topology parameter and enabling multi-homing, the system achieves improved reliability while managing complexity through standardized connection procedures.
2Reliability
If a gNB-DU connects to multiple gNB-CU-CP apparatuses, then the reliability is improved through failover capability, but the device complexity increases
Solution Approach 1:
The system performs preliminary actions by pre-establishing connections to multiple gNB-CU-CP apparatuses and pre-configuring failover relationships before any failure occurs. This allows the gNB-DU to have backup connections ready, eliminating the need for complex real-time decision-making during failure events.
Solution Approach 2:
The gNB-DU autonomously manages its connections to multiple gNB-CU-CPs by automatically detecting failures and switching to backup connections without requiring complex external coordination. The system implements self-healing through automatic failure detection and reconnection procedures.
3Loss of time
If backup gNB-CU-CPs are implemented, then the loss of time during failure recovery is reduced, but the device complexity increases due to additional apparatuses
Solution Approach 1:
The gNB-CU-CP apparatuses in the pool are designed with multi-functionality, where each apparatus can serve as both a primary and backup connection for different gNB-DUs. This universal design allows the same physical apparatus to fulfill multiple roles, reducing the total number of dedicated backup units needed.
Solution Approach 2:
The system creates logical copies of connection states and configurations across multiple gNB-CU-CP apparatuses. When a primary gNB-CU-CP fails, the gNB-DU can rapidly switch to a backup by utilizing pre-synchronized connection state copies, minimizing recovery time without requiring complete physical redundancy.
Data Source
AI summary
This disclosure proposes solutions for providing a resiliency of gNB-CU against possible node failures. The node failure includes unexpected system reset, system rebooting, system stall, system congestion and communication failure with neighboring nodes.A method of a gNB Distributed Unit (gNB-DU) apparatus includes communicating with a User Equipment, and communicating with a plurality of a gNB Centralized Unit Control Plane (gNB-CU-CP) apparatuses.