Edge Light Mobile Core for Low-Latency Traffic Offload
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile core deployments in 4G and 5G networks are resource-intensive and costly, leading to higher latencies and reduced quality of experience due to centralized traffic routing, which is detrimental for latency-critical applications and requires frequent bandwidth re-dimensioning.
Innovation Solution
A light mobile core architecture that deploys only P-GW functionality at the edge node, offloads traffic at the RAN level, and supports Control and User Plane Separation (CUPS) with IP interfaces, utilizing a processor and memory unit with application awareness algorithms to manage traffic offloading and policy enforcement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If centralized mobile core deployment is used, then network control and management is simplified, but latency increases and resource requirements increase
Solution Approach 1:
The mobile core is segmented into distributed edge nodes deployed at multiple locations (e.g., base stations, edge data centers) rather than a single centralized core. Each edge node independently handles local traffic, reducing the distance data must travel and eliminating centralized bottlenecks, thereby reducing latency while maintaining manageable complexity through standardized modules
Solution Approach 2:
Local edge nodes are deployed at specific locations close to users to handle local traffic with minimal latency. Each node provides tailored services to local users based on local conditions, while the overall system maintains consistency through standardized protocols. This allows low latency for local traffic without requiring complete system reconfiguration
2Device complexity
If centralized mobile core deployment is used, then network infrastructure is simplified, but resource consumption increases and bandwidth requirements increase
Solution Approach 1:
The core network is divided into multiple independent edge nodes that can be deployed selectively based on traffic distribution. This segmentation allows resources to be allocated only where needed, reducing overall resource consumption compared to a monolithic centralized core that must accommodate peak demands everywhere simultaneously
Solution Approach 2:
Instead of deploying full mobile core functionality at every possible location, the system deploys edge nodes partially at strategic locations where traffic requires local handling. This partial deployment reduces resource consumption while providing sufficient capacity for latency-critical and locally-intensive traffic patterns
3Reliability
If traffic is routed through centralized core, then network security and control are maintained, but quality of experience deteriorates for latency-critical applications
Solution Approach 1:
The network is segmented into distributed edge nodes that maintain local control and security functions while reducing traffic routing distance. Each edge node independently secures and controls local traffic, maintaining reliability through distributed trust while improving quality of experience by eliminating centralized routing delays
Solution Approach 2:
Edge nodes act as intermediary elements between users and the centralized core, handling security and control functions locally while maintaining connectivity to the core for broader network management. This intermediary layer preserves quality of experience by processing traffic locally while still enabling centralized security and control through selective core connectivity
Data Source
AI summary
Described herein is a method and system for communication in an edge network that interconnects with eNodeB (4G) (108) or gNB (5G) (116). A light mobile core with an IP interface interconnects the edge network with eNodeB (4G) (108) or gNB (5G) (116). Mobile traffic is offloaded at the edge either fully or partially, rather than have the full data ripple through the entire 4G or 5G network to one of the following: Internet, MEC (Multi-Access Edge Compute) platform or a specialized edge cache or edge compute node. The system maintains conformance with 3GPP standards and does not disrupt the S1 interface between eNodeB (108) and EPC (Evolved Packet Core) in 4G networks, and does not disrupt the N3 interface between gNB and core in 5G networks. The system described herein provides the full functionality of 4G or 5G mobile core, and comprises control plane and data plane components.


