Real-time event-based notification system

• US 10,757,154 B1
• Filed: 11/23/2016
• Issued: 08/25/2020
• Est. Priority Date: 11/24/2015
• Status: Active Grant

• Current Assignee: Experian Information Solutions Incorporated (Experian plc)
• Original Assignee: Experian Information Solutions Incorporated (Experian plc)
• Inventors: Jacobs, Dwayne Charles, Kanthadai, Srikumar Puthupadi
• Primary Examiner(s): Tokuta, Shean
• Assistant Examiner(s): Turriate Gastulo, Juan C
• Application Number:
  US15/360,496
• Time in Patent Office: 1,371 Days
• CPC Class Codes: G06Q 40/03 Credit; Loans; Processing thereof
• CPC Class Codes: H04L 65/611 for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06

Abstract

Methods and systems are provided for generating alerts in association with a request for credit data or an update to credit data. For example, information identifying an individual may be received from a credit bureau when an individual applies for a product or service from a requesting entity. The requesting entity may be a product or service provider that requests credit data of potential purchasers of its products. An electronic notification may then be sent in association with an event object generated by a notification system that is broadcast for delivery to one or more other systems, where the event object may be broadcast substantially in real time, such as via an enterprise server bus, relative to the requesting entity'"'"'s initial request.

Claims

1. A computing system comprising:

an electronic data store configured to store credit data;

a first computing system comprising one or more computing devices, said computing system in communication with the electronic data store and configured to at least;

receive an indication of at least one of;

a request for information regarding an individual submitted by a requesting entity or information about an action that affects the individual'"'"'s credit data;

based at least in part on the indication, determine that the request for information meets one or more event broadcast criteria;

generate a broadcast event object, wherein the broadcast event object includes an event type and at least a portion of the indication of the request for information;

electronically post the generated broadcast event object to an enterprise service bus,

wherein posting the generated broadcast event object triggers a plurality of listeners based on the event type, wherein the event type comprises at least one of;

requesting for a loan, paying off a debt, or a credit inquiry, each of the plurality of listeners having access to the enterprise service bus and each associated with processing and/or reporting related to particular broadcast event objects to identify a plurality of subscribers registered to receive broadcast event objects from the enterprise service bus that relate to the event type, wherein the plurality of subscribers are computing systems associated with one or more entities other than the individual, the requesting entity, and the plurality of listeners; and

send the broadcast event object to the identified subscribers, wherein at least one identified subscriber is configured to generate a message based on the broadcast event object and transmit the message directly to the individual.

2. The computing system of claim 1, wherein the identified subscribers receive the broadcast event object at substantially the same time as each other.

3. The system of claim 1, wherein the message is further based at least in part on information about the individual not included in the request for information.

4. The computing system of claim 1, wherein the request comprises at least one of:

a request for a credit file, a credit status dispute, a credit freeze, a credit lock, a credit thaw, a credit lift, or a security event.

16. The system of claim 1, wherein a listener of the plurality of listeners is configured to, in response to being executed by the first computing system, generate a first payload for a first subscriber and a second payload for a second subscriber, wherein the first payload is different than the second payload.

17. The system of claim 1, wherein is the first computing system is further configured to, in response to the plurality of listeners being executed by the first computing system, generate a first payload including first data, and generate a second payload for a second listener of the plurality of listeners based on the first data, wherein the second listener is configured to generate a third payload including second data and send the third payload to at least one of the plurality of subscribers.

18. The system of claim 1, wherein sending the broadcast event object to the identified subscribers occurs in real time with respect to receiving the indication.

19. The system of claim 1, wherein transmitting the message directly to the individual occurs in real time of the at least one identified subscriber receiving the broadcast event object.

5. A computer-implemented notification method comprising:

receiving an indication of at least one of;

a request for information regarding an individual has been submitted by a requesting entity or information about an action that affect credit data of the individual;

based at least in part on the indication, determine that the request for information meets one or more event broadcast criteria;

generate a broadcast event object associated with the indication, wherein the broadcast event object includes at least (a) data associated with the request for information regarding the individual, and (b) an indicator of an event type;

electronically post the broadcast event object to an enterprise service bus, wherein posting the broadcast event object triggers a plurality of listeners based on the event type, wherein the event type comprises at least one of;

requesting for a loan, paying off a debt, or a credit inquiry;

identify subscribers registered to receive broadcast event objects from the enterprise service bus that relate to the event type; and

send the broadcast event object to the identified subscribers, wherein receipt of the broadcast event object by at least one identified subscriber causes the at least one identified subscriber to generate a message based on the broadcast event object and send the message directly to the individual.

6. The method of claim 5, wherein the message includes suggestions of actions the individual can perform to improve the information requested by the requesting entity.

7. The method of claim 5, wherein the request comprises at least one of:

a request for a credit file, a credit status dispute, a credit freeze, a credit lock, a credit thaw, a credit lift, or a security event.

8. The method of claim 5, wherein the indication is associated with a change in credit data, and the event broadcast criteria comprises whether the change in credit data meets a threshold value.

9. A computer-implemented notification method comprising:

receiving an indication of an action that affects credit information related to an entity;

generate a first broadcast event object associated with the credit information, wherein the first broadcast event object includes at least data associated with the update;

electronically post the generated first broadcast event object to an enterprise service bus, wherein posting the generated first broadcast event object triggers a plurality of listeners based on an event type, each of the plurality of listeners having access to the enterprise service bus and each associated with one or more of;

processing or reporting related to particular broadcast event objects to identify a plurality of subscribers registered to receive broadcast event objects that relate to the event type associated with the indication, wherein the event type comprises at least one of;

a request for a loan, paying off a debt, or a credit inquiry, wherein the plurality of subscribers include a first subscriber that comprises a first computing system associated with a second entity that is different than the entity and the listeners; and

send the first broadcast event object to a first computing system of the first subscriber, wherein the broadcast event object causes the first computing system of the first subscriber to generate a message based on the broadcast event object and send the message directly to the individual.

10. The method of claim 9, wherein the request comprises at least one of:

a request for credit information, a request for a credit file, a credit status dispute, a credit freeze, a credit lock, a credit thaw, a credit lift, or a security event.

11. The method of claim 9, further comprising:

receiving non-credit information related to the entity,

wherein the broadcast event is further associated with the non-credit information of the entity.

12. The method of claim 9, further comprising:

determine that the update to credit information meets one or more event broadcast criteria,

wherein broadcasting the first broadcast event object is in response to determining that the update to the credit information meets the one or more event broadcast criteria.

13. The method of claim 12, wherein the update comprises a change in a credit score, and the broadcast criteria comprises whether the change in the credit score meets a threshold value.

14. The method of claim 12, wherein the message includes suggestions the entity can perform to improve the credit information.

15. The method of claim 12, further comprising:

generating a second broadcast event object based on the first broadcast event object; and

broadcast the second broadcast event object to a subscriber.