RAN Gateway Context Binding for SDN Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network architectures for mobile networks face challenges in efficiently managing data traffic growth, particularly in integrating sophisticated gateway functions like charging and policy control, which are not adequately addressed by existing solutions that split control and user plane functions, leading to high implementation barriers and costs.
Innovation Solution
An apparatus and method that bind uplink and downlink bearers to an internet protocol address based on a gateway context controlled by a control device, incorporating buffering, handover supervision, context building, and enforcement mechanisms, allowing for centralized control of gateway functions without the need for specialized hardware, and enabling software-defined networking (SDN) based transport networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If gateway functions are split into control plane and user plane with specialized hardware, then network functionality is enhanced, but device complexity and implementation costs increase
Solution Approach 1:
The patent segments gateway functions into control plane functions (performed by controller 40) and user plane functions (performed by gateway device 30). The control plane handles signaling, policy control, and charging, while the user plane handles data forwarding. This segmentation allows enhanced functionality while managing complexity through clear separation of concerns.
Solution Approach 2:
The patent introduces a control device as an intermediary between the gateway device and network elements. The control device manages gateway context, performs policy control, and coordinates charging functions, allowing the gateway device to focus on user plane operations while maintaining sophisticated control capabilities through the intermediary control plane entity.
2Reliability
If specialized mobile gateway nodes are deployed, then network performance is improved, but cost efficiency deteriorates
Solution Approach 1:
The gateway device 30 is designed to perform multiple functions including data forwarding, buffering during handover, and supporting both LIPA and non-LIPA traffic. By making the gateway device multi-functional rather than requiring specialized nodes for each function, the patent achieves good network performance while improving cost efficiency through resource consolidation.
Solution Approach 2:
The gateway device autonomously performs user plane operations including data buffering during hard handover, local IP address assignment for LIPA traffic, and context management. This self-service capability reduces the need for centralized control for every operation, improving performance while reducing the complexity and cost of specialized gateway nodes.
3Adaptability or versatility
If control and user plane are separated with SDN architecture, then network flexibility is improved, but ease of manufacture deteriorates due to redesign requirements
Solution Approach 1:
The patent implements SDN architecture by segmenting control plane functions (in controller 40) from user plane functions (in gateway device 30). The control plane uses OpenFlow protocol to dynamically program the user plane, providing network flexibility while using standardized interfaces that reduce implementation barriers compared to complete redesigns.
Solution Approach 2:
The patent reuses existing SGW and PGW software components in the gateway device 30, adapting them for SDN-based operation rather than requiring complete redesign. This copying and adaptation approach maintains network flexibility while significantly reducing implementation costs and barriers by leveraging proven software components.
Data Source
AI summary
It is provided a method, comprising binding, for a terminal, at least one of an uplink and a downlink bearer to an IP address based on a gateway context, wherein the gateway context is controlled by a control device; and at least one of buffering and idle mode handling; wherein the buffering is adapted to buffer data for the terminal during hard handover of the terminal and to forward the data to the terminal after the hard handover is completed; the idle mode handling is adapted to forward a packet received for the terminal to a control device if the gateway context does not comprise an identification of a base station to which the terminal is attached.