Mobile Resource Accelerator via Local Cache In-lining

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In client/server environments with slow connection speeds and high latencies, such as mobile networks, resource references in HTML pages take a long time to load due to the need for re-transmission of resources on subsequent visits, leading to inefficiencies and performance issues.

Innovation Solution

Implementing a system where resources are in-lined the first time they are requested and cached locally for subsequent use, using an accelerator proxy that intercepts client requests and embeds resources within HTML pages, allowing them to be stored in local storage and referenced from there, thereby avoiding re-transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If resources are in-lined into HTML text using data URIs, then latency is reduced and resources are transmitted with every response, but re-transmission of resources on subsequent visits leads to inefficiencies and adversely affects responsiveness and performance

Engineering Contradiction:
ImprovelatencyVSAvoidperformance
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The system performs preliminary action by in-lining resources into the HTML text during the initial request, so that the resources are already embedded in the page before the user needs to access them again. This eliminates the need for re-transmission on subsequent visits, resolving the contradiction between reducing latency and maintaining performance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the resource embedded within the HTML text using data URIs. This copy is stored in the client's local cache, allowing the resource to be accessed locally on subsequent visits without re-transmission. This copying mechanism resolves the contradiction by enabling both immediate access (reducing latency) and efficient subsequent access (maintaining performance).

Inventive Principle:
Principle #26Copying

2Loss of time

If resources are in-lined into HTML text, then resources are transmitted with every response, but this leads to inefficiencies and increases data transmission overhead

Engineering Contradiction:
Improveresponse timeVSAvoiddata transmission overhead
Core Design Contradiction:
Loss of timeVSLoss of energy

Solution Approach 1:

The system performs preliminary action by in-lining resources during the initial request, so that the resources are already embedded in the page. This eliminates the need for re-transmission on subsequent visits, reducing data transmission overhead while maintaining fast response times.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the resource embedded within the HTML text using data URIs, which is then stored in the client's local cache. This copy allows the resource to be accessed locally on subsequent visits without re-transmission, reducing data transmission overhead while maintaining fast access speeds.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9292467B2Mobile resource accelerator
Publication Date: 2016.03.22 RADWARE LTD
  • US9292467B2 patent drawing
  • US9292467B2 patent drawing
  • US9292467B2 patent drawing

AI summary

In a client/server environment wherein resources are returned in response to client requests, a resource can be in-lined the first time it is requested, and then cached locally for use in connection with subsequent requests. When a user returns to the page for a subsequent visit, the resource requests are served from the local cache, thus avoiding the need for re-transmission with each response. According to various embodiments, the system and method of the present invention can be implemented in connection with delivery of any content in a client/server system, including for example HTML responses to requests for web pages. In at least one embodiment, the techniques described herein are tailored to mobile data network constraints; however, these techniques can be applied to any data network.