gNB-CU-UP Bearer Context Modification for VM Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing communication systems, particularly in 5G networks, face challenges in context modification procedures for the E1 interface in gNBs, which are complex and lack a procedure to modify bearer contexts initiated by the user plane, leading to issues such as local problems and virtual machine migration.
Innovation Solution
A Bearer Context Modification procedure is introduced, allowing the gNB-CU-UP to initiate a Bearer Context Modification Required message to inform the gNB-CU-CP of necessary modifications, enabling dynamic resource scaling and virtual machine migration by updating UL and DL GTP Tunnel Endpoints, and utilizing a Software Defined Network switch for packet data unit revisions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the existing context modification procedure for E1 interface is used, then the control plane can modify bearer contexts, but the user plane cannot initiate modifications leading to local problems and inability to handle VM migration
Solution Approach 1:
The patent inverts the traditional control plane-initiated modification approach by enabling the user plane (gNB-CU-UP) to initiate context modifications. This is achieved through a new message flow where gNB-CU-UP sends modification requests to gNB-CU-CP, allowing the user plane to trigger necessary changes for VM migration and resource scaling without waiting for control plane initiation.
Solution Approach 2:
The patent segments the context modification procedure into distinct initiation paths: control plane initiation (existing) and user plane initiation (new). This segmentation allows each plane to independently trigger modifications based on its specific needs, with the user plane able to initiate changes for local problems and VM migration while the control plane handles other scenarios.
2Adaptability or versatility
If dynamic resource scaling and VM migration are implemented, then network adaptability improves, but transport overhead increases due to frequent context modifications
Solution Approach 1:
The patent implements preliminary action by establishing a direct user plane initiation mechanism that allows gNB-CU-UP to trigger context modifications proactively based on local conditions. This enables the system to prepare and execute resource scaling and VM migration operations before they become critical, reducing the frequency and overhead of reactive modifications.
3Reliability
If the gNB-CU-UP can initiate context modifications, then seamless operation during VM migration is achieved, but the complexity of the modification procedure increases
Solution Approach 1:
The patent introduces an intermediary message flow between gNB-CU-UP and gNB-CU-CP that mediates user plane initiation requests. The gNB-CU-CP acts as an intermediary that receives modification requests from the user plane, processes them appropriately, and coordinates the actual context changes, ensuring seamless operation while managing the complexity through structured communication.
Data Source
AI summary
Systems and methods of modifying the bearer context of a DRB of an E1 interface for a gNB are described. To modify the bearer context associated with a DRB for a particular UE, the gNB-CU-UP transmits a Bearer Context Modification Required message through the E1 interface and receives in response a Bearer Context Modification Confirm message that confirms the modification of the bearer context. The Bearer Context Modification Required message and Bearer Context Modification Confirm message both include the new GTP TEID and TNL address to be used after modification of the bearer context, a gNB-CU-CP UE E1AP ID that uniquely identifies a UE association over the E1 interface within the gNB-CU-CP, a gNB-CU-UP UE E1AP ID that uniquely identifies a UE association over the E1 interface within the gNB-CU-UP, and a DRB ID IE that uniquely identifies the DRB.