Subscriber-Aware Disaggregator for Multi-IP Traffic Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing disaggregators are incapable of directing network traffic based on multiple IP addresses assigned to a single subscriber, leading to challenges in managing and enforcing network policies effectively.
Innovation Solution
A network traffic management system that maps network addresses to a subscriber database, identifies a master network address, and routes network packets to a determined processing node based on this address, aggregating traffic from multiple IP addresses into a single thread for effective policy enforcement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If existing disaggregators direct network traffic based on a single source or destination IP address to a single thread, then traffic management is simplified, but subscribers with multiple IP addresses cannot be properly managed or have policies enforced
Solution Approach 1:
The patent introduces a subscriber database as an intermediary layer between the disaggregator and the thread pool. This database stores the mapping relationship between multiple IP addresses and a single subscriber identifier, allowing the system to first resolve IP addresses to subscriber IDs, then route traffic to appropriate threads. This intermediary mechanism enables both simplified thread-based processing and proper multi-IP subscriber management.
Solution Approach 2:
The system performs preliminary action by pre-establishing the mapping relationships between multiple IP addresses and subscriber identifiers in a subscriber database before traffic arrives. When traffic needs to be routed, the disaggregator queries this pre-built mapping to determine the correct thread, eliminating the need for complex real-time decisions and enabling efficient policy enforcement for multi-IP subscribers.
2Productivity
If network traffic from multiple IP addresses is distributed to different threads, then load balancing is improved, but policy enforcement consistency for a single subscriber deteriorates
Solution Approach 1:
The subscriber database acts as a mediator that translates between IP address-based traffic and subscriber identifier-based policy enforcement. By resolving multiple IP addresses to a single subscriber ID before thread assignment, the system ensures that all traffic from a subscriber's multiple IP addresses is consistently routed to the same thread, maintaining policy enforcement reliability while still achieving load balancing across the thread pool.
Solution Approach 2:
The patent applies local quality by making the thread assignment dependent on the specific subscriber's characteristics (their multiple IP addresses) rather than treating all traffic uniformly. Each subscriber's traffic pattern is locally optimized by mapping their specific set of IP addresses to a consistent thread, while the overall system maintains global load balancing through the distributed thread pool architecture.
Data Source
AI summary
Methods, network traffic management apparatuses, non-transitory computer readable media, and network traffic management systems that control network traffic with a subscriber-aware disaggregator include mapping a network address in a network packet received from a client to one of a plurality of subscribers in a subscriber database. A master network address for the one of the subscribers is identified from the mapped network address, where the subscriber has at least one other network address associated with the one of the subscribers. The network packet is routed to a determined one of a plurality of processing nodes and processing threads based on the master network address for the one of the subscribers.