PFCP Session Load Balancing for Low-Latency MEC Packet Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional 5G cellular data communication networks incur increased latency due to the requirement of routing packets through a user plane function (UPF) before redirecting them to an alternate MEC server, which is inefficient and increases packet transmission time.
Innovation Solution
Implementing a PFCP proxy and translation modules that bypass the UPF by directly routing packets between gNodeB and an SRv6 network, utilizing translation modules to convert between GTP and SRv6 protocols, and employing a routing/SDN controller to optimize packet redirection paths.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If packets are routed through the UPF for redirection to an alternate MEC server, then protocol compatibility and network architecture compliance are maintained, but packet transmission latency increases
Solution Approach 1:
The patent introduces a translation module as an intermediary component between the gNodeB and UPF. This translation module performs protocol translation between GTP and SRv6, enabling direct routing while maintaining compatibility with the existing UPF-based architecture. The intermediary handles the protocol conversion necessary for the UPF to understand and process SRv6 encapsulated packets, thus resolving the contradiction between maintaining protocol compatibility and reducing latency.
Solution Approach 2:
The patent segments the packet routing function by introducing a separate translation module that handles protocol conversion. This segmentation allows the main data path to be optimized for speed (direct routing via SRv6) while the translation module handles the compatibility requirements separately. The segmentation of functions enables parallel processing where possible and optimizes the critical data transmission path.
2Loss of time
If direct routing between gNodeB and MEC servers is implemented using SRv6, then packet transmission latency is reduced, but device complexity increases due to protocol translation requirements
Solution Approach 1:
The patent merges the translation module functionality with existing network infrastructure components. The translation module is integrated into the network architecture in a way that combines protocol translation capabilities with existing routing and forwarding functions. This merging approach reduces overall system complexity by consolidating functions rather than adding separate independent components.
Solution Approach 2:
The translation module is designed with multi-functionality to handle various protocol translation scenarios. It can translate between GTP and SRv6, and is capable of handling different types of packet redirection scenarios. This universality reduces the need for multiple specialized components, thereby reducing overall device complexity while maintaining the ability to handle diverse translation requirements.
3Reliability
If packets are redirected through the UPF to an alternate MEC server, then network control and routing management are maintained, but network efficiency and productivity decrease
Solution Approach 1:
The patent implements preliminary action by pre-configuring the translation module with routing information and protocol translation rules. The translation module is pre-programmed with the necessary information to perform protocol conversion and routing decisions, reducing the need for real-time complex processing. This preliminary preparation enables faster packet forwarding while maintaining routing control, thus improving network efficiency without sacrificing reliability.
Data Source
AI summary
Importing of a UE address into a VRF of perimeter equipment is facilitate by receiving a VPN update from the perimeter equipment including a route target of the perimeter equipment and a gNodeB address. In addition, session information is obtained by intercepting traffic between the UE address and a UPF. The session information including the UE address and address of a gNodeB to which the UE is connected. By matching the gNodeB addresses from the VPN update and the session information, the route target of the perimeter equipment to which the UE is connected may be determined. The UE address may then be imported exclusively into the VRF of the perimeter equipment.