Systems And Methods Of Processing Insurance Data Using A Web-Scale Data Fabric

• US 20140278575A1
• Filed: 03/07/2014
• Published: 09/18/2014
• Est. Priority Date: 03/15/2013
• Status: Abandoned Application

• Current Assignee: State Farm Mutual Automobile Insurance Company (State Farm)
• Original Assignee: State Farm Mutual Automobile Insurance Company (State Farm)
• Inventors: Anton, Alex, Sanidas, Tim G., Perschall, Jeff, Bernico, Michael, Cook, Michael K., Calvo, Lynn, Kanneganti, V. Rao
• Application Number:
  US14/201,046
• Publication Number:
  US 20140278575A1
• Time in Patent Office: Days
• US Class Current: 705/4
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 16/9537 Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
• CPC Class Codes: G06Q 40/08 Insurance
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Methods and systems for processing data, such as insurance data, using a Web-Scale Data Fabric (WSDF). According to embodiments, a stream ingestion hardware component can ingest messages related to an actionable event and send data objects to an in-memory data store based on the messages. The in-memory data store can retrieve insurance policy information that may be applicable to the actionable event and store the insurance policy information in cache memory. A search-based application interfaces with the in-memory data store to search for and retrieve data associated with the insurance policy information, from which a user or administrator may process or otherwise access the information. The systems and methods can further initiate insurance claim processing as well as enrich the data using various techniques to enable real-time search.

Claims

1. A system for processing insurance data, the system comprising:

a stream ingestion hardware component adapted to receive data relating to an actionable event and configured to generate a data object based on the received data;

a historical data store adapted to store a plurality of customer insurance policies;

an in-memory data store adapted to communicate with the stream ingestion hardware component and with the historical data store, the in-memory data store configured to;

receive the data object from the stream ingestion hardware, and

use the data object to retrieve, from the historical data store, insurance data associated with at least one of the plurality of customer insurance policies; and

a search application adapted to interface with the in-memory data store and configured to;

receive, from a requesting entity, a request to access at least a portion of the insurance data,

retrieve at least the portion of the insurance data from the in-memory data store, and

provide at least the portion of the insurance data to the requesting entity.

2. The system of claim 1, wherein the stream ingestion hardware component receives the data relating to an actionable event as an advanced message queuing protocol (AMQP) message and generates the data object as a data transfer object (DTO).

3. The system of claim 1, wherein the in-memory data store is further configured to:

employ complex event processing (CEP) to examine the data object to identify an actionable event, and wherein the in-memory data store retrieves the insurance data associated with the at least one of the plurality of customer insurance policies in response to identifying the actionable event.

4. The system of claim 1, wherein the in-memory data store includes a data cache, wherein the in-memory data store is configured to store the insurance data in the data cache.

5. The system of claim 4, wherein the stream ingestion hardware component receives the data relating to the actionable event as data related to a first notice of loss (FNOL) event.

6. The system of claim 5, further comprising a claim system adapted to interface with the in-memory data store, wherein the in-memory data store compares the retrieved insurance data to the additional data object to determine that the actionable event is covered by the at least one of the plurality of customer insurance policies, and wherein the in-memory data store is further configured to:

generate a policy transaction for the at least one of the plurality of customer insurance policies, the policy transaction based on the actionable event, and

submit the policy transaction to the claim system.

7. The system of claim 6, wherein the in-memory data store is further configured to send data indicative of the policy transaction to the historical data store, and wherein the historical data store is further configured to update the at least one of the plurality of customer insurance policies with the data indicative of the policy transaction.

8. The system of claim 1, wherein the in-memory data store is further configured to examine the data object to identify a geographical area associated with the actionable event, wherein the at least one of the plurality of customer insurance policies is retrieved based on the geographical area.

9. The system of claim 1, wherein the in-memory data store is further configured to enrich the data object using at least one of low-latency indexing and semantic processing, and wherein the search application is further configured to:

retrieve the enriched data object from the in-memory data store, and

provide the enriched data object to the requesting entity.

10. The system of claim 9, wherein the in-memory data store is further configured to generate processed insurance data based on the enriched data object and at least the portion of the insurance data.

11. A method of processing insurance data, the method comprising:

receiving, from a source, a message related to an event;

generating a data object based on the message;

examining the data object to determine that the event is an actionable event related to insurance data processing;

responsive to examining the data object, retrieving, from a historical data store using the data object, insurance data associated with at least one customer insurance policy;

storing the insurance data in a cache memory;

receiving, from a requesting entity, a request to access at least a portion of the insurance data;

responsive to receiving the request, retrieving at least the portion of the insurance data from the cache memory; and

providing at least the portion of the insurance data to the requesting entity.

12. The method of claim 11, wherein receiving the message comprises receiving an advanced message queuing protocol (AMQP) message, and wherein generating the data object comprises generating a data transfer object (DTO).

13. The method of claim 11, wherein examining the data object comprises employing complex event processing (CEP) to examine the data object.

14. The method of claim 11, wherein receiving the message related to the event comprises one of receiving a feed from a service or receiving an alert from a supporting business entity.

15. The method of claim 14, wherein receiving the message related to the event comprises receiving data relating to a first notice of loss (FNOL) event.

16. The method of claim 11, further comprising:

determining that the actionable event is covered by the at least one customer insurance policy;

generating a policy transaction for the at least one customer insurance policy, the policy transaction based on the actionable event; and

submitting the policy transaction to a claim system.

17. The method of claim 16, further comprising:

sending data indicative of the policy transaction to the historical data store, wherein the historical data store updates the at least one of the plurality of customer insurance policies with the data indicative of the policy transaction.

18. The method of claim 11, further comprising:

examining the data object to identify a geographical area associated with the actionable event, wherein the at least one of the plurality of customer insurance policies is retrieved based on the geographical area.

19. The method of claim 11, further comprising:

enriching the data object using at least one of low-latency indexing and semantic processing; and

providing the enriched data object to the requesting entity.

20. The method of claim 19, further comprising generating processed insurance data based on the enriched data object and at least the portion of the insurance data.

21. A system for processing data, the system comprising:

a stream ingestion hardware component adapted to receive data and generate a data object based on the received data;

a historical data store adapted to store historical data related to the received data;

an in-memory data store adapted to communicate with the stream ingestion hardware component and with the historical data store, the in-memory data store configured to;

receive the data object from the stream ingestion hardware, and

use the data object to retrieve, from the historical data store, at least a portion of the historical data; and

a search application adapted to interface with the in-memory data store and configured to;

receive, from a requesting entity, a request to access at least the portion of the historical data,

retrieve at least the portion of the historical data from the in-memory data store, and

provide at least the portion of the historical data to the requesting entity.

22. The system of claim 21, wherein the historical data includes customer data.

23. The system of claim 21, wherein the stream ingestion hardware component receives the data as an advanced message queuing protocol (AMQP) message and generates the data object as a data transfer object (DTO).

24. The system of claim 21, wherein the in-memory data store is further configured to enrich the data object using at least one of low-latency indexing and semantic processing, and wherein the search application is further configured to:

retrieve the enriched data object from the in-memory data store, and

provide the enriched data object to the requesting entity.

25. The system of claim 21, wherein the in-memory data store includes a data cache, wherein the in-memory data store is configured to store at least the portion of the historical data in the data cache.