Dynamic MME Selection via DNS Pointer Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 4G and 5G wireless networks, mobility management entities (MME) and access and mobility management functions (AMF) are constrained by static Tunnel Network Layer (TNL) connections, leading to service disruptions during failures or planned maintenance in cloud-centric deployments, as alternate MME/AMF instances in different cloud regions have different IP addresses and TNL links.
Innovation Solution
Implementing a dynamic configuration of connectivity between base stations and MME/AMFs using a service registry and discovery mechanism, such as a Domain Name Server (DNS) or repository device, to update database pointers based on network maintenance, outages, and instance additions/deletions, ensuring service continuity by identifying available MME/AMFs for user equipment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If static TNL connections are used between base stations and MME/AMF instances, then network configuration is simple and stable, but service continuity is disrupted during failures or maintenance in cloud-centric deployments
Solution Approach 1:
The patent implements dynamic connectivity configuration where the base station maintains multiple TNL connection parameters to different MME/AMF instances and dynamically selects which connection to use based on current network conditions, instance availability, and load status. This allows the system to adapt to failures and maintenance events automatically, resolving the contradiction between static configuration simplicity and service continuity reliability
Solution Approach 2:
The patent introduces a network function that acts as an intermediary between the base station and MME/AMF instances, managing the selection and switching of connectivity paths. This intermediary handles the complexity of dynamic configuration and selection logic, allowing the base station to maintain service continuity without directly managing the complexity of multiple TNL connections
2Reliability
If alternate MME/AMF instances are deployed in different cloud regions for redundancy, then service reliability is improved, but connectivity management becomes complex due to different IP addresses and TNL links
Solution Approach 1:
The patent implements a universal connectivity management mechanism that handles multiple MME/AMF instances across different cloud regions through a unified interface and selection procedure. The base station uses a standardized process to select among alternate instances regardless of their location or specific TNL parameters, making the system easier to operate while maintaining service availability across multiple regions
Solution Approach 2:
The patent dynamically changes TNL connection parameters (such as selected instance IP address and connection state) based on the current operational status of MME/AMF instances. Instead of manually configuring each connection, the system automatically adjusts parameters like the active instance selection and TNL link states in response to network conditions, simplifying connectivity management while maintaining reliability
Data Source
AI summary
A first network device determines a first pointer value associated with a first management instance that includes at least one of network access or mobility management functions for user equipment (UE) interaction with a wireless network. The first network device installs, at a second network device, the first management instance, along with the first pointer value. The first network device changes the first pointer value in response to a first event associated with the wireless network or one or more other networks. The first pointer value is used for selecting at least one management instance, among a plurality of management instances that include the first management instance, for servicing wireless service requests from UEs to the wireless network.


