Asymmetric Computational Challenge for Batch Request Restriction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for restricting batch requests, such as anti-brush techniques, are ineffective due to ease of bypass and high false blocking rates, particularly with the advancement of machine intelligence, and often inconvenience legitimate users, especially with verification codes and SMS-based authentication.

Innovation Solution

A method and apparatus where a server poses a calculation question requiring more computing resources from the terminal than itself, ensuring legitimate terminals can complete the task without significant resource consumption, while malicious batch requests are hindered by increased resource demands, avoiding the limitations of prior authentication methods.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If verification codes or SMS authentication are used to restrict batch requests, then the reliability of restricting batch operations is improved, but the ease of operation deteriorates due to additional user steps and inconveniences

Engineering Contradiction:
Improvereliability of restricting batch operationsVSAvoidease of operation for legitimate users
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies asymmetry by designing calculation questions that require asymmetric computational effort between the server and terminal. The terminal must perform complex calculations (e.g., cryptographic operations, large number factorization, or resource-intensive algorithms) that are computationally feasible for individual users but prohibitively expensive for automated batch programs. This creates an asymmetric barrier that legitimate users can overcome with minimal effort while batch requests are effectively blocked.

Inventive Principle:
Principle #4Asymmetry

Solution Approach 2:

The patent substitutes mechanical authentication systems (verification codes, SMS) with a computational challenge system. Instead of relying on message-based authentication that requires user interaction and incurs communication costs, the system uses computational questions that leverage the terminal's processing capabilities. This replacement eliminates the need for additional user steps and communication infrastructure while maintaining security.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Ease of manufacture

If network layer restrictions such as access frequency control are implemented, then the ease of manufacture and deployment is improved, but the reliability deteriorates due to high false blocking rates and ease of bypass

Engineering Contradiction:
Improveease of deployment of restrictionsVSAvoidreliability of restricting batch operations
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent introduces a computational challenge as an intermediary between the request and the service. Instead of directly blocking requests at the network layer based on IP or frequency, the system inserts a verification step where the terminal must solve a calculation question. This intermediary layer filters out batch requests while allowing legitimate traffic to pass through, eliminating false blocking and bypass issues inherent in network-layer approaches.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameter of restriction from network-layer parameters (IP address, request frequency, HTTP headers) to computational parameters (calculation question complexity, resource consumption). This parameter transformation makes the restriction system more reliable because computational challenges cannot be easily spoofed or bypassed like network parameters, while still being solvable by legitimate users with normal hardware capabilities.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If batch registration programs execute parallel operations to register thousands of users, then the productivity of the attack is improved, but the computing resources consumed by legitimate services deteriorates

Engineering Contradiction:
Improveproductivity of batch operationsVSAvoidcomputing resources consumed
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent creates asymmetric computational requirements where legitimate single-user operations consume minimal resources while batch operations are blocked. The calculation question is designed to be computationally intensive enough to prevent parallel batch processing but light enough for individual users to complete quickly. This asymmetry allows the system to maintain high productivity for legitimate services while effectively limiting the impact of batch attacks.

Inventive Principle:
Principle #4Asymmetry

Solution Approach 2:

The patent converts the potential harm of computational resource consumption into a benefit for security. By designing the calculation question to require significant computational effort, the system creates a natural barrier that protects against batch requests. The computational challenge itself becomes the security mechanism, transforming what could be seen as a resource burden into an effective defense that automatically adapts to the capabilities of requesting systems.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

Data Source

PatentUS10366223B2Methods and apparatus for restricting batch requests for service
Publication Date: 2019.07.30 BEIJING JINGDONG SHANGKE INFORMATION TECH CO LTD
  • US10366223B2 patent drawing

AI summary

The present invention provides a method and apparatus for restricting batch requests for a service, facilitating restriction on requesting the service in batch and contributing to overcome some deficiencies in the prior art. The method comprises: receiving, by a server, service request information sent by a terminal (S11); sending, by the server, a calculation problem to the terminal, the question requiring a larger amount of computing recourses of the terminal than that of the server (S12); receiving, by the server, a calculation result of the calculation question from the terminal (S13), and verifying the calculation result (S14), and if the calculation result is correct, providing the service to the terminal (S15), otherwise, rejecting to provide the service to the terminal (S16).