PMIPv6 Mobility Management for Private LTE Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Private LTE/5G networks face challenges in mobility management due to the need for complex 3GPP radio and Evolved Packet Core functions designed for service-oriented architectures, which are not suitable for enterprise wireless services, leading to unnecessary features and inefficiencies in enterprise deployments.
Innovation Solution
Implementing a Proxy Mobile Internet Protocol version 6 (PMIPv6) mobility management system that establishes a 3GPP data plane between user equipment and gateway devices, and a PMIPv6 data plane between gateway and anchor devices, allowing for interworking with LTE/5G networks, thereby eliminating the need for Mobility Management Entities (MME) and Access and Mobility Management Functions (AMF) by mapping Non-Access Stratum (NAS) signaling to PMIPv6 protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If 3GPP EPC functions (MME, SGW, PGW) are deployed for private LTE/5G networks, then mobility management and core network services are provided, but system complexity and deployment difficulty increase significantly
Solution Approach 1:
The patent extracts and removes unnecessary EPC functions (MME, SGW, PGW) from the private network deployment, keeping only the essential mobility management capabilities through PMIPv6. This extraction principle directly addresses the contradiction by eliminating complex components while preserving core functionality.
Solution Approach 2:
The PMIPv6 infrastructure acts as a universal mobility management solution that can serve multiple private networks and different access technologies (LTE, 5G, Wi-Fi) through a common protocol framework. This multi-functionality reduces the need for separate EPC deployments for each network, thereby reducing overall system complexity.
2Adaptability or versatility
If full EPC/5GC elements are deployed for enterprise wireless service, then complete 3GPP service-oriented architecture is implemented, but features and functions become unnecessary and inefficient for enterprise context
Solution Approach 1:
The patent extracts only the necessary mobility management functions from the complete EPC/5GC architecture, implementing them through PMIPv6. This selective extraction removes unnecessary service-oriented architecture components while maintaining essential mobility capabilities, directly improving deployment simplicity.
Solution Approach 2:
Instead of implementing the standard 3GPP service-oriented architecture and then adapting it for enterprise use, the patent inverts the approach by using PMIPv6 (designed for access-technology agnostic mobility) to provide mobility management in enterprise networks. This inversion eliminates the need to adapt complex EPC features for enterprise contexts.
3Reliability
If MME and AMF functions are retained for mobility management, then 3GPP protocol compliance is maintained, but operational simplicity and efficiency are reduced
Solution Approach 1:
The PMIPv6 protocol acts as an intermediary between the access networks (eNodeB, gNB) and the core network, handling mobility management functions that would otherwise require MME/AMF. This intermediary approach maintains protocol compliance while simplifying operations by eliminating the need for complex 3GPP mobility management entities.
Data Source
AI summary
A first data plane is established between a user equipment device and a gateway device, wherein the user equipment device comprises a 3rd Generation Partnership Project (3GPP) user equipment device, and wherein the first data plane comprises a 3GPP data plane. A second data plane is established between the gateway device and an anchor device, wherein the second data plane comprises a Proxy Mobile Internet Protocol version 6 (PMIPv6) data plane. Mobility management is performed for the user equipment device via communications between the gateway device and the anchor device.