Split gNB Architecture for NFV Lifecycle Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The management of next generation evolved Node B (gNB) within the Network Functions Virtualization (NFV) framework in 5G mobile communications networks is challenging due to the complexity of integrating virtualized and non-virtualized network functions, requiring efficient mechanisms for lifecycle management and quality of service assurance.
Innovation Solution
The implementation of a split architecture for gNB, where the central unit (CU) is virtualized and distributed units (DUs) are non-virtualized, with the use of Network Service (NS) update operations to add, remove, or replace DUs, and the incorporation of a bandwidth attribute in the Quality of Service (QoS) information element to support transport bandwidth requirements between CU and DU.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If gNB is fully virtualized as VNF, then network flexibility and resource utilization are improved, but control reliability and real-time performance deteriorate
Solution Approach 1:
The gNB is segmented into two distinct parts: CU (Central Unit) implemented as VNF for flexible resource utilization, and DU (Distributed Unit) implemented as PNF for reliable real-time control. This segmentation allows each part to be optimized for its specific function, resolving the contradiction between flexibility and reliability.
2Productivity
If gNB is fully virtualized as VNF, then resource utilization is improved, but latency and real-time control capability worsen
Solution Approach 1:
The gNB architecture separates control functions (DU as PNF) from resource management functions (CU as VNF). The DU handles time-critical real-time control with low latency, while the CU manages non-real-time resource allocation, thus resolving the latency issue while maintaining high resource utilization.
3Adaptability or versatility
If split architecture with CU-VNF and DU-PNF is implemented, then network flexibility is improved, but system complexity worsens
Solution Approach 1:
The system is divided into standardized CU and DU interfaces with well-defined protocols. This segmentation with clear interface boundaries simplifies the overall system complexity while maintaining flexibility, as each component can be independently managed and deployed.
Solution Approach 2:
The CU-VNF can be deployed as a universal virtualized component that can control multiple DU-PNF instances through standardized interfaces. This multi-functionality reduces system complexity by reusing the same CU software across different deployments.
4Ease of operation
If NS update operation is used to add/remove/replace DUs, then lifecycle management is improved, but operational complexity worsens
Solution Approach 1:
The NS update operation enables automated lifecycle management of DU-PNF instances. The system can automatically add, remove, or replace DUs through standardized update procedures, reducing manual operational complexity while improving ease of management.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
Network Functions Virtualization (NFV) abstracts network functions, allowing them to be installed, controlled, and manipulated by software running on standardized compute nodes such as cloud computing platform rather than on dedicated hardware. In a 5G mobile communications network, the base station or gNB may be split into virtualized and non-virtualized network functions (NFs). Described herein are systems and methods for managing such gNBs within the NFV framework.