# US 2021/0263768 A1 · Browser-based processing of data

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

- Number: US 2021/0263768 A1
- Document ID: US20210263768A1
- Status: Published application
- Kind: A1
- Application number: 16/801,411
- Filed: 2020-02-26
- Published: 2021-08-26
- Earliest claimed: 2020-02-26
- Assignees: The Toronto-Dominion Bank
- Applicants: The Toronto-Dominion Bank
- Inventors: Walter Osmond; Osama Syed Hashimi; Ivan Shibanov
- Web page: https://patentgrep.com/patent/US20210263768A1

## CPC

- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 9/451: Execution arrangements for user interfaces
- G06F 9/5061: {Partitioning or combining of resources}
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 2209/5018: Thread allocation
- G06F 2209/541: Client-server
- G06F 2209/545: Gui
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In some implementations, a user interface for an application is displayed using a web browser instance on a client device. An input is received to present data on the user interface in a particular view. In response to the input, a first web worker thread corresponding to the web browser instance obtains data from a server, and executes first library routines to store the data in local storage at the client device. A second web worker thread, which corresponds to the web browser instance and the user interface, accesses the data from the local storage by using one or more second library routines, and processes the data to convert to a presentation format corresponding to the particular view. The second web worker thread stores the processed data in the local storage by using one or more third library routines, and provides the processed data for display on the user interface.

## Claims

### Claim 1

A method comprising:
displaying, using a web browser instance on a client device, a first user interface for an application;
receiving an input to present data on the first user interface in a particular view;
in response to the input, obtaining, using a first web worker thread corresponding to the web browser instance, data from a server that is communicably coupled to the client device;
executing, using the first web worker thread, one or more first library routines to store the data in local storage at the client device;
accessing, by a second web worker thread using one or more second library routines, the data from the local storage, wherein the second web worker thread corresponds to the web browser instance and the first user interface;
processing, by the second web worker thread, the data to convert to a presentation format corresponding to the particular view;
storing, by the second web worker thread using one or more third library routines, the processed data in the local storage; and
providing, by the second web worker thread, the processed data for display on the first user interface.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
displaying, using a second web browser instance on the client device, a second user interface for the application;
receiving a second input to present data on the second user interface in a second view;
in response to the second input, accessing, by a third web worker thread using the one or more second library routines, second data from the local storage, wherein the third web worker thread corresponds to the second web browser instance and the second user interface;
processing, by the third web worker thread, the second data to convert to a second presentation format corresponding to the second view;
providing, by the third web worker thread, the processed second data for display on the second user interface; and
storing, by the third web worker thread using one or more third library routines, the processed second data in the local storage.

### Claim 3 (depends on 2)

The method of claim 2, wherein receiving the second input to present data on the second user interface in the second view further comprises:
obtaining, in response to the second input and using the first web worker thread, the second data from the server; and
executing, using the first web worker thread, the one or more first library routines to store the second data in the local storage at the client device.

### Claim 4 (depends on 2)

The method of claim 2, wherein at least a portion of the second data is same as the data processed by the first web worker thread.

### Claim 5 (depends on 2)

The method of claim 2, wherein the web browser instance and the second web browser instance are instances of a same web browser executed on the client device.

### Claim 6 (depends on 2)

The method of claim 2, wherein displaying the second user interface comprises:
displaying the second user interface concurrently with displaying the first user interface.

### Claim 7 (depends on 2)

The method of claim 2, further comprising:
obtaining, using the first web worker thread, additional data from the server;
executing, using the first web worker thread, the one or more first library routines to store the additional data in the local storage at the client device; and
causing at least one of the second web worker thread or the third web worker thread to access the additional data from the local storage for processing.

### Claim 8 (depends on 7)

The method of claim 7, wherein obtaining the additional data from the server comprises:
obtaining first additional data corresponding to the first user interface; and
obtaining second additional data corresponding to the second user interface, wherein at least a portion of the second additional data is distinct from the first additional data.

### Claim 9 (depends on 1)

The method of claim 1, wherein the local storage includes an IndexedDB datastore, and wherein at least one of the first library routines, the second library routines, or the third library routines includes an IndexedDB Promised Library routine.

### Claim 10 (depends on 1)

The method of claim 1, wherein the data obtained from the server includes Real-time Rendering Engine (RTRE) data and the processed data includes crunched data, and wherein processing the data by the second web worker thread comprises:
aggregating, using the second web worker thread, the RTRE data accessed from the local storage to a crunched presentation format corresponding to the particular view.

### Claim 11

One or more non-transitory media storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
displaying, using a web browser instance on a client device, a first user interface for an application;
receiving an input to present data on the first user interface in a particular view;
in response to the input, obtaining, using a first web worker thread corresponding to the web browser instance, data from a server that is communicably coupled to the client device;
executing, using the first web worker thread, one or more first library routines to store the data in local storage at the client device;
accessing, by a second web worker thread using one or more second library routines, the data from the local storage, wherein the second web worker thread corresponds to the web browser instance and the first user interface;
processing, by the second web worker thread, the data to convert to a presentation format corresponding to the particular view;
storing, by the second web worker thread using one or more third library routines, the processed data in the local storage; and
providing, by the second web worker thread, the processed data for display on the first user interface.

### Claim 12 (depends on 11)

The one or more non-transitory media of claim 11, wherein the operations further comprise:
displaying, using a second web browser instance on the client device, a second user interface for the application;
receiving a second input to present data on the second user interface in a second view;
in response to the second input, accessing, by a third web worker thread using the one or more second library routines, second data from the local storage, wherein the third web worker thread corresponds to the second web browser instance and the second user interface;
processing, by the third web worker thread, the second data to convert to a second presentation format corresponding to the second view;
providing, by the third web worker thread, the processed second data for display on the second user interface; and
storing, by the third web worker thread using one or more third library routines, the processed second data in the local storage.

### Claim 13 (depends on 12)

The one or more non-transitory media of claim 12, wherein receiving the second input to present data on the second user interface in the second view further comprises:
obtaining, in response to the second input and using the first web worker thread, the second data from the server; and
executing, using the first web worker thread, the one or more first library routines to store the second data in the local storage at the client device.

### Claim 14 (depends on 12)

The one or more non-transitory media of claim 12, wherein the web browser instance and the second web browser instance are instances of a same web browser executed on the client device.

### Claim 15 (depends on 12)

The one or more non-transitory media of claim 12, wherein the operations further comprise:
obtaining, using the first web worker thread, additional data from the server;
executing, using the first web worker thread, the one or more first library routines to store the additional data in the local storage at the client device; and
causing at least one of the second web worker thread or the third web worker thread to access the additional data from the local storage for processing.

### Claim 16 (depends on 11)

The one or more non-transitory media of claim 11, wherein the local storage includes an IndexedDB datastore, and wherein at least one of the first library routines, the second library routines, or the third library routines includes an IndexedDB Promised Library routine.

### Claim 17 (depends on 11)

The one or more non-transitory media of claim 11, wherein the data obtained from the server includes Real-time Rendering Engine (RTRE) data and the processed data includes crunched data, and wherein processing the data by the second web worker thread comprises:
aggregating, using the second web worker thread, the RTRE data accessed from the local storage to a crunched presentation format corresponding to the particular view.

### Claim 18

A system comprising:
one or more processors; and
one or more non-transitory media storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
displaying, using a web browser instance on a client device, a first user interface for an application;
receiving an input to present data on the first user interface in a particular view;
in response to the input, obtaining, using a first web worker thread corresponding to the web browser instance, data from a server that is communicably coupled to the client device;
executing, using the first web worker thread, one or more first library routines to store the data in local storage at the client device;
accessing, by a second web worker thread using one or more second library routines, the data from the local storage, wherein the second web worker thread corresponds to the web browser instance and the first user interface;
processing, by the second web worker thread, the data to convert to a presentation format corresponding to the particular view;
storing, by the second web worker thread using one or more third library routines, the processed data in the local storage; and
providing, by the second web worker thread, the processed data for display on the first user interface.

### Claim 19 (depends on 18)

The system of claim 18, wherein the operations further comprise:
displaying, using a second web browser instance on the client device, a second user interface for the application;
receiving a second input to present data on the second user interface in a second view;
in response to the second input, accessing, by a third web worker thread using the one or more second library routines, second data from the local storage, wherein the third web worker thread corresponds to the second web browser instance and the second user interface;
processing, by the third web worker thread, the second data to convert to a second presentation format corresponding to the second view;
providing, by the third web worker thread, the processed second data for display on the second user interface; and
storing, by the third web worker thread using one or more third library routines, the processed second data in the local storage.

### Claim 20 (depends on 18)

The system of claim 18, wherein the local storage includes an IndexedDB datastore, and wherein at least one of the first library routines, the second library routines, or the third library routines includes an IndexedDB Promised Library routine.
