Dynamic Content Fragment Assembly for Portal Sites

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current content delivery systems face inefficiencies in updating static content, leading to stale information and high resource costs due to the lack of automated coordination between content delivery and management systems, particularly in large-scale portal sites.

Innovation Solution

The system interfaces content delivery and management systems at the page or sub-page level, tracking dependencies and using caching mechanisms to dynamically update and assemble content fragments on-demand, ensuring timely and efficient propagation of changes across the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If all web pages are reproduced at regular intervals to incorporate content changes, then content freshness is improved, but system resource consumption and time required increase significantly

Engineering Contradiction:
Improvecontent freshnessVSAvoidsystem efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent segments the web page into multiple fragments (header, navigation, content, footer, etc.) that can be independently managed and updated. Instead of reproducing the entire page, only the affected fragments are updated when content changes, significantly reducing system resource consumption while maintaining content freshness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system pre-generates and caches multiple fragments of web pages in advance. When a content change occurs, the system quickly assembles updated pages by combining cached fragments with updated content, eliminating the need for complete page reproduction and reducing update time.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If portal applications use dynamic scripting to assemble pages on-the-fly, then content adaptability is improved, but system complexity increases

Engineering Contradiction:
Improvecontent assembly flexibilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the portal application into independent, reusable fragments that can be dynamically assembled. Each fragment is self-contained with its own metadata, allowing flexible combination without requiring complex scripting logic to manage interdependencies between page elements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses templates to define fragment structures and relationships. These templates can be copied and reused across multiple pages, providing adaptability and versatility while reducing system complexity through standardized, repeatable patterns rather than custom scripting for each page.

Inventive Principle:
Principle #26Copying

3Ease of manufacture

If web pages are updated at fixed intervals, then implementation simplicity is maintained, but content staleness increases between updates

Engineering Contradiction:
Improveupdate process simplicityVSAvoidcontent staleness
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The patent implements dynamic fragment updates where content is refreshed based on actual changes rather than fixed intervals. The system monitors content sources and automatically updates only the affected fragments when changes are detected, maintaining simplicity while eliminating staleness.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms that monitor content sources for changes. When changes are detected, the system triggers selective fragment updates, creating a responsive update process that maintains content freshness without requiring complex scheduling or fixed intervals.

Inventive Principle:
Principle #23Feedback

4Manufacturing precision

If complete web pages are reproduced for every content change, then content accuracy is improved, but time consumption and resource usage increase

Engineering Contradiction:
Improvecontent update accuracyVSAvoidupdate time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent segments pages into independent fragments, allowing precise updates of only the affected portions. This maintains content accuracy by ensuring updated content is properly integrated while reducing update time by excluding unchanged portions from the reproduction process.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts and updates only the specific fragments that contain changed content, separating them from the rest of the page. This extraction approach ensures accurate content updates while minimizing the scope of work required, thereby reducing time consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12067074B2System and method for the dynamic provisioning of static content
Publication Date: 2024.08.20 OPEN TEXT SA ULC
  • US12067074B2 patent drawing
  • US12067074B2 patent drawing
  • US12067074B2 patent drawing

AI summary

Disclosed herein are embodiments of a system and method for the dynamic provisioning of static content. In one embodiment, information presented on a content delivery system can be refreshed based on information published on a content management system. One embodiment can interface the content delivery system and the content management system at the page level. More specifically, content dependencies across pages employing the same content or portion(s) thereof can be tracked in a timely, accurate manner. Upon receiving a notification of a change to the content or a portion thereof from the content management system, a content generation system may operate to determine, based on the dependencies, what pages are affected by the change and, based on the determination, dynamically regenerate any and all affected pages. The regenerated pages may then be stored and/or pushed to the web tier for delivery to end users.