Edge Caching Personalized Webpages via Fragment Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional edge caching solutions fail to efficiently cache personalized web content in content delivery networks (CDNs) due to the lack of separation between personalization decisions and content rendering, and the retrieval of user information, which limits the ability to serve personalized web pages quickly and cost-effectively.

Innovation Solution

The system separates personalization decisions from content rendering and retrieves user data once from domain services, caching it at the CDN for efficient reuse, allowing for caching of rendered content without impacting cacheability, and uses ESI directives to optimize CDN caching by aggregating personalization decisions and decision variables into a single request.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If conventional edge caching solutions are used to serve web pages from CDN, then page delivery speed is improved, but the ability to cache personalized content is lost

Engineering Contradiction:
Improvepage delivery speedVSAvoidpersonalized content caching capability
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The patent segments the web page into multiple fragments, separating personalized content from static content. Each fragment can be independently cached at the CDN edge, allowing personalized pages to be served efficiently while maintaining caching capability. The page is divided into template fragments and content fragments, with different caching strategies applied to each.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-fetching and caching user data and personalized content fragments at the CDN edge before they are needed for page assembly. This allows the final personalized page to be assembled quickly from pre-cached components, maintaining both speed and personalization capability.

Inventive Principle:
Principle #10Preliminary action

2Manufacturing precision

If user data is retrieved for each personalization decision, then accurate personalization is achieved, but data retrieval time increases

Engineering Contradiction:
Improvepersonalization accuracyVSAvoiddata retrieval time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent retrieves user data once in advance and caches it at the CDN edge, rather than retrieving it repeatedly for each personalization decision. This preliminary data retrieval eliminates redundant network calls and significantly reduces the time required for personalization while maintaining accurate user-specific content delivery.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges multiple data retrieval operations into a single unified data fetch. By consolidating user data retrieval and caching it for reuse across multiple personalization decisions, the system reduces total data retrieval time while maintaining the accuracy needed for personalized content assembly.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If personalization decisions are separated from content rendering, then content cacheability is improved, but system complexity increases

Engineering Contradiction:
Improvecontent cacheabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the page rendering process into separate concerns: template rendering, content fragment generation, and personalization decision-making. This segmentation allows each component to be independently cached and reused, improving overall content cacheability while managing system complexity through clear separation of responsibilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (the fragment directive manager and ESI directives) that mediates between personalization decisions and content rendering. This intermediary enables content to be cached independently of personalization logic, improving cacheability while managing complexity through a standardized interface layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Manufacturing precision

If multiple data retrieval operations are performed for personalization, then decision accuracy is maintained, but network traffic increases

Engineering Contradiction:
Improvepersonalization decision accuracyVSAvoidnetwork traffic
Core Design Contradiction:
Manufacturing precisionVSLoss of energy

Solution Approach 1:

The patent merges multiple data retrieval operations into a single unified data fetch at the origin server, followed by caching of the consolidated user data at the CDN edge. This consolidation maintains the accuracy needed for personalization decisions while significantly reducing network traffic and energy consumption by eliminating redundant data transfers.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent performs preliminary data retrieval and consolidation before content assembly, caching the user data once at the edge. This preliminary action eliminates the need for multiple network round-trips during personalization, reducing network traffic and energy usage while maintaining decision accuracy through access to complete user data.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11210360B2Edge-caching optimization of personalized webpages
Publication Date: 2021.12.28 BBY SOLUTIONS INC
  • US11210360B2 patent drawing
  • US11210360B2 patent drawing
  • US11210360B2 patent drawing

AI summary

Systems and techniques for edge-cache optimization of personalized webpages are described herein. A request may be received for a web page from a content delivery network. Requests may be received for user fragments, page layout fragments, personalization decisions fragments, and page content fragments. Directives may be generated in response to the requests including user fragment directives, page layout fragment directives, user data storage directives, a set of fixed section directives, and a set of personalized section directives. The generated directives may be used to construct content fragment caching directives for the page fragments. The content fragment caching directives are transmitted to the content delivery network to provide cashing instructions for the page fragments.