DOM Reuse via Static Template Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for rendering a page on computing devices, such as web pages, are inefficient due to the time-consuming process of constructing a new document object model (DOM) for each instance, especially in resource-constrained environments like mobile devices, leading to a less than satisfactory user experience.

Innovation Solution

The implementation of a method that reuses a shared DOM, comprising a static portion common to multiple instances and dynamic portions unique to each instance, allowing for efficient rendering by reusing the static DOM and updating only the dynamic portions, thereby reducing processing and communication resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a new DOM tree is constructed for each page instance, then the page rendering is accurate and complete, but the processing time and resource consumption increase significantly

Engineering Contradiction:
Improvepage rendering accuracyVSAvoidpage loading time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The DOM tree is segmented into a template portion (common structure) and an instance-specific portion (dynamic content). The template DOM is constructed once and reused across multiple page instances, while only the dynamic portions are regenerated for each instance. This segmentation allows the system to maintain rendering accuracy for the common structure while significantly reducing processing time by avoiding redundant construction of identical DOM elements.

Inventive Principle:
Principle #1Segmentation

2Reliability

If a new DOM tree is constructed for each page instance, then the page structure is complete and accurate, but the memory overhead and processing resources increase

Engineering Contradiction:
ImproveDOM structure completenessVSAvoidmemory overhead
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Multiple page instances share a common template DOM structure in memory, merging the common structural elements into a single reusable object. Instead of creating separate DOM trees for each instance, the system combines the template DOM with instance-specific dynamic portions, reducing overall memory overhead while maintaining complete and accurate DOM structures for rendering.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If the entire DOM is stored and reused for each page instance, then the page loading is fast, but the code complexity and memory usage increase

Engineering Contradiction:
Improvepage rendering speedVSAvoidcode complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The DOM is divided into static template portions and dynamic instance-specific portions. This segmentation allows the system to store and reuse only the common structural template once, while generating fresh dynamic portions for each instance as needed. The approach maintains fast rendering by reusing the template DOM structure while avoiding the complexity of managing entirely pre-generated DOMs for every possible page instance variation.

Inventive Principle:
Principle #1Segmentation

4Productivity

If the entire DOM is stored and reused for each page instance, then the page loading is fast, but the memory overhead increases

Engineering Contradiction:
Improvepage rendering speedVSAvoidmemory overhead
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system merges the common template DOM structure with instance-specific dynamic content, allowing multiple page instances to share the same base DOM structure in memory. This combining approach enables fast page loading by reusing the template DOM while minimizing memory overhead, as the common structural elements are stored only once rather than being duplicated for each instance.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9311425B2Rendering a page using a previously stored DOM associated with a different page
Publication Date: 2016.04.12 QUALCOMM INC
  • US9311425B2 patent drawing
  • US9311425B2 patent drawing
  • US9311425B2 patent drawing

AI summary

Aspects relate to apparatus and methods for rendering a page on a computing device, such as a web page. The apparatus and methods include receiving a request for a requested instance of a page and determining if the requested instance of the page corresponds to a document object model (DOM) for the page stored in a memory. Further, the apparatus and methods include retrieving a dynamic portion of the DOM corresponding to the requested instance if the requested instance of the page corresponds to the DOM stored in the memory. The dynamic portion may be unique to the requested instance of the page. Moreover, the apparatus and methods include storing the dynamic portion of the DOM corresponding to the requested instance of the page in a relationship with the static portion of the DOM.