Decentralized Control Plane for Mobile Gateway Session Anchoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile networks face scalability issues in handling increasing numbers of concurrent communication sessions due to centralized control plane architectures, which can lead to bottlenecks and reduced efficiency in managing subscriber sessions.
Innovation Solution
A decentralized control plane architecture is implemented within a mobile gateway device, where subscriber session management is offloaded to a set of service units, allowing dynamic load balancing and eliminating the need for a central entity to manage session requests, thereby increasing scalability and responsiveness.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a centralized control plane architecture is used to manage subscriber sessions, then session management control is simplified and centralized, but scalability is limited and bottlenecks occur when handling increasing numbers of concurrent communication sessions
Solution Approach 1:
The control plane is segmented into multiple independent service units (SU1, SU2, SU3, etc.), each capable of autonomously managing subscriber sessions. This segmentation distributes the session management workload across multiple units, eliminating the single-point bottleneck of centralized architecture while maintaining standardized control functions. Each service unit can independently process session requests, enabling linear scalability as session demands increase.
Solution Approach 2:
The patent transitions from a single-dimensional centralized control model to a multi-dimensional distributed control architecture. By introducing multiple service units operating in parallel across different dimensional spaces within the gateway, the system achieves scalability without proportionally increasing physical gateway resources. This dimensional expansion allows the network to handle exponentially more concurrent sessions.
2Productivity
If more service units are added to handle increasing session requests, then scalability improves, but device complexity and coordination overhead increase
Solution Approach 1:
Each service unit is designed with universal, standardized interfaces and identical functional capabilities. All service units implement the same session management protocols and can independently perform authentication, authorization, and session control functions. This universality eliminates the need for complex coordination mechanisms, as any service unit can handle any subscriber session request without requiring specialized knowledge or inter-unit communication for task allocation.
Solution Approach 2:
Service units operate autonomously with self-service capabilities, independently processing session requests without requiring centralized coordination or inter-unit communication. Each unit maintains its own session state and management logic, eliminating coordination overhead. The system achieves scalability through this self-service model where adding service units simply increases capacity without introducing management complexity.
3Reliability
If session requests are distributed among multiple service units, then load balancing improves and no single point of failure exists, but session request routing complexity increases
Solution Approach 1:
All service units are designed to be homogeneous with identical interfaces, capabilities, and operational characteristics. This homogeneity simplifies the routing mechanism, as session requests can be distributed to any service unit without requiring complex load-balancing algorithms or unit-specific routing logic. The standardized interface allows simple round-robin or hash-based distribution strategies that maintain low routing complexity while achieving excellent load balancing and reliability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In general, techniques are described for decentralizing handling of subscriber sessions within a gateway device of a mobile network. A mobile network gateway comprises a data plane having a plurality of forwarding components to receive session requests from a mobile service provider network in which the mobile network gateway resides. A control plane comprises a plurality of distributed subscriber management service units coupled by a switch fabric to the data plane. Each of the subscriber management service units serve as anchors for communication sessions for mobile devices that are accessing one or more packet data network by the mobile service provider network. A request delegation module within each of the forwarding components directs the session requests to the subscriber management service units unit to provide management services for the sessions requested by the mobile device.