Network Service Request Throttling via Intermediary Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network service environments face challenges in efficiently throttling access to network services to prevent denial of service attacks, ensure fair resource allocation, and manage bandwidth and computing resource usage across disparate locations.
Innovation Solution
A request throttling system that includes a request throttling server and client, which enforce throttling policies to grant or deny access to network services based on parameters such as client identity, IP address, and request rates, utilizing a management system to store and manage throttling policies and usage data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network services are made accessible to multiple clients over the network, then service availability and connectivity are improved, but the system becomes vulnerable to denial of service attacks and resource exhaustion
Solution Approach 1:
The patent introduces a request throttling server as an intermediary component between clients and network services. This mediator monitors and controls request rates, filtering out excessive requests before they reach the network services, thereby preventing denial of service attacks while maintaining service availability for legitimate clients
Solution Approach 2:
The system performs preliminary throttling actions by evaluating request rates against predefined thresholds before requests are processed by network services. The throttling server proactively identifies and blocks potential denial of service attacks in advance, preventing resource exhaustion before it occurs
2Reliability
If request throttling policies are enforced to prevent denial of service attacks, then system security and resource protection are improved, but request processing time and system complexity increase
Solution Approach 1:
The throttling server implements partial throttling by applying rate limiting only to requests that exceed predefined thresholds, while allowing requests within acceptable ranges to pass through with minimal or no additional processing time. This selective approach maintains security without unnecessarily delaying legitimate requests
Solution Approach 2:
The system employs self-service mechanisms where the throttling server automatically monitors request rates, compares them against thresholds, and enforces policies without requiring manual intervention. This automated approach reduces processing overhead compared to manual security checks
3Productivity
If request throttling is implemented to manage resource usage, then resource allocation efficiency is improved, but device complexity and implementation cost increase
Solution Approach 1:
The request throttling server is designed as a universal component that can serve multiple network services and handle various types of requests through a single implementation. This multi-functional approach consolidates throttling logic into one system rather than requiring separate throttling mechanisms for each service, thereby reducing overall system complexity
Solution Approach 2:
The system manages complexity by using configurable parameters such as request rate thresholds and time windows that can be adjusted without changing the underlying throttling logic. This parameter-based approach allows flexible resource management while maintaining a simple, consistent throttling mechanism
Data Source
AI summary
Disclosed are various embodiments for throttling requests for a network service. A request for a network service is received from a client application and parameters are extracted from the request. Throttling policies applicable to the parameters are identified and retrieved, and it is determined whether the request should be processed based at least upon the throttling policies and the request parameters.