API Request Throttling for Merchant Service Resource Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Merchant service providers face resource overload and delays in processing higher priority tasks due to excessive requests from merchant applications, which can be caused by malfunctions or denial-of-service attacks, leading to reduced revenue and system responsiveness.
Innovation Solution
Implementing a throttling system that allows merchants to set limits on the number of requests through an API, with a centralized server detecting and alerting on excessive call rates, enabling the service provider to throttle or deny lower priority requests and maintain resource allocation for higher priority tasks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a merchant application generates a large number of requests for data or functions from the merchant service provider, then the merchant can access more services and data, but the merchant service provider experiences delays or errors in performing higher priority processing tasks
Solution Approach 1:
The patent segments request processing by priority levels, dividing the monolithic request queue into multiple priority-based queues. High-priority requests (e.g., payment transactions) are processed separately from low-priority requests (e.g., report generation), ensuring that excessive low-priority requests do not block critical high-priority processing while still allowing both types of requests to be handled.
Solution Approach 2:
The patent implements dynamic request throttling that adjusts the rate at which requests are processed based on current system conditions. When the system detects excessive request volumes or resource constraints, it dynamically limits the throughput of low-priority requests while maintaining normal processing of high-priority requests, thereby adapting to changing load conditions and preventing system overload.
2Adaptability or versatility
If the merchant service provider processes all requests without limitation, then service completeness is maintained, but system resources are overwhelmed and higher priority tasks suffer
Solution Approach 1:
The patent applies different processing qualities and resource allocations to different request types based on their priority. High-priority requests receive preferential treatment with dedicated resources and faster processing, while low-priority requests are subject to throttling and resource constraints. This local differentiation ensures critical services maintain high throughput while less critical services are limited, preventing overall system overload.
Solution Approach 2:
The patent changes the processing parameters (such as request rate limits, queue depths, and resource allocation ratios) dynamically based on system conditions. When resource utilization exceeds thresholds, the system adjusts parameters to reduce low-priority request processing while maintaining high-priority request handling capacity, thereby optimizing overall productivity without completely blocking any service category.
3Productivity
If request limits are imposed on merchant applications, then resource allocation for higher priority tasks is preserved, but the merchant may experience service disruptions due to malfunctions or attacks
Solution Approach 1:
The patent implements a feedback mechanism where the merchant service provider monitors request patterns and system resource utilization in real-time. When unusual patterns are detected (such as sudden spikes indicating attacks or malfunctions), the system adjusts throttling parameters and sends notifications to the merchant. This feedback loop allows the system to respond adaptively to problems while maintaining resource protection, balancing productivity preservation with service continuity.
Solution Approach 2:
The patent establishes pre-configured request limits and throttling parameters before excessive requests occur. These preliminary constraints are set based on historical data and service level agreements, allowing the system to automatically enforce resource protection without waiting for overload conditions to develop. This preliminary action prevents resource exhaustion while providing predictable service behavior.
Data Source
AI summary
Systems, apparatuses and methods for preventing requests to access a system's resources from having a negative impact on higher priority data processing operations being performed by the system. The invention is directed to preventing the number of calls made by a merchant's applications through an application programming interface (API) for access to the lower priority services of a merchant service provider from having a negative impact on the ability of the service provider to perform the processing necessary to support higher priority services. The invention provides a user interface that may be used by a merchant or the service provider to configure the operation of a “throttle” that is designed to generate an alert when the number of calls by a merchant application for access to a specific service provider function or application exceeds a value or limit, where exceeding the value or limit may indicate a malfunction of the merchant's application or an attack by a malicious agent.