Dynamic MME Selection for M2M Traffic Segregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional access networking and core networking technologies face challenges in handling the growing connectivity demands of machine-to-machine (M2M) devices, particularly in establishing faster connections on demand and during outage or disaster situations, leading to communication failures and poor customer satisfaction due to overwhelming instantaneous loads on Mobility Management Entities (MMEs).
Innovation Solution
The system implements a dynamic control plane node selection mechanism that allows eNodeBs to intelligently select the most suitable MME based on data exchanged during device attachment and internal mapping, avoiding static NAS layer re-routing and pre-provisioning, thereby optimizing control plane device allocation and routing for M2M traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If M2M devices attach to eNodeB and communicate with MME using conventional procedures, then devices can connect to the network, but the serving MME cannot handle large instantaneous loads from growing volumes of M2M devices, resulting in communication failures
Solution Approach 1:
The patent segments M2M traffic from conventional traffic by introducing a dedicated M2M IP gateway that handles M2M device connections separately. This segmentation allows M2M devices to attach to the network through a specialized pathway, preventing the serving MME from being overwhelmed by large volumes of M2M attachment requests while maintaining reliable connectivity for these devices.
2Adaptability or versatility
If the network uses static NAS layer re-routing and pre-provisioning for M2M devices, then device connectivity can be established, but the system cannot adapt dynamically to changing network conditions, outages, or disaster situations
Solution Approach 1:
The patent introduces an M2M IP gateway as an intermediary component between M2M devices and the core network. This gateway dynamically routes M2M traffic based on current network conditions, MME availability, and disaster recovery requirements, eliminating the need for complex static pre-provisioning while providing adaptive routing capabilities that respond to changing network states.
Solution Approach 2:
The system implements dynamic routing where the M2M IP gateway continuously monitors network conditions and adjusts MME selection in real-time. This dynamic approach allows the network to adapt to outages, disaster situations, and varying load conditions without requiring complex pre-configured static routing tables, simplifying the overall system while maintaining high adaptability.
3Reliability
If all M2M devices are routed through the same serving MME, then the network architecture remains simple, but communication failures occur during outage or disaster situations when certain network elements may recover from failure after interruptions
Solution Approach 1:
The patent implements local quality by creating a specialized M2M IP gateway with specific functionality dedicated to M2M traffic handling. This gateway provides localized intelligence for M2M device management, including dynamic MME selection and disaster recovery capabilities, while leaving the rest of the network architecture unchanged. This approach enhances network resilience for M2M services without requiring complex changes throughout the entire network.
Solution Approach 2:
The M2M IP gateway acts as an intermediary that provides disaster recovery capabilities by monitoring MME health and dynamically switching M2M device connections to alternative MMEs when failures occur. This intermediary layer absorbs the complexity of resilience mechanisms, protecting the rest of the network from needing complex changes while ensuring continuous M2M service availability during outages and disaster situations.
Data Source
AI summary
Control plane devices are selected by an access point for establishment of end-to-end control plane for a user equipment (UE) coupled to (or requesting to couple to) the access point. In one aspect, the selection is based on data extracted during the setup and/or registration messages communicated between the access point and UE during attachment of the UE to the access point and/or an internal derived mapping of the control pane devices to the access point. In one example, a control plane device pool is segregated to and different sets of control plane devices are selected and utilized to handle traffic associated with different services to improve scaling and flexibility.


