Mobile-Terminated Packet Routing with Dynamic Gateway Reselection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 3GPP LTE systems face challenges in managing mobile-terminated packet transmissions due to inflexible network load adaptation, leading to delays and reduced quality of service when boundary data gateways fail, become overloaded, or when stringent latency requirements are not met.
Innovation Solution
A software-defined network (SDN)-based architecture separates control plane signaling and user plane data interfaces, allowing a centralized SDN controller to dynamically reconfigure data gateways based on real-time network load, ensuring seamless mobile-terminated packet transmission by maintaining IP address allocation and preserving service continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a traditional 3GPP LTE system is used with fixed boundary data gateways, then network architecture stability is maintained, but network load adaptation flexibility deteriorates
Solution Approach 1:
The patent segments the network architecture by introducing a centralized SDN controller that separates control plane functions from user plane functions. The boundary data gateways are divided into multiple instances that can be independently managed and dynamically selected based on network conditions, allowing flexible load adaptation without requiring complex changes to the entire network architecture.
Solution Approach 2:
The SDN controller acts as an intermediary between the network core and boundary data gateways. It receives service flow information, determines appropriate gateways based on current network load, and directs traffic accordingly. This intermediary layer provides adaptability while keeping the overall architecture relatively simple and manageable.
2Reliability
If multiple boundary data gateways are deployed for load balancing, then network reliability improves, but signaling overhead increases
Solution Approach 1:
The system performs preliminary actions by pre-establishing service flow information and gateway selection criteria in the SDN controller before actual data transmission occurs. When a service flow arrives, the controller has already determined the appropriate boundary data gateway, eliminating the need for additional signaling during data transmission and reducing overall signaling overhead.
Solution Approach 2:
The boundary data gateways are configured to self-identify and self-manage based on instructions from the SDN controller. Once the controller assigns a gateway to a service flow, the gateway autonomously handles the data transmission without requiring continuous signaling or coordination with other gateways, thereby reducing signaling overhead while maintaining reliability through multiple available gateways.
3Reliability
If dynamic gateway reconfiguration is implemented, then quality of service improves, but network control complexity increases
Solution Approach 1:
The SDN controller is designed as a universal network control entity that handles multiple functions including service flow information reception, gateway selection, path determination, and dynamic reconfiguration. By consolidating these diverse control functions into a single multi-functional controller, the system improves quality of service through dynamic adaptation while avoiding the complexity that would arise from distributing these functions across multiple specialized components.
Data Source
AI summary
Methods, apparatus circuitry, and storage media are described for mobile-terminated packet transmissions. In one embodiment, an apparatus of a control plane device configured to operate within an evolved packet network core identifies a first service flow event trigger associated with a first packet data unit (PDU) session and processes a path reselection for a first PDU session in response to the first service flow event trigger, wherein the path reselection determines a new gateway for the first PDU session resulting from the path reselection. Transmission of a change notification to an application server controller associated with the first PDU session is initiated in response to the path reselection. Transmission of a routing update to the new gateway in response to the path reselection is also initiated. In various embodiments, the trigger may be a mobility event, a load balancing event, or operations in association with an application server controller.