MME Relocation via External Control Node for Virtualized Core Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP specifications do not provide procedures for relocating mobility management and bearer management of mobile terminals between Mobility Management Entities (MMEs) initiated by the Evolved Packet Core (EPC) or external control nodes, such as Software-Defined Network (SDN) controllers, Network Function Virtualization (NFV) controllers, or Operations Support Systems (OSS), despite the growing demand for core network virtualization.
Innovation Solution
A method and device for relocating mobility management and bearer management of mobile terminals between network nodes, including transmitting a relocation command message from a control node to perform mobility management and bearer management relocation between MMEs, allowing for relocation regardless of the mobile terminal's movement, using a control node coupled with the core network to manage the process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If mobility management and bearer management are relocated between MMEs based on external control node commands, then network flexibility and adaptability are improved, but device complexity and control overhead increase
Solution Approach 1:
An external control node is introduced as an intermediary to manage MME relocation decisions. The control node receives relocation requests, selects appropriate target MMEs based on network conditions, and coordinates the relocation process between source and target MMEs, thereby improving network flexibility while centralizing control complexity outside the core MME architecture
Solution Approach 2:
The MME relocation mechanism is made dynamic by allowing real-time changes in MME assignments based on network conditions, load balancing requirements, and service demands. The system can dynamically relocate mobility management and bearer management contexts between different MMEs without requiring UE reattachment, enabling adaptive network resource allocation
2Productivity
If MME relocation is performed regardless of mobile terminal movement, then productivity and network efficiency are improved, but reliability and service continuity may be compromised
Solution Approach 1:
The source MME performs preliminary actions by preparing the relocation context information and selecting a suitable target MME before actually transferring the UE context. This includes pre-establishing necessary signaling paths and ensuring the target MME is ready to accept the relocation, thereby minimizing service disruption
Solution Approach 2:
The relocation process incorporates feedback mechanisms where the target MME confirms receipt of the UE context and validates its ability to continue service. The system monitors relocation success and can implement corrective actions if service continuity is compromised, ensuring reliable operation during dynamic MME changes
3Adaptability or versatility
If core network virtualization is implemented to support MME relocation, then adaptability and resource utilization are improved, but device complexity and implementation difficulty increase
Solution Approach 1:
The MME relocation framework is designed with universal interfaces and standardized procedures that can be implemented across different virtualization platforms and network architectures. The control node uses generic signaling messages and the MMEs follow standardized relocation protocols, making the solution applicable to various virtualized core network implementations without requiring platform-specific modifications
Solution Approach 2:
The MME functionality is segmented into relocatable context information and fixed infrastructure components. The mobility management and bearer management contexts are extracted as separable, transferable data structures that can be moved between virtualized MME instances, while the underlying virtualization infrastructure remains unchanged, simplifying implementation
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
A control node (142) used in connection with a core network (120) operates to transmit a relocation command message related to a first network node (121S) located in the core network (120) and performing mobility management and bearer management of a plurality of mobile terminals (111) that have attached to the core network (120). The relocation command message causes relocation, from the first network node (121S) to at least one second network node (121T), of the mobility management and the bearer management for at least one of the plurality of mobile terminals (111). This contributes, for example, to relocation of mobility management and bearer management of a plurality of mobile terminals between network nodes regardless of the movement of those mobile terminals.