Subscriber-Aware Network Address Filtering via RPC Framework
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network address filtering techniques consume excessive resources and fail to effectively filter different sets of blacklisted network addresses for different subscribers, leading to erroneous provision of blacklisted traffic and network outages.
Innovation Solution
Implementing subscriber-aware network address filtering using an open configuration RPC framework, which allows for specific blacklists to be requested and managed for each subscriber, enabling precise blocking or allowing of traffic based on individual blacklists.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a common network address database is used for all subscribers, then device complexity is reduced, but filtering precision deteriorates because different subscribers cannot have different blacklist sets
Solution Approach 1:
The patent segments the common network address database into multiple subscriber-specific blacklist sets, where each subscriber has their own dedicated blacklist. This allows the system to maintain individualized filtering rules for each subscriber while still using a unified database structure managed by the network device.
Solution Approach 2:
The patent applies local quality by allowing different subscribers to have different blacklist contents and filtering characteristics. Each subscriber's traffic is filtered against their specific blacklist, enabling localized filtering precision for each subscriber while maintaining a centralized database structure.
2Measurement precision
If subscriber-specific blacklists are implemented, then filtering precision is improved, but resource consumption increases due to managing multiple separate blacklist sets
Solution Approach 1:
The network device is designed with multi-functionality to serve multiple subscribers simultaneously, managing multiple blacklist sets and filtering traffic for different subscribers in a unified manner. This universal design allows the system to handle subscriber-specific filtering without requiring separate dedicated resources for each subscriber.
Solution Approach 2:
The patent merges the management of multiple subscriber-specific blacklists into a single unified database structure. By combining all blacklist sets into one centralized database that the network device manages, the system reduces the overhead of managing multiple separate databases while still maintaining the ability to apply individualized filtering rules.
3Measurement precision
If subscriber-specific blacklists are implemented, then traffic filtering accuracy is improved, but device complexity increases due to managing multiple blacklist subscriptions
Solution Approach 1:
The patent segments the blacklist management function into subscriber-specific portions, where each subscriber has their own blacklist set that can be independently managed and updated. This segmentation allows the network device to handle each subscriber's filtering requirements separately while maintaining an organized overall structure.
Solution Approach 2:
The network device implements a universal blacklist management mechanism that handles multiple subscribers' blacklists through a unified interface and process. This multi-functional approach allows the same database structure and management logic to serve all subscribers, reducing the complexity that would arise from implementing completely separate management systems for each subscriber.
Data Source
AI summary
A network device may provide a request for blacklists specific to respective subscribers. The network device may receive a first blacklist of network addresses associated with a first subscriber and a second blacklist of network addresses associated with a second subscriber. The network device may receive first traffic associated with a first network address and destined for the first subscriber, and may determine whether the first network address is included in the first blacklist. The network device may prevent the first traffic from being provided to the first subscriber when the network address is included in the first blacklist, or may allow the first traffic to be provided to the first subscriber when the network address is not included in the first blacklist.