3GPP Mobile Gateway Scaling via TEID Assignment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for scaling mobile gateways in 3GPP networks are inflexible, limited by resource binding, and face challenges with session migration during downtime or upgrades, often requiring complex external load-balancing mechanisms and adding significant parsing or protocol redundancy, which hinders scalability.
Innovation Solution
The system leverages software-defined networks (SDN) and network functions virtualization (NFV) to dynamically create or destroy gateway instances based on load, using TEID or IP routing for efficient forwarding of signaling and user data traffic, enabling independent scaling of user plane and signal processing with standardized protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If traditional gateway scaling methods are used, then network capacity can be increased, but system complexity and resource binding increase significantly
Solution Approach 1:
The patent segments the gateway functionality into virtualized network functions that can be independently deployed and scaled. By separating control plane and user plane functions, and using virtual gateway instances, the system can scale capacity without proportionally increasing overall system complexity. Each virtual gateway instance is an independent, standardized unit that can be managed individually.
Solution Approach 2:
The patent implements universal gateway virtual instances that can handle multiple types of traffic and services through standardized interfaces. The SDN controller provides centralized management that works across different gateway instances, creating a multi-functional system where a single architecture supports various network functions without requiring separate complex systems for each function.
2Adaptability or versatility
If external load-balancing mechanisms are added to enable scaling, then gateway flexibility improves, but protocol redundancy and parsing complexity increase
Solution Approach 1:
The SDN controller acts as an intermediary that manages gateway instances and traffic distribution through standardized protocols. Rather than adding complex external load-balancing mechanisms with proprietary protocols, the SDN controller uses standardized interfaces to orchestrate multiple gateway instances, reducing protocol redundancy while maintaining flexibility.
Solution Approach 2:
The patent changes the operational parameters of gateway instances by using virtualization to dynamically allocate resources and modify gateway behavior through software configuration rather than hardware changes. This allows flexible adaptation to different traffic patterns and service requirements without adding physical complexity or protocol overhead.
3Productivity
If gateway instances are dynamically created and destroyed, then network scalability improves, but session migration during downtime becomes more challenging
Solution Approach 1:
The SDN controller implements feedback mechanisms that track active sessions across gateway instances. When gateway instances are dynamically created or destroyed, the controller receives feedback about session states and automatically manages migration by redirecting traffic and updating routing tables, ensuring session continuity during scalability operations.
Solution Approach 2:
The system performs preliminary actions by pre-configuring session state information and routing rules in the SDN controller before gateway instances are destroyed or migrated. This allows seamless session migration because the controller already has the necessary information to redirect traffic to new gateway instances without interruption or data loss.
Data Source
AI summary
Particular embodiments described herein provide for a system that can be configured to initialize a gateway, assign a range of tunnel endpoint identifiers (TEID) to the gateway, where the range of TEIDs are associated with the gateway, and communicate the range of TEIDs to routers, where each TEID in the range of TEIDs is used to by the router to route packets to the gateway. In an example, the range of TEIDS associated with the gateway are assigned to the gateway when the gateway was initialized and the gateway assigns the TEID for the session.