Web Service Call Limiter for Distributed Server Enforcement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the field of web services, it is challenging to effectively limit access to subscribers based on contractual terms when using distributed data centers or server locations, as it is difficult to enforce agreed-upon service request limits across multiple geographic server locations.

Innovation Solution

Implementing a rate limiter at each server location to monitor and enforce per-subscriber web services call limits, with the ability to intercept and manage API calls, decrement counters, and facilitate lease transactions between server locations to manage and distribute service requests according to contractual limits.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If distributed data centers are used to deliver web services, then service availability and coverage are improved, but it becomes difficult to enforce contractual service request limits across multiple server locations

Engineering Contradiction:
Improveservice delivery capabilityVSAvoidcontractual limit enforcement
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments the call limiting function by deploying independent rate limiters at each server location, allowing local enforcement of call limits while maintaining overall contractual compliance across the distributed system

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A provisioning server acts as an intermediary to distribute call limits to various server locations and to coordinate lease transactions between rate limiters, enabling centralized control over distributed resources

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If call limits are enforced at each server location independently, then contractual compliance is improved, but service distribution flexibility and resource utilization deteriorate

Engineering Contradiction:
Improvecontractual limit complianceVSAvoidservice distribution flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The provisioning server mediates between independent rate limiters, coordinating lease transactions that allow servers to borrow available calls from each other while maintaining overall contractual compliance

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Rate limiters continuously monitor available calls and communicate with the provisioning server and peer servers, enabling dynamic adjustment of service distribution based on real-time resource availability

Inventive Principle:
Principle #23Feedback

3Speed

If service requests are allowed to proceed without verification, then processing speed is improved, but subscribers may exceed their contractual call limits

Engineering Contradiction:
Improverequest processing speedVSAvoidcall limit enforcement
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The rate limiter performs preliminary verification of subscriber call limits before processing service requests, checking available calls and enforcing limits in advance to prevent overuse

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

For authenticated subscribers with verified available calls, the rate limiter skips detailed verification and allows requests to proceed rapidly, maintaining high throughput for compliant users

Inventive Principle:
Principle #21Skipping (Rushing through)

Data Source

PatentUS7908363B2Call limiter for web services
Publication Date: 2011.03.15 R2 SOLUTIONS LLC
  • US7908363B2 patent drawing
  • US7908363B2 patent drawing
  • US7908363B2 patent drawing

AI summary

Embodiments of methods, apparatuses, devices and systems associated with web services are disclosed. In a particular implementation, web services calls from one or more subscribers to a first server location may be tracked. One or more other server locations may be contacted to determine whether additional web services calls for the at least one of the one or more subscribers are available in response to at least one of the one or more subscribers reaching an established subscriber limit.