IP Library Granted Patent US 12,468,691
Granted Patent B2
US 12,468,691 · App. 18/540,797 · Granted Nov 11, 2025

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 12,468,691
App. No.
18/540,797
Granted
Nov 11, 2025
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 (64)

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 and pull-based data from a plurality of platform services; integrate, by the first edge node, the push-based data and the pull-based data into integration data having a format compatible with the plurality of platform services; present, at a second edge node of the integration platform and via a user interface (UI), a first view of the integration data, the first view including a first selectable icon representing a first incentive; receive, at the second edge node, an input via the first selectable icon, the input: being indicative of an activity associated with an incentive program, and causing the computing device to update, at the first edge node, incentive data in the integration data based on the activity associated with the incentive program; and initiate, based on the input and via an application programming interface (API), a first asynchronous call to populate, at the second edge node, a second view of the integration data, the second view including updated incentive data; wherein the instructions, when executed by the processor, further cause the computing device to: track, at the second edge node, an additional activity associated with the incentive program, the additional activity being conducted by a second user participating in the incentive program; update, at the first edge node, the incentive data in the integration data based on the additional activity; and initiate, via the API, a second asynchronous call to present to the user, at the second edge node, a third view of the integration data, the third view including updated incentive data based on the additional activity conducted by the second user.

2 . The non-transitory computer-readable medium of claim 1 , wherein the push-based data and the pull-based data are received in real-time, and the instructions, when executed by the processor, further cause the computing device to:

generate, at the first edge node, a plurality of views of the integration data, the plurality of views including the first view;

extract, by the first edge node, event-based data from the push-based data and the pull-based data;

generate, by the first edge node, queued events based on the event-based data;

queue, by the first edge node, the plurality of views of the integration data based on the queued events; and

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

3 . The non-transitory computer-readable medium of claim 1 , wherein the push-based data and the pull-based data are received as batched data, and the instructions, when executed by the processor, further cause the computing device to:

generate, at the first edge node, a plurality of views of the integration data, the plurality of views including the first view;

queue, by the first edge node, the plurality of views of the integration data according to the batched data; and

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

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

categorize, by the first edge node, the integration data into a plurality of subject types corresponding to a plurality of subject areas, respectively,

wherein the plurality of subject areas include agreement, customer, associate, claim, or financial transaction.

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

generate, at the first edge node, a plurality of views of the integration data based on the plurality of subject types.

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

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

generate, by the first edge node, a plurality of data structures in the database,

wherein the plurality of data structures represent the plurality of views of the integration data and facilitate access of the integration data via the API.

7 . 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 and pull-based data from a plurality of platform services; integrate, by the first edge node, the push-based data and the pull-based data into integration data having a format compatible with the plurality of platform services; present, at a second edge node of the integration platform and via a user interface (UI), a first view of the integration data, the first view including a first selectable icon representing a first incentive; receive, at the second edge node, an input via the first selectable icon, the input: being indicative of an activity associated with an incentive program, and causing the computing device to update, at the first edge node, incentive data in the integration data based on the activity associated with the incentive program; and initiate, based on the input and via an application programming interface (API), a first asynchronous call to populate, at the second edge node, a second view of the integration data, the second view including updated incentive data; wherein the instructions, when executed by the processor, further cause the computing device to: track, at the second edge node, an additional activity associated with the incentive program, the additional activity being conducted by a second user participating in the incentive program; update, at the first edge node, the incentive data in the integration data based on the additional activity; and initiate, via the API, a second asynchronous call to present to the user, at the second edge node, a third view of the integration data, the third view including updated incentive data based on the additional activity conducted by the second user.

8 . The method of claim 7 , wherein the push-based data and the pull-based data are received in real-time, and further comprises:

generating, at the first edge node, a plurality of views of the integration data, the plurality of views including the first view;

extracting, by the first edge node, event-based data from the push-based data and the pull-based data;

generating, by the first edge node, queued events based on the event-based data;

queueing, by the first edge node, the plurality of views of the integration data based on the queued events; and

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

9 . The method of claim 7 , wherein the push-based data and the pull-based data are received as periodically received as batched data, and further comprises:

generating, at the first edge node, a plurality of views of the integration data, the plurality of views including the first view;

queueing, by the first edge node, the plurality of views of the integration data according to the batched data; and

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

10 . The method of claim 7 , further comprising:

categorizing, by the first edge node, the integration data into a plurality of subject types corresponding to a plurality of subject areas, respectively,

wherein the plurality of subject areas include agreement, customer, associate, claim, or financial transaction.

11 . The method of claim 10 , further comprising:

generating, at the first edge node, a plurality of views of the integration data based on the plurality of subject types.

12 . 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 and pull-based data from a plurality of platform services; integrate, by the first edge node, the push-based data and the pull-based data into integration data having a format compatible with the plurality of platform services; present, at a second edge node of the integration platform and via a user interface (UI), a first view of the integration data, the first view including a first selectable icon representing a first incentive; receive, at the second edge node, an input via the first selectable icon, the input being indicative of an activity associated with an incentive program and causing an update, at the first edge node, incentive data in the integration data based on the activity associated with the incentive program; and initiate, based on the input and via an application program interface (API), a first asynchronous call to populate, at the second edge node, a second view of the integration data, the second view including updated incentive data; wherein the instructions, when executed by the processor, further cause the computing device to: track, at the second edge node, an additional activity associated with the incentive program, the additional activity being conducted by a second user participating in the incentive program; update, at the first edge node, the incentive data in the integration data based on the additional activity; and initiate, via the API, a second asynchronous call to present to the user, at the second edge node, a third view of the integration data, the third view including updated incentive data based on the additional activity conducted by the second user.

13 . The system of claim 12 , wherein the push-based data and the pull-based data are received in real-time, and the computer-executable instructions, when executed by the processor, further cause the processor to:

generate, at the first edge node, a plurality of views of the integration data, the plurality of views including the first view;

obtain, by the first edge node, event-based data from the push-based data and the pull-based data;

generate, by the first edge node, queued events based on the event-based data;

queue, by the first edge node, the plurality of views of the integration data based on the queued events; and

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

14 . The system of claim 12 , wherein the instructions, when executed by the processor, further cause the processor to:

categorize, by the first edge node, the integration data into a plurality of subject types corresponding to a plurality of subject areas, respectively,

wherein the plurality of subject areas include agreement, customer, associate, claim, or financial transaction.

15 . The system of claim 14 , wherein the instructions, when executed by the processor, further cause the processor to:

generate, at the first edge node, a plurality of views of the integration data based on the plurality of subject types.

16 . The system of claim 15 , wherein the instructions, when executed by the processor, further cause the processor to:

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

generate, by the first edge node, a plurality of data structures in the database,

wherein the plurality of data structures represent the plurality of views of the integration data and facilitate access of the integration data via the API.

17 . A system comprising:

a non-transitory memory;

a processor;

means for receiving by the processor, at a first edge node of an integration platform of the system, push-based data and pull-based data from a plurality of platform services;

means for integrating by the processor, by the first edge node, the push-based data and the pull-based data into integration data having a format compatible with the plurality of platform services;

means for presenting by the processor, at a second edge node of the integration platform of the system and via a user interface (UI), a first view of the integration data, the first view including a first selectable icon representing a first incentive;

means for receiving by the processor, at the second edge node, an input via the first selectable icon, the input being indicative of an activity associated with an incentive program and causing an update, at the first edge node, incentive data in the integration data based on the activity associated with the incentive program; and

means for initiating by the processor, based on the input and via an application program interface (API), a first asynchronous call to populate, at the second edge node, a second view of the integration data, the second view including updated incentive data.

18 . The non-transitory computer-readable medium of claim 1 , wherein the second view of the integration data includes a second selectable icon representing a second incentive.

19 . The non-transitory computer-readable medium of claim 1 , wherein

the activity associated with the incentive program indicates that a user participating in the incentive program meets a goal, and

updating the incentive data includes updating an incentive plan setup for the user based on the user meeting the goal.

Assignments (1)
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 →
Continuity (4)
Continuation 17980456 · Nov 3, 2022
Continuation 16417943 · May 21, 2019
Provisional Application 62731449 · Sep 14, 2018
Related Publication 20240111761A1 · Apr 4, 2024
References Cited (65)
US 6351761B1 · Cantone et al. · 2002 [cited by applicant]
US 9426833B2 · Mufti et al. · 2016 [cited by applicant]
US 9779173B2 · Parsons et al. · 2017 [cited by applicant]
US 9805078B2 · Agarwal et al. · 2017 [cited by applicant]
US 10049407B2 · Bradshaw · 2018 [cited by applicant]
US 10545951B1 · Lieberman · 2020 [cited by applicant]
US 10713726B1 · Allen et al. · 2020 [cited by applicant]
US 10775976B1 · Abdul-Jawad et al. · 2020 [cited by applicant]
US 10944641B1 · Zacks et al. · 2021 [cited by applicant]
US 11087403B2 · Crabtree · 2021 [cited by applicant]
US 11176104B2 · Chauhan · 2021 [cited by applicant]
US 20020188702A1 · Short, III et al. · 2002 [cited by applicant]
US 20040143464A1 · Houle · 2004 [cited by applicant]
US 20060136273A1 · Zizzamia et al. · 2006 [cited by applicant]
US 20070061487A1 · Moore et al. · 2007 [cited by applicant]
US 20070195944A1 · Korenblit et al. · 2007 [cited by applicant]
US 20080172391A1 · Adelman et al. · 2008 [cited by applicant]
US 20100180206A1 · Silva, Jr. et al. · 2010 [cited by applicant]
US 20110022471A1 · Brueck et al. · 2011 [cited by applicant]
US 20110265116A1 · Stern et al. · 2011 [cited by applicant]
US 20130246588A1 · Borowicz et al. · 2013 [cited by applicant]
US 20130346151A1 · Bleakley et al. · 2013 [cited by applicant]
US 20140156806A1 · Karpistsenko · 2014 [cited by examiner]
US 20140279764A1 · Lahr · 2014 [cited by applicant]
US 20140282796A1 · Walker et al. · 2014 [cited by applicant]
US 20140325366A1 · Dunphey · 2014 [cited by examiner]
US 20150040052A1 · Noel et al. · 2015 [cited by applicant]
US 20150142501A1 · Nair · 2015 [cited by applicant]
US 20150146963A1 · Klein et al. · 2015 [cited by applicant]
US 20160034491A1 · Chen · 2016 [cited by examiner]
US 20160086082A1 · Babinowich et al. · 2016 [cited by applicant]
US 20160328775A1 · Lloyd et al. · 2016 [cited by applicant]
US 20170006135A1 · Siebel et al. · 2017 [cited by applicant]
US 20170048095A1 · Sun et al. · 2017 [cited by applicant]
US 20170168878A1 · Chandra et al. · 2017 [cited by applicant]
US 20170171050A1 · Puzis et al. · 2017 [cited by applicant]
US 20170192758A1 · Apte et al. · 2017 [cited by applicant]
US 20170220334A1 · Hart et al. · 2017 [cited by applicant]
US 20170223128A1 · Shuvaev et al. · 2017 [cited by applicant]
US 20170331923A1 · Smedberg et al. · 2017 [cited by applicant]
US 20170353946A1 · Rico Alvarino et al. · 2017 [cited by applicant]
US 20180159746A1 · Li et al. · 2018 [cited by applicant]
US 20180239615A1 · Ravid et al. · 2018 [cited by applicant]
US 20190155961A1 · Alonso et al. · 2019 [cited by applicant]
US 20190287032A1 · Seabolt et al. · 2019 [cited by applicant]
US 20190362290A1 · Rogynskyy · 2019 [cited by examiner]
US 20190378428A1 · Nevarez et al. · 2019 [cited by applicant]
US 20200012656A1 · Pugh · 2020 [cited by examiner]
US 20200053280A1 · Han et al. · 2020 [cited by applicant]
US 20210326336A1 · Garapati et al. · 2021 [cited by applicant]
US 20230042238A1 · Reynolds · 2023 [cited by applicant]
US 20230096917A1 · Garapati · 2023 [cited by applicant]
WO WO2006031747 · 2006 [cited by applicant]
Non Final Office Action dated Aug. 19, 2020 for U.S. Appl. No. 16/417,943, “Big-Data View Integration Platform”, Garapati, 13 pages. [cited by applicant]
Non Final Office Action dated Aug. 24, 2020 for U.S. Appl. No. 16/417,919, “Big-Data View Integration Platform”, Garapati, 15 pages. [cited by applicant]
Office Action dated Feb. 16, 2021 for U.S. Appl. No. 16/417,943, “Big-Data View Integration Platform”, Garapati, 14 pages. [cited by applicant]
Office Action for U.S. Appl. No. 16/417,943, mailed Apr. 18, 2022, Garapati, “Big-Data View Integration Platform”, 20 pages. [cited by applicant]
Office Action for U.S. Appl. No. 16/417,943, mailed on Jun. 8, 2021, Garapati, “Big-Data View Integration Platform”, 15 Pages. [cited by applicant]
Office Action for U.S. Appl. No. 16/417,943, mailed on Dec. 8, 2021, Garapati, “Big-Data View Integration Platform”, 17 Pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/365,432, mailed Aug. 5, 2022, Garapati, “Big-Data View Integration Platform”, 24 pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/392,734, mailed on Jan. 31, 2023, Reynolds, “Systems and Methods for Generating Insurance Business Plans”, 18 pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/392,734, mailed on Oct. 13, 2022, Reynolds, “Systems and Methods for Generating Insurance Business Plans”, 15 Pages. [cited by applicant]
Oracle Business Process Services, Big Data, and Enterprise Data, Bridging Two Worlds with Oracle Data Integration, White Paper, Jan. 2019, 9 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 18/465,348, dated Dec. 31, 2024, 24 pages. [cited by applicant]
Office Action for U.S. Appl. No. 18/465,348, dated Apr. 29, 2925, 21 pages. [cited by applicant]