Configuration-Based Content Templates for Dynamic Web Page Loading

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing web technologies consume excessive computing resources and involve inefficient iterative development and deployment steps for managing static, similarly-configured web pages with minor variations, leading to redundant storage and resource consumption.

Innovation Solution

Implementing configuration-based templates that aggregate user-independent and user-specific data with a shared template to generate dynamic content units, enabling efficient storage and streamlined creation of content units using minimal resources, with client-side form validation for reduced network and computing overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If static web pages with similar configurations are stored separately, then each page can be accessed independently, but excessive computing resources and storage space are consumed

Engineering Contradiction:
Improveindependent access capabilityVSAvoidstorage space consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple similar web pages into a single template structure, combining shared content elements and configurations. Instead of storing each web page separately, the system stores a common template that can generate multiple pages, significantly reducing storage space while maintaining independent access capability through parameterized instantiation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The template serves multiple functions by being able to generate various web pages through parameter substitution. A single template structure can produce multiple different web pages by changing instance parameters, making the template universal and eliminating the need for separate storage of each page.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If iterative development and deployment steps are used for managing web pages, then each page can be customized, but development cycles are extended and efficiency is reduced

Engineering Contradiction:
Improvepage customization capabilityVSAvoiddevelopment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by pre-defining the template structure, layout, and common configurations before actual page generation. The template contains all reusable elements and logic, so when a web page needs to be created or modified, only specific parameters need to be changed rather than undergoing complete iterative development, thus accelerating the process while maintaining customization.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If configuration data and entity-specific data are managed separately, then data integrity can be maintained, but network overhead and computing resources increase

Engineering Contradiction:
Improvedata integrityVSAvoidnetwork overhead
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent merges configuration data and entity-specific data into a unified data structure that associates both types of information together. This integration reduces the need for separate data retrieval and processing operations, decreasing network overhead and computing resources while maintaining data integrity through the structured relationship between configuration and entity data.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12554791B2Loading content using configuration-based templates
Publication Date: 2026.02.17 CAPITAL ONE SERVICES LLC
  • US12554791B2 patent drawing
  • US12554791B2 patent drawing
  • US12554791B2 patent drawing

AI summary

In some implementations, a device may receive, from a user device associated with an entity, a request identifying a content unit that is to be loaded into an electronic document. The device may transmit, via a first service, a configuration request for configuration data for the content unit. The device may receive, via the first service, the configuration data. The device may transmit, via a second service, a data request for entity-specific data for the content unit. The device may receive, via the second service, the entity-specific data. The device may transmit, for the user device, a response indicating presentation data to cause insertion of the content unit, in accordance with the presentation data, into a document object model of the electronic document, where the presentation data is based on the configuration data and the entity-specific data.