IP Library Granted Patent US 11,880,357
Granted Patent B2
US 11,880,357 · App. 17/980,456 · Granted Jan 23, 2024

Big-data view integration platform

Inventors: Sunitha Garapati (Normal, IL); Venu Madhav Valluri (Johns Creek, GA); Brent Giosta (Bloomington, IL); Jennifer Pearsall (Bloomington, IL); Ryan M. Kroutil (Sugar Hill, GA)
Assignee: State Farm Mutual Automobile Insurance Company
G06F16/2393G06F3/0482G06F3/0484G06F16/2379G06F16/2465G06F16/252G06F16/254G06F16/26G06F16/287G06F2203/04803
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,880,357
App. No.
17/980,456
Granted
Jan 23, 2024
Kind
B2
Abstract

A big-data view integration platform generates integration guided user interfaces (GUIs). A first edge node ingests push-based and pull-based data from a plurality of platform services, which include legacy and non-legacy services having incompatible communication protocols. An event-based queue receives from the first edge node a plurality of queue events as indirect push-based data. A second set of queue events includes direct push-based data as received directly from a non-legacy platform service. A conformity component integrates the push-based data, the pull-based data, and the plurality of queue events into integration data having an enhanced integration format. A view integration component generates a plurality of data views from the integration data. A second edge node exposes the plurality of data views via an access services application programming interface (API). A new service execution component accesses the access services API to generate integration GUIs based on the data views.

Claims (78)

1. A non-transitory computer-readable medium storing instructions, that when executed by a processor of a computing device, cause the computing device to:

receive, at a first edge node of an integration platform, push-based data, pull-based data, and queue-based data from a plurality of platform services;

integrate, by the first edge node, the push-based data, the pull-based data, and the queue-based data into integration data having an enhanced integration format;

present, at a second edge node of the integration platform and via a guided user interface (GUI), a first data view of the integration data, the first data view including a first selectable icon representing a first incentive;

receive, at the first edge node, a first update on activities of users participating an incentive program;

update, by the first edge node and based on the first update, the integration data;

receive an input via the first selectable icon; and

based on the input, cause the GUI to initiate a first asynchronous call, via an application programming interface (API), to populate a second data view of the integration data, wherein the second data view includes:

a second selectable icon representing a second incentive, and

information indicative of the first update on the activities of the users participating the incentive program.

2. The non-transitory computer-readable medium of claim 1 , wherein the instructions, when executed by the processor, further cause the computing device to:

receive, at the first edge node, a second update on the push-based data, the pull-based data, and the queue-based data from the plurality of platform services; and

update, by the first edge node and based on the second update, the integration data.

3. The non-transitory computer-readable medium of claim 2 , wherein the second data view further includes information indicative of the second update on the push-based data, the pull-based data, and the queue-based data from the plurality of platform services.

4. The non-transitory computer-readable medium of claim 2 , wherein the instructions, when executed by the processor, further cause the computing device to:

receive, at the first edge node, a third update on business plans from a plurality of business units; and

update, by the first edge node and based on the third update, the integration data.

5. The non-transitory computer-readable medium of claim 1 , wherein the instructions, when executed by the processor, further cause the computing device to:

receive, at the first edge node, the push-based data, the pull-based data, and the queue-based data in a pre-determined time interval;

generate, at the first edge node, a plurality of data views of the integration data, according to the pre-determined time interval, the plurality of data views including the first data view and the second data view; and

queue, by the first edge node, the plurality of data views in a database.

6. The non-transitory computer-readable medium of claim 5 , wherein the instructions, when executed by the processor, further cause the computing device to:

receive, at the first edge node, the first update on the activities of users participating an incentive program in real-time;

update, by the first edge node and based on the first update, the queued plurality of data views in the database.

7. The non-transitory computer-readable medium of claim 1 , wherein the first asynchronous call is based on an asynchronous JavaScript and extensible markup language (AJAX).

8. A method, comprising:

receiving, at a first edge node of an integration platform, push-based data, pull-based data, and queue-based data from a plurality of platform services in a pre-determined time interval;

integrating, by the first edge node, the push-based data, the pull-based data, and the queue-based data into integration data having an enhanced integration format;

generating, at the first edge node, a plurality of data views of the integration data, according to the pre-determined time interval;

presenting, at a second edge node of the integration platform and via a guided user interface (GUI), a first data view of the plurality of data views, the first data view including a first selectable icon representing a first incentive;

receiving, at the first edge node, a first update on activities of users participating an incentive program;

updating, by the first edge node and based on the first update, the integration data;

receiving an input via the first selectable icon; and

based on the input, causing the GUI to initiate a first asynchronous call via an application programming interface (API) to populate a second data view of the integration data,

wherein the second data view includes:

a second selectable icon representing a second incentive, and

information indicative of the first update on the activities of the users participating the incentive program.

9. The method of claim 8 , further comprising:

receiving, at the first edge node, a second update on the push-based data, the pull-based data, and the queue-based data from the plurality of platform services; and

updating, by the first edge node and based on the second update, the integration data.

10. The method of claim 9 , wherein the second data view further includes information indicative of the second update on the push-based data, the pull-based data, and the queue-based data from the plurality of platform services.

11. The method of claim 9 , further comprising:

queueing, by the first edge node, the plurality of data views of the integration data in a database; and

updating, by the first edge node and based on the second update, the plurality of data views.

12. The method of claim 11 , further comprising:

receiving, at the first edge node, a third update on business plans from a plurality of business units; and

updating, by the first edge node and based on the third update, the plurality of data views.

13. The method of claim 12 , wherein

the push-based data and the pull-based data are received from a first platform service utilizing a first communication protocol, and

the queue-based data is received from a first platform service and at least a second platform service utilizing a second communication protocol, the second communication protocol being different from the first communication protocol.

14. The method of claim 8 , wherein the first asynchronous call is based on an asynchronous JavaScript and extensible markup language (AJAX).

15. A system comprising:

a non-transitory memory storing a set of computer-executable instructions; and

a processor configured to execute the computer-executable instructions to cause the processor to:

receive, at a first edge node of an integration platform, push-based data, pull-based data, and queue-based data from a plurality of platform services;

integrate, by the first edge node, the push-based data, the pull-based data, and the queue-based data into integration data having an enhanced integration format;

present, at a second edge node of the integration platform and via a guided user interface (GUI), a first data view of the integration data, the first data view including a first selectable icon representing a first incentive;

receive, at the first edge node, a first update on activities of users participating an incentive program;

update, by the first edge node and based on the first update, the integration data;

receive an input via the first selectable icon; and

based on the input, cause the GUI to initiate a first asynchronous call via an application programming interface (API) to populate a second data view of the integration data,

wherein the second data view includes:

a second selectable icon representing a second incentive, and

the first update on the activities of the users participating the incentive program.

16. The system of claim 15 , wherein the processor is configured to execute the computer-executable instructions to cause the processor further to:

receive, at the first edge node, a second update on the push-based data, the pull-based data, and the queue-based data from the plurality of platform services; and

update, by the first edge node and based on the second update, the integration data.

17. The system of claim 16 , wherein the second data view further includes information indicative of the second update on the push-based data, the pull-based data, and the queue-based data from the plurality of platform services.

18. The system of claim 16 , wherein the processor is configured to execute the computer-executable instructions to cause the processor further to:

receive, at the first edge node, a third update on business plans from a plurality of business units; and

update, by the first edge node and based on the third update, the integration data.

19. The system of claim 15 , wherein the processor is configured to execute the computer-executable instructions to cause the processor further to:

receive, at the first edge node, the push-based data, the pull-based data, and the queue-based data in a pre-determined time interval;

generate, at the first edge node, a plurality of data views of the integration data, according to the pre-determined time interval, the plurality of data views including the first data view and the second data view; and

queue, by the first edge node, the plurality of data views in a database.

20. The system of claim 19 , wherein the processor is configured to execute the computer-executable instructions to cause the processor further to:

receive, at the first edge node, the first update on the activities of users participating an incentive program in real-time;

update, by the first edge node and based on the first update, the queued plurality of data views in the database.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 8, 2025
From: GARAPATI, SUNITHA; GIOSTA, BRENT; PEARSALL, JENNIFER; VALLURI, VENU MADHAV
To: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
Reel/Frame 071975/0869 →
EMPLOYMENT AGREEMENT Recorded Jul 3, 2025
From: KROUTIL, RYAN
To: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
Reel/Frame 071878/0013 →
Continuity (3)
Continuation 16417943 · May 21, 2019
Provisional Application 62731449 · Sep 14, 2018
Related Publication 20230096917A1 · Mar 30, 2023