Cache-Based Retry Handling for Content Recommendation Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In areas with poor network environments, a high failure rate of content recommendation requests during peak service periods leads to delayed or inaccurate content delivery to clients, resulting in wasted effective push content.

Innovation Solution

A content recommendation request processing method and apparatus that verifies a target request identifier to determine if it's a retry request. If it is, the method retrieves corresponding recommended content from a cache using the identifier, avoiding re-pulling from the recommendation service.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system sends a new content recommendation request to the recommendation service after a failure, then the client can obtain new recommended content, but the response time increases and the content may be inaccurate

Engineering Contradiction:
Improvecontent recommendation delivery reliabilityVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system pre-obtains and caches recommended content before it is needed. When a content recommendation request is made, the system first checks the cache for existing content. If found, it immediately returns the cached content without contacting the recommendation service, thus eliminating the time delay and ensuring reliable content delivery even under poor network conditions or high service load.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If the system re-pulls recommended content from the recommendation service for retry requests, then the content may be updated, but the effective push content is wasted and system resources are consumed

Engineering Contradiction:
Improvecontent update capabilityVSAvoidsystem resource consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The system recovers and reuses previously obtained recommended content by storing it in a cache. When a retry request occurs, instead of discarding the previously fetched content and pulling new content from the recommendation service, the system retrieves the cached content and reuses it, thereby conserving system resources and avoiding waste of effective push content while maintaining content availability.

Inventive Principle:
Principle #34Discarding and recovering

3Measurement precision

If the system processes each content recommendation request by calling the recommendation service, then the content is fresh, but the service load increases and latency increases during peak periods

Engineering Contradiction:
Improvecontent recommendation accuracyVSAvoidservice throughput
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system segments the content recommendation process into two parts: a caching layer that stores previously obtained recommended content and a service calling layer that contacts the recommendation service. By segmenting the workflow, the system can serve retry requests from the cache without burdening the recommendation service, thereby maintaining service throughput during peak periods while still obtaining accurate content when needed.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250181505A1Method, apparatus, electronic device, and storage medium for processing a content recommendation request
Publication Date: 2025.06.05 LEMON INC(GB)
  • US20250181505A1 patent drawing
  • US20250181505A1 patent drawing
  • US20250181505A1 patent drawing

AI summary

The present disclosure relates to the field of network communication, and in particular, to a content recommendation request processing method and apparatus, an electronic device, and a storage medium. According to the method provided in embodiments of the present disclosure, whether a content recommendation request is a retry request is determined based on a target request identifier. If the content recommendation request is a retry request, it indicates that a client has failed to obtain recommended content before. In this case, a server may directly obtain the request identifier and corresponding target recommended content from a cache, and during this process, the recommended content is not required to be re-pulled by using a recommendation service.