Client Web Page Generation Without Markup Languages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current web page generation systems require significant resources on web page servers, leading to inefficiencies during high traffic periods and underutilization during low traffic times, as they need to handle both static and dynamic content generation, which can result in delayed response times and wasted resources.

Innovation Solution

A method and apparatus where a client data processing system receives metadata describing a web page, identifies and retrieves necessary content, and generates the web page without using markup languages, thereby reducing the load on web page servers and allowing for faster display on client systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If web page servers generate web pages using markup language interpretation and dynamic content generation, then web pages can be displayed with complete functionality, but server resources are heavily consumed and response times increase during high traffic periods

Engineering Contradiction:
Improveweb page generation completenessVSAvoidresponse speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent pre-generates static web pages as template files during low-traffic periods and stores them on the server. When a user requests a web page, the server quickly retrieves the pre-generated template and combines it with dynamic content, avoiding the need to interpret markup languages and generate static content in real-time. This preliminary preparation significantly reduces response time during high-traffic periods while maintaining complete web page functionality.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent divides web page generation into separate components: static content (pre-generated templates), dynamic content (generated on-demand), and combination logic. By segmenting the generation process, the server can efficiently handle static content through template retrieval rather than full markup interpretation, reserving computational resources for only the necessary dynamic content generation and combination operations.

Inventive Principle:
Principle #1Segmentation

2Productivity

If multiple web page servers are deployed to handle high traffic, then response times are improved, but resource utilization becomes inefficient during low traffic periods

Engineering Contradiction:
Improvetraffic handling capacityVSAvoidresource underutilization
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent implements dynamic resource allocation where the server adapts its operation mode based on traffic conditions. During low-traffic periods, the server performs pre-generation of web page templates in advance, preparing content proactively. During high-traffic periods, the server switches to rapid template retrieval and dynamic content combination. This dynamic adjustment allows the system to handle variable traffic loads efficiently without requiring multiple permanently active servers, reducing resource underutilization during low-traffic periods.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent employs periodic pre-generation of web page templates during intervals between user requests, particularly during low-traffic periods. This periodic preparation ensures that templates are ready for rapid delivery when users request pages, enabling the server to handle traffic spikes without needing continuous high-resource allocation. The periodic action pattern allows efficient resource usage by alternating between preparation phases and delivery phases.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS10742764B2Web page generation system
Publication Date: 2020.08.11 ADP INC
  • US10742764B2 patent drawing
  • US10742764B2 patent drawing
  • US10742764B2 patent drawing

AI summary

A method, apparatus and computer program product for displaying a web page. Metadata describing a web page is received by a client data processing system. The metadata defines what the web page looks like without content for the web page. The content needed for the web page based on the metadata is identified by the client data processing system. The content for the web page is obtained by the client data processing system. The web page using the metadata and the content is created by the client data processing system without using a markup language. The web page on a graphical user interface on the client data processing system is displayed by the client data processing system.