Request Filtration System for Downstream Load Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The sheer volume of content items on the internet makes it difficult for request processing systems to provide both timely and relevant content to users, often leading to bottlenecks and poor user experiences due to high request volumes and varying service throughput.

Innovation Solution

A request filtration system that filters requests before processing, using filters to eliminate non-relevant or fraudulent requests, thereby reducing the load on downstream services and ensuring timely and relevant content delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the request processing system processes all requests from content item exchanges, then comprehensive content delivery is achieved, but the system experiences bottlenecks and slow response times due to high request volumes

Engineering Contradiction:
Improverequest processing throughputVSAvoidresponse time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by filtering requests before they reach the downstream content delivery services. The filtering system pre-processes incoming requests, eliminating non-relevant or duplicate requests before they can consume resources in the main processing pipeline. This advance filtering reduces the burden on downstream services and prevents bottlenecks, directly addressing the contradiction between handling comprehensive requests and maintaining fast response times.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple services are used to select relevant content items, then content relevance is improved, but services with lower throughput create bottlenecks that slow down the entire system

Engineering Contradiction:
Improvecontent relevanceVSAvoidsystem throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts and removes requests that are unlikely to result in relevant content matches before they enter the multi-service content selection pipeline. By taking out non-relevant requests early in the process, the system maintains the benefit of using multiple specialized services for content matching while preventing these services from becoming bottlenecks due to excessive request volumes. This extraction approach preserves content relevance while improving overall system throughput.

Inventive Principle:
Principle #2Taking out (Extraction)

3Quantity of substance

If the system processes high volumes of requests, then content availability is maintained, but user experience deteriorates due to slow loading and poor responsiveness

Engineering Contradiction:
Improvecontent volumeVSAvoiduser experience
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

The filtering system performs preliminary action by pre-processing and reducing the request volume before it reaches the content delivery infrastructure. This early filtering maintains the availability of relevant content while preventing the system from becoming overwhelmed by excessive requests. As a result, the system can maintain comprehensive content availability while delivering responses quickly enough to preserve good user experience, directly resolving the contradiction between content volume and ease of operation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10484284B2Reducing load to downstream services by filtering requests
Publication Date: 2019.11.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10484284B2 patent drawing
  • US10484284B2 patent drawing
  • US10484284B2 patent drawing

AI summary

A request filtration system that implements techniques to reduce load on a downstream service by efficiently filtering requests before they are processed by the downstream service. The request filtration system may be used by a request processing system to eliminate requests that satisfy any of one or more filters. For example, each filter specifies one or more attributes that may apply to one or more requests. If a request satisfies a filter, then the request is not considered by the downstream service or a content item does not need to be selected by the request processing system in response to the request.