# US 10,455,043 B2 · Systems and methods for managing loading priority or sequencing of fragments of a web object

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,455,043 B2
- Document ID: US10455043B2
- Status: Granted
- Kind: B2
- Application number: 15/061,711
- Filed: 2016-03-04
- Published: 2016-06-30
- Granted: 2019-10-22
- Earliest claimed: 2013-09-20
- Assignees: Yottaa Inc.
- Applicants: Yottaa Inc.
- Inventors: Coach K. Wei; Robert Buffone
- Web page: https://patentgrep.com/patent/US10455043B2

## CPC

- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- G06F 9/46: Multiprogramming arrangements
- G06F 9/54: Interprogram communication
- G06F 16/00: Information retrieval; Database structures therefor; File system structures therefor
- G06F 40/143: Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/561: Adding application-functional data or data for application control, e.g. adding metadata
- H04L 67/564: Enhancement of application control based on intercepted application data
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- G06F 2209/541: Client-server
- G06F 2209/542: Intercept
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

This disclosure is directed to methods and systems for managing rendering of a web page in a browser. A client operated by a user may execute code within a first fragment of a web page as the first fragment is presented to the user. The code may be injected into the first fragment by an intermediary between the client and a server of the web page. The intermediary may have split the web page into the first fragment and a plurality of fragments, and may have modified a default rendering characteristic for each of the plurality of fragments. Each of the modified rendering characteristic may include a trigger and action for rendering of a corresponding fragment. The executing code may dynamically detect a trigger for rendering of a second fragment from the plurality of fragments. The executing code may initiate a corresponding action for rendering of the second fragment.

## Claims

### Claim 1

A method for managing rendering of a web page, the method comprising:
splitting, by an intermediary between a client and a server, a web page requested by the client into a first fragment and at least one other fragment, the at least one other fragment including a second fragment;
modifying, by the intermediary, a default rendering characteristic for each of the at least one other fragment, wherein the default rendering characteristic for the second fragment of the at least one other fragment comprises a rendering sequence for the second fragment with respect to one or more other fragments as arranged in the web page by the server, and a modified rendering characteristic of the second fragment comprises a trigger to cause rendering of the second fragment; and
injecting, by the intermediary, code within the first fragment for delivery to the client, wherein the code, when executed on the client, is configured to dynamically detect, according to the modified rendering characteristic of the second fragment, a trigger to cause rendering of the second fragment within the first fragment, the trigger comprising a document object model event with a corresponding change in a viewing region of a browser or client display of the client, that involves a display or use of the second fragment.

### Claim 2 (depends on 1)

The method of claim 1, comprising intercepting, by the intermediary, a request from the client to the server for the web page.

### Claim 3 (depends on 1)

The method of claim 1, comprising sending, by the intermediary to the client, the first fragment with the injected code.

### Claim 4 (depends on 1)

The method of claim 1, wherein the code comprises at least one of: code expressed in ECMAScript language or a language similar or related to the ECMAScript language, code expressed in ActionScript language, code expressed in hypertext markup language, code expressed in visual basic language, a plug-in, code referencing a browser plug-in, or code referencing a native module.

### Claim 5 (depends on 1)

The method of claim 1, further comprising modifying, by the intermediary according to a configuration, the default rendering characteristic for each of the at least one other fragment.

### Claim 6 (depends on 1)

The method of claim 1, wherein the code is further configured to perform a pre-trigger action for the second fragment prior to detecting the trigger, the pre-trigger action comprising at least one of: withholding rendering of the second fragment, displaying nothing at an identified location of the web page, or displaying at least one item, the at least one item comprising at least one of: an indicator or message indicating that an item is loading, a temporary or placeholder item or image, an advertisement, or a special call-to-action item.

### Claim 7 (depends on 1)

The method of claim 1, wherein the document object model event comprises one of: a click event, a tap event, a touch event, a mouse-over event or a scroll event on the web page.

### Claim 8 (depends on 1)

The method of claim 1, wherein the code is further configured to detect that a viewing region of the client corresponds to a portion of the web page involving a display or use of the second fragment of the web page.

### Claim 9 (depends on 1)

The method of claim 1, wherein the code is further configured to detect that a viewing region of the client corresponds to a portion of the first fragment that includes a unique identifier for the second fragment.

### Claim 10 (depends on 1)

The method of claim 1, wherein the second fragment comprises one of at least a portion of: an image, a cascading style sheet (CSS), a script, a video object, an audio object, a flash file or small web format (SWF) file, or a HTML file.

### Claim 11

A system for managing rendering of a web page, the system comprising:
code for injection into a first fragment of a web page requested by a client; and
an intermediary hardware device between the client and a server, the intermediary hardware device configured to:
split the web page requested by the client into the first fragment and at least one other fragment, the at least one other fragment including a second fragment;
modify a default rendering characteristic for each of the at least one other fragment, wherein the default rendering characteristic for the second fragment of the at least one other fragment comprises a rendering sequence for the second fragment with respect to one or more other fragments as arranged in the web page by the server, and a modified rendering characteristic of the second fragment comprises a trigger to cause rendering of the second fragment; and
inject code within the first fragment for delivery to the client, wherein the code, when executed on the client, is configured to dynamically detect, according to the modified rendering characteristic of the second fragment, a trigger to cause rendering of the second fragment within the first fragment, the trigger comprising a document object model event with a corresponding change in a viewing region of a browser or client display of the client, that involves a display or use of the second fragment.

### Claim 12 (depends on 11)

The system of claim 11, wherein the intermediary is further configured to intercept a request from the client to the server for the web page.

### Claim 13 (depends on 11)

The system of claim 11, wherein the intermediary is further configured to send the first fragment with the injected code to the client.

### Claim 14 (depends on 11)

The system of claim 11, wherein the code comprises at least one of:
code expressed in ECMAScript language or a language similar or related to the ECMAScript language, code expressed in ActionScript language, code expressed in hypertext markup language, code expressed in visual basic language, a plug-in, code referencing a browser plug-in, or code referencing a native module.

### Claim 15 (depends on 11)

The system of claim 11, wherein the intermediary is configured to modify the default rendering characteristic for each of the at least one other fragment according to a configuration of the intermediary.

### Claim 16 (depends on 11)

The system of claim 11, wherein the code is further configured to perform a pre-trigger action for the second fragment prior to detecting the trigger, the pre-trigger action comprising at least one of: withholding rendering of the second fragment, displaying nothing at an identified location of the web page, or displaying at least one item, the at least one item comprising at least one of: an indicator or message indicating that an item is loading, a temporary or placeholder item or image, an advertisement, or a special call-to-action item.

### Claim 17 (depends on 11)

The system of claim 11, wherein the document object model event comprises one of: a click event, a tap event, a touch event, a mouse-over event or a scroll event on the web page.

### Claim 18 (depends on 11)

The system of claim 11, wherein the code is further configured to detect that a viewing region of the client corresponds to a portion of the web page involving a display or use of the second fragment of the web page.

### Claim 19 (depends on 11)

The system of claim 11, wherein the code is further configured to detect that a viewing region of the client corresponds to a portion of the first fragment that includes a unique identifier for the second fragment.

### Claim 20 (depends on 11)

The system of claim 11, wherein the second fragment comprises one of at least a portion of: an image, a cascading style sheet (CSS), a script, a video object, an audio object, a flash file or small web format (SWF) file, or a HTML file.