Split SGW PDN-GW Architecture for Mobile Edge Computing Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional LTE network architecture limits the placement of cloudlets or compute servers close to the Radio Access Network (RAN) due to user traffic being carried over GTP and UDP tunnels, preventing dynamic switching of traffic to locally deployed MEC Servers, which is costly and requires changes to eNodeBs and 3GPP standards.
Innovation Solution
Splitting Serving Gateways (SGWs) and Packet Data Network Gateways (PDN-GWs) to provision resources for local deployment of data-plane entity instances at the RAN edge, using a dedicated bearer to route traffic through split SGs and PDNs, and configuring the bearer with an IP address of cloudlets for efficient access to MEC applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If user traffic is carried over GTP and UDP tunnels between eNodeB and SGW, then traffic routing is standardized and reliable, but dynamic switching of traffic to locally deployed MEC servers is prevented
Solution Approach 1:
The patent introduces a local gateway as an intermediary device deployed at the RAN edge that mediates between the GTP tunnel-based core network and locally deployed MEC servers. This local gateway can dynamically switch traffic between the tunnel and local servers without requiring changes to the standardized GTP protocol or existing eNodeB/SGW implementations, thus resolving the contradiction between routing flexibility and network complexity.
2Adaptability or versatility
If eNodeB and SGW implementations are changed to incorporate local traffic offload, then traffic can be dynamically switched to MEC servers, but deployment costs increase and 3GPP standard changes are required
Solution Approach 1:
The local gateway serves as a standalone intermediary that provides traffic offload capability without requiring modifications to existing eNodeB or SGW implementations. This approach avoids expensive hardware changes and 3GPP standard modifications, instead introducing a separate, deployable component that achieves the same functional goal at lower cost.
Solution Approach 2:
The patent segments the traffic routing function by separating it from the core GTP tunnel infrastructure and placing it in a dedicated local gateway at the RAN edge. This segmentation allows the core network to remain unchanged while enabling local offload capabilities independently, reducing deployment complexity and cost.
3Loss of time
If cloudlets are deployed locally at RAN edge, then latency is reduced for MEC applications, but resource provisioning becomes complex without standardized support
Solution Approach 1:
The local gateway acts as a standardized intermediary that simplifies resource provisioning by providing a uniform interface between the core network and diverse local MEC resources. It handles the complexity of resource allocation, authentication, and traffic management locally, reducing provisioning complexity while maintaining low latency access to cloudlet resources.
Data Source
AI summary
Systems and methods for standards compatible Mobile Edge Computing (MEC), including splitting Serving gateways (SGWs) and Packet Data Network gateways (PDN-GWs) to provision sufficient resources to deploy data-plane entity instances locally at a Radio Access Network (RAN) edge with one or more cloudlets. One or more local controller nodes is deployed in one or more operator clouds, a dedicated bearer is leveraged to route traffic from the one or more cloudlets through the split SGWs and PDN-GWs, and the dedicated bearer is configured with a traffic flow template (TFT) including an Internet Protocol (IP) address of the one or more cloudlets. Efficient access to one or more MEC applications at the RAN edge is provided to one or more user devices using the dedicated bearer.