Client Webpage Template Storage for Reducing Data Transmission Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for generating webpages suffer from significant latency due to the transmission of large amounts of HTML code across long distances, which can result in a poor user experience, especially when the client device is geographically distant from the server or under unfavorable network conditions.

Innovation Solution

The technique involves storing common webpage code as a template on the client device, allowing the server to transmit only the unique code required for each webpage, which the client can combine with the template to generate the webpage, thereby reducing data transmission and latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the server transmits complete HTML code for webpages, then the webpage can be rendered accurately, but the data transmission size increases significantly causing latency

Engineering Contradiction:
Improvewebpage rendering accuracyVSAvoiddata transmission latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The webpage code is segmented into two parts: a template containing common structural elements stored locally on the client device, and additional code containing unique content-specific elements transmitted from the server. This segmentation reduces the amount of data that needs to be transmitted while ensuring complete webpage rendering.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The template containing common webpage structure and styling is prepared in advance and stored on the client device before the user requests a webpage. This preliminary action eliminates the need to retransmit this data with each request, significantly reducing transmission latency for subsequent page loads.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the server transmits complete HTML code for each webpage, then all webpage elements are available, but the transmission data quantity increases causing latency

Engineering Contradiction:
Improvewebpage element completenessVSAvoidtransmitted data volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The common template portion is extracted from the complete webpage code and stored locally on the client device. Only the remaining additional code specific to each webpage is transmitted from the server, significantly reducing the quantity of transmitted data while maintaining element completeness through the local template.

Inventive Principle:
Principle #2Taking out (Extraction)

3Loss of time

If the client device stores templates locally, then data transmission is reduced, but the device complexity increases

Engineering Contradiction:
Improvedata transmission timeVSAvoidclient device structure
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

Instead of storing complete webpages or complex processing systems, the client device stores simplified template copies containing common structural elements. This copying approach reduces device complexity while still enabling significant data transmission reduction through local template utilization.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11138287B1System for reducing size of transmitted content
Publication Date: 2021.10.05 AMAZON TECH INC
  • US11138287B1 patent drawing
  • US11138287B1 patent drawing
  • US11138287B1 patent drawing

AI summary

To reduce the amount of data sent to a device to generate a webpage, a requesting device provides an indication of locally stored templates. Multiple webpages may use similar code represented by a single template. If the requested webpage is associated with a stored template, a response provided to the device includes an indication of the template and webpage code that corresponds to portions of the webpage not included in the template. The requesting device then generates a first portion of the webpage using code in the template and a second portion using the received webpage code. If the requested webpage is associated with a template not indicated in the request, both the template and code that corresponds to the second portion of the webpage are sent. The requesting device then stores the template for future use when accessing the same or a similar webpage associated with the same template.