Screen Rendering Time Estimation via Data Flow Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for measuring web page loading time (PLT) do not account for the time it takes to render the first screen of a web page, which is crucial for user experience, and are not scalable, requiring involvement of web and network administrators, and modifying user hardware and communication resources.

Innovation Solution

A method to estimate the screen rendering time by observing data flow to a client entity, determining content data associated with rendering the first screen, and extracting relevant data items to calculate the time required to render the content in the screen area, using passive deep packet inspection and browser-like software analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional PLT measurement methods are used, then complete page download time can be measured, but the measurement does not reflect user experience and requires involvement of administrators and modification of user hardware

Engineering Contradiction:
Improvescreen rendering time measurement accuracyVSAvoidmeasurement system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent creates a simplified copy of the browser rendering process that runs independently on the client device. This copy mimics the essential rendering operations without requiring full browser functionality or administrator involvement, enabling accurate screen rendering time measurement while keeping the system simple

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces a rendering time measurement component as an intermediary between the web page content and the user experience assessment. This intermediary captures rendering time data without interfering with the actual browsing experience or requiring modifications to the browser itself

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If complete page download time is measured, then all content transfer time is captured, but the time to display the first screen which is crucial for user experience is not accounted for

Engineering Contradiction:
Improveuser perception timeVSAvoidrendering time information
Core Design Contradiction:
Loss of timeVSLoss of information

Solution Approach 1:

The patent segments the web page loading process into distinct phases: network download time and client-side rendering time. By separating these phases, the measurement system can specifically capture the rendering time of the first screen, which directly impacts user experience, without being conflated with total download time

Inventive Principle:
Principle #1Segmentation

3Productivity

If web server logs or custom Javascript code are used for measurement, then PLT can be analyzed, but web server administrator involvement is required which limits large scale measurement capability

Engineering Contradiction:
Improvemeasurement scalabilityVSAvoidadministrator involvement requirement
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent implements a self-service measurement mechanism where the client device autonomously measures its own rendering time without requiring external coordination. The measurement component runs independently on the user's device, automatically capturing rendering metrics and reporting them without needing web server administrator configuration or intervention, enabling large-scale deployment

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9940309B2Measuring web page rendering time
Publication Date: 2018.04.10 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US9940309B2 patent drawing
  • US9940309B2 patent drawing
  • US9940309B2 patent drawing

AI summary

A method in a network setup that includes a client entity and a network for handling a data flow to the client entity. The method estimates a screen rendering time of content at the client entity. The method includes the steps of observing the data flow to the client entity, estimating a screen area at the client entity based on the observed data flow, determining, from the data flow, content data associated with rendering content in the screen area, extracting at least data items from the determined content data, and estimating, as the screen rendering time, the time required to render the content in the screen area at the client entity based on the extracted data items.