Virtualized eNB Connectivity for Dynamic 5G–4G X2 Associations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in establishing efficient connectivity between virtualized 5G gNBs and 4G eNodeBs, particularly due to limitations when multiple ENBs share the same global eNB IDs, leading to increased connection overhead and complexity in managing X2 associations.
Innovation Solution
The implementation of a HetNet Gateway (HNG) that virtualizes BBUs and home eNodeBs over a standard S1 interface, establishing macro interfacing with an EPC, communicating with MME over the S1 interface for control plane signaling, and with SAEGW over a standard GTPU interface for data plane, thereby simplifying the mesh topology into a star topology and reducing connection overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple eNodeBs share the same global eNB IDs in virtualized environments, then resource utilization and flexibility are improved, but connection overhead and complexity of managing X2 associations increase
Solution Approach 1:
The patent introduces a Virtualized eNodeB (v eNB) manager as an intermediary entity that centralizes the management of X2 associations. This manager handles the complexity of establishing and maintaining X2 connections between multiple virtualized eNodeBs, abstracting away the individual connection management from each eNodeB instance. The intermediary coordinates X2 association setup, modification, and teardown operations, thereby reducing the overall system complexity while enabling flexible virtualization.
Solution Approach 2:
The patent segments the X2 association management function into separate modular components. Each virtualized eNodeB maintains only its essential local state and interfaces, while the management of inter-eNodeB associations is segmented into a centralized management plane. This segmentation allows independent scaling and management of virtualized instances without requiring each instance to manage all peer connections, thus reducing complexity.
2Speed
If direct X2 connections are established between all pairs of virtualized eNodeBs, then handover performance is improved, but the number of connections and overhead increase exponentially
Solution Approach 1:
The patent merges multiple virtualized eNodeBs that share common infrastructure or logical groupings into aggregated units or pools. Instead of establishing individual X2 connections between every pair of virtualized eNodeBs, the merger creates representative points or gateway eNodeBs that handle inter-group communications. This combining approach maintains handover capability while dramatically reducing the total number of X2 connections required, as connections are established at the aggregated level rather than at the individual virtualized instance level.
3Ease of operation
If virtualization technology is adopted for baseband processing, then ease of maintenance and configuration is improved, but network topology complexity increases
Solution Approach 1:
The patent introduces a virtualization manager or orchestration entity as an intermediary that handles the complexity of virtualized network topology. This intermediary manages the mapping between physical and virtual resources, handles configuration propagation, and maintains topology information. By centralizing these functions, the system gains the operational ease of virtualization (easy maintenance, flexible configuration) while the intermediary absorbs the topology complexity, preventing it from propagating throughout the entire network.
Data Source
AI summary
A method for establishing indirect and/or dual connectivity between virtualized 5G gENBs and virtualized 4G eNodeBs for dynamic X2 is disclosed. In one embodiment a method includes virtualizing, with a HetNet Gateway (HNG), BBUs and home eNodeBs over a standard S1 interface; establishing the HNG as a macro interfacing an EPC on 3GPP standard interfaces; communicating with an MME over the S1 interface for control plane signaling; and communicating with SAEGW over a standard GTPU interface for a data plane.