Real-time event-based notification system

Information

  • Patent Grant
  • 11729230
  • Patent Number
    11,729,230
  • Date Filed
    Wednesday, September 22, 2021
    3 years ago
  • Date Issued
    Tuesday, August 15, 2023
    a year ago
  • CPC
    • H04L65/611
    • G06Q40/03
  • Field of Search
    • CPC
    • H04L65/611
    • G06Q40/025
  • International Classifications
    • H04L29/06
    • H04L65/611
    • G06Q40/03
    • Disclaimer
      This patent is subject to a terminal disclaimer.
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.
Description
BACKGROUND

When an individual applies for a product or service with an entity, the entity often times requires credit information of the individual. The entity requests credit information for the individual from a credit bureau. Then the entity factors in credit information when negotiating the terms of the product or service with the individual. For example, an entity may present a loan with lower interest rates for individuals with higher credit scores than for individuals with lower credit scores. Credit information may also affect ancillary terms of an agreement. For example, the entity may require a different down payment for a real estate loan based on a credit score. When a credit bureau receives a request for credit information regarding a given consumer from a requesting entity, the bureau typically retrieves the relevant data from a credit database maintained by the bureau, generates a credit score (if requested), returns the credit data and score to the requesting entity, and may record additional information in the consumer's credit file (such as recording that a credit inquiry was received).





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1A is a functional block diagram showing a sample high-level flow of events related to a notification system, according to certain embodiments.



FIG. 1B is a functional block diagram showing another sample high-level flow of events related to a notification system, according to certain embodiments.



FIG. 2A is a flowchart illustrating one embodiment of a method for sending a broadcast event to subscribers based on a request for credit data.



FIG. 2B is a flowchart illustrating one embodiment of a method for sending a broadcast event to subscribers based on an action that affects credit data.



FIG. 3A illustrates one embodiment of a system that implements aspects of the present disclosure, such as broadcasting events to one or more subscribers.



FIG. 3B is a flow diagram illustrating an example embodiment of a notification system that outputs custom payloads to multiple subscribers.



FIG. 3C is a flow diagram illustrating the example notification system executing a multi-phase processing of an event in order to generate a custom payload for a subscriber.



FIG. 3D is a flow diagram illustrating an example processing method that may be performed by the notification system to reduce processing cycles required to identify matching listeners from a large set of multiple available listeners (e.g., hundreds, thousands, or millions of different listeners).



FIG. 3E is a flow diagram illustrating example event/payload data that may be transformed in various ways to provide a custom payload to a subscriber.



FIGS. 3F, 3G, and 3H are example payloads that may be provided to a subscriber.



FIG. 4A is an illustrative representation of a table associating individual consumer information with credit information and information associated with a request for credit data.



FIG. 4B is an illustrative representation of a table associating financial institutions with vendors and/or service providers, along with corresponding contact and other information.



FIG. 5 is an illustrative representation of block diagram illustrating the ecosphere of notification system and associated modules.





These and other features will now be described with reference to the drawings summarized above. The drawings and the associated descriptions are provided to illustrate certain embodiments and not to limit the scope of the invention. Throughout the drawings, reference numbers may be re-used to indicate correspondence between referenced elements.


DETAILED DESCRIPTION

Among other things, this disclosure describes systems and methods for providing alerts in association with monitored events, where the alerts may be electronically delivered to a number of event subscribers substantially in real time relative to the occurrence of an underlying event trigger.


In conventional negotiations and transactions, an entity that is selling products or services may have more information (e.g. credit information) than a buyer when bargaining for the entity's products or services. Without understanding, at the point of negotiation, the condition of an individual's credit data, the individual is placed at a disadvantage. The individual does not know whether an offer for sale or extension of credit is a reasonable one based on the individual's credit data. Furthermore, the individual may not know whether credit data can be easily improved to order to simply return at a later time for a better product or service. The individual may not know if the offer for the service or product is reasonable based on other services and products that the individual is qualified for from other vendors.


Furthermore, credit data may be maintained by a credit bureau which may include account data for millions of customers based on information retrieved from a myriad of different sources. The credit bureaus receive information that may result in changes to credit data (e.g. payments or inquiries change a credit file), but many of these payments take about thirty to sixty days to update. Generally, a credit bureau system utilizes batch processing on a periodic basis to update the credit file. Thus, an individual may not have access to opportunities such as an extension of credit or better products or services until the update takes effect on the credit data. Product and service providers would also have to wait before identifying the individual as having met a certain criteria for a product or service.


Disclosed herein are systems and methods for generating event objects that meet a certain criteria and then generating an alert including an event message that may be electronically delivered to a number of event subscribers substantially in real time relative to the occurrence of an underlying event trigger. In some embodiments, a “publish and subscribe” events-based architecture may be implemented to distribute the alert in real time to target end point systems. Aspects of the present disclosure include a notification system that provides an alert to event subscribers to cause the event subscribers to send relevant information to an individual (e.g. current credit data, credit score) in association with activity related to credit data, such as a request for credit data from the credit bureau, as well as providing notification to the individual on other information (e.g. alternative products or services, suggestions and advice).


As used herein, a “notification module” generally describes any software, firmware, and/or hardware that provides a backbone to publish and subscribe events. For example, a notification module may include an enterprise service bus (“ESB”), data streaming technology, or any other technology that can publish to subscribers. Certain examples herein refer to an enterprise bus or ESB for ease of description, but those embodiments may be implemented with any other notification module discussed herein and/or later developed. For example, the notification module may leverage an Enterprise Service Bus (“ESB”) architecture when a trigger event meets certain broadcast criteria (e.g. an increase of a credit score by a certain value, a credit score meeting a threshold, or debt below a certain number). The notification system may generate an event object based on the broadcast criteria to post to an ESB, and the notification module may send a broadcast event message based on the event object to subscribers, allowing subscribers to obtain information on the individual in real-time.


Subscribers may use the information in the event object to send alerts to individuals in real time. Equipping the individual with such information empowers the individual with real time facts that will help him or her in the negotiation process. For example, in some embodiments, information identifying an individual may be sent to a credit bureau from a requesting entity in response to a request for a car loan. The requesting entity may be, in some embodiments, a vendor or service provider for the car loan and the entity that receives information from the individual to send to the credit bureau asking for credit data. In response to the credit bureau receiving the request for credit data from the requesting entity, the credit bureau may respond with credit data to the requesting entity. The credit bureau may also determine information derived from the inquiry (e.g. name of the requesting entity, purpose for the inquiry) and send the derived information to a notification system.


The notification system may assess the information derived from the inquiry, in particular whether the information meets a certain broadcast event criteria. This assessment may be the decisioning for generating a broadcast event object. For example, the notification system may assess whether the request meets a certain criteria (e.g. a credit score increase of 80 points or a total score greater than 700), which may be associated with one or more subscribers. Based on such criteria, the notification system may generate a broadcast event object. The notification system may generate a broadcast event object if the information received from the credit bureau indicates that a broadcast event criteria has been met. In other embodiments, the notification may generate multiple broadcast event objects where each broadcast event object is created based on its own set of broadcast criteria, which may each have been established with respect to different subscribers.


In some embodiments, the notification system receives information derived from the inquiry for credit data. The notification system can additionally receive other information about the individual, such as transactional data, personal identification information (“PID”), medical information, information associated with big data (e.g. search or browser history), and/or other information to determine and generate an event. In some embodiments, the event can identify (or be associated with data that identifies) a category of subscribers to receive information or updates associated with the individual. In some embodiments, the event can include information that can be posted to an enterprise service bus to be sent to subscribers to the enterprise service bus. The subscribers can then determine alerts that can be generated that provide value to the individual. For example, the individual may receive an alert that indicates the individual's latest credit score and/or other relevant information (e.g. how the credit data has changed recently, any mechanisms or actions that can be used or performed to increase the credit score, and/or other information).


Furthermore, the subscriber may extend offers to the individual providing the individual a baseline for the negotiation and that provides immediate alternative offers to compare. For example, the notification system may receive an indication from the credit bureau that the request for credit information came from a car dealership. The notification system may have a broadcast event criterion that identifies requests for individuals interested in a car loan. The notification system may generate a broadcast event object for the criterion, and post the broadcast event object to an ESB and/or other notification module. The ESB can then send a broadcast event message based on the broadcast event object to subscribers that are subscribed to the broadcast event criterion. The subscriber may receive information that the individual requested a car loan from a particular car dealership. The subscriber may determine loan details that the individual may be pre-qualified for to send to the individual based on the individual's credit data. Then, as the individual is negotiating with the car dealership, the individual will be empowered with an alternative loan such that the individual can simply walk away from the loan from the car dealership and go with the loan in the alert. The individual may also be equipped with sufficient information to understand that the individual can step away, take mitigating actions to improve the credit data, and reapply for the product/service for better terms.


Aspects of the present disclosure offer technical advancements that provide vendors and service/product providers with a new and effective way to market their products immediately at the point of sale. Traditionally, vendors and providers can send their marketing alerts at particular times (e.g. daily, monthly), or embedded in certain websites (e.g. searching for a particular product on a search engine or social media feed). However, aspects of the present disclosure provide a notification system that can generate a broadcast event object based on certain criteria and utilize a notification module (e.g. an ESB) to send a broadcast event message to vendors and service/product providers in substantially real-time from the event trigger in order to enable vendors and service/product providers to offer alternative offers for sale in real time as the individual is negotiating a competitor's offer for sale.


Various embodiments of systems, methods, processes, and data structures will now be described with reference to the drawings. Variations to the systems, methods, processes, and data structures that represent other embodiments will also be described.


Credit data may be maintained by a credit bureau or similar entity. Credit data maintained by a given credit bureau may include account data for millions or even billions of customers, where each customer identified in the data may have one or more accounts. The credit data may be based on several sources of data which include existing trade data, new trade data, inquiries, public record data (for example, bankruptcy filings), change of address data, and so forth. A common type of credit data is “tradeline data” (or trade data). Tradeline data may be an entry by a credit grantor to a consumer's credit history which is maintained by a credit reporting agency. A tradeline describes the consumer's account status and activity and can include names of companies with which the applicant has accounts, dates the accounts were opened, credit limits, types of accounts, account balances, payment histories, and/or other data.


In the United States, for example, multiple credit bureaus are constantly receiving data from a large number of data sources, including, for example, banks, creditors and other account providers. The credit bureaus use the data, among other things, to provide credit reports, credit scores and other credit-related products or services to consumers and businesses. The systems of a given credit bureau are typically tailored to specific legal and business requirements based on a number of factors, as well as the needs of its customers, which may have evolved over a long period of time.


In the United States, three hundred million consumers make payments to over fifty thousand entities every month, totaling thirty-five billion payments each year. The entities may include a variety of banks, utility companies, property owners, and the like. Many of these payments take about thirty to sixty days to show up on the consumers' credit ledgers after the payments are made. Generally, the reporting entities and a typical credit bureau system utilize batch processes on a periodic basis to update many aspects of a credit bureau's electronic records.


Disclosed herein are systems and methods for delivering key event alerts, such as credit inquiries and credit dispute status updates, in real time or near-real time from a system operated by a credit bureau to other systems either internal or external to the credit bureau. In some embodiments, a “publish and subscribe” events-based architecture may be implemented to build a real time “pub/sub” protocol, whereby transactions or business events from a producer system (e.g., a central credit bureau system, and/or various other systems) can be distributed to target end point systems (such as subscribers) simultaneously in real time. In some embodiments, the notification system uses data streaming to distribute the events.


In some embodiments, an event may be sent via a notification module when a significant change of state occurs in the producer system in which one or more target systems or end-point subscribers are interested. This events-based architecture may complement Services Oriented Architecture principles, whereby each change of state in the producer system may be considered a unique event and wrapped as a “business service” to be delivered to target end points or systems. Aspects of the present disclosure may provide a foundation for a loosely coupled enterprise architecture, thereby significantly reducing if not eliminating the need for point-to-point integration between application systems and the associated complexity.


Aspects of the present disclosure may leverage the capability of a notification module, such as an ESB, data streaming, or other publish and subscribe middleware, to implement an events-based architecture, and may be used to deliver atomic events in a publish and subscribe model. The publisher may be a system of records that creates various atomic events, and the subscriber may be a system that consumes the events. The publisher may deliver the events to various subscribers by posting the event in an Enterprise Service Bus. In some embodiments, the ESB may eliminate any point-to-point integration between the publisher and subscriber, and act as a backbone channel for both delivery of events to many subscribers and the clustering of different application systems within the enterprise. An ESB software suite, potentially combined with specialized hardware in some embodiments, may provide a mechanism wherein the events manifested from the publishing system can be cataloged, and each subscribing system can subscribe to certain atomic events from the catalog based on event type and/or various data or metadata associated with each event. In some embodiments, the publisher of events may not even know how many subscribers are there, as the ESB may render these events to different subscribers through listeners which are associated with each subscriber in the ESB framework. The ESB may also provide a flexibility whereby the role of producers and subscribers can be reversed, so that each application system can be either producing events or consuming events. In some embodiments, a single system may be both a producer and subscriber with respect to different events. For example, a given system may automatically produce an event in response to some other event that it consumes. The ESB backbone can also be leveraged, in some embodiments, to implement request-reply web services for any application systems clustered in an ESB cluster.


In some embodiments, a publish and subscribe model as described herein may provide functionality whereby a publisher effectively posts an event once for consumption by a large number of listeners or subscribers. Individual listeners may be configured to react to certain events uniquely by event type and/or other information, then repost a subsequent response event to the ESB.


In general, it is desirable for the payload of an event posted to the bus to be relatively small (e.g., less than a few hundred bytes). Accordingly, in some embodiments, an application programming interface (“API”) and/or other functionality provided by an operator of a credit bureau may be configured to receive data from various sources and package the data into an event object in a manner that ensures a payload size below a pre-established threshold set based on size or efficiency benchmarks established to meet the technical and/or business needs of the ESB and/or credit bureau. For example, the event may provide notification of a change in credit data, personal identification information, information on the requesting entity, and/or other credit data.


In some embodiments, an API may be provided that enables consumers and/or financial entities (e.g., banks, credit card providers, etc.) to report credit data for inclusion in a credit bureau database in a real time manner utilizing features of the ESB architecture. As volume needs increase, systems disclosed herein may be scalable and self-adjusting, such as by automatically triggering multiple instances of an API to scale to volume or bandwidth needs. In some embodiments, many aspects of the system may be designed to have built-in redundancy and/or may be modular in order to enable increased flexibility.


The data layout of an event may depend on the type of event. For example, a generic layout may be established and used for certain events, while other events may be organized in a customized format based on the event type, specific subscriber needs, the producer's needs, and/or other factors. As a specific example in one embodiment, the payload of an event for reporting a credit inquiry may include fields indicating a consumer's basic information (e.g., name, birthday and social security number), credit data, address information, and the name of the inquiring entity. In some embodiments, the payload of an event may be in a JSON format in order to minimize ties to any specific schema, although other configurations (e.g., XML) are contemplated and intended to be within the scope of this disclosure. In some embodiments where multiple payload formats can be posted to and processed by the same ESB, only certain listeners/subscribers may be configured to process specific formats (e.g., a customized data layout may be used for a specific bank listener).


In some embodiments, the ESB may be configured to process both regulated and non-regulated data. For example, certain types of credit data and personal information may be regulated by one or more government entities in a given region or country. The ESB may be configured such that any events posted to the bus are checked automatically to determine whether the data types involved trigger any rules that require certain consumer consent or other special treatment. In the case that one or more consent rules are triggered, the producer system may be configured to automatically check for a record of the appropriate consent in an electronic data store, where the consent may have been previously obtained from a consumer via an API (such as the consumer agreeing to certain consents when previously self-reporting credit data to the credit bureau via an API, or in association with a firm offer of credit).


As mentioned above, a single system, in some embodiments, can act as both publisher and subscriber. For example, a given listener (e.g., a continuous scoring listener) can be configured to automatically perform an action (e.g., generate a credit report) upon listening to a certain even type, and then automatically post a resulting new event (e.g., a credit score) back to the ESB in real time. Events may be split into different parallel queues based on filtering, rule sets and/or load balancing, then a regulator associated with a given queue may determine one or more specific listeners to receive each queued event.


According to certain embodiments, a notification system, which may include an enterprise service bus, may broadcast an event to subscribers to cause the subscribers to provide an alert to an individual when an entity uses information of the individual to request credit data. In other embodiments, the notification system may generate an event to send directly to a consumer computing device. In some such embodiments, the consumer computing device may be a subscriber, and may launch an application upon receiving an event message in order to provide additional related information to the consumer. For example, a notification system, as disclosed herein, may provide an alert to a device associated with the individual when identification information associated with the individual is included in a request associated with a request for credit data, such as requesting a credit file.


In some embodiments, the credit bureau and/or the notification system may determine information underlying the request, such as the name of the requesting entity and/or the purpose for the request. The notification system may also determine third party vendors, financial institutions, or subscribers to which to broadcast the event. In some embodiments, the financial institution may be, for example, a bank or credit card issuer that maintains credit accounts for individuals on behalf of a separate entity, such as a vendor or service provider. The notification system may determine how the event will be broadcasted (e.g. categories of event receivers or particular receivers of the broadcast event). The notification system may, in some embodiments, provide information associated with related offers (e.g. categories of relevant offers for the receivers of the broadcast event).


In some embodiments, the notification system as described herein may include a subscription component. For example, the subscription component may be offered via a monitoring service that enrolls third parties to the enterprise service bus to receive broadcast messages. In some embodiments, a notification system may have a relationship with a credit bureau, or other entities (e.g. subscribers to the enterprise service bus, product or service providers, and/or financial institutions), such that certain requests that are received by the credit bureau or other entities are sent to the notification system prior to being processed by the credit bureau or the other entities. Furthermore, in some embodiments the notification system may be an intermediary that receives requests associated with a request for credit data from requesting entities or financial institutions and transmits the requests to one or more credit bureaus or other entities after (or concurrently with) extraction of information regarding an individual identified in the request and initiation of alert transmission to the consumer.


In some embodiments, alerts and/or events may be generated very quickly (e.g., in real-time or substantially in real-time) after a request associated with credit data or other event-triggering action occurs. For example, alerts may be transmitted to subscribers within seconds of the triggering event occurring. Similarly, notifications from subscribers indicating feedback, relevant offers, suggestions, and the like may be transmitted to the individual also in real-time or substantially in real-time. Although the disclosure discusses offers, feedback, information, and the like sent to the individual, the same notification or alert can be sent to other entities (such as the requesting entity). In other embodiments, notifications or alerts to individuals may be transmitted in batches, where the batch processing may occur every N seconds, minutes, hours, or other period.


In some embodiments, identity information that may be included in a request for credit data may broadly include various types of data associated with an individual. Examples that may be considered identity information, in some embodiments, include name, address, telephone number, email address, social security number, etc. Although the description provided herein refers to individuals, consumers, or customers, the terms “user,” “individual,” “consumer,” and “customer” may, according to some embodiments, include groups of individuals, such as, for example, married couples or domestic partners, organizations, groups, and business entities. Furthermore, request for credit data may broadly include various types of data associated with the requesting entity, for example, requesting entity name, address, and the like. The request for credit data may also include information on the purpose of the inquiry, for example, a loan amount, a purpose for the loan, etc.


A request for credit data may generally refer to a request for more information on the individual based at least in part on one or more pieces of identification information. For example, the request for information may be non-credit data and/or credit data. For the purposes of discussion, the request will be described as a request for credit data directed to a credit bureau. In some embodiments, a request for credit data may be a part of an account opening transaction or request. For example, when an entity initiates a process to open a new credit account or other account for an individual, the entity may first attempt to receive credit data of the individual. The entity may subsequently request credit data associated with the individual as a part of the account opening process. In other embodiments, the entity may open an account for the individual by submitting a credit data request. As will be appreciated, examples described herein with reference to requests for credit data may also be applicable to requests for other types of requests associated with the opening of an account, line of credit, or other transaction. Examples of account types that may be associated with a request to open a new account may include, for example, a mortgage, a revolving loan, a credit card, financial services, utilities, leasing, renting, television service, telephone service, and/or other types of credit or non-credit accounts.



FIG. 1A is a functional block diagram showing a sample high-level flow of events in a notification system, according to certain embodiments. As shown in FIG. 1A, an individual applies for an account with a product or service provider (requesting entity) 102. For purposes of example, the individual applying for the account may be an individual named of Jim Smith. The requesting entity 102 may be attempting to open a credit account, for example, in the name of Jim, such as a department store credit card. As will be appreciated, the product or service provider (requesting entity) 102 could be any of a number of business types involved in products or services, even for products or services ancillary to credit data. For example, the requesting entity 102 may be involved in opening accounts for consumers, including credit accounts and/or non-credit accounts. While credit bureaus are often referred to in this disclosure to maintain credit data, it is appreciated that in other embodiments, some or all of the credit data may be maintained by other entities (such as the subscriber 105, financial institution 104, or third party vendor 103. In some embodiments, the requesting entities may be the entities to receive the broadcast event message. In some embodiments, the entities receiving the broadcast event message may be the requesting entity. Thus, a given system may both provide input to the notification system that triggers an event object to be created, and may receive event messages as a subscriber.


The credit bureau 120 may determine information regarding the request for credit data. For example, the credit bureau 120 may identify the name of the product or service provider (requesting entity) 102, the purpose of the request for credit data, or the like. The credit bureau 120 may retrieve credit data (e.g. a credit file) for the individual from a credit data store 121. In the illustrated example, the credit bureau 120 generates and provides the requested credit information to the product or service provider 102. A request for credit data is also sent to a notification system 150. As will be appreciated, requests for credit data and/or other requests associated with an account opening may additionally or alternatively be received by entities other than a credit bureau (such as an authentication service in the event of an account opening transaction, where the authentication service may be operated by the same operator or different operator than the credit bureau services).


In some embodiments, the notification system 150 may also receive consumer information from a consumer information data store 112. For example, the consumer information may include non-credit information that may be used by the notification system 150 when identifying whether an incoming request or other occurrence satisfies criteria for broadcasting the occurrence as a broadcast event. The consumer information may include information such as transaction data, browser data, personal information, and/or any other information that may be used when determining whether to generate a broadcast event object related to a request for data. Such information may be provided by financial institutions, credit bureaus, vendor or service providers, big data providers, the individual, and/or other entities that have relevant information on the individual. The consumer information data store 112 may include multiple data stores, in some embodiments.


Next, in the embodiment illustrated in FIG. 1A, the notification system 150 may identify that a broadcast event object related to the request for credit data should be generated as a result of the incoming notification meeting previously established event criteria, as will be discussed in more detail below. For example, the broadcast event object may include information regarding a credit file and/or other credit data, changes in credit data, consumer information (such as personal information, and/or non-credit data such as browser history), requesting entity information, information related to the purpose for the request for credit information, and/or the like. The notification system 150 may comprise a notification module, such as enterprise bus 155, data streaming, or other technology that can publish to subscribers (herein referred to as an enterprise bus for convenience, but any discussions of an enterprise bus are equally applicable to other notification module) as will be described in further detail below.


The notification system 150 may determine one or more broadcast event types in response to information received by the credit bureau 120. For example, the notification system 150 may determine that one broadcast event type is an increase in credit score over a specified threshold. In another example, the notification system 150 may determine a broadcast event type based on the type of requesting entity 102 (e.g. a car dealership), or the purpose of the information received from the credit bureau 120 (e.g. a car loan). In some embodiments, the broadcast criteria may include whether the information received by the credit bureau 120 falls under a particular event type. This event type information may be incorporated into an event object generated by the notification system 150.


In some embodiments, the notification system 150 may use the enterprise service bus 155 to send broadcast event messages to other entities. For example, the notification system 150 can send the broadcast event message to subscribers 105 of the enterprise service bus. In some embodiments, the notification system 150 may send the broadcast event message to third party vendors 103, financial institutions 104, and/or any other third party that may use the broadcast event message and/or related request information to determine an alert to send to the individual.


In some embodiments, the notification module comprises data streaming configured to publish events to subscribers. Data streaming, as used herein, generally refer to any technology that processes events in the order they occur, and may include the transfer of data at a high speed sufficient to support sufficient bandwidth and for real-time human perception of data. One example includes the KAFKA stream configured to stream messaging data in a publish and subscribe architecture. The KAFKA stream is a distributed streaming platform that allows the platform to publish and subscribe, to store streams of records, and to process streams of records as they occur. Other examples of data streaming technology include FLINK, and SPARK. “The Forrester Wave™: Big Data Streaming Analytics, Q1 2016,” by Mike Gualtieri and Rowan Curran, published Mar. 30, 2016 by Forrester™, available at http://www.sas.com/content/dam/SAS/en_us/doc/analystreport/forrester-big-data-streaming-analytics-108218.pdf, and “Top Streaming Technologies for Data Lakes and Real-Time Data” by Greg Wood, published Sep. 20, 2016 by Zaloni The Data Lake Company, available at http://blog.zaloni.com/top-streaming-technologies-for-data-lakes-and-real-time-data, which are hereby incorporated by reference in their entirety, describe additional details and options in using data streaming technology that may be used in certain embodiments of notification systems discussed herein. The notification module may include a form of middleware, data streaming, other technology that may allow a system to publish/subscribe architecture, to publish or sent to an entity to consume, or send to subscribers of a certain event.


The entities (third party vendor 103, subscriber 105, and financial institution 104) that receive a broadcast event message may then, extract the information related to the request for credit data from the message, and determine relevant offers to send to the individual. Then, one or more entities may send an offer, an alert, notification, and/or message to a consumer computing device 130. The alert may include a notification of information (e.g. current credit score), suggestions for the consumer (e.g. mitigation factors to increase credit score), competing offers (e.g. other offers for a car loan), or any other information that may be helpful for the individual (e.g. helpful for the purpose of the inquiry).


The event message receiving entities (third party vendor 103, subscriber 105, financial institution 104) may, in some embodiments, de-dupe, parse, and/or re-phrase the broadcast event messages received from the notification system 150. For example, multiple alerts may be generated by the entities (third party vendor 103, subscriber 105, and/or financial institution 104) for the same consumer activity, such as when multiple entities may generate and transmit alerts to the consumer computing device 130. The consumer computing device 130 and or other system may parse and/or re-phrase the alert to make it user friendly. For example, the consumer computing device 130 may correlate information included in the alert, such as alert type, with a particular alert message and/or integrate the messages together in a single application or message. Additionally, different alert messages or formats may be accessed depending on the delivery medium, such as e-mail, software application, SMS, voice, etc.


The notification system 150 and/or an entity that receives an event message (such as third party vendor 103, subscriber 105, or financial institution 104) may determine contact information and/or contact preferences for the individual based on, for example, information that the individual provided when enrolling in a monitoring service or alert/notification service. The one or more alerts may be provided in various manners, and may depend in part on the device type. For example, alerts may be delivered, in some embodiments, via one or more of e-mail, text message, phone call, an online portal that is accessible to alert members (e.g., a credit monitoring or identity protection website), printed digests, mobile applications, etc.


In the embodiment of FIG. 1A, the individual may provide an indication back to the relevant entity (such as third party vendor 103, subscriber 105, or financial institute 104) to receive more information on the offer, such as details on the counter offer or view mitigating steps to improve credit score. The respective entity (such as third party vendor 103, subscriber 105, or financial institute 104) may implement one or more responsive actions in order to provide the individual with more information, or more detail on the contents of the offer. In some embodiments, the individual may have preconfigured notification/alert preferences. For example, the individual may allow for certain notifications (such as alternative counter-offers), but not authorize messages to be sent suggesting mitigating steps to improve the individual's credit score.


The alerts to consumers may include detailed information regarding the requesting entity. For example, rather than simply indicating the name of a chain store from which the request for credit data was received, in some embodiments the alerts may include the particular information regarding the individual that was provided to the requesting entity. Having more detailed information on the information provided to the requesting entity allows the consumer to better determine its negotiation stance.



FIG. 1B is a functional block diagram showing another sample high-level flow of events in a notification system, according to certain embodiments. As shown in FIG. 1B, an individual can perform an action with a product or service provider (requesting entity) 102 that affects credit data. For example, the individual may have a debt with the product or service provider 102. However, the individual may pay off the balance of the debt, which would thereby affect the individual's credit score. Accordingly, as illustrated, the product or service provider 102 may send updated information on the action (e.g. paying off the debt) as performed to the product or service provider 102 by the individual. Alternatively, the credit bureau 120 may request such information upon the change, at different time intervals, upon a request for such information (e.g. request for a credit file), and the like.


The credit bureau 120 may update the credit data store based on the information related to the action that affects the credit data (e.g. paying off the debt). For example, the credit bureau 120 may update statistics on the credit file, such as total debt, or the like. The credit bureau 120 may also generate updates on the credit file, such as an updated credit score. The updated credit data and/or the action that affects the credit data can also be sent to the notification system 150. As will be appreciated, updates to the credit data may additionally or alternatively be received by entities other than a credit bureau.


In some embodiments, the notification system 150 may also receive consumer information from a data store 112, similar to FIG. 1A. Next, in the embodiment illustrated in FIG. 1B, the notification system 150 may generate a broadcast event object related to the credit data and/or action that affected the credit data. For example, the broadcast event object may include information associated with a credit file and/or other credit data, changes in credit data, consumer information (such as personal information, non-credit data such as browser history), requesting entity information, information related to the purpose for the request for credit information, and/or the like.


In some embodiments, the notification system 150 may use the enterprise service bus 155 to send broadcast event messages to other entities, as in FIG. 1A. The other entities (such as third party vendor 103, subscriber 105, and/or financial institution 104) may then each receive a broadcast event message, extract the information related to the updated credit data and/or actions that affected the credit data, determine relevant offers to send to the individual, and send an offer to a consumer computing device 130, as in FIG. 1A.


Although the embodiments of FIGS. 1A and 1B describe the notification system 150 including the enterprise service bus 155, and entities (e.g. subscriber 105, financial institution 104, third party vendor 103) external to the notification system 150, it is appreciated that part or all of the enterprise service bus 155 (and other modules described in the notification system 150 in FIG. 3A) may be placed external to the notification system 150, and part or all of the entities (e.g. subscriber 105, financial institution 104, third party vendor 103) may be local to the notification system 150.



FIG. 2A is a flowchart illustrating one embodiment of a method for sending a broadcast event message to subscribers based on a request for credit data, as described in FIG. 1A. The illustrative method may be implemented by a notification system, such as the notification system 150. In some embodiments, the notification system 150 may include an enterprise service bus 155 that implements some of the steps of the method illustrated in FIG. 2A. The illustrative method begins at block 202, where the notification system 150 receives an indication related to a requesting entity's request for credit data of an individual or other entity. As discussed above, an individual may apply for a service or product from a service or product provider 102. The request may be associated, for example, with a transaction to open an account on behalf of the individual. As used in the illustrated example, the underlying vendor or service provider 102 that submitted the initial request to the credit bureau 120 may be referred to as the requesting entity 102. In other embodiments, the notification system 150 may receive the indication related to the request for credit data from an entity other than the credit bureau 120, such as a subscriber 105, a financial institution 104, a third party vendor 103, an authentication service, or other entity.


Once the notification system 150 receives the indication related to a requesting entity's request for credit data, the method proceeds to block 204, where the notification system 150 accesses information associated with the identified consumer. The information can include personal identification information of the individual, transaction data, sociodemographic information, preferences, browser history, and/or any other information relevant to the consumer. For example, the notification system 150 may retrieve contact information from one or more data stores based on a determined match between the consumer identification information included in the request for credit data and contact information associated with a number of different consumers. The contact information retrieved may include, for example, one or more of an e-mail address, phone number, address, IP address, a user account name associated with enrollment in a monitoring service, etc.


At block 206, the notification system 150 may, in some embodiments, determine if the request for credit data meets event broadcast criteria based on the indication related to a requesting entity's request for credit data. The notification system 150 can also use a variety of other information in its decisioning whether to generate and/or how to generate the broadcast event object. The notification system 150 can use information directed to a change in the credit file. For example, the notification system may generate a broadcast event object if the credit score has increased by 80 points, or if the total credit score is above 700. The notification system 150 may also apply criteria directed to the requesting entity. For example, the notification system 150 may generate a broadcast event object if the requesting entity is associated with luxury brands (e.g. generate a broadcast event object if the requesting entity is associated with a luxury brand car dealership).


In some embodiments, the notification system 150 may generate a broadcast event object based on information on the requesting entity. The notification system 150 may generate an event broadcast criteria when the request for credit data is associated with a particular financial institution. For example, a subscriber that is a financial institution may subscribe for broadcast event messages that are associated with itself or its competitors. A financial institution may desire to receive messages in real time for requests associated with itself to identify better offers than the ones allowed by the requesting entity. The financial institution may have special promotions or have a long standing relationship with the individual that the financial institution would like to promote and foster. In some embodiments, the request for credit data may only provide the name of the requesting entity and not a financial entity associated with the requesting entity. The notification system 150 may retrieve data from one or more data stores that associates each of a number of different financial entities with one or more requesting entities with which the given financial entity is associated. Such association data is described with more detail below with reference to FIG. 4B. In this manner, the notification system 150 may set criteria to create a broadcast event object based on an association with a financial institution even if the request for credit data does not contain the financial institution. For example, if the data store links a real estate company to a particular financial institution, then the notification system can identify the financial institution from the identity of the real estate company that may be the requesting entity requesting credit data. In some embodiments, the notification system 150 and/or the subscriber 105 may provide the consumer directly with an alert about the specific underlying requesting entity in order for the consumer to better determine if the offer for the service or product is a fair one.


In some embodiments, the notification system 150 may generate a broadcast event object based on criteria related to information on the individual. The notification system 150 may generate a broadcast event object for a particular individual, or characteristic associated with the individual. For example, the notification system 150 may generate a broadcast event object for individuals based on gender, geolocation/residence, socio-economic attributes, race, age, level of education, income and employment, psychiatric or medical data, a personality trait, an interest, values, attitudes, lifestyles, opinions, preferences, likes or dislikes, predilections, purchase history, browser history, financial history and data, credit history and data, personal history and data, other activity data, and the like. The notification system 150 may receive information from the credit bureau 120 that may identify the individual, and may access other information on the individual from the consumer information data store 112.


In some embodiments, the notification system 150 may generate a broadcast event object based on criteria related to the request itself. For example, the notification system 150 may generate an object if there are a number of requests by a particular requesting entity or for a particular individual. Subscribers may subscribe to receive broadcast event messages when multiple occurrences of a request for credit file is placed for a particular individual. The notification system 150 may also assess the purpose of the inquiry to determine whether to generate a broadcast event object. For example, the notification system 150 may generate a broadcast event object for requests to open a line of credit, or for real estate loans for a particular amount in a specified area.


At block 208, the notification system 150 generates a broadcast event object associated with the request for credit information and optionally other non-credit information (e.g. information regarding the requesting entity, information regarding the consumer, etc.), and, at block 210, posts a corresponding broadcast event message to an intermediary message broker. The broadcast event object may include the indication related to the requesting entity's request, information on the requesting entity, information on the individual, information on the request itself (such as the purpose of the request), the criteria for the broadcast event object, the intermediary message broker, and/or other information that may be used by the intermediary message broker, the enterprise service bus 155, the individual, or the subscriber 105. The enterprise service bus 155 identifies subscribers 105 registered to receive subscriptions from the intermediary message broker at block 212. In some embodiments, each subscriber may be subscribed to one or more broadcast criteria. For example, a subscriber may be subscribed to receive broadcast event messages where (1) credit score is greater than 700, as well as receiving broadcast event messages from (2) individuals residing in California.


At block 214, the notification system 150 transmits the broadcast event message to subscribers 105 to cause the subscribers 105 to determine relevant offers for the entity (e.g. the individual) based on the indication related to the requesting entity's request for credit data at block 204. The broadcast event message may include at least a portion of the broadcast event object, routing information, information on the subscriber, and the like. Then, the subscribers can transmit a notification or alert to the consumer using one or more delivery mediums according to the contact information retrieved. For example, the alert may be delivered via e-mail, within a software application, an online portal or website, SMS text message, voice call, etc. In some embodiments, the delivery method may be selected based on preferences previously provided by the consumer. In some embodiments, the blocks of FIG. 2A may all be performed substantially in real time (such as within seconds or milliseconds, in one embodiment) with respect to the indication being received at block 202.



FIG. 2B is a flowchart illustrating one embodiment of a method for sending a broadcast event message to subscribers based on an action affecting credit data (such as paying off debt), as described in FIG. 1B. The illustrative method may be implemented by a notification system, such as the notification system 150. In some embodiments, the notification system 150 may include an enterprise service bus 155 that implements some of the steps of the method illustrated in FIG. 2A. The illustrative method begins at block 232, where the notification system 150 receives information on an action that affects credit data. As discussed above, an individual may pay off a debt owed to a service or product provider 102. As used in the illustrated example, the underlying vendor or service provider 102 that submitted the change to the credit bureau 120 will be referred to as the reporting entity. In other embodiments, the notification system 150 may receive the indication related to a change, update, or action that affects credit data from an entity other than the credit bureau 120, such as a subscriber 105, a financial institution 104, a third party vendor 103, or other entity.


Once the notification system 150 receives the indication related to a requesting entity's request for credit data, the method proceeds to block 234, similar to block 214, where the notification system 150 accesses information associated with the identified consumer. The information can include personal identification information of the individual, transaction data, sociodemographic information, preferences, browser history, and/or any other information relevant to the consumer. For example, the notification system 150 may retrieve contact information from one or more data stores based on a determined match between the consumer identification information included in the request for credit data and contact information associated with a number of different consumers. The contact information retrieved may include, for example, one or more of an e-mail address, phone number, address, IP address, a user account name associated with enrollment in a monitoring service, etc.


At block 236, the notification system 150 may, in some embodiments, determine if the information regarding the action that affects credit data meets an event broadcast criteria. The notification system may generate a broadcast event object based on criteria relating to the individual, the requesting entity, the action affecting credit data, and the like. For example, the broadcast event criteria may include a threshold or a particular change to the credit data (e.g. an increase of 50 points to the credit score) that one or more subscribers have previously indicated an interest in being notified about.


At block 238, the notification system 150 generates a broadcast event object associated with the information on the action that affects the credit data and other non-credit information (e.g. information on the requesting entity, information on the consumer), and, at block 240, posts the broadcast event object to an intermediary message broker. The enterprise service bus 155 identifies subscribers registered to receive subscriptions from the intermediary message broker at block 242, and at block 244, the notification system 150 transmits the broadcast event object to subscribers to cause the subscribers to determine relevant offers for the entity based on the information on the action that affects credit data. Then, the subscribers can transmit a notification or alert to the consumer using one or more delivery mediums according to the contact information retrieved. In some embodiments, the blocks of FIG. 2B may all be performed substantially in real time (such as within seconds or milliseconds, in one embodiment) with respect to the information being received at block 232.



FIG. 3A illustrates a notification system 150 in communication with various systems, according to one embodiment. As illustrated, the various systems are in communication via network 160, which may be one or more of a LAN, WAN, and/or the Internet, for example. As illustrated, the notification system 150 is in communication with a consumer computing device 130. The notification system 150 may receive request for credit data from a credit bureau 120, which may provide the basis for the notification system 150 to generate and deliver an alert to one or more entities (such as third party vendor 103, financial institution 104, and/or subscriber 105). Alternatively or additionally, the notification system 150 may receive notification of a request for credit data for a given consumer from an entity (e.g. third party vendor 103, financial institution 104, or subscriber 105), which may be a basis for an alert to be delivered to the consumer, in some embodiments. As will be appreciated, the alert delivery device may be in communication with credit bureaus, a number of other alert providers, vendors, service providers, and consumer devices not illustrated in FIG. 3A.


In the illustrated embodiment, a notification system 150, which includes an enterprise service bus 155, a services registry 310, a services orchestration 320, a generic score monitoring listener 330, and a score-able events listener 340, is in communication with a network 160 and various systems are also in communication with the network 160. The notification system 150 may be used to implement systems and methods described herein. For example, the notification system 150 may be associated with an event generator that causes an event to be broadcasted to another entity (e.g. third party vendor 103, financial institution 104, and/or subscriber 105) to deliver a notification or alerts to a user. The alert and/or notification can additionally or alternatively be performed by the notification system 150. In other embodiments, a credit bureau, third party vendor 103, financial institution 104, subscriber 105, and/or other third-party system may include a computing system that includes components of notification system 150.


The notification system 150 may include, for example, a personal computer that is IBM, Macintosh, or Linux/Unix compatible or a server or workstation. In one embodiment, the notification system 150 comprises a server, a laptop computer, a cell phone, a personal digital assistant, a kiosk, or an audio player, for example. In one embodiment, the exemplary notification system 150 includes one or more central processing unit (“CPU”) (not shown), which may each include a conventional or proprietary microprocessor. The computing system 700 further includes one or more memory (not shown), such as random access memory (“RAM”) for temporary storage of information, one or more read only memory (“ROM”) for permanent storage of information, and one or more mass storage device (not shown), such as a hard drive, diskette, solid state drive, or optical media storage device. Typically, the modules of the notification system 150 are connected to the computer using a standard based bus system (not shown). In different embodiments, the standard based bus system could be implemented in Peripheral Component Interconnect (“PCI”), Microchannel, Small Computer System Interface (“SCSI”), Industrial Standard Architecture (“ISA”) and Extended ISA (“EISA”) architectures, for example. In addition, the functionality provided for in the components and modules of notification system 150 may be combined into fewer components and modules or further separated into additional components and modules.


The notification system 150 is generally controlled and coordinated by operating system software, such as Windows XP, Windows Vista, Windows 7, Windows Server, Unix, Linux, SunOS, Solaris, or other compatible operating systems. In Macintosh systems, the operating system may be any available operating system, such as MAC OS X. In other embodiments, the notification system 150 may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface, such as a graphical user interface (“GUI”), among other things.


The exemplary notification system 150 may include one or more commonly available input/output (I/O) devices and interfaces (not shown), such as a keyboard, mouse, touchpad, and printer. In one embodiment, the I/O devices and interfaces (not shown) include one or more display devices, such as a monitor, that allows the visual presentation of data to a user. More particularly, a display device provides for the presentation of GUIs, application software data, and multimedia presentations, for example.


In the embodiment of FIG. 3A, the I/O devices and interfaces provide a communication interface to various external devices. In the illustrated embodiment, the notification system 150 is electronically coupled to a network 160, which comprises one or more of a LAN, WAN, and/or the Internet, for example, via a wired, wireless, or combination of wired and wireless, communication link. The network 160 communicates with various computing devices and/or other electronic devices via wired or wireless communication links.


According to FIG. 3A, information is provided to the notification system 150 over the network 160 from one or more data sources including, for example, the credit bureau 120, or other entities (e.g. third party vendor 103, financial institution 104, and/or subscriber 105). The information supplied by the various data sources may include a request for credit information such as credit data, personal information, application information, and/or other like data, notification of a request for credit information, or information on the requesting entity or the purpose for the request, for example. In addition to the devices that are illustrated in FIG. 3A, the network 160 may communicate with other data sources or other computing devices, such as a requesting entity 102. In addition, the data sources may include one or more internal and/or external data sources. In some embodiments, one or more of the databases or data sources may be implemented using a relational database, such as Sybase, Oracle, CodeBase and Microsoft® SQL Server as well as other types of databases such as, for example, a flat file database, an entity-relationship database, and object-oriented database, and/or a record-based database.


A consumer computing device 130 may be connected to the network 160 and used by a user to receive and respond to alerts provided by the notification system 150. The consumer computing device 130 may be a desktop computer, a mobile computer, or any other mobile device such as a mobile phone or other similar handheld computing devices. In some embodiments, a consumer can be a subscriber. For example, a consumer may subscribe to receive broadcast event messages from the notification system 150 on a consumer computing device 130.


In the embodiment of FIG. 3A, the notification system 150 also includes an enterprise service bus 155, a services registry 310, a services orchestration 320, a generic score monitoring listener 330, and a scorable events listener 340 that may be stored in the mass storage device as executable software code that is executed by the CPU. This components or modules may include, by way of example, software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. In the embodiment shown in FIG. 3A, the notification system 150 is configured to execute the enterprise service bus 155, a services registry 310, a services orchestration 320, a generic score monitoring listener 330, and a scorable events listener 340 in order to receive indication of a request for credit information or other underlying action or occurrence, generate event objects and messages, transmit broadcast event messages to other entities (e.g. third party vendor 103, financial institution 104, and/or subscriber 105), receive feedback from consumers regarding provided alerts, and/or other functionality described elsewhere in this specification.


The notification system 150 may include an enterprise service bus 155 that includes several process clusters (process cluster 1 302, process cluster 2 304, process cluster 3 306) to process services related to the notification system 150. The notification system 150 may also include a services registry 310 that is used to publish or post events to the intermediary message broker. In some embodiments, the service registry stores a catalog or index of events that the subscriber can access to select event subscriptions. The catalog of events may include a grouping of event types or may include an a la carte selection of different listings of events. For example, a new inquiry for a credit file may be an event type, and may publish to any subscribers who are interested in a new inquiry. Account level events may be another example of an event type, where account level events may include changes to account information (e.g. balance updates), adding an authorized user, opening/closing an account, and the like. Depending on the embodiment, the subscriber can subscribe to event types on various levels of granularity, such as subscribing generally to “account level events” as well as subscribing to individual account level events, such as one or more of those noted above. In some embodiments, each subscriber has associated access rights that identify types of events, sets of consumers, and/or other criteria required for that subscriber to enroll for notifications of particular events. For example, a financial institution may be limited to subscribing to events for that financial institutions customers. In some embodiments, each subscriber must have a “permissible purpose” under applicable Fair Credit Reporting Act (FCRA) regulations to access credit data of consumers associated with subscribed events.


The intermediary message broker (also referred to as the services orchestration 320, or bus) may also be included in the notification system 150, used to broker messages, and perform mediation and transformation of the events. The services orchestration 320 may use EBS, other middle layer technology, data streaming, or other technology that is able to recognize events and publish events to subscribers to the event.


For example, the mediation and transformation of the events may include changing the payload to the format that the subscriber 105 has enrolled in. In some embodiments, the mediation and transformation may also include changing payload formats for consumer computing devices that the subscribers 105 will send alerts and notifications to. The mediation and transformation can change the payload to a text file to send as a text message or format the message to fit in an application of a mobile device. The notification system 150 may also include generic score monitoring listener 330 (also referred to as a custom score listener) that may be created for subscribers that request to listen to a score event (e.g. listen to score changes and have the ability to select score ranges to tune into). The notification system 150 may connect to one or more subscriber systems for decisioning services based on the credit data. The notification system 150 may also include a score-able events listener 340 that may be used to listen to real time events such as hard inquiries, credit card payments, etc. The score-able events may flow into a scoring process that invokes a credit score calculator, creates a payload containing consumer identification and an updated credit score, and posts the score event back onto the bus.


While an enterprise service bus is often used as an example herein, other forms of middleware may be used in addition to or instead of an ESB, in some embodiments, or data streaming technology may be utilized. Middleware may include any hardware and/or software suitably configured to facilitate communications and/or process transactions between disparate computing systems. Middleware may be implemented through commercially available hardware and/or software, through custom hardware and/or software components, or through a combination thereof. Middleware may reside in a variety of configurations (e.g. as a part of the notification system 150), may exist as a standalone system, or may be a software component residing on the Internet server. Middleware may be configured to process transactions between the various components of a notification system 150 and any number of internal or external systems for any of the purposes disclosed herein. In various embodiments, where more than one notification system 150 components are dispersed across a network, middleware may be used to carry messages between components. These messages could be organized in any logical manner. WebSphere MQ™ (formerly MQSeries) by IBM, Inc. (Armonk, N.Y.) is an example of a commercially available middleware product. An Enterprise Service Bus (“ESB”) application is another example of middleware.


The credit bureau system 120 may include a credit data store 121 that contains credit data for individuals, businesses, and/or entities. The credit bureau 120 may include a batch processing system 350 that processes the individual modules in batches, where the batches may include: inquiry updates 352, public record updates 354, single updates 360, trade updates 356, changes of addresses 358 or other personal information, consumer updates 362, a PIN merge 364, a PIN split 366, and/or other processes 368. In other embodiments, the credit bureau processes these modules in substantial real time upon receipt of a change, request, or other action or information that would initiate an action performed with respect to any one of these modules.


A consumer may include any individual, user, business, entity, government organization, software and/or hardware that interacts with a system to receive offers for products or services. A consumer computing device 130 may include any hardware and/or software suitably configured to facilitate input, receipt and/or review of information relating to alerts, notifications, and the other means of communication that may include information on the consumer, such as credit data and/or offers for products and services.


A consumer computing device 130 may include any device (e.g., personal computer) which communicates (in any manner discussed herein) via a network. The consumer computing device 130 may take the form of a computer or set of computers, although other types of computing units or systems may be used, including laptops, notebooks, hand held computers, personal digital assistants, set-top boxes, workstations, computer-servers, main frame computers, mini-computers, PC servers, pervasive computers, network sets of computers, and/or the like.


As used herein, the term “network” (or similar terms) shall include any electronic communications means which incorporates both hardware and software components of such. Communication among the parties may be accomplished through any suitable communication channels, such as, for example, a telephone network, an extranet, an intranet, Internet, point of interaction device (point of sale device, personal digital assistant, cellular phone, kiosk, etc.), online communications, satellite communications, off-line communications, wireless communications, transponder communications, local area network (LAN), wide area network (WAN), virtual private network (“VPN”), networked or linked devices, keyboard, mouse and/or any suitable communication or data input modality. Moreover, the network 160 may also be implemented using IPX, Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec), or any number of existing or future protocols.



FIG. 3B is a flow diagram illustrating an example embodiment of a notification system 150 that outputs custom payloads 302B to multiple subscribers 105A, 105B, 105N (herein referred to as subscribers 105). As discussed above, in some embodiments the services registry 310 allows subscribers 105 to indicate which of multiple credit events 301 the particular subscriber 105 would like to receive. Thus, for a particular credit event type (or other credit event criteria that may be identified by a potential subscriber 105), multiple subscribers 105 may request receipt of matching events 301 (or custom payloads that are generated based on the matching events). In FIG. 3B, the notification system 150 receives an event 301 that executes one or more process clusters 302, 304,306 to generate a generic payload 302A. Then, the generic payload 302A is provided to the notification module 154 (or some other component such as data stream) as an event, such that the notification module 154 may trigger one or more additional process clusters 302, 304, 306 based on receipt of the generic payload event. Additionally, the generic payload 302A is processed by one or more listeners 330A, 330B, 330N (herein referred to as listener 330A) to determine if any custom payloads 302B should be generated. As discussed elsewhere herein, each of the listeners 330 include criteria, rules, requirements, etc. for identifying particular events, which will then be processed to generate corresponding custom payloads 302.


In the example of FIG. 3B, the listener 330A determines that the generic payload 302A matches criteria for generating a custom payload 302B by the listener 330A. One or more additional listeners may also generate custom payloads based on matching the listener criteria to the generic payload 302A. The listener 330A then generates the custom payload 302B and transmits to any subscribers 105 that have subscribed to receive that custom payload 302B. In the example of FIG. 3B, the custom payload 302B is transmitted to each of multiple subscribers, including 105A, 105B, and 105N (which signifies that any amount of subscribers may receive that same custom payload 302B). As an example application of FIG. 3B, the event 301 may comprise an indication of a late payment that is received from a bank on a consumer's credit card account. The generic payload 302A may be triggered based on a rule that indicates a new credit score should be calculated when any of a certain group of changes are identified, including a late payment. Thus, the listener 330 A may then generate the particular consumer's credit score as the custom payload 302B and transmit the newly calculated credit score to multiple subscribers. Furthermore, each subscriber 105A, 105B, and 105N may receive the same custom payload 302B. In other embodiments, each subscriber 105A, 105B, and 105N may request a payload that is customized to the subscriber 105A, 105B, and 105N (e.g. different formats, varying levels of information). The payload can also be published as an application program interface (API) or implemented as an HTTP direct push.



FIG. 3C is a flow diagram illustrating the example notification system 150 executing a multi-phase processing of an event in order to generate a custom payload for a subscriber. In this example, the event 301 is initially transformed into a generic payload 302A which is detected by the listener 330A. The listener 330A then transforms the generic payload 302A into a custom payload 302B. In some embodiments, the custom payload 302B may be transmitted to one or more subscribers (not shown in this figure). In this example, the custom payload 302B is provided back to the notification module 154 (or some other component of the notification system 150 such as a data stream component), such as in the form of an event. Listener 330B then identifies custom payload 302B as matching that listeners processing criteria. Thus, Listener 330B generates custom payload 302C which, again, is provided back to the notification module 154. The custom payload 302C is identified by listener 330C as matching that listener's criteria, which generates custom payload 302D for transmission to a subscriber 105C. As one example of the various payloads, the generic payload 302A may be a credit inquiry, payment on a credit account, balance change, late fee, etc. The custom payload 302B may be a credit score, such as the Experian Plus credit score, the custom payload 302C may be a customer specific risk score (e.g., a lender-specific risk score), and payload 302D may include prequalification results that are based at least on the lender-specific risk score. Advantageously, each of the custom payloads may be identified by multiple listeners and processed into multiple different custom payloads. Thus, a single event 301 may advantageously trigger generation of one or more custom payloads and transmission of one or more different custom payloads to a plurality of subscribers, all in substantially real-time in response to the notification system 150 receiving the event 301. For example, the prequalification offers may be provided to the subscriber 105C, such as an automobile lender, while the consumer is at the point of sale, e.g. the automobile dealership, in response to the consumer paying off a credit card balance to increase the consumer's credit score and chances of the consumer qualifying for an automobile loan. In this example, the listeners 330A, 330B, 330C are internal subscribers to the notification system 150 and the subscriber 105C is external to the notification system 150. However, it is appreciated that listeners 330A, 330B, 330C and the subscribers 105 may be external, internal, or a combination of internal and external to the notification system 150.



FIG. 3D is a flow diagram illustrating an example processing method that may be performed by the notification system 150 to reduce processing cycles required to identify matching listeners from a large set of multiple available listeners (e.g., hundreds, thousands, or millions of different listeners). As discussed above, the listeners may include generic listeners 330G which are triggered when generic payloads are placed on the bus, and custom listeners 330C, which are triggered when custom payloads are placed on the bus. In this embodiment, the notification module 154, or some other component of the notification system 150 (such as data stream), determines whether an event 301 comprises a generic payload or a custom payload (e.g., whether the event is received from a financial institution or from an internal listener) and provides the payload to only a set of corresponding listeners. For example, any new events or payloads received by the notification module 154 would be analyzed by the generic listeners 330G. Similarly, any custom payloads received by the notification module 154 are processed by the custom listeners 330C. In this way, processing of incoming events is optimized by reducing processing power required and increasing speed at which events may be processed.



FIG. 3E is a flow diagram illustrating example event/payload data that may be transformed in various ways to provide a payload to a subscriber. In this example, the event comprises information regarding a balance change on an account owned by John Doe in the amount of −$400, and resulting in an account balance of zero dollars. In this example, the notification module 154 makes the payload available to the listeners, or to only a set of generic listeners in some embodiments. In the example of FIG. 3E, a listener 330A is illustrated as triggering generation of a payload in response to the event, but as discussed above, multiple listeners may be triggered in response to the same payload. In this example, the custom payload A comprises a credit score of 725 for John Doe, who is identified only by an alphanumeric identifier in this example payload. As shown, that payload A is made available to the listeners by the notification module 154 and, in this example, triggers listener 330B, which generates a bank—specific risk score for John Doe of BBB. For example, the bank—specific risk score may be calculated based on an algorithm from a particular bank, such as the subscriber 105 illustrated in FIG. 3E. Next, the payload B is recognized by the listener 330C, which transmits the payload B, or in some embodiments generates a new payload that includes additional information indicated by the subscriber 105, to the subscriber 105. As noted above, this process advantageously is performed in real-time or near real-time in response to receiving of the original balance change event by the notification module 154.


In some embodiments, the payloads are in an “atomic format” that provides minimal information regarding the event and any calculated custom data (e.g., calculated scores). For example, as shown in FIG. 3E, the custom payload B that is transmitted to the subscriber 105 includes only two data elements, a consumer identifier and a calculated bank risk score associated with that consumer identifier. Provision of only this minimal level of information allows the system to process larger amounts of events and more quickly and efficiently transmit payloads to subscribers, which can help provide distribution to a wider range of listeners and/or subscribers. The small payloads may be used by the subscribers to then provide alerts and notifications to consumer computing devices 130 that are also small in payload size to further improve speed and efficiency of the dissemination of information back to the individual, thus supporting the implementation of a response in substantially real-time. Thus, the payload may not need to send a full credit file, or a substantial portion thereof, but may only need to transmit the information the subscriber is interested in. Then, if the subscriber is further interested, the subscriber may request for more credit data or a full credit file for the individual.



FIGS. 3F and 3G are example payloads that may be provided to a subscriber. The payload in FIG. 3F illustrates a version number for the payload, a sourceID that may be used as an identifier for the transmitter of the payload, a UniqueTransactionID used to identify the individual, and an event type of 2. The event may trigger a listener based on the EventType matching an event type to which a subscriber has subscribed. For example, event type 2 may refer to a change in address. Thus, the payload includes information on the address of the individual. Furthermore, the payload may include a CompanyID that may indicate the source of the change of address for the individual (e.g. the individual requests a change of address in a company associated with the identifier NationalB). FIG. 3G is another example of a payload, where a consumer identifier is sent, and the event type is a 4. In this example, this event type references a change in credit score. Thus, the payload also transmits the score of 733, and a change in the score of +25 points. FIG. 3H is another example of a payload including a CreditBureauSubscriberID that may be used to identify the individual associated with the credit data using a credit bureau identifier of the individual. In this example, the EventType is “I”, which indicates a credit inquiry. Thus, subscribers enrolled to receive alerts on credit inquiries may receive a payload include data similar to what is illustrated in example 3H. Information identifying the entity that submitted the inquiry request may be included as well, such as the name and address.


As a further example of event and alert content (e.g., the payload of these communications), below are some example payloads. These examples do not limit the type or content of data included in payloads in other embodiments. First below is an example of an alert payload, such as the data that may be received from a credit bureau by the notification system indicating that an inquiry request was received for the individual, John Doe:


{“Id”:“XYZ23424242342323”,


“CompanyId”:“3323”,


“PortfolioId”:“11”,


“CampaignId”:“42111”,


“VersionNum”:“001”},


“EventInfo”:{“EventType”:“X”,


“ExperianConsumerIdentifier”:“V”,


“EventDisplayCode”:“SECUR”,


“MonitoredAccount”:“PIN00432425243242”,


“ConsumerStatementIndicator”:“A”,


“FactaCode”:“26”,


“FCRAAttr”:“00 0100”},


“CustomerSuppliedName”:{“Name”:{“FirstName”:“JOHN”,“MiddleName”:“D”,


“Surname”:“DOE”,


“SecondSurname”:“DOETWO”,“Gen”:“D”}},


“CustomerSuppliedData”:“CUSTOMER SUPPLIED DATA PRESENT”,


“BestAddressInformation”:{“PrimaryStreetId”:“1111”,


“PreDirectional”:null,


“StreetName”:“STREET”,


“PostDirectional”:null,


“StreetSuffix”:“ST”,


“UnitType”:null,


“UnitID”:null,


“City”:“DOETOWN”,


“State”:“MN”,


“Zip”:“111111”,


“NonStandardAddress”:null},


“SecurityAlertEventInformation”:{“SecurityAlertDate”:“234234234”,


“SecurityAlertType”:“26”,


“SecurityAlertText”:“26& 2016-11-22 3999997 ID SECURITY ALERT:


FRAUDULENT APPLICATIONS MAY BE SUBMITTED IN MY NAME OR MY IDENTITY MAY HAVE BEEN USED WITHOUT MY CONSENT TO FRAUDULENTLY OBTAIN GOODS OR SERVICES. DO NOT EXTEND CREDIT WITHOUT FIRST VERIFYING THE IDENTITY OF THE APPLICANT. THIS SECURITY ALERT WILL BE MAINTAINED FOR 90 DAYS BEGINNING 07-10-15.”},


“NumOfStatements”:“0001”,


“ConsumerStatement”:[{“StatementIndicator”:“A”,


“StatementType”:“26”,


“SubscriberName”:null,


“AccountReferenceNumber”:null,


“DateOpenedFiled”:null,


“AcctCond”:null,


“Status”:null,


“StatementText”:“26& 2016-11-22 3999997 ID SECURITY ALERT:


FRAUDULENT APPLICATIONS MAY BE SUBMITTED IN MY NAME OR MY IDENTITY MAY HAVE BEEN USED WITHOUT MY CONSENT TO FRAUDULENTLY OBTAIN GOODS OR SERVICES. DO NOT EXTEND CREDIT WITHOUT FIRST VERIFYING THE IDENTITY OF THE APPLICANT. THIS SECURITY ALERT WILL BE MAINTAINED FOR 90 DAYS BEGINNING 07-10-15.”}]}


Next, below is an example of a custom data package that may be generated by the notification system and transmitted to subscribers to inquiry requests (for a group of individuals that includes John Doe), such as in an HTTP data package or via an API.


{“Id”:“RTE000022421000110000008357T60023001”,


“CompanyId”:“224210”,


“PortfolioId”:“11”,


“Campaign Id”:“8357”,


“VersionNum”:“001”},


“EventInfo”:{“EventType”:“1”,


“ExperianConsumerldentifier”:“KLJFOI34343DSFAD”,


“EventDisplayCode”:“INSTI”,


“MonitoredAccount”:“POSITIVE9227”,


“ConsumerStatementIndicator”:null,


“FCRAAttr”:“00 0601”},


“CustomerSuppliedName”:{“Name”:{“FirstName”:“JOHN”,


“MiddleName”:“D”,


“Surname”:“DOE”,


“SecondSurname”:null,


“Gen”:null}},


“CustomerSuppliedData”:null,


“BestAddressInformation”:{“PrimaryStreetId”:“1111”,


“PreDirectional”:null,


“StreetName”:“STREET”,


“PostDirectional”:null,


“UnitType”:null,


“UnitID”:null,


“City”:“DOETOWN”,


“State”:MN″,


“Zip”:“111111”,


“NonStandardAddress”:null},


“InquiryEventInformation”:{“KOB”:“IZ”,


“PurposeType”:“OA”,


“InquiryDate”:“2016-11-22”}}


Below is an example custom payload that may be transmitted to a subscriber, such as a credit access control system associated with a credit bureau, to request freezing of an individual's credit file:


{“RTTRG”:{“RecordType”:“T”,“VersionNum”:“2.00”,


“UniqueTransactionId”:“65465464536546543”,


“EventType”:“2”,


“SystemID”:“CAP”,


“ReturnedPin”:“ ”,


“Logging Pin”:251369794,


“OptOut”:“ ”,


“OnsInd”:“ ”,


“FCRAAttr”:“ ”,


“InquiryPre”:“ ”,


“CrsReferralPre”:“ ”},


“RTFRZ”:{


“NCACId”:“5445343”,


“Type”:“FREEZE”,


“CapId”:“4534543543543”,


“StartDate”:“2016-11-22”,


“AdditionalText”:“A security freeze has been successfully placed on your credit report”}}


Below is an example event payload that may be received by the notification system, indicating that the security freeze has been placed on the individuals credit file:


{“Id”:“RTE00002242100011000000835707222016001753000003655”,


“TransactionInfo”:{“EventDeliveryDate”:“2016-11-22”,


“EventDeliveryTime”:“001753”,


“CompanyId”:“45454”,


“PortfolioId”:“11”,


“CampaignId”:“8357”,


“VersionNum”:“001”},


“EventInfo”:{“EventType”:“2”,


“ExperianConsumerIdentifier”:“235445243DFGSDFG3456345”,


“EventDisplayCode”:“FRTHL”,


“MonitoredAccount”:“PIN45345243”,


“ConsumerStatementIndicator”:null},


“CustomerSuppliedName”:{“Name”:{“FirstName”:“JANE”,


“MiddleName”:null,


“Surname”:“DOE”,


“SecondSurname”:null,


“Gen”:null}},


“CustomerSuppliedData”:null,


“FreezeEventInformation”:{“NCACId”:“454545454545”,


“Type”:“FREEZE”,


“CapId”:“45454545454”,


“StartDate”:“2016-11-22”,


“AdditionalText”:“A security freeze has been successfully placed on your credit report”}}



FIG. 4A is an illustrative representation of a table 400 associating credit data with other information, such as information from the inquiry for credit data, along with corresponding personal information for the individual. The data represented in illustrative table 400 may be stored in one or more data stores accessible to the notification system 150. The data may be determined and stored, for example, based on information provided by each financial institution to the notification system 150, either in bulk prior to sending individual requests for credit data or in a piecemeal fashion as requests for credit data or other requests are processed by the notification system 150. In some embodiments, when the notification system 150 receives indications of requests for credit data, the notification system 150 may consult the data in table 400 to determine information on the consumer and the request for credit data to be used in generating an event to broadcast to the other entities.


Example table 400 includes columns indicating the name of an individual 420, consumer personal identification information 422, other consumer information 424 that may be relevant to the alert, credit information 426 of the individual, and credit request history 428 for the individual or related information. This information can be gathered from one or more of the credit data store 121, the non-credit consumer information data store 112, and/or other database. The table of information may be stored in separate tables of information located within different entities, but accessible by the notification system 150.


As illustrated in table 400, row 402 includes information associated with Jordan Lee, 404 for John Doe, and 406 Jim Smith. Column 422 includes consumer PID for the three individuals, which may be relevant for the notification system to send to the subscriber when the subscriber is generating the alert to send to the individual, or event object to generate by the notification system with respect to the individual's action(s). For example, the consumer PID may include the contact information to send the alert, such as a phone number or email address.


Column 424 may include consumer information and column 426 credit data regarding the three individuals. For example, for Jordan Lee, there may be information about his income that may be relevant to an alert to send based on the request for credit data. For example, if it is known that Jordan Lee's income is $422,000 and his credit score is above a certain threshold, then the notification system 150 can use this information to determine an appropriate event for the request for credit data (e.g. an event for lenders that may have certain loans at better rates for individuals with high income and good credit score than the loans provided by the lender associated with the requesting entity).


In another example, John Doe in row 404 has been watching a lot of online videos and a large portion of his browser history is direct to boat purchases and price comparisons around $70,000 in column 424, and the credit request history includes a requested loan for $70,000, which may indicate his decision to purchase a boat, which may be used by the notification system 150 to generate an event object. In row 406, Jim Smith recently purchased a stroller as shown in column 424, opened several credit cards in a short period of time and has many purchases directed to childcare. The notification system 150 may generate an event object based on these types of information (e.g. identifies entities or subscribers to broadcast event information that may have products or services related to products or services that the user is currently seeking). A subscriber may receive an event message regarding John Doe and suggest better loan rates based on a discount for loans for boat purchases. A credit card supplier may offer a credit card with a high balance and low interest rate to suggest Jim Smith to consolidate his total debt of $13,455 into a single credit card.



FIG. 4B is an illustrative representation of a table associating financial institutions with vendors and/or service providers, along with corresponding contact and other information. Column 470 shows the identifier for the vendor/service provider, shown in column 472. Column 474 shows contact information for the vendor/service provider. The vendor/service provider is linked with a financial institution 476.


The requesting entity can be associated with the request by matching data included in the request with data previously stored in table 450. In this manner, the notification system may quickly provide an alert to subscribers who may use the alert to send information to the consumer that includes additional information (such as the identity of the requesting entity) that was not necessarily included in the request for credit data itself. As illustrated in table 450, row 452 includes a financial entity identifier (“ABL5533”) associated with the vendor “ABL Cable Co.” In some embodiments, the identifier may be included in the request for credit data without any other indication of the identity of the product/service provider. The product/service provider is tied to the financial institution American Bank. The vendors for American Bank are identified as “ABL Cable Co.” and “Quality Cellular Phones” in columns 452 and 454. The identifier may also be an identifier for a financial institution, which may have been the identifier included in the request for credit data. For example, the request for credit data may have been associated with an individual visiting BL Cable Co. (vendor of row 452), but the request for credit data may include the identifier 545AM1 associated with American Bank. In some embodiments, the requests for credit data from the vendor/service providers may include the vendor identifier associated with the requesting entity, such that the notification system can determine the name and contact information of the requesting entity by matching the vendor identifier in the request with data in table 450. As indicated in rows 452, 454, 456, the stored data associated with each vendor or service provider includes contact information, which may include multiple forms of contact information for a single vendor, such as one or more e-mail addresses and/or phone numbers. The stored information may also include contact information for the financial institution.



FIG. 5 is a block diagram of an example notification system in communication with various publishers and subscribers. The notification system includes a message QUEUE client that queues the messages as they come into the notification system, sends the messages to the notification module (or other middleware, data streaming, or other publish and subscribe technology), the notification module contains the catalog of events that the subscriber can enroll in, the services orchestration uses the USB to recognize events and publish events to subscribers to the event, and the subscriber or informal listener can receive such events.


The notification system may receive data to and/or send data to a variety of modules that may be internal, external, or a combination of both to the notification system. For the sake of discussion, the descriptions will be shown to be external to the notification system.


In some embodiments, the ecosystem includes Sending Contributing Data which are applications responsible for sending data from contributors into Credit Bureau that may affect credit data. The Sending Contributing Data can be both Subscriber and Publisher of Credit events actions to be sent through notification system.


In some embodiments, the ecosystem includes Consumer Disputes that is an application responsible for creation and management of consumer disputes (e.g. disputes reported to consumer call center either through Agents or through Webapps or API). The Consumer Disputes can be both subscriber and publisher of credit events actions to be sent through notification system.


In some embodiments, the ecosystem includes Data Furnishers (real time updates) that can be responsible for providing data to the bureau either through Real time, API, or Batch process.


In some embodiments, the ecosystem includes Freeze/block transactions that are transactions where specific data furnishes account information and status could be disputed. In some embodiments, the freeze/block transactions cannot be accessed. This transaction types may be publisher of events to the notification system that others can subscribe to.


In some embodiments, the ecosystem includes a Billing System that may be responsible for processing billing transactions from the system of records and feeding the records to a central billing system, which could be both a publisher or subscriber to the notification system.


In some embodiments, the ecosystem includes a Customer Master that may be responsible for maintaining customer information (e.g. maintaining credit files for individuals) and the products for which the individuals are authorized to use.


In some embodiments, the ecosystem includes Business Information Services that may be responsible for managing Business information related to credit data similar to a consumer information related to credit data. The Business Information Services can use the same underpinning notification infrastructure to perform subscription and publication of events.


In some embodiments, the ecosystem includes Decision Analytics that may be responsible for managing decisioning related products such modeling, aggregation, tools and fraud services. The ecosystem may also include an Event Transaction Analytics that is done at an event level (e.g. atomic payload level). The Event Transaction Analytics may also feed into the Decision Analytics for further processing and analysis at the macro level.


In some embodiments, the ecosystem includes a real time prescreen notification that may be responsible for receiving event notification that is related to a prescreen of customers. For example, events may be published to subscribers that would like to prescreen customers based on a certain credit criteria. The notification system may send event notifications to marketing services that may use the published event notifications to market to consumers. The notification system may send event notifications to external clients that may have interest in the published event notifications.


In some embodiments, the ecosystem includes the real-time event notification that can receive notification in real-time, or substantially real time. The real-time event notification may then be able to notify or alert the individual in real-time and empower the individual with information at the point of sale or during negotiation. In some embodiments, the ecosystem includes a real-time account review notification, where a business uses an existing relationship with the individual. For example, if an entity is notified of a new delinquency reported on one of their subscribers, the entity may take proactive action to mitigate risks while managing their accounts.


In some embodiments, the notification system may send events to a continuous scoring module that continuously listens to a particular score, such as changes to a credit score.


In some embodiments, the notification system may send event notifications through HTTP direct pushes, in continuous batches, through API services, and other modes of communication. In some embodiments, the ecosystem includes an event transaction enrichment which may be responsible for the ability to add enhancement in real time to an event. For example, upon closing a balance on a revolving account, the event can be enriched by further calculating a generic credit score or a custom model score. The event enhancement can be sent with or without the event in combination.


In some embodiments, the ecosystem includes a skip tracing notification, which notifies any changes to credit data from a collections perspective. For example, a new address for the consumer will be sent to the skip tracing notification.


In some embodiments, the ecosystem includes platforms that can deliver products such as prescreen or account monitoring. The ecosystem may also include products for commercial application, in a business-to-business context or directly to consumers. Furthermore, the ecosystem may also include platforms that allow consumers to share their own credit reports or other credit data to others, such as sharing credit reports with potential tenant screeners for renting.


In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, or any other tangible medium. Such software code may be stored, partially or fully, on a memory device of the executing computing device, such as the computing system 700, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage.


Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.


Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.


All of the methods and processes described above may be embodied in, and partially or fully automated via, software code modules executed by one or more general purpose computers. The methods may be executed on the computing devices in response to execution of software instructions or other executable code read from a tangible, non-transitory computer readable medium. A tangible computer readable medium is a data storage device that can store data that is readable by a computer system. Examples of computer readable mediums include read-only memory, random-access memory, other volatile or non-volatile memory devices, CD-ROMs, magnetic tape, flash drives, and optical data storage devices.


Although this disclosure has been described in terms of certain example embodiments and applications, other embodiments and applications that are apparent to those of ordinary skill in the art, including embodiments and applications that do not provide all of the benefits described herein, are also within the scope of this disclosure.


Unless otherwise explicitly stated, articles such as “a” or “an” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.


Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.

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: generate a broadcast event object based on a request from an entity for information regarding an individual or information about an action that affects credit data of the individual, wherein the broadcast event object corresponds to an event type, wherein the event type comprises a type of action that affects the credit data of the individual; andelectronically post the generated broadcast event object to a data streaming service;wherein posting the generated broadcast event object triggers a plurality of listeners based on the event type;wherein at least a subset of the plurality of listeners have access to the data streaming service and are 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 data streaming service that relate to the event type;wherein at least one subscriber is configured to generate a message based on the broadcast event object and transmit the message directly to the individual;wherein transmitting the message directly to the individual occurs in real time of the at least one identified subscriber receiving the broadcast event object; andwherein the message provides the individual with a baseline for negotiating with the entity that requested the information.
  • 2. The computing system of claim 1, wherein the event type comprises at least one of: requesting for a loan, paying off a debt, or a credit inquiry.
  • 3. The computing system of claim 1, wherein the plurality of subscribers are computing systems associated with one or more entities other than the individual, a requesting entity requesting the information, and the plurality of listeners.
  • 4. The computing 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.
  • 5. The computing system of claim 1, wherein the identified subscribers receive the broadcast event object at substantially the same time as each other.
  • 6. 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.
  • 7. The computing 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.
  • 8. The computing 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.
  • 9. The computing system of claim 1, wherein sending the broadcast event object to the identified subscribers occurs in real time with respect to receiving the request.
  • 10. A computer-implemented notification method comprising: generating a broadcast event object based on a request from an entity for information regarding an individual or information about an action that affects credit data of the individual, wherein the broadcast event object corresponds to an event type, wherein the event type comprises a type of action that affects the credit data of the individual; andelectronically posting the generated broadcast event object to a data streaming service;wherein posting the generated broadcast event object triggers a plurality of listeners based on the event type;wherein at least a subset of the plurality of listeners have access to the data streaming service and are 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 data streaming service that relate to the event type;wherein at least one subscriber is configured to generate a message based on the broadcast event object and transmit the message directly to the individual;wherein transmitting the message directly to the individual occurs in real time of the at least one identified subscriber receiving the broadcast event object; andwherein the message provides the individual with a baseline for negotiating with the entity that requested the information.
  • 11. The method of claim 10, wherein the message includes suggestions of actions the individual can perform to improve the information requested by a requesting entity requesting the information.
  • 12. The method of claim 10, further comprising determining that an update to credit data meets one or more event broadcast criteria, wherein the request is associated with a change in credit data, and the event broadcast criteria comprises whether the change in credit data meets a threshold value.
  • 13. A non-transitory computer storage medium storing computer-executable instructions that, when executed by a processor, cause the processor to perform the following operations: generating a first broadcast event object based on a request from an entity for information regarding an individual or information about an action that affects credit data of the individual, wherein the first broadcast event object corresponds to an event type, wherein the event type comprises a type of action that affects the credit data of the individual; andelectronically posting the generated first broadcast event object to a data streaming service;wherein posting the generated first broadcast event object triggers a plurality of listeners based on the event type;wherein at least a subset of the plurality of listeners have access to the data streaming service and are 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 data streaming service that relate to the event type;wherein at least one subscriber is configured to generate a message based on the broadcast event object and transmit the message directly to the individual;wherein transmitting the message directly to the individual occurs in real time of the at least one identified subscriber receiving the broadcast event object; andwherein the message provides the individual with a baseline for negotiating with the entity that requested the information.
  • 14. The non-transitory computer storage medium of claim 13, wherein the operations further comprise receiving non-credit information related to the individual, wherein the first broadcast event object is further associated with the non-credit information of the individual.
  • 15. The non-transitory computer storage medium of claim 13, wherein the operations further comprise determining that an update to credit data 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 data meets the one or more event broadcast criteria.
  • 16. The non-transitory computer storage medium of claim 15, wherein the update comprises a change in a credit score, and the event broadcast criteria comprises whether the change in the credit score meets a threshold value.
  • 17. The non-transitory computer storage medium of claim 15, wherein the message includes suggestions the individual can perform to improve the credit data.
  • 18. The non-transitory computer storage medium of claim 15, wherein the operations further comprise generating a second broadcast event object based on the first broadcast event object and broadcasting the second broadcast event object to a subscriber.
CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 16/999,686, filed Aug. 21, 2020, which is a continuation of U.S. patent application Ser. No. 15/360,496, filed Nov. 23, 2016, which claims the benefit of U.S. provisional application No. 62/259,548, filed Nov. 24, 2015, the disclosure of which are hereby incorporated herein by reference in their entirety.

US Referenced Citations (1410)
Number Name Date Kind
3316395 Lavin et al. Apr 1967 A
4305059 Benton Dec 1981 A
4346442 Musmanno Aug 1982 A
4491725 Pritchard Jan 1985 A
4578530 Zeidler Mar 1986 A
4736294 Gill Apr 1988 A
4774664 Campbell et al. Sep 1988 A
4812628 Boston et al. Mar 1989 A
4872113 Dinerstein Oct 1989 A
4876592 Von Kohorn Oct 1989 A
4891503 Jewell Jan 1990 A
4895518 Arnold Jan 1990 A
4947028 Gorog Aug 1990 A
5013038 Luxenberg et al. May 1991 A
5025138 Cuervo Jun 1991 A
5025373 Keyser, Jr. et al. Jun 1991 A
5034807 Von Kohorn Jul 1991 A
5060153 Nakagawa Oct 1991 A
5148365 Dembo Sep 1992 A
5220501 Lawlor et al. Jun 1993 A
5239462 Jones et al. Aug 1993 A
5259766 Sack Nov 1993 A
5262941 Saladin Nov 1993 A
5274547 Zoffel et al. Dec 1993 A
5301105 Cummings, Jr. Apr 1994 A
5317636 Vizcaino May 1994 A
5317733 Murdock May 1994 A
5336870 Hughes et al. Aug 1994 A
5361201 Jost et al. Nov 1994 A
5500513 Langhans et al. Mar 1996 A
5557514 Seare et al. Sep 1996 A
5583760 Klesse Dec 1996 A
5590038 Pitroda Dec 1996 A
5611052 Dykstra et al. Mar 1997 A
5615408 Johnson Mar 1997 A
5630127 Moore et al. May 1997 A
5640577 Scharmer Jun 1997 A
5644778 Burks et al. Jul 1997 A
5649114 Deaton et al. Jul 1997 A
5659725 Levy et al. Aug 1997 A
5696907 Tom Dec 1997 A
5699527 Davidson Dec 1997 A
5704029 Wright, Jr. Dec 1997 A
5704044 Tarter et al. Dec 1997 A
5708422 Blonder et al. Jan 1998 A
5732400 Mandler Mar 1998 A
5739512 Tognazzini Apr 1998 A
5745654 Titan Apr 1998 A
5745706 Wolfberg et al. Apr 1998 A
5748098 Grace May 1998 A
5754632 Smith May 1998 A
5754939 Herz et al. May 1998 A
5764923 Tallman et al. Jun 1998 A
5774883 Andersen Jun 1998 A
5793972 Shane Aug 1998 A
5802142 Browne Sep 1998 A
5819291 Haimowitz et al. Oct 1998 A
5822410 McCausland et al. Oct 1998 A
5828837 Eikland Oct 1998 A
5832068 Smith Nov 1998 A
5832447 Rieker et al. Nov 1998 A
5842211 Horadan et al. Nov 1998 A
5844218 Kawan et al. Dec 1998 A
5857174 Dugan Jan 1999 A
5870721 Norris Feb 1999 A
5875236 Jankowitz Feb 1999 A
5878403 DeFrancesco Mar 1999 A
5884287 Edesess Mar 1999 A
5903830 Joao et al. May 1999 A
5903881 Schrader et al. May 1999 A
5907828 Meyer et al. May 1999 A
5914472 Foladare et al. Jun 1999 A
5918217 Maggioncalda et al. Jun 1999 A
5924082 Silverman et al. Jul 1999 A
5926800 Baronowski et al. Jul 1999 A
5930759 Moore et al. Jul 1999 A
5930764 Melchione et al. Jul 1999 A
5930776 Dykstra et al. Jul 1999 A
5933809 Hunt et al. Aug 1999 A
5940812 Tengel et al. Aug 1999 A
5950172 Klingman Sep 1999 A
5950179 Buchanan et al. Sep 1999 A
5953710 Fleming Sep 1999 A
5956693 Geerlings Sep 1999 A
5960430 Haimowitz et al. Sep 1999 A
5961593 Gabber et al. Oct 1999 A
5966695 Melchione et al. Oct 1999 A
5966699 Zandi Oct 1999 A
5970478 Walker et al. Oct 1999 A
5978780 Watson Nov 1999 A
5991411 Kaufman et al. Nov 1999 A
5995947 Fraser et al. Nov 1999 A
5999596 Walker et al. Dec 1999 A
6006333 Nielsen Dec 1999 A
6012044 Maggioncalda et al. Jan 2000 A
6014632 Gamble et al. Jan 2000 A
6014645 Cunningham Jan 2000 A
6018723 Siegel et al. Jan 2000 A
6021397 Jones et al. Feb 2000 A
6029149 Dykstra et al. Feb 2000 A
6029178 Martin et al. Feb 2000 A
6038551 Barlow et al. Mar 2000 A
6044351 Jones Mar 2000 A
6044352 Deavers Mar 2000 A
6055570 Nielsen Apr 2000 A
6064987 Walker May 2000 A
6067522 Warady et al. May 2000 A
6070141 Houvener May 2000 A
6070147 Harms et al. May 2000 A
6070241 Edwards et al. May 2000 A
6073104 Field Jun 2000 A
6073106 Rozen et al. Jun 2000 A
6073140 Morgan et al. Jun 2000 A
6078922 Johnson et al. Jun 2000 A
6088686 Walker et al. Jul 2000 A
6094643 Anderson et al. Jul 2000 A
6098052 Kosiba et al. Aug 2000 A
6105007 Norris Aug 2000 A
6108641 Kenna et al. Aug 2000 A
6115690 Wong Sep 2000 A
6115694 Cheetham et al. Sep 2000 A
6119103 Basch et al. Sep 2000 A
6128599 Walker Oct 2000 A
6128602 Northington et al. Oct 2000 A
6128603 Dent Oct 2000 A
6129273 Shah Oct 2000 A
6144948 Walker et al. Nov 2000 A
6154729 Cannon et al. Nov 2000 A
6157707 Baulier et al. Dec 2000 A
6163770 Gamble et al. Dec 2000 A
6171112 Clark et al. Jan 2001 B1
6182229 Nielsen Jan 2001 B1
6185543 Galperin et al. Feb 2001 B1
6199077 Inala et al. Mar 2001 B1
6202053 Christiansen et al. Mar 2001 B1
6208973 Boyer et al. Mar 2001 B1
6233566 Levine et al. May 2001 B1
6249770 Erwin et al. Jun 2001 B1
6253202 Gilmour Jun 2001 B1
6253203 O'Flaherty et al. Jun 2001 B1
6263447 French et al. Jul 2001 B1
6269325 Lee et al. Jul 2001 B1
6269369 Robertson Jul 2001 B1
6275824 O'Flaherty et al. Aug 2001 B1
6282658 French et al. Aug 2001 B2
6285987 Roth et al. Sep 2001 B1
6298348 Eldering Oct 2001 B1
6304860 Martin et al. Oct 2001 B1
6311169 Duhon Oct 2001 B2
6317783 Freishtat et al. Nov 2001 B1
6321205 Eder Nov 2001 B1
6321339 French et al. Nov 2001 B1
6324524 Lent et al. Nov 2001 B1
6330546 Gopinathan et al. Dec 2001 B1
6330575 Moore et al. Dec 2001 B1
6339790 Inoue Jan 2002 B1
6343279 Bissonette et al. Jan 2002 B1
6374229 Lowrey et al. Apr 2002 B1
6374230 Walker et al. Apr 2002 B1
6374264 Bohannon et al. Apr 2002 B1
6384844 Stewart et al. May 2002 B1
6385594 Lebda et al. May 2002 B1
6393406 Eder May 2002 B1
6397197 Gindlesperger May 2002 B1
6397224 Zubeldia et al. May 2002 B1
6405173 Honarvar Jun 2002 B1
6405181 Lent et al. Jun 2002 B2
6424878 Barker et al. Jul 2002 B1
6430539 Lazarus et al. Aug 2002 B1
6453297 Burks et al. Sep 2002 B1
6456983 Keyes et al. Sep 2002 B1
6463533 Calamera et al. Oct 2002 B1
6477509 Hammons et al. Nov 2002 B1
6487540 Smith et al. Nov 2002 B1
6496827 Kozam et al. Dec 2002 B2
6496936 French et al. Dec 2002 B1
5870721 Norris Jan 2003 C1
6513018 Culhane Jan 2003 B1
6523021 Monberg et al. Feb 2003 B1
6523041 Morgan et al. Feb 2003 B1
6529880 McKeen et al. Mar 2003 B1
6532450 Brown et al. Mar 2003 B1
6542894 Lee et al. Apr 2003 B1
6543683 Hoffman Apr 2003 B2
6564210 Korda et al. May 2003 B1
6567791 Lent et al. May 2003 B2
6581059 Barrett et al. Jun 2003 B1
6581075 Guturu et al. Jun 2003 B1
6587841 DeFrancesco Jul 2003 B1
6598030 Siegel et al. Jul 2003 B1
6601173 Mohler Jul 2003 B1
6611816 Lebda et al. Aug 2003 B2
6622131 Brown et al. Sep 2003 B1
6622266 Goddard et al. Sep 2003 B1
6629245 Stone et al. Sep 2003 B1
6636803 Hartz, Jr. et al. Oct 2003 B1
6647383 August et al. Nov 2003 B1
6658393 Basch et al. Dec 2003 B1
6684093 Kuth Jan 2004 B2
6714944 Shapiro et al. Mar 2004 B1
6734886 Hagan et al. May 2004 B1
6750985 Rhoads Jun 2004 B2
6754665 Futagami et al. Jun 2004 B1
6766327 Morgan, Jr. et al. Jul 2004 B2
6766946 Iida et al. Jul 2004 B2
6782390 Lee et al. Aug 2004 B2
6795812 Lent et al. Sep 2004 B1
6804346 Mewhinney Oct 2004 B1
6805287 Bishop et al. Oct 2004 B2
6807533 Land et al. Oct 2004 B1
6823319 Lynch et al. Nov 2004 B1
6826535 Wood et al. Nov 2004 B2
6832229 Reed Dec 2004 B2
6839690 Foth et al. Jan 2005 B1
6842782 Malik et al. Jan 2005 B1
6845448 Chaganti et al. Jan 2005 B1
6847942 Land et al. Jan 2005 B1
6857073 French et al. Feb 2005 B2
6873972 Marcial et al. Mar 2005 B1
6901406 Nabe et al. May 2005 B2
6910624 Natsuno Jun 2005 B1
6912483 Frederick Jun 2005 B2
6934714 Meinig Aug 2005 B2
6950807 Brock Sep 2005 B2
6950858 Ogami Sep 2005 B2
6954757 Zargham et al. Oct 2005 B2
6962336 Glass Nov 2005 B2
6968319 Remington et al. Nov 2005 B1
6983379 Spalink et al. Jan 2006 B1
6985887 Sunstein et al. Jan 2006 B1
6988085 Hedy Jan 2006 B2
6993510 Guy Jan 2006 B2
6999941 Agarwal Feb 2006 B1
7003476 Samra et al. Feb 2006 B1
7003491 Starkman Feb 2006 B2
7013310 Messing et al. Mar 2006 B2
7016870 Jones et al. Mar 2006 B1
7028052 Chapman et al. Apr 2006 B2
7039607 Watarai et al. May 2006 B2
7058817 Ellmore Jun 2006 B1
7062458 Maggioncalda et al. Jun 2006 B2
7065566 Menard et al. Jun 2006 B2
7069240 Spero et al. Jun 2006 B2
7069249 Stolfo et al. Jun 2006 B2
7072842 Provost et al. Jul 2006 B2
7076462 Nelson et al. Jul 2006 B1
7076475 Honarvar et al. Jul 2006 B2
7083087 Gangi Aug 2006 B1
7107241 Pinto Sep 2006 B1
7107249 Dively et al. Sep 2006 B2
7117172 Black Oct 2006 B1
7120599 Keyes Oct 2006 B2
7124144 Christianson et al. Oct 2006 B2
7133840 Kenna et al. Nov 2006 B1
7133935 Hedy Nov 2006 B2
7143063 Lent Nov 2006 B2
7165037 Lazarus et al. Jan 2007 B2
7171371 Goldstein Jan 2007 B2
7174302 Patricelli et al. Feb 2007 B2
7181427 DeFrancesco Feb 2007 B1
7188169 Buus et al. Mar 2007 B2
7191150 Shao et al. Mar 2007 B1
7191451 Nakagawa Mar 2007 B2
7197468 Patricelli et al. Mar 2007 B1
7206768 deGroeve et al. Apr 2007 B1
7212995 Schulkins May 2007 B2
7213064 Smith et al. May 2007 B2
7229006 Babbi et al. Jun 2007 B2
7234156 French et al. Jun 2007 B2
7234160 Vogel et al. Jun 2007 B2
7236950 Savage et al. Jun 2007 B2
7240363 Ellingson Jul 2007 B1
7243075 Shaffer et al. Jul 2007 B1
7246067 Austin et al. Jul 2007 B2
7246068 Thomas, Jr. Jul 2007 B2
7249076 Pendleton et al. Jul 2007 B1
7249096 Lasater et al. Jul 2007 B1
7249113 Continelli et al. Jul 2007 B1
7251625 Anglum Jul 2007 B2
7254558 Hinkle et al. Aug 2007 B2
7263497 Wiser et al. Aug 2007 B1
7277869 Starkman Oct 2007 B2
7280980 Hoadley et al. Oct 2007 B1
7280983 Kuroda et al. Oct 2007 B2
7281652 Foss Oct 2007 B2
7289971 O'Neil et al. Oct 2007 B1
7295988 Reeves Nov 2007 B1
7296734 Pliha Nov 2007 B2
7298872 Glisson Nov 2007 B2
7302420 Aggarwal et al. Nov 2007 B2
7305359 Bonnell Dec 2007 B2
7308417 Nathan Dec 2007 B1
7310617 Cunningham Dec 2007 B1
7313538 Wilmes et al. Dec 2007 B2
7314166 Anderson et al. Jan 2008 B2
7318224 Honarvar et al. Jan 2008 B2
7328276 Alisuag Feb 2008 B2
7330835 Deggendorf Feb 2008 B2
7333635 Tsantes et al. Feb 2008 B2
7333937 Baldwin, Jr. et al. Feb 2008 B2
7337133 Bezos et al. Feb 2008 B1
7337468 Metzger Feb 2008 B2
7340424 Gang et al. Mar 2008 B2
7340434 Schnall Mar 2008 B2
7343295 Pomerance Mar 2008 B2
7346576 Lent et al. Mar 2008 B2
7356506 Watson et al. Apr 2008 B2
7356516 Richey et al. Apr 2008 B2
7366694 Lazerson Apr 2008 B2
7370044 Mulhern et al. May 2008 B2
7376603 Mayr et al. May 2008 B1
7379913 Steele et al. May 2008 B2
7380707 Fredman Jun 2008 B1
7383215 Navarro et al. Jun 2008 B1
7383988 Slonecker, Jr. Jun 2008 B2
7386466 McLean et al. Jun 2008 B2
7392216 Palmgren et al. Jun 2008 B1
7395232 Pilato Jul 2008 B1
7395273 Khan et al. Jul 2008 B2
7403919 Chacko et al. Jul 2008 B2
7403923 Elliott et al. Jul 2008 B2
7403942 Bayliss Jul 2008 B1
7409369 Homuth et al. Aug 2008 B1
7418417 Chacko et al. Aug 2008 B2
7433864 Malik Oct 2008 B2
7451095 Bradley et al. Nov 2008 B1
7451113 Kasower Nov 2008 B1
7460857 Roach, Jr. Dec 2008 B2
7464067 Chestnut Dec 2008 B2
7467401 Cicchitto Dec 2008 B2
7478157 Bohrer et al. Jan 2009 B2
7479949 Jobs et al. Jan 2009 B2
7480631 Merced et al. Jan 2009 B1
7490356 Lieblich et al. Feb 2009 B2
7505939 Lent et al. Mar 2009 B2
7527967 Chao et al. May 2009 B2
7529698 Joao May 2009 B2
7536329 Goldberg et al. May 2009 B2
7536346 Aliffi et al. May 2009 B2
7536348 Shao et al. May 2009 B2
7542993 Satterfield et al. Jun 2009 B2
7543739 Brown et al. Jun 2009 B2
7546266 Beirne et al. Jun 2009 B2
7546271 Chmielewski et al. Jun 2009 B1
7552080 Willard et al. Jun 2009 B1
7552086 Rajasekar et al. Jun 2009 B1
7556192 Wokaty, Jr. Jul 2009 B2
7559217 Bass Jul 2009 B2
7562184 Henmi et al. Jul 2009 B2
7562814 Shao et al. Jul 2009 B1
7571138 Miri et al. Aug 2009 B2
7580884 Cook Aug 2009 B2
7584127 Byrne et al. Sep 2009 B2
7584146 Duhon Sep 2009 B1
7587366 Grim, III et al. Sep 2009 B2
7593889 Raines et al. Sep 2009 B2
7593891 Kornegay et al. Sep 2009 B2
7593892 Balk et al. Sep 2009 B2
7596512 Raines et al. Sep 2009 B1
7596716 Frost et al. Sep 2009 B2
7603317 Adler et al. Oct 2009 B2
7603701 Gaucas Oct 2009 B2
7606725 Robertson et al. Oct 2009 B2
7610229 Kornegay Oct 2009 B1
7617116 Amar et al. Nov 2009 B2
7620592 O'Mara et al. Nov 2009 B2
7624068 Heasley et al. Nov 2009 B1
7630932 Danaher et al. Dec 2009 B2
7630933 Peterson et al. Dec 2009 B2
7640200 Gardner et al. Dec 2009 B2
7647274 Peterson et al. Jan 2010 B2
7647344 Skurtovich, Jr. et al. Jan 2010 B2
7653592 Flaxman et al. Jan 2010 B1
7653593 Zarikian et al. Jan 2010 B2
7672833 Blume et al. Mar 2010 B2
7676410 Petralia Mar 2010 B2
7676418 Chung et al. Mar 2010 B1
7689451 Vives Mar 2010 B2
7689505 Kasower Mar 2010 B2
7689506 Fei et al. Mar 2010 B2
7690032 Peirce Mar 2010 B1
7693787 Provinse Apr 2010 B2
7698214 Lindgren Apr 2010 B1
7698217 Phillips et al. Apr 2010 B1
7698445 Fitzpatrick et al. Apr 2010 B2
7707102 Rothstein Apr 2010 B2
7708196 Palmieri et al. May 2010 B2
7711635 Steele et al. May 2010 B2
7711636 Robida et al. May 2010 B2
7720750 Brody May 2010 B2
7725385 Royer et al. May 2010 B2
7729959 Wells et al. Jun 2010 B1
7729983 Ellis Jun 2010 B1
7734522 Johnson et al. Jun 2010 B2
7739139 Robertson et al. Jun 2010 B2
7747559 Leitner et al. Jun 2010 B2
7752132 Stewart et al. Jul 2010 B2
7756789 Welker et al. Jul 2010 B2
7765311 Itabashi et al. Jul 2010 B2
7769657 Chacko et al. Aug 2010 B2
7769696 Yoda Aug 2010 B2
7769998 Lynch et al. Aug 2010 B2
7774257 Maggioncalda et al. Aug 2010 B2
7774270 MacCloskey Aug 2010 B1
7783515 Kumar et al. Aug 2010 B1
7783562 Ellis Aug 2010 B1
7788147 Haggerty et al. Aug 2010 B2
7788152 Haggerty et al. Aug 2010 B2
7788155 Jones et al. Aug 2010 B2
7792715 Kasower Sep 2010 B1
7792716 Gooding et al. Sep 2010 B2
7792732 Haggerty et al. Sep 2010 B2
7797725 Lunt et al. Sep 2010 B2
7797734 Babi et al. Sep 2010 B2
7801807 DeFrancesco et al. Sep 2010 B2
7801812 Conlin et al. Sep 2010 B2
7801828 Candella et al. Sep 2010 B2
7805345 Abrahams et al. Sep 2010 B2
7814004 Haggerty et al. Oct 2010 B2
7814005 Imrey et al. Oct 2010 B2
7818228 Coulter Oct 2010 B1
7818229 Imrey et al. Oct 2010 B2
7832006 Chen et al. Nov 2010 B2
7835983 Lefner et al. Nov 2010 B2
7836111 Shan Nov 2010 B1
7840484 Haggerty et al. Nov 2010 B2
7841008 Cole et al. Nov 2010 B1
7848972 Sharma Dec 2010 B1
7848978 Imrey et al. Dec 2010 B2
7849004 Choudhuri et al. Dec 2010 B2
7849014 Erikson Dec 2010 B2
7853493 DeBie et al. Dec 2010 B2
7853518 Cagan Dec 2010 B2
7853984 Antell et al. Dec 2010 B2
7853998 Blaisdell et al. Dec 2010 B2
7856386 Hazlehurst et al. Dec 2010 B2
7860782 Cash et al. Dec 2010 B2
7860786 Blackburn et al. Dec 2010 B2
7870078 Clark et al. Jan 2011 B2
7873677 Messing et al. Jan 2011 B2
7877304 Coulter Jan 2011 B1
7880728 de los Reyes et al. Feb 2011 B2
7890420 Haggerty et al. Feb 2011 B2
7899750 Klieman et al. Mar 2011 B1
7900052 Joans Mar 2011 B2
7904306 Johnson et al. Mar 2011 B2
7904367 Chung et al. Mar 2011 B2
7908242 Achanta Mar 2011 B1
7912770 Haggerty et al. Mar 2011 B2
7912842 Bayliss et al. Mar 2011 B1
7912865 Akerman et al. Mar 2011 B2
7925578 Hong et al. Apr 2011 B1
7925582 Kornegay et al. Apr 2011 B1
7930195 Heyns et al. Apr 2011 B2
7930252 Bender et al. Apr 2011 B2
7937416 Hossfeld et al. May 2011 B2
7941363 Tanaka et al. May 2011 B2
7941365 Bradley et al. May 2011 B1
7945510 Bradley et al. May 2011 B1
7953213 Babi et al. May 2011 B2
7966192 Pagliari et al. Jun 2011 B2
7966255 Wong et al. Jun 2011 B2
7970676 Feinstein Jun 2011 B2
7970679 Kasower Jun 2011 B2
7970698 Gupta et al. Jun 2011 B2
7974919 Conlin et al. Jul 2011 B2
7979908 Millwee Jul 2011 B2
7983975 Jones et al. Jul 2011 B2
7983976 Nafeh et al. Jul 2011 B2
7983979 Holland, IV Jul 2011 B2
7987124 Holden et al. Jul 2011 B1
7991689 Brunzell et al. Aug 2011 B1
8001034 Chung et al. Aug 2011 B2
8001040 Keithley Aug 2011 B2
8001041 Hoadley et al. Aug 2011 B2
8001042 Brunzell et al. Aug 2011 B1
8001043 Walker et al. Aug 2011 B1
8001153 Skurtovich, Jr. et al. Aug 2011 B2
8005738 Chacko et al. Aug 2011 B2
8005759 Hirtenstein et al. Aug 2011 B2
8005795 Galipeau et al. Aug 2011 B2
8015107 Kornegay et al. Sep 2011 B2
8019828 Cash et al. Sep 2011 B2
8019843 Cash et al. Sep 2011 B2
8024263 Zarikian et al. Sep 2011 B2
8024778 Cash et al. Sep 2011 B2
8032932 Speyer et al. Oct 2011 B2
8055579 Davies et al. Nov 2011 B2
8060424 Kasower Nov 2011 B2
8060441 Stewart et al. Nov 2011 B2
8064586 Shaffer et al. Nov 2011 B2
8065233 Lee et al. Nov 2011 B2
8065234 Liao et al. Nov 2011 B2
8073768 Haggerty et al. Dec 2011 B2
8073785 Candella et al. Dec 2011 B1
8078524 Crawford et al. Dec 2011 B2
8078527 Cerise et al. Dec 2011 B2
8078528 Vicente et al. Dec 2011 B1
8082202 Weiss Dec 2011 B2
8086523 Palmer Dec 2011 B1
8095443 DeBie Jan 2012 B2
8095458 Peterson et al. Jan 2012 B2
8099309 Bober Jan 2012 B1
8099341 Varghese Jan 2012 B2
8099356 Feinstein et al. Jan 2012 B2
8104679 Brown Jan 2012 B2
8127982 Casey et al. Mar 2012 B1
8127986 Taylor et al. Mar 2012 B1
8131614 Haggerty et al. Mar 2012 B2
8131685 Gedalius et al. Mar 2012 B1
8135642 Krause Mar 2012 B1
8160960 Fei et al. Apr 2012 B1
8165940 Meimes et al. Apr 2012 B2
8165962 LeKachman Apr 2012 B1
8195549 Kasower Jun 2012 B2
8201257 Andres et al. Jun 2012 B1
8204774 Chwast et al. Jun 2012 B2
8204812 Stewart et al. Jun 2012 B2
8219535 Kobori et al. Jul 2012 B1
8224723 Bosch et al. Jul 2012 B2
8225395 Atwood et al. Jul 2012 B2
8234498 Britti et al. Jul 2012 B2
8239130 Upstill et al. Aug 2012 B1
8255971 Webb et al. Aug 2012 B1
8255978 Dick Aug 2012 B2
8260699 Smith et al. Sep 2012 B2
8285613 Coulter Oct 2012 B1
8285656 Chang et al. Oct 2012 B1
8290840 Kasower Oct 2012 B2
8296229 Yellin et al. Oct 2012 B1
8311936 Haggerty et al. Nov 2012 B2
8312033 McMillan Nov 2012 B1
8315942 Haggerty et al. Nov 2012 B2
8321334 Kornegay et al. Nov 2012 B1
8321339 Imrey et al. Nov 2012 B2
8327429 Speyer et al. Dec 2012 B2
8335741 Kornegay et al. Dec 2012 B2
8340685 Cochran et al. Dec 2012 B2
8347364 Babi et al. Jan 2013 B2
8355967 Debie et al. Jan 2013 B2
8359278 Domenikos et al. Jan 2013 B2
8364518 Blake et al. Jan 2013 B1
8364588 Celka et al. Jan 2013 B2
8380618 Kazenas et al. Feb 2013 B1
8386377 Xiong et al. Feb 2013 B1
8392334 Hirtenstein et al. Mar 2013 B2
8412593 Song et al. Apr 2013 B1
8418254 Britti et al. Apr 2013 B2
8433512 Lopatenko et al. Apr 2013 B1
8433648 Keithley et al. Apr 2013 B2
8442886 Haggerty et al. May 2013 B1
8458062 Dutt et al. Jun 2013 B2
8458074 Showalter Jun 2013 B2
8463595 Rehling et al. Jun 2013 B1
8464939 Taylor et al. Jun 2013 B1
8473353 Matsuda et al. Jun 2013 B2
8473354 Psota et al. Jun 2013 B2
8478686 Giles Jul 2013 B1
8489502 Morris et al. Jul 2013 B2
8515844 Kasower Aug 2013 B2
8527596 Long et al. Sep 2013 B2
8533030 Dhir et al. Sep 2013 B1
8533118 Weller et al. Sep 2013 B2
8543498 Silbernagel et al. Sep 2013 B2
8560161 Kator et al. Oct 2013 B1
8560436 Ingram et al. Oct 2013 B2
8566029 Lopatenko et al. Oct 2013 B1
8566141 Nagdev et al. Oct 2013 B1
8571971 Brown et al. Oct 2013 B1
8572083 Snell et al. Oct 2013 B1
8589069 Lehman Nov 2013 B1
8589208 Kruger et al. Nov 2013 B2
8589286 Kornegay et al. Nov 2013 B1
8595101 Daukas et al. Nov 2013 B1
8600886 Ramavarjula et al. Dec 2013 B2
8606694 Campbell et al. Dec 2013 B2
8621562 Antell et al. Dec 2013 B2
8626618 Psota et al. Jan 2014 B2
8631242 Britti et al. Jan 2014 B2
8639616 Rolenaitis et al. Jan 2014 B1
8646101 Millwee Feb 2014 B1
8650407 Britti et al. Feb 2014 B2
8660919 Kasower Feb 2014 B2
8671107 Scully et al. Mar 2014 B2
8671115 Skurtovich, Jr. et al. Mar 2014 B2
8694420 Oliai Apr 2014 B1
8712907 Stibel et al. Apr 2014 B1
8719159 Keithley May 2014 B2
8725613 Celka et al. May 2014 B1
8732004 Ramos et al. May 2014 B1
8738516 Dean et al. May 2014 B1
8744956 DiChiara et al. Jun 2014 B1
8756099 Keithley et al. Jun 2014 B2
8760417 Haug Jun 2014 B2
8762243 Jenkins et al. Jun 2014 B2
8768914 Scriffignano et al. Jul 2014 B2
8775299 Achanta et al. Jul 2014 B2
8781882 Arboletti et al. Jul 2014 B1
8781951 Lewis et al. Jul 2014 B2
8781953 Kasower Jul 2014 B2
8806218 Hatakeda Aug 2014 B2
8856894 Dean et al. Oct 2014 B1
8930216 Johnson et al. Jan 2015 B1
8930251 DeBie Jan 2015 B2
8930262 Searson et al. Jan 2015 B1
8930263 Mahacek et al. Jan 2015 B1
8931058 DiChiara et al. Jan 2015 B2
8938399 Herman Jan 2015 B1
8938432 Rossmark et al. Jan 2015 B2
8949981 Trollope et al. Feb 2015 B1
8983867 Stibel et al. Mar 2015 B2
9015171 Bayliss Apr 2015 B2
9043930 Britti et al. May 2015 B2
9053589 Kator et al. Jun 2015 B1
9053590 Kator et al. Jun 2015 B1
9058627 Wasser et al. Jun 2015 B1
9076276 Kator et al. Jul 2015 B1
9116918 Kim Aug 2015 B1
9143541 Szamonek et al. Sep 2015 B1
9147042 Haller et al. Sep 2015 B1
9183363 Millwee Nov 2015 B1
9189789 Hastings et al. Nov 2015 B1
9213461 Eraker et al. Dec 2015 B2
9251541 Celka et al. Feb 2016 B2
9256624 Skurtovich, Jr. et al. Feb 2016 B2
9256904 Haller et al. Feb 2016 B1
9443268 Kapczynski et al. Sep 2016 B1
9449346 Hockey et al. Sep 2016 B1
9489694 Haller et al. Nov 2016 B2
9553936 Dijk et al. Jan 2017 B2
9558519 Burger Jan 2017 B1
9569797 Rohn et al. Feb 2017 B1
9595023 Hockey et al. Mar 2017 B1
9607336 Dean Mar 2017 B1
9652802 Kasower May 2017 B1
9684905 Haller et al. Jun 2017 B1
9690820 Girulat, Jr. Jun 2017 B1
9697263 Girulat, Jr. Jul 2017 B1
9710523 Skurtovich, Jr. et al. Jul 2017 B2
9710852 Olson et al. Jul 2017 B1
9760553 Hecht-Nielse Sep 2017 B1
9792648 Haller et al. Oct 2017 B1
9892457 Kapczynski Feb 2018 B1
10003591 Hockey et al. Jun 2018 B2
10104059 Hockey et al. Oct 2018 B2
10115155 Haller et al. Oct 2018 B1
10319029 Hockey et al. Jun 2019 B1
10362058 Hu et al. Jul 2019 B2
10380654 Hirtenstein et al. Aug 2019 B2
10402792 Lin et al. Sep 2019 B2
10417704 Searson et al. Sep 2019 B2
10523653 Hockey et al. Dec 2019 B2
10528545 Girulat, Jr. Jan 2020 B1
10530761 Hockey et al. Jan 2020 B2
10565643 Rohn et al. Feb 2020 B2
10579647 Allsopp et al. Mar 2020 B1
10586279 Ramos et al. Mar 2020 B1
10614463 Hockey et al. Apr 2020 B1
10650448 Haller et al. May 2020 B1
10671749 Felice-Steele et al. Jun 2020 B2
10726491 Hockey et al. Jul 2020 B1
10735183 Mehta et al. Aug 2020 B1
10757154 Jacobs et al. Aug 2020 B1
10880313 Manna et al. Dec 2020 B2
10909617 Kasower Feb 2021 B2
10937090 Debie et al. Mar 2021 B1
10949428 Poirel et al. Mar 2021 B2
10984404 Nack et al. Apr 2021 B2
11004147 Haller et al. May 2021 B1
11025629 Chasman et al. Jun 2021 B2
11025638 Ford et al. Jun 2021 B2
11050767 Black et al. Jun 2021 B2
11157997 Robida et al. Oct 2021 B2
11159593 Jacobs et al. Oct 2021 B1
11227001 Rege et al. Jan 2022 B2
11265324 Felice-Steele et al. Mar 2022 B2
11347715 Girulat, Jr. May 2022 B2
11373261 Ramos et al. Jun 2022 B1
11379821 Butvin et al. Jul 2022 B2
11399029 Manna et al. Jul 2022 B2
11410230 Olson et al. Aug 2022 B1
20010011247 O'Flaherty et al. Aug 2001 A1
20010014868 Herz et al. Aug 2001 A1
20010014878 Mitra et al. Aug 2001 A1
20010027413 Bhutta Oct 2001 A1
20010029470 Schultz et al. Oct 2001 A1
20010029482 Tealdi et al. Oct 2001 A1
20010034618 Kessler et al. Oct 2001 A1
20010034631 Kiselik Oct 2001 A1
20010039523 Iwamoto Nov 2001 A1
20010039532 Coleman, Jr. et al. Nov 2001 A1
20010042785 Walker et al. Nov 2001 A1
20010044729 Pomerance Nov 2001 A1
20010044756 Watkins et al. Nov 2001 A1
20010047307 Bennett et al. Nov 2001 A1
20010049620 Blasko Dec 2001 A1
20020004736 Roundtree et al. Jan 2002 A1
20020004774 Defarlo Jan 2002 A1
20020010594 Levine Jan 2002 A1
20020026519 Itabashi et al. Feb 2002 A1
20020032635 Harris et al. Mar 2002 A1
20020032645 Nozaki et al. Mar 2002 A1
20020032647 Delinsky et al. Mar 2002 A1
20020035511 Haji et al. Mar 2002 A1
20020035520 Weiss Mar 2002 A1
20020042763 Pillay et al. Apr 2002 A1
20020049624 Raveis, Jr. Apr 2002 A1
20020052836 Galperin et al. May 2002 A1
20020052841 Guthrie et al. May 2002 A1
20020055869 Hegg May 2002 A1
20020069122 Yun et al. Jun 2002 A1
20020077964 Brody et al. Jun 2002 A1
20020087460 Hornung Jul 2002 A1
20020091635 Dilip et al. Jul 2002 A1
20020091650 Ellis Jul 2002 A1
20020099635 Guiragosian Jul 2002 A1
20020099641 Mills et al. Jul 2002 A1
20020099824 Bender et al. Jul 2002 A1
20020107765 Walker Aug 2002 A1
20020107849 Hickey et al. Aug 2002 A1
20020111816 Lortscher et al. Aug 2002 A1
20020111890 Sloan et al. Aug 2002 A1
20020116247 Tucker et al. Aug 2002 A1
20020119824 Allen Aug 2002 A1
20020128962 Kasower Sep 2002 A1
20020133365 Grey et al. Sep 2002 A1
20020133462 Shteyn Sep 2002 A1
20020138297 Lee Sep 2002 A1
20020138445 Laage et al. Sep 2002 A1
20020138470 Zhou Sep 2002 A1
20020147617 Schoenbaum et al. Oct 2002 A1
20020147669 Taylor et al. Oct 2002 A1
20020147695 Khedkar et al. Oct 2002 A1
20020152166 Dutta et al. Oct 2002 A1
20020156676 Ahrens et al. Oct 2002 A1
20020156797 Lee et al. Oct 2002 A1
20020161664 Shaya et al. Oct 2002 A1
20020165757 Lisser Nov 2002 A1
20020165839 Taylor et al. Nov 2002 A1
20020169747 Chapman et al. Nov 2002 A1
20020173994 Ferguson, III Nov 2002 A1
20020174048 Dheer et al. Nov 2002 A1
20020174124 Haas et al. Nov 2002 A1
20020178146 Akella et al. Nov 2002 A1
20020184054 Cox et al. Dec 2002 A1
20020188478 Breeland et al. Dec 2002 A1
20020194103 Nabe Dec 2002 A1
20020194117 Nabe et al. Dec 2002 A1
20020194120 Russell et al. Dec 2002 A1
20020198736 Harrison Dec 2002 A1
20020198806 Blagg et al. Dec 2002 A1
20020198824 Cook Dec 2002 A1
20020198830 Randell et al. Dec 2002 A1
20030009415 Lutnick et al. Jan 2003 A1
20030009418 Green et al. Jan 2003 A1
20030009426 Ruiz-Sanchez Jan 2003 A1
20030014336 Dao et al. Jan 2003 A1
20030018549 Fei et al. Jan 2003 A1
20030018558 Heffner et al. Jan 2003 A1
20030027635 Walker et al. Feb 2003 A1
20030028402 Ulrich et al. Feb 2003 A1
20030028477 Stevenson et al. Feb 2003 A1
20030033231 Turner et al. Feb 2003 A1
20030036926 Starkey et al. Feb 2003 A1
20030036995 Lazerson Feb 2003 A1
20030037054 Dutta et al. Feb 2003 A1
20030041019 Vagim, III et al. Feb 2003 A1
20030041021 Kogler et al. Feb 2003 A1
20030041031 Hedy Feb 2003 A1
20030046112 Dutta et al. Mar 2003 A1
20030046222 Bard et al. Mar 2003 A1
20030046311 Baidya et al. Mar 2003 A1
20030050795 Baldwin, Jr. et al. Mar 2003 A1
20030050796 Baldwin, Jr. et al. Mar 2003 A1
20030064705 Desierio Apr 2003 A1
20030065563 Elliott et al. Apr 2003 A1
20030069839 Whittington et al. Apr 2003 A1
20030078877 Beirne et al. Apr 2003 A1
20030078897 Florance et al. Apr 2003 A1
20030097342 Whittingtom May 2003 A1
20030097380 Mulhern et al. May 2003 A1
20030101111 Dang et al. May 2003 A1
20030110111 Nalebuff et al. Jun 2003 A1
20030115122 Slater et al. Jun 2003 A1
20030126072 Brock Jul 2003 A1
20030144907 Cohen, Jr. et al. Jul 2003 A1
20030144933 Huang Jul 2003 A1
20030154162 Danaher et al. Aug 2003 A1
20030158960 Engberg Aug 2003 A1
20030163416 Kitajima Aug 2003 A1
20030163435 Payone Aug 2003 A1
20030163483 Zingher et al. Aug 2003 A1
20030172039 Guy Sep 2003 A1
20030177091 Paglin Sep 2003 A1
20030187780 Arthus et al. Oct 2003 A1
20030195830 Merkoulovitch et al. Oct 2003 A1
20030195859 Lawrence Oct 2003 A1
20030204752 Garrison Oct 2003 A1
20030208412 Hillestad et al. Nov 2003 A1
20030212618 Keyes et al. Nov 2003 A1
20030220858 Lam et al. Nov 2003 A1
20030225729 Maloche et al. Dec 2003 A1
20030229507 Perge Dec 2003 A1
20030229580 Gass et al. Dec 2003 A1
20030233259 Mistretta et al. Dec 2003 A1
20030236738 Lange et al. Dec 2003 A1
20040006488 Fitall et al. Jan 2004 A1
20040006536 Kawashima et al. Jan 2004 A1
20040010443 May et al. Jan 2004 A1
20040010458 Friedman Jan 2004 A1
20040023637 Johnson et al. Feb 2004 A1
20040024709 Yu et al. Feb 2004 A1
20040030621 Cobb Feb 2004 A1
20040030629 Freeman et al. Feb 2004 A1
20040030649 Nelson et al. Feb 2004 A1
20040030667 Xu et al. Feb 2004 A1
20040039688 Sulkowski et al. Feb 2004 A1
20040044563 Stein Mar 2004 A1
20040044615 Xue et al. Mar 2004 A1
20040044617 Lu Mar 2004 A1
20040044673 Brady et al. Mar 2004 A1
20040049473 Gower et al. Mar 2004 A1
20040050928 Bishop et al. Mar 2004 A1
20040054619 Watson et al. Mar 2004 A1
20040064402 Dreyer et al. Apr 2004 A1
20040073456 Gottlieb et al. Apr 2004 A1
20040078323 Johnston et al. Apr 2004 A1
20040078324 Lonnberg et al. Apr 2004 A1
20040088237 Moenickheim et al. May 2004 A1
20040088255 Zielke et al. May 2004 A1
20040103147 Flesher et al. May 2004 A1
20040111292 Hutchins Jun 2004 A1
20040111305 Gavan et al. Jun 2004 A1
20040111358 Lange et al. Jun 2004 A1
20040111359 Hudock Jun 2004 A1
20040111363 Trench et al. Jun 2004 A1
20040117235 Shacham Jun 2004 A1
20040117302 Weichert et al. Jun 2004 A1
20040128150 Lundegren Jul 2004 A1
20040128230 Oppenheimer et al. Jul 2004 A1
20040133460 Berlin Jul 2004 A1
20040133493 Ford et al. Jul 2004 A1
20040133509 McCoy et al. Jul 2004 A1
20040133513 McCoy et al. Jul 2004 A1
20040133515 McCoy et al. Jul 2004 A1
20040138935 Johnson et al. Jul 2004 A1
20040138994 DeFrancesco et al. Jul 2004 A1
20040138995 Hershkowitz et al. Jul 2004 A1
20040139025 Coleman Jul 2004 A1
20040143546 Wood et al. Jul 2004 A1
20040153437 Buchan Aug 2004 A1
20040153521 Kogo Aug 2004 A1
20040158521 Newton Aug 2004 A1
20040158523 Dort Aug 2004 A1
20040158723 Root Aug 2004 A1
20040159700 Khan et al. Aug 2004 A1
20040167793 Masuoka et al. Aug 2004 A1
20040177030 Shoham Sep 2004 A1
20040177114 Friedman et al. Sep 2004 A1
20040186807 Nathans et al. Sep 2004 A1
20040193535 Barazesh Sep 2004 A1
20040193538 Raines Sep 2004 A1
20040199456 Flint et al. Oct 2004 A1
20040199458 Ho Oct 2004 A1
20040199462 Starrs Oct 2004 A1
20040215553 Gang et al. Oct 2004 A1
20040215554 Kemper et al. Oct 2004 A1
20040215555 Kemper et al. Oct 2004 A1
20040215556 Merkley, Jr. et al. Oct 2004 A1
20040215584 Yao Oct 2004 A1
20040220865 Lozowski et al. Nov 2004 A1
20040220896 Finlay et al. Nov 2004 A1
20040220918 Scriffignano et al. Nov 2004 A1
20040225545 Turner et al. Nov 2004 A1
20040225594 Nolan, III et al. Nov 2004 A1
20040225597 Oppenheimer et al. Nov 2004 A1
20040225643 Alpha et al. Nov 2004 A1
20040230534 McGough Nov 2004 A1
20040243450 Bernard, Jr. et al. Dec 2004 A1
20040243506 Das Dec 2004 A1
20040243588 Tanner et al. Dec 2004 A1
20040249532 Kelly et al. Dec 2004 A1
20040255127 Arnouse Dec 2004 A1
20040267660 Greenwood et al. Dec 2004 A1
20040267714 Frid et al. Dec 2004 A1
20050004855 Jenson et al. Jan 2005 A1
20050004870 McGaughey Jan 2005 A1
20050005168 Dick Jan 2005 A1
20050010513 Duckworth et al. Jan 2005 A1
20050027633 Fortuna et al. Feb 2005 A1
20050027983 Klawon Feb 2005 A1
20050027995 Menschik et al. Feb 2005 A1
20050055231 Lee Mar 2005 A1
20050055275 Newman et al. Mar 2005 A1
20050058262 Timmins et al. Mar 2005 A1
20050071328 Lawrence Mar 2005 A1
20050080697 Foss et al. Apr 2005 A1
20050080716 Belyi et al. Apr 2005 A1
20050080821 Breil et al. Apr 2005 A1
20050086071 Fox, Jr. et al. Apr 2005 A1
20050086072 Fox, Jr. et al. Apr 2005 A1
20050086126 Patterson Apr 2005 A1
20050086176 Dahlgren Apr 2005 A1
20050091164 Varble Apr 2005 A1
20050096950 Caplan et al. May 2005 A1
20050097017 Hanratty May 2005 A1
20050097039 Kulcsar et al. May 2005 A1
20050097320 Golan et al. May 2005 A1
20050102180 Gailey et al. May 2005 A1
20050102206 Savasoglu et al. May 2005 A1
20050102226 Oppenheimer et al. May 2005 A1
20050105719 Huda May 2005 A1
20050125291 Demkiw Grayson et al. Jun 2005 A1
20050125350 Tidwell et al. Jun 2005 A1
20050125397 Gross et al. Jun 2005 A1
20050130704 McParland et al. Jun 2005 A1
20050137899 Davies et al. Jun 2005 A1
20050137912 Rao et al. Jun 2005 A1
20050137963 Ricketts et al. Jun 2005 A1
20050144452 Lynch et al. Jun 2005 A1
20050154617 Ruggieri et al. Jul 2005 A1
20050154664 Guy et al. Jul 2005 A1
20050154665 Kerr Jul 2005 A1
20050154769 Eckart et al. Jul 2005 A1
20050159996 Lazaraus et al. Jul 2005 A1
20050197953 Broadbent et al. Sep 2005 A1
20050203768 Florance Sep 2005 A1
20050209880 Drelicharz et al. Sep 2005 A1
20050209922 Hofmeister Sep 2005 A1
20050216953 Ellingson Sep 2005 A1
20050228748 Togher et al. Oct 2005 A1
20050251474 Shinn et al. Nov 2005 A1
20050267840 Holm-Blagg et al. Dec 2005 A1
20050273423 Kiai et al. Dec 2005 A1
20050273431 Abel et al. Dec 2005 A1
20050276401 Madill et al. Dec 2005 A1
20050279827 Mascavage et al. Dec 2005 A1
20050288998 Verma et al. Dec 2005 A1
20060014129 Coleman et al. Jan 2006 A1
20060015425 Brooks Jan 2006 A1
20060029107 McCullough et al. Feb 2006 A1
20060031158 Orman Feb 2006 A1
20060032909 Seegar Feb 2006 A1
20060036543 Blagg et al. Feb 2006 A1
20060059073 Walzak Mar 2006 A1
20060059086 Mulhern Mar 2006 A1
20060069635 Ram et al. Mar 2006 A1
20060074793 Hibbert et al. Apr 2006 A1
20060080139 Mainzer Apr 2006 A1
20060080233 Mendelevich et al. Apr 2006 A1
20060080251 Fried et al. Apr 2006 A1
20060085334 Murphy Apr 2006 A1
20060089842 Medawar Apr 2006 A1
20060095363 May May 2006 A1
20060100944 Reddin et al. May 2006 A1
20060100954 Schoen May 2006 A1
20060106670 Cai et al. May 2006 A1
20060123461 Lunt et al. Jun 2006 A1
20060131390 Kim Jun 2006 A1
20060149674 Cook et al. Jul 2006 A1
20060155573 Hartunian Jul 2006 A1
20060155639 Lynch et al. Jul 2006 A1
20060163347 Foss et al. Jul 2006 A1
20060173772 Hayes et al. Aug 2006 A1
20060177226 Ellis, III Aug 2006 A1
20060178971 Owen et al. Aug 2006 A1
20060178983 Nice et al. Aug 2006 A1
20060184410 Ramamurthy et al. Aug 2006 A1
20060184440 Britti et al. Aug 2006 A1
20060184585 Grear et al. Aug 2006 A1
20060195351 Bayburtian Aug 2006 A1
20060195391 Stanelle Aug 2006 A1
20060202012 Grano et al. Sep 2006 A1
20060204051 Holland, IV Sep 2006 A1
20060212386 Willey et al. Sep 2006 A1
20060212407 Lyon Sep 2006 A1
20060229799 Nimmo et al. Oct 2006 A1
20060229943 Mathias et al. Oct 2006 A1
20060229961 Lyftogt et al. Oct 2006 A1
20060229996 Keithley et al. Oct 2006 A1
20060233332 Toms Oct 2006 A1
20060235743 Long et al. Oct 2006 A1
20060241923 Xu et al. Oct 2006 A1
20060242046 Haggerty et al. Oct 2006 A1
20060248106 Milne et al. Nov 2006 A1
20060259364 Strock et al. Nov 2006 A1
20060265323 Winter et al. Nov 2006 A1
20060267999 Cash et al. Nov 2006 A1
20060271457 Romain et al. Nov 2006 A1
20060271633 Adler Nov 2006 A1
20060277092 Williams Dec 2006 A1
20060277141 Palmer Dec 2006 A1
20060278704 Saunders et al. Dec 2006 A1
20060282359 Nobili et al. Dec 2006 A1
20060287764 Kraft Dec 2006 A1
20060287766 Kraft Dec 2006 A1
20060287767 Kraft Dec 2006 A1
20060288090 Kraft Dec 2006 A1
20060293979 Cash et al. Dec 2006 A1
20060294199 Bertholf Dec 2006 A1
20070011083 Bird et al. Jan 2007 A1
20070016500 Chatterji et al. Jan 2007 A1
20070016501 Chatterji et al. Jan 2007 A1
20070016517 Solomon Jan 2007 A1
20070016518 Atkinson et al. Jan 2007 A1
20070016520 Gang et al. Jan 2007 A1
20070022141 Singleton et al. Jan 2007 A1
20070022297 Britti et al. Jan 2007 A1
20070027778 Schellhammer et al. Feb 2007 A1
20070038483 Wood Feb 2007 A1
20070038497 Britti et al. Feb 2007 A1
20070038568 Greene et al. Feb 2007 A1
20070043654 Libman Feb 2007 A1
20070045402 Rothschild Mar 2007 A1
20070045405 Rothschild Mar 2007 A1
20070067207 Haggerty et al. Mar 2007 A1
20070067297 Kublickis Mar 2007 A1
20070078741 Haggerty et al. Apr 2007 A1
20070083460 Bachenheimer Apr 2007 A1
20070083463 Kraft Apr 2007 A1
20070088950 Wheeler et al. Apr 2007 A1
20070093234 Willis et al. Apr 2007 A1
20070094137 Phillips et al. Apr 2007 A1
20070094230 Subramaniam et al. Apr 2007 A1
20070094241 M. Blackwell et al. Apr 2007 A1
20070106582 Baker et al. May 2007 A1
20070112668 Celano et al. May 2007 A1
20070118410 Nadai May 2007 A1
20070130070 Williams Jun 2007 A1
20070156692 Rosewarne Jul 2007 A1
20070156718 Hossfeld et al. Jul 2007 A1
20070162414 Horowitz et al. Jul 2007 A1
20070168267 Zimmerman et al. Jul 2007 A1
20070179798 Inbarajan Aug 2007 A1
20070192121 Routson et al. Aug 2007 A1
20070192122 Routson et al. Aug 2007 A1
20070198336 Thompson Aug 2007 A1
20070198407 Winter Aug 2007 A1
20070208640 Banasiak et al. Sep 2007 A1
20070214000 Shahrabi et al. Sep 2007 A1
20070226047 Ward Sep 2007 A1
20070226093 Chan et al. Sep 2007 A1
20070226114 Haggerty et al. Sep 2007 A1
20070233591 Newton Oct 2007 A1
20070244732 Chatterji et al. Oct 2007 A1
20070250459 Schwarz et al. Oct 2007 A1
20070255654 Whipple et al. Nov 2007 A1
20070255655 Kemper et al. Nov 2007 A1
20070258626 Reiner Nov 2007 A1
20070260539 Delinsky Nov 2007 A1
20070261114 Pomerantsev Nov 2007 A1
20070262137 Brown Nov 2007 A1
20070266439 Kraft Nov 2007 A1
20070279187 Hekmatpour et al. Dec 2007 A1
20070282730 Carpenter et al. Dec 2007 A1
20070282736 Conlin et al. Dec 2007 A1
20070284433 Domenica et al. Dec 2007 A1
20070288338 Hoadley Dec 2007 A1
20070288360 Seeklus Dec 2007 A1
20070288490 Longshaw Dec 2007 A1
20070294195 Curry et al. Dec 2007 A1
20070294431 Adelman et al. Dec 2007 A1
20070299699 Policelli et al. Dec 2007 A1
20070299770 Delinsky Dec 2007 A1
20070299771 Brody Dec 2007 A1
20080010203 Grant Jan 2008 A1
20080010206 Coleman Jan 2008 A1
20080015954 Huber Jan 2008 A1
20080015979 Bentley Jan 2008 A1
20080022281 Dubhashi et al. Jan 2008 A1
20080027841 Eder Jan 2008 A1
20080027859 Nathans et al. Jan 2008 A1
20080033742 Bernasconi Feb 2008 A1
20080046351 Wiener et al. Feb 2008 A1
20080052182 Marshall Feb 2008 A1
20080052224 Parker Feb 2008 A1
20080052244 Tsuei et al. Feb 2008 A1
20080059317 Chandran Mar 2008 A1
20080059352 Chandran Mar 2008 A1
20080059364 Tidwell et al. Mar 2008 A1
20080065530 Talbert et al. Mar 2008 A1
20080086400 Ardelean et al. Apr 2008 A1
20080091519 Foss Apr 2008 A1
20080097768 Godshalk Apr 2008 A1
20080103799 Domenikos et al. May 2008 A1
20080103959 Carroll et al. May 2008 A1
20080103972 Lanc May 2008 A1
20080109315 Huang et al. May 2008 A1
20080109740 Prinsen et al. May 2008 A1
20080109875 Kraft May 2008 A1
20080115191 Kim et al. May 2008 A1
20080120133 Krishnaswami et al. May 2008 A1
20080133322 Kalia et al. Jun 2008 A1
20080140507 Hamlisch et al. Jun 2008 A1
20080162383 Kraft Jul 2008 A1
20080172324 Johnson Jul 2008 A1
20080177655 Zalik Jul 2008 A1
20080184270 Cole et al. Jul 2008 A1
20080189202 Zadoorian et al. Aug 2008 A1
20080195548 Chu et al. Aug 2008 A1
20080201257 Lewis et al. Aug 2008 A1
20080205655 Wilkins et al. Aug 2008 A1
20080205774 Brinker et al. Aug 2008 A1
20080208610 Thomas et al. Aug 2008 A1
20080208726 Tsantes et al. Aug 2008 A1
20080208873 Boehmer Aug 2008 A1
20080221972 Megdal et al. Sep 2008 A1
20080222015 Megdal et al. Sep 2008 A1
20080222027 Megdal et al. Sep 2008 A1
20080222706 Renaud et al. Sep 2008 A1
20080255922 Feldman et al. Oct 2008 A1
20080263058 Peden Oct 2008 A1
20080270209 Mauseth et al. Oct 2008 A1
20080270294 Lent et al. Oct 2008 A1
20080270295 Lent et al. Oct 2008 A1
20080288283 Baldwin, Jr. et al. Nov 2008 A1
20080294501 Rennich et al. Nov 2008 A1
20080294540 Celka et al. Nov 2008 A1
20080294996 Hunt et al. Nov 2008 A1
20080301016 Durvasula et al. Dec 2008 A1
20080306750 Wunder et al. Dec 2008 A1
20080312969 Raines et al. Dec 2008 A1
20080319832 Liebe Dec 2008 A1
20080319889 Hammad Dec 2008 A1
20080319909 Perkins et al. Dec 2008 A1
20090007231 Kaiser et al. Jan 2009 A1
20090012889 Finch Jan 2009 A1
20090018996 Hunt et al. Jan 2009 A1
20090024428 Hudock, Jr. Jan 2009 A1
20090030776 Walker et al. Jan 2009 A1
20090031426 Dal Lago et al. Jan 2009 A1
20090043691 Kasower Feb 2009 A1
20090044279 Crawford et al. Feb 2009 A1
20090055322 Bykov et al. Feb 2009 A1
20090055894 Lorsch Feb 2009 A1
20090060343 Rosea Mar 2009 A1
20090089190 Girulat, Jr. Apr 2009 A1
20090094674 Schwartz et al. Apr 2009 A1
20090099960 Robida et al. Apr 2009 A1
20090106846 Dupray et al. Apr 2009 A1
20090112650 Iwane Apr 2009 A1
20090119199 Salahi May 2009 A1
20090119299 Rhodes May 2009 A1
20090132347 Anderson et al. May 2009 A1
20090138335 Lieberman May 2009 A1
20090144160 Haggerty et al. Jun 2009 A1
20090150166 Leite et al. Jun 2009 A1
20090150238 Marsh et al. Jun 2009 A1
20090158030 Rasti Jun 2009 A1
20090164232 Chmielewski et al. Jun 2009 A1
20090164380 Brown Jun 2009 A1
20090171723 Jenkins Jul 2009 A1
20090172815 Gu et al. Jul 2009 A1
20090210886 Bhojwani et al. Aug 2009 A1
20090222308 Zoldi et al. Sep 2009 A1
20090222375 Choudhuri et al. Sep 2009 A1
20090222377 Choudhuri et al. Sep 2009 A1
20090222379 Choudhuri et al. Sep 2009 A1
20090234775 Whitney et al. Sep 2009 A1
20090240624 James et al. Sep 2009 A1
20090248573 Haggerty et al. Oct 2009 A1
20090254971 Herz et al. Oct 2009 A1
20090271248 Sherman et al. Oct 2009 A1
20090271265 Lay et al. Oct 2009 A1
20090276244 Baldwin, Jr. et al. Nov 2009 A1
20090289110 Regen et al. Nov 2009 A1
20090299911 Abrahams et al. Dec 2009 A1
20090327120 Eze et al. Dec 2009 A1
20090328173 Jakobson et al. Dec 2009 A1
20100009320 Wilkelis Jan 2010 A1
20100009663 Chang Jan 2010 A1
20100010935 Shelton Jan 2010 A1
20100011428 Atwood et al. Jan 2010 A1
20100023434 Bond Jan 2010 A1
20100023448 Eze Jan 2010 A1
20100030677 Melik-Aslanian et al. Feb 2010 A1
20100042517 Paintin et al. Feb 2010 A1
20100042583 Gervais Feb 2010 A1
20100049803 Ogilvie et al. Feb 2010 A1
20100082476 Bowman Apr 2010 A1
20100107225 Spencer et al. Apr 2010 A1
20100114724 Ghosh et al. May 2010 A1
20100114744 Gonen May 2010 A1
20100122316 Lyon May 2010 A1
20100142698 Spottiswoode et al. Jun 2010 A1
20100145836 Baker et al. Jun 2010 A1
20100174638 Debie et al. Jul 2010 A1
20100185546 Pollard Jul 2010 A1
20100188684 Kumara Jul 2010 A1
20100205087 Hubler et al. Aug 2010 A1
20100217837 Ansari et al. Aug 2010 A1
20100223168 Haggerty et al. Sep 2010 A1
20100223211 Johnson et al. Sep 2010 A1
20100228658 Ketelsen et al. Sep 2010 A1
20100250411 Ogrodski Sep 2010 A1
20100250497 Redlich et al. Sep 2010 A1
20100250509 Andersen Sep 2010 A1
20100253686 Alsbury et al. Oct 2010 A1
20100257102 Perlman Oct 2010 A1
20100262535 Lent et al. Oct 2010 A1
20100268660 Ekdahl Oct 2010 A1
20100293090 Domenikos et al. Nov 2010 A1
20100299251 Thomas Nov 2010 A1
20100299252 Thomas Nov 2010 A1
20100299260 Thomas Nov 2010 A1
20100299262 Handler Nov 2010 A1
20100324986 Thomas Dec 2010 A1
20100325035 Hilgers et al. Dec 2010 A1
20100325036 Thomas Dec 2010 A1
20110004514 Thomas Jan 2011 A1
20110004546 Thomas Jan 2011 A1
20110029427 Haggerty et al. Feb 2011 A1
20110035315 Langley Feb 2011 A1
20110040736 Kalaboukis Feb 2011 A1
20110054981 Faith et al. Mar 2011 A1
20110060654 Elliott et al. Mar 2011 A1
20110060673 Delinsky et al. Mar 2011 A1
20110078073 Annappindi et al. Mar 2011 A1
20110125632 Neel May 2011 A1
20110126275 Anderson et al. May 2011 A1
20110131123 Griffin et al. Jun 2011 A1
20110137924 Hunt et al. Jun 2011 A1
20110161218 Swift Jun 2011 A1
20110166988 Coulter Jul 2011 A1
20110173116 Yan et al. Jul 2011 A1
20110178841 Rane et al. Jul 2011 A1
20110178899 Huszar Jul 2011 A1
20110184838 Winters et al. Jul 2011 A1
20110196791 Dominguez Aug 2011 A1
20110270779 Showalter Nov 2011 A1
20110270925 Mina Nov 2011 A1
20110282779 Megdal et al. Nov 2011 A1
20110295733 Megdal et al. Dec 2011 A1
20120005070 McFall et al. Jan 2012 A1
20120023011 Hurwitz Jan 2012 A1
20120030771 Pierson et al. Feb 2012 A1
20120066065 Switzer Mar 2012 A1
20120066084 Sneyders Mar 2012 A1
20120066106 Papadimitriou Mar 2012 A1
20120072464 Cohen Mar 2012 A1
20120078932 Skurtovich, Jr. et al. Mar 2012 A1
20120101938 Kasower Apr 2012 A1
20120101939 Kasower Apr 2012 A1
20120108274 Acebo Ruiz et al. May 2012 A1
20120109990 Yamasaki May 2012 A1
20120116951 Chung et al. May 2012 A1
20120123931 Megdal et al. May 2012 A1
20120123942 Song et al. May 2012 A1
20120136763 Megdal et al. May 2012 A1
20120136774 Imrey et al. May 2012 A1
20120158574 Brunzell et al. Jun 2012 A1
20120158654 Behren et al. Jun 2012 A1
20120173406 Fei et al. Jul 2012 A1
20120173417 Lohman et al. Jul 2012 A1
20120191596 Kremen et al. Jul 2012 A1
20120198556 Patel et al. Aug 2012 A1
20120204026 Shi et al. Aug 2012 A1
20120215682 Lent et al. Aug 2012 A1
20120226916 Hahn et al. Sep 2012 A1
20120232958 Silbert Sep 2012 A1
20120239553 Gonen et al. Sep 2012 A1
20120239583 Dobrowolski Sep 2012 A1
20120246048 Cohen et al. Sep 2012 A1
20120246060 Conyack, Jr. et al. Sep 2012 A1
20120253852 Pourfallah et al. Oct 2012 A1
20120254018 Davies et al. Oct 2012 A1
20120265607 Belwadi Oct 2012 A1
20120265661 Megdal et al. Oct 2012 A1
20120271660 Harris et al. Oct 2012 A1
20120278767 Stibel et al. Nov 2012 A1
20120284118 Mamich, Jr. et al. Nov 2012 A1
20120290660 Rao et al. Nov 2012 A1
20120317016 Hughes Dec 2012 A1
20120324388 Rao et al. Dec 2012 A1
20120330689 McLaughlin et al. Dec 2012 A1
20130006825 Robida et al. Jan 2013 A1
20130007891 Mogaki Jan 2013 A1
20130018795 Kolhatkar et al. Jan 2013 A1
20130018811 Britti et al. Jan 2013 A1
20130031624 Britti et al. Jan 2013 A1
20130060603 Wagner Mar 2013 A1
20130066775 Milam Mar 2013 A1
20130103571 Chung et al. Apr 2013 A1
20130110565 Means et al. May 2013 A1
20130117087 Coppinger May 2013 A1
20130124263 Amaro et al. May 2013 A1
20130173449 Ng et al. Jul 2013 A1
20130173451 Kornegay et al. Jul 2013 A1
20130173481 Hirtenstein et al. Jul 2013 A1
20130185293 Boback Jul 2013 A1
20130191261 Chandler et al. Jul 2013 A1
20130205135 Lutz Aug 2013 A1
20130211986 Debie et al. Aug 2013 A1
20130268357 Heath Oct 2013 A1
20130317954 Psota et al. Nov 2013 A1
20130332338 Yan et al. Dec 2013 A1
20130332341 Papadimitriou Dec 2013 A1
20130332342 Kasower Dec 2013 A1
20130332467 Bornea et al. Dec 2013 A1
20130339249 Weller et al. Dec 2013 A1
20140012734 Megdal et al. Jan 2014 A1
20140019333 Morris et al. Jan 2014 A1
20140032265 Paprocki et al. Jan 2014 A1
20140032300 Zhang et al. Jan 2014 A1
20140032723 Nema Jan 2014 A1
20140061302 Hammad Mar 2014 A1
20140081835 Choudhuri et al. Mar 2014 A1
20140089167 Kasower Mar 2014 A1
20140110477 Hammad Apr 2014 A1
20140136422 Jung et al. May 2014 A1
20140156500 Lassen et al. Jun 2014 A1
20140156501 Howe Jun 2014 A1
20140156503 Lassen et al. Jun 2014 A1
20140157375 Britti et al. Jun 2014 A1
20140258083 Achanta et al. Sep 2014 A1
20140258089 Pearson et al. Sep 2014 A1
20140279329 Dancel Sep 2014 A1
20140279382 Drakeley et al. Sep 2014 A1
20140372367 McLean et al. Dec 2014 A1
20150026014 Kasower Jan 2015 A1
20150073929 Psota et al. Mar 2015 A1
20150112874 Serio et al. Apr 2015 A1
20150161738 Stempora Jun 2015 A1
20150186529 Rope Jul 2015 A1
20150199757 Lindholme et al. Jul 2015 A1
20150200948 Cairns et al. Jul 2015 A1
20150228016 Chandler Aug 2015 A1
20150254329 Agarwal et al. Sep 2015 A1
20150269506 Britti et al. Sep 2015 A1
20150278944 Searson et al. Oct 2015 A1
20150287091 Koran Oct 2015 A1
20150295906 Ufford et al. Oct 2015 A1
20150310543 DeBie Oct 2015 A1
20150339769 deOliveira et al. Nov 2015 A1
20160055487 Votaw et al. Feb 2016 A1
20160071175 Reuss et al. Mar 2016 A1
20160092997 Shen et al. Mar 2016 A1
20160125412 Cannon May 2016 A1
20160224996 Hunt et al. Aug 2016 A1
20170041296 Ford et al. Feb 2017 A1
20170046526 Chan et al. Feb 2017 A1
20170046652 Haldenby et al. Feb 2017 A1
20170046664 Haldenby et al. Feb 2017 A1
20170046693 Haldenby et al. Feb 2017 A1
20170048021 Yanovsky et al. Feb 2017 A1
20170061138 Lambert Mar 2017 A1
20170109735 Sheng et al. Apr 2017 A1
20170161486 Jeon et al. Jun 2017 A1
20170200223 Kasower Jul 2017 A1
20170228820 Rohn Aug 2017 A1
20170249481 Edison Aug 2017 A1
20170262758 Boyapalle et al. Sep 2017 A1
20170278182 Kasower Sep 2017 A1
20170323063 Krause et al. Nov 2017 A1
20170323358 Psota et al. Nov 2017 A1
20170352014 Smith et al. Dec 2017 A1
20180040063 Buechler et al. Feb 2018 A1
20180060596 Hamel et al. Mar 2018 A1
20180060600 Hamel et al. Mar 2018 A1
20180062835 Hamel et al. Mar 2018 A1
20180075527 Nagla et al. Mar 2018 A1
20180082371 Chandler Mar 2018 A1
20180176267 Malatesha et al. Jun 2018 A1
20180183768 Lobban et al. Jun 2018 A1
20180204279 Painter et al. Jul 2018 A1
20180205707 Bellala et al. Jul 2018 A1
20180218069 Rege et al. Aug 2018 A1
20180218448 Thomas et al. Aug 2018 A1
20180239914 Chen et al. Aug 2018 A1
20180253702 Dowding Sep 2018 A1
20180276661 van Wingerden Sep 2018 A1
20180285886 Yan et al. Oct 2018 A1
20180302215 Salgueiro et al. Oct 2018 A1
20180309567 Wooden Oct 2018 A1
20190019185 Chitalia et al. Jan 2019 A1
20190034625 Ford et al. Jan 2019 A1
20190066203 Smith et al. Feb 2019 A1
20190102832 Robida et al. Apr 2019 A1
20190156227 Duke et al. May 2019 A1
20190188717 Putnam et al. Jun 2019 A1
20190251558 Liu et al. Aug 2019 A1
20190318122 Hockey et al. Oct 2019 A1
20190347627 Lin et al. Nov 2019 A1
20200034927 Smith et al. Jan 2020 A1
20200074099 Felice-Steele et al. Mar 2020 A1
20200074100 Raneri et al. Mar 2020 A1
20200074541 Finneran et al. Mar 2020 A1
20200074542 Manna et al. Mar 2020 A1
20200076813 Felice-Steele et al. Mar 2020 A1
20200106764 Hockey et al. Apr 2020 A1
20200106765 Hockey et al. Apr 2020 A1
20200143363 Schmidt May 2020 A1
20200153627 Wentz May 2020 A1
20200201878 Putnam et al. Jun 2020 A1
20200202425 Taylor-Shoff et al. Jun 2020 A1
20200211099 Smith et al. Jul 2020 A1
20200211103 Searson et al. Jul 2020 A1
20200213206 Bracken et al. Jul 2020 A1
20200219181 Kasower Jul 2020 A1
20200226284 Yin Jul 2020 A1
20200233850 Girulat, Jr. Jul 2020 A1
20200327610 Rohn et al. Oct 2020 A1
20200349639 Mousseau Nov 2020 A1
20200372506 Billman et al. Nov 2020 A1
20200389461 Felice-Steele et al. Dec 2020 A1
20210065160 Butvin et al. Mar 2021 A1
20210194885 Manna Jun 2021 A1
20220051315 Robida et al. Feb 2022 A1
20220138238 Rege et al. May 2022 A1
20220217146 Felice-Steele et al. Jul 2022 A1
Foreign Referenced Citations (74)
Number Date Country
3 060 136 May 2020 CA
1290373 Apr 2001 CN
101452555 Jun 2009 CN
102096886 Jun 2011 CN
102663650 Sep 2012 CN
0 350 907 Jan 1990 EP
0 468 440 Jan 1992 EP
0 554 083 Aug 1993 EP
0 566 736 Aug 1993 EP
0 869 652 Oct 1998 EP
0 913 789 May 1999 EP
0 919 942 Jun 1999 EP
1 028 401 Aug 2000 EP
1 550 960 Jul 2005 EP
1 988 501 Nov 2008 EP
1 322 809 Jul 1973 GB
2001-282957 Oct 2001 JP
2002-163449 Jun 2002 JP
2003-016261 Jan 2003 JP
2003-316950 Nov 2003 JP
10-2004-0078798 Sep 2004 KR
10-0638324 Oct 2006 KR
10-2013-0107394 Oct 2013 KR
2 181 216 Apr 2002 RU
I256569 Jun 2006 TW
WO 94012943 Jun 1994 WO
WO 95012857 May 1995 WO
WO 97022073 Jun 1997 WO
WO 99046710 Sep 1999 WO
WO 00011574 Mar 2000 WO
WO 00052616 Sep 2000 WO
WO 00055778 Sep 2000 WO
WO 00065469 Nov 2000 WO
WO 01004821 Jan 2001 WO
WO 01016896 Mar 2001 WO
WO 01039090 May 2001 WO
WO 01039589 Jun 2001 WO
WO 01041083 Jun 2001 WO
WO 01041355 Jun 2001 WO
WO 01045012 Jun 2001 WO
WO 01057720 Aug 2001 WO
WO 01080053 Oct 2001 WO
WO 01084281 Nov 2001 WO
WO 02013047 Feb 2002 WO
WO 02071176 Sep 2002 WO
WO 2004114160 Dec 2004 WO
WO 2005022348 Mar 2005 WO
WO 2005029369 Mar 2005 WO
WO 2005107405 Nov 2005 WO
WO 2005124619 Dec 2005 WO
WO 2006099081 Sep 2006 WO
WO 2006099492 Sep 2006 WO
WO 2006135451 Dec 2006 WO
WO 2007004158 Jan 2007 WO
WO 2007106393 Sep 2007 WO
WO 2007106786 Sep 2007 WO
WO 2007106787 Sep 2007 WO
WO 2008021061 Feb 2008 WO
WO 2008022289 Feb 2008 WO
WO 2008147918 Dec 2008 WO
WO 2009061342 May 2009 WO
WO 2009064840 May 2009 WO
WO 2009099448 Aug 2009 WO
WO 2009117468 Sep 2009 WO
WO 2010129257 Nov 2010 WO
WO 2013009920 Jan 2013 WO
WO 2013066633 May 2013 WO
WO 2014088895 Jun 2014 WO
WO 2014137759 Sep 2014 WO
WO 2016070096 May 2016 WO
WO 2018144612 Aug 2018 WO
WO 2019103979 May 2019 WO
WO 2020051154 Mar 2020 WO
WO 2020146667 Jul 2020 WO
Non-Patent Literature Citations (333)
Entry
Menge,Falko. “Enterprise Service Bus”. Retrieved on Sep. 23, 2022 from <httos://odfs.semanticscholar.org/7539/3c46ab62d8c25d13f79d68ef42e232474b53pdf> (Year: 2007).
U.S. Appl. No. 12/705,489, filed Feb. 12, 2010, Bargoli et al.
U.S. Appl. No. 12/705,511, filed Feb. 12, 2010, Bargoli et al.
“A New Approach to Fraud Solutions”, BasePoint Science Solving Fraud, pp. 8, 2006.
Abrahams, Steven W., “The New View in Mortgage Prepayments: Insight from Analysis at the Loan-By-Loan Level,” The Journal of Fixed Income, Jun. 1997, vol. 7, No. 1, pp. 8-21.
“ACS Company Birch & Davis Wins Texas CHIP Contract,” PR Newswire, Section: Financial News, May 17, 2000, Dallas, TX, pp. 3.
Aharony et al., “Social Area Networks: Data Networking of the People, by the People, for the People,” 2009 International Conference on Computational Science and Engineering, May 2009, pp. 1148-1155.
“An Even Better Solution to Financing Elective Surgery . . . ”, Unicorn Financial, pp. 7, http://web.archive.org/web/20000816161359/http://www.unicornfinancial.com/, as downloaded Oct. 15, 2008.
Apte, et al., “A Probabilistic Estimation Framework for Predictive Modeling Analytics,” IBM Systems Journal, 2002, vol. 41, No. 3, pp. 438-448.
“Authorizing Safety Net Public Health Programs,” Hearing before the Subcommittee on Health of the Committee on Energy and Commerce, House of Representatives, One Hundred Seventh Congress, First Session, Serial No. 107-57, dated Aug. 1, 2001, 226 pgs.
AISG's National Underwriting Database, A-PLUS, is Now the Largest in the Industry, Business Wire, Aug. 7, 1997.
Agarwal et al., “Determinants of Credit Card Delinquency and Bankruptcy: Macroeconomic Factors”, Journal of Economics and Finance, 2003, vol. 27, pp. 75-84 (12 pages).
An Expert System for Determining Medicaid Eligibility, Journal of Medical Systems, vol. 12, Nov. 5, 1988, in 10 pages.
Announcing TrueProfiler, http://web.archive.org/web/20021201123646/http://www.truecredit.com/index.asp, dated Dec. 1, 2002, 2 pages.
Anonymous, “Credit-Report Disputes Await Electronic Resolution,” Credit Card News, Chicago, Jan. 15, 1993, vol. 5, No. 19, p. 5.
Anonymous, “MBNA Offers Resolution of Credit Card Disputes,” Hempstead, Feb. 2002, vol. 68, No. 2, p. 47.
Antonopoulos, Andreas M., “Mastering Bitcoin: Unlocking Digital Crypto-Currencies”, O'Reilly, Dec. 2014, First Edition, pp. 282.
“AT&T Expected to Turn Up Heat in Card Wars”, American Banker, May 27, 1993, vol. 158, No. 101, pp. 3.
Avery et al., “Consumer Credit Scoring: Do Situational Circumstances Matter?”, Journal of Banking & Finance, vol. 28, 2004, pp. 835-856.
Awoonor-Williams, Princess Josephine, Ph.D. “Gender and Credit: An Analysis of Women's Experience in the Credit Market”, ProQuest Dissertations and Theses, May 2004, pp. 148.
“Balance Transfers Offer Opportunities”, Risk Credit Risk Management Report, Jan. 29, 1996, vol. 6, No. 2, pp. 2.
Bancroft, John, “Tools Help Managers with Risk Management,” Real Estate Finance Today, May 26, 1997, pp. 11-12.
“Bank of America Direct Web-Based Network Adds Core Functionality to Meet Day-To-Day Treasury Needs”, Business Wire, Oct. 25, 1999. pp. 2.
Barone, Robert P., “The Integrated Approach to Branch Service Delivery,” American Banker, Aug. 6, 1991, http://www.highbeam.com/doc/1G1-11128400.html.
Barry, Ellen, “Life, Liberty, and the Pursuit of Lipo,” The Boston Phoenix, News & Opinion, dated Apr. 6, 1998, as downloaded at http://weeklywire.com/ww/04-06-98/boston_feature_1.html (1 of 12) [Oct. 15, 2008 2:35:25 PM].
Belford, Terrence, “Technology Quarterly: Computers, Internet Speeds Credit Checks System Tailored for Doctors, Dentists,” The Globe and Mail (Canada), Section: Report on Business Special Reports, p. C10, Mar. 18, 1997.
“Beverly Hills Man Convicted of Operating ‘Bust-Out’ Schemes that Caused More than $8 Million in Losses”, Department of Justice, Jul. 25, 2006, 2 Pgs.
Bienkowski, Nik, “A New Tool for Portfolio Risk Management—Gold Bullion”, Apr. 2003, pp. 6.
Bilotta, Caryn, “Understanding Credit Scores,” Pittsburgh Post-Gazette, May 9, 2010.
“Birch & Davis Wins Texas CHIP Contract,” Birch & Davis Press Release, dated Jan. 4, 2000, 3 pgs., as downloaded from http://web.archive.org/web/20010304065515/www.birchdavis.com/txchip.htm (1 of 3) [Oct. 20, 2008 9:49:18 AM].
Boss, Shira J. “Elective Surgery Without the Plastic: Low-Interest Medical Financing Provides Alternative to Credit Cards,” factiva, Grain's New York Business, 2 pgs., dated Jun. 22, 1998.
Broward County CAP Grant Application, as printed on Aug. 10, 2009, 41 pgs.
Brown et al., “ALCOD IDSS: Assisting the Australian Stock Market Surveillance Team's Review Process,” Applied Artificial Intelligence Journal, Dec. 1, 1996, pp. 625-641.
Burr Ph.D., et al., “Utility Payments as Alternative Credit Data: A Reality Check”, Asset Builders of America, Inc., Oct. 5, 2006, pp. 1-18, Washington, D.C.
“Bust-Out Schemes”, Visual Analytics Inc. Technical Product Support, Newsletter vol. 4, Issue 1, Jan. 2005, pp. 7.
Calnan, Christopher, “Tenet, Fair Isaac invest $20M in startup,” MHT, Mass High Tech: The Journal of New England Technology, dated Jul. 23, 2007, 2 pgs.
Cantor, R. and Packer, F., “The Credit Rating Industry,” FRBNY Quarterly Review, Summer-Fall, 1994, pp. 1-24.
Capps et al., “Recent Changes in Texas Welfare and Work, Child Care and Child Welfare Systems,” Assessing the New Federalism, The Urban Institute, State Update No. 1, 24 pgs., Jun. 2001.
CAPStone Newsletter, Sep. 2001, 8 pgs., as downloaded from http://web.archive.org/web/20011213115738/www.capcommunity.hrsa.gov/Newsletter/Newsletter12.htm (1 of 8) [Oct. 18, 2008 2:39:47 PM].
Card Marketing, Use the Latest CRM Tools and Techniques, www.CardForum.com, vol. 5 No. 10, Dec. 2001.
“Chase Gets Positive,” Bank Technology News, May 6, 2000, vol. 14, No. 5, p. 33.
Chatterjee et al., “Expenditure Patterns and Aggregate Consumer Behavior, Some Experiments with Australian and New Zealand Data”, The Economic Record, vol. 70, No. 210, Sep. 1994, pp. 278-291.
Cheney, Karen, “Fix Your Nose, If You Wish, But Not With This New Loan,” Money Magazine, vol. 27, No. 5, 1 pg., dated May 1, 1998.
Chores & Allowances, “Do Kids Have Credit Reports?” Oct. 15, 2007, http://choresandallowances.blogspot.com/2007/10/do-kids-have-credit-reports.html, pp. 5.
Cisco: What-If Simulator, http://www.ciscocredit.com/whatifsim.html printed Oct. 12, 2012 in 2 pages.
Cisco: Your Mortgage Credit Reporting Specialists, http://www.ciscocredit.com/cc_Services.html printed Oct. 12, 2012 in 4 pages.
“Cole Taylor Bank Chooses Integrated E-Banking/E-Payments/Reconciliation Solution From Fundtech”, Business Wire, Oct. 21, 1999, pp. 2.
“Consumer Reports Finds American-Made Vehicles Close Reliability Gap with European-Made Vehicle—As Japanese Continue to Set New Benchmarks for the Industry”, Consumer Reports: Consumers Union, Yonkers, NY, Apr. 2003, pp. 2.
CreditAnalyst, Digital Matrix Systems, as printed out Mar. 4, 2008, pp. 2.
CreditSesame; “FAQ's”; http://www.creditsesame.com/how-we-help/faqs/#cb printed Dec. 5, 2011 in 8 pages.
CreditSesame; “Promote Your Financial Responsibility to Get an Edge in Life”; http://www.creditsesame.com/credit-badge/ printed Dec. 2, 2011 in 1 page.
CreditToolkit, Digital Matrix Systems, as printed out Mar. 4, 2008, pp. 2.
CreditXpert, http://www.creditxpert.com/Products/individuals.asp printed Oct. 12, 2012 in 1 page.
“Credit Information Bureaus and ‘CIBIL’”, http://www.icicibank.com/cibil.html printed Aug. 22, 2012 in 3 pages.
CreditKarma: How Credit Karma Works, http://www.creditkarma.com/help/howitworks printed Oct. 12, 2012 in 2 pages.
Credit Source Online: The Secrets of Raising Your Credit Score, http://www.creditsourceonline.com/secrets-of-raising-your-credit-score.html printed Oct. 12, 2012 in 4 pages.
ComScore Networks Launches Business Unit to Help Credit Card Marketers Master Online and Multi-Channel Strategies—Solutions Provide Unprecedented Insight Into Customer Acquisition and Usage Opportunities, Reston, VA, Oct. 11, 2001, 2 pages.
“Consumers Gain Immediate and Full Access to Credit Score Used by Majority of U.S. Lenders”, PR Newswire, ProQuest Copy, Mar. 19, 2001, p. 1.
Credit Card Management, “Neural Nets Shoot for Jackpot,” Dec. 1995, pp. 1-6.
“CreditCheck Monitoring Services,” Dec. 11, 2000, pp. 1, lines 21-23.
Credit Risk Management Report, Potomac, Mar. 9, 1998, vol. 8, No. 4.
CreditXpert Inc., CreditXpert 3-Bureau Comparison™, 2002, pp. 5, as archived Jun. 8, 2003 from http://web.archive.org/web/20030608171018/http://creditxpert.com/CreditXpert%203-Bureau%20Comparison(TM)%20sample.pdf.
CreditXpert Inc., CreditXpert Credit Score & Analysis™, Jan. 11, 2000, pp. 6, http://web.archive.org/web/20030611070058/http://www.creditxpert.com/CreditXpert%20Score%20&%20Analysis%20and%20Credit%20Wizard%20sample.pdf.
CreditXpert Inc., CreditXpert Essentials™, Advisor View—Experian on Jul. 7, 2003, http://www.creditxpert.com/cx_ess_app.pdf.
CreditXpert Inc., CreditXpert Essentials™, Advisor View—TransUnion on Oct. 10, 1999, pp. 6, http://web.archive.org/web/20041211052543/http://creditxpert.com/cx_ess_app.pdf.
CreditXpert Inc., CreditXpert Essentials™, Applicant View—TransUnion on Oct. 10, 1999, pp. 6, http://www.creditxpert.com/cx_ess_app.pdf.
CreditXpert Inc., CreditXpert What-If Simulator™, 2002, pp. 8, as archived Jun. 30, 2003 from http://web.archive.org/web/20030630132914/http://creditxpert.com/CreditXpert%20What-If%20Simulator(TM)%20sample.pdf.
Credit Scoring Systems Used to Measure Bankruptcy Risk. (1991). Credit Risk Management Report, 1(2), N/A. Retrieved from https://dialog.proquest.com/professional/docview/1078503725?accountid= 131444, pp. 7.
“D&B Corporate Family Linkage”, D&B Internet Access for U.S. Contract Customers, https://www.dnb.com/ecomp/help/linkage.htm as printed Dec. 17, 2009, pp. 1.
Dash, Julekha, “Java on the Street,” Software Magazine, Oct. 1, 1997, vol. 17, No. 11, p. 2.
Dataman Group, “Summarized Credit Statistics,” Aug. 22, 2001, http://web.archive.org/web/20010822113446/http://www.datamangroup.com/summarized_credit.asp.
“Data Loss Prevention (DLP) Software”, http://www.symantec.com/data-loss-prevention/ printed Apr. 8, 2013 in 8 pages.
“Data Protection”, http://compliantprocessing.com/data-protection/ printed Apr. 8, 2013 in 4 pages.
David, Alexander, “Controlling Information Premia by Repackaging Asset-Backed Securities,” The Journal of Risk and Insurance, Dec. 1997, 26 pages.
Davis, Lisa, “Safety in Numbers,” Business North Carolina, Sep. 1, 1995, vol. 15, No. 9, p. 24.
“Debt Settlement: Watch Video on how to Pay Your Debt Faster”, http://www.debtconsolidationcare.com/debt-settlement.html printed Jan. 9, 2013 in 6 pages.
Demby, Elayne, “Special Report: Letting Consumers Know the Score—and More”, Collections and Credit Risk, New York, Feb. 2003, vol. 8, Issue 2, p. 53, pp. 3.
DentalFinancing.com, “Financial services for patients and dental professionals,”, 7 pgs., as downloaded from http://web.archive.org/web/20010607151954/www.dentalfinancing.com/dentist/index.asp (1 of 2) [Oct. 15, 2008 3:55:16 PM].
Department of Real Estate, http://web.archive.org/web/20040619190012/http://www.dre.ca.gov/pubs_sub.htm, Jun. 19, 2004, in 5 pages.
Department of Real Estate, “Reference Book,” http://web.archive.org/web/20041011063158/http://www.dre.ca.gov/pdf_docs/ref17.pdf, Jun. 18, 2004, Chapter 17, pp. 311-382.
DiBartolomeo, Dan, “Portfolio Optimization: The Robust Solution,” Prudential Securities Quantitative Conference, Dec. 21, 1993, pp. 8.
Dietz, Ellen, “Dental Office Management,” 8 pgs., pp. 316-321, Jul. 16, 1999.
Dillon et al., “Good Science”, Marketing Research: A Magazine of Management & Applications TM, Winter 1997, vol. 9, No. 4; pp. 11.
Downes et al., Dictionary of Finance and Investment Terms, Fifth Edition, Nov. 1, 1998, pp. 332-333.
Downing, Jr.; Richard, “Changes to the Credit Reporting Act,” Mortgage Banking, Apr. 1, 1998, vol. 58, No. 7, pp. 82-85.
Dymi, Amilda, Need for Leads Spurs Some Upgrades, Origination News-Special Report, May 1, 2008, Vol. vol. 17, Issue No. 8, Pages p. 24, Atlanta, Copyright 2008 SourceMedia, Inc.
Ecredable: Discover your AMP Credit Rating™, http://www.ecredable.com/how-it-works/amp-credit-rating printed Oct. 12, 2012 in 2 pages.
EFunds Introduces QualiFileSM, Deluxe Corporation, eFunds Press Release and Product Launch, Sep. 23, 1999, Milwaukee, WI.
Electronic Privacy Information Center, “The Fair Credit Reporting Act” 15 USC 1681 (1992), 10 pgs., as downloaded from http://epic.org/privacy/financial/fcra.html on Mar. 19, 2008.
Ellwood, Marilyn, “The Medicaid Eligibility Maze: Coverage Expands, but Enrollment Problems Persist, Findings from a Five-State Study,” Mathematica Policy Research, Inc., Occasional Paper No. 30, 56 pgs., Dec. 1999.
Equifax: Consumer Bureau, http://www.equifax.co.in/financial-services/consumer_bureau/en_in#RiskScore printed Oct. 12, 2012 in 3 pages.
Equifax Consumer Credit Report http://www.equifax.com/home/, as retrieved on Sep. 17, 2008.
Ettorre, “Paul Kahn on Exceptional Marketing,” Management Review, vol. 83, No. 11, Nov. 1994, pp. 48-51.
“Equifax and FICO Serve Consumers”, Mortgage Servicing News, Mar. 2001, vol. 5, No. 3, p. 19.
Expensr.com http://www.expensr.com/, as retrieved on Sep. 17, 2008.
Experian, http://www.experian.com/printed Oct. 12, 2012 in 1 page.
Experian Announces PLUS Score; Experian Press Release dated Oct. 16, 2003; Experian Global Press Office.
Experian Consumer Credit Report http://www.experian.com/, as retrieved on Sep. 17, 2008.
“Experian Launches Portfolio Monitor—Owner NoticesSM”, News Release, Feb. 2003, Costa Mesa, CA.
Experian-Scorex Announces New Credit Simulation Tool, PR Newswire, Costa Mesa, CA, Jun. 13, 2005.
Experian, Custom Strategist and Qualifile from Funds, Jun. 2000, in 2 pages.
Experian, “Enabling e-business”, White Paper, Jan. 2001, pp. 21.
Experian Information Solutions, Inc., Credit Trends: Access Credit Trending Information Instantly, http://kewaneecreditbureau.com/Credit.Trends.pdf, Aug. 2000, pp. 4.
Experian, “Instant Prescreen: Offer preapproved credit at the point of sale”, Oct. 2000, pp. 2, http://www.cdillinois.com/pdf_file/instant_prescreen_ps.pdf.
Experian, “Experian Rental Payment Data,” http://www.experian.com/rentbureau/rental-data.html printed Nov. 22, 2013 in 2 pages.
Fair Isaac Announces Integrated, End-to-End Collection and Recovery Solution, Business Wire, New York, Sep. 2, 2004, p. 1.
Fair Isaac Corporation, myFICO: Calculators: Credit Assessment, as printed Jun. 8, 2005 in 2 pages, http://www.myfico.com/CreditEducation/Calculators/CreditAssessment.aspx.
Fair Isaac Corporation, myFICO: Help: FICO Score Simulator, as printed Jun. 8, 2005 in 2 pages, http://www.myfico.com/Help/Simulator.aspx?fire=5.
Fair Isaac Corporation, myFICO: Products: Suze Orman's FICO Kit Platinum, as printed Jun. 8, 2005 in 4 pages, http://www.myfico.com/Products/FICOKit/Description.aspx.
Fair Isaac Corporation, myFICO: Products: Suze Orman's FICO® Kit Platinum: FICO Score Check, as printed Jun. 7, 2005 in 1 page, http://www.myfico.com/Products/FICOKit/Sample03.html.
Fair Isaac Corporation, myFICO: Products: Suze Orman's FICO®. Kit Platinum: Look for Errors, as printed Jun. 7, 2005 in 3 pages http://www.myfico.com/Products/FICOKit/Sample02.html.
Fair Isaac Corporation, myFICO: Products: Suze Orman's FICO® Kit Platinum: Your FICO Score, as printed Jun. 7, 2005 in 1 page, http://www.mvfico.com/Products/FICOKit/Sample01.html.
Fair Isaac Corporation, myFICO: Sample: FICO Score Simulator, as printed Jun. 8, 2005 in 5 pages, http://www.rnyfico.com/Content/Samples/Sample_ScoreSimulator.asp.
Fair Isaac Corporation, myFICO: Sample: FICO Score Simulator: Max Out All Your Credit Cards, as printed Jun. 8, 2005 in 2 pages, http://www.myfico.com/Content/Samples/Sample_ScoreSimulatorResults. asp?Simulation=4&ReportID=1&productID=&Execute.x=105&Execute.y=23.
Fair Isaac Corporation, myFICO: Sample: FICO Score Simulator: Miss Payments on All Accounts With a Payment Due, as printed Jun. 8, 2005 in 2 pages, http://www.myfico.com/Content/Samples/Sample_ScoreSimulatorResults.asp?miss_payment=radiobutton&Simulation=2&ReportID=1&ProductID=&Execute.x81&Execute.y=28>.
Fair Isaac Corporation, myFICO: Sample: FICO Score Simulator: Pay Down Delinquent Balances First, as printed Jun. 8, 2005 in 2 pages, http://www.myfico.com/Content/Samples/Sample_ScoreSimulatorResults.asp?textfieldCC=750&Simulation=7&ReportID=1&ProductID=&PayDelinquent.x=78&PayDelinquent.y=30.
Fair Isaac Corporation, myFICO: Sample: FICO Score Simulator: Pay Down the Balances on All Your Credit Cards, as printed Jun. 8, 2005 in 2 pages, http://www.myfico.com/Content/Samples/Sample_ScoreSimulatorResults.asp?textfieldCC1=750&SelectMonths=1&PayOption=radiobutton&textfieldCC=750&Simulation=3&ReportID=1&ProductID=&Execute.x=57&Execute.y=22.
Fair Isaac Corporation, myFICO: Sample: FICO Score Simulator: Pay Your Bills on Time, as printed Jun. 8, 2005 in 2 pages, http://www.myfico.com/Content/Samples/Sample_ScoreSimulatorResults.asp?select1=1&Simulation=1&ReportID=1&ProductID=&PayBillsOnTime.x=93&PayBillsOnTime.y=23.
Fair Isaac Corporation, myFICO: Sample: FICO Score Simulator: Seek New Credit, as printed Jun. 8, 2005 in 2 pages, http://www.myfico.com/Content/Samples/Sample_ScoreSimulatorResults.asp?new_credit=radiobutton&textfield5A=3000&tectfield5B=&textfield5C=&Simulation=5&ReportID=1&ProductID=&NewCredit.x=62&NewCredit.y=20.
Fair Isaac Corporation, myFICO: Sample: FICO Score Simulator: Suggested Best Action, as printed Jun. 8, 2005 in 2 pages, http://www.myfico.com/Content/Samples/Sample_ScoreSimulatorResults.asp?Simulation=111&ReportID=1&ProductID=&TopAction.x=66&TopAction.y=16.
Fair Isaac Corporation, myFICO: Sample: FICO Score Simulator: Transfer Credit Card Balances, as printed Jun. 8, 2005 in 2 pages, http://www.myfico.com/Content/Samples/Sample_ScoreSimulatorResults.asp?textfield222=5000&Simulation=6&ReportID=1&ProductID=&TransferBalance.x=86&TransferBalance.y=24.
FamilySecure.com; “Identity Theft Protection for the Whole Family | FamilySecure.com” http://www.familysecure.com/, as retrieved on Nov. 5, 2009.
Fan et al., “Design of Customer Credit Evaluation System for E-Business”, 2004 IEEE International Conference on Systems, Man and Cybernetics, 2004, pp. 392-397.
Felsenthal, Edward, “Health Costs; Managed Care Helps Curb Costs, Study Says,” The Wall Street Journal, dated Aug. 12, 1991.
Fickenscher, Lisa, “Merchant American Express Seeks to Mine its Data on Cardholder Spending Patterns,” American Banker, vol. 162, Issue 56, Mar. 24, 1997, pp. 1-2.
“Fictitious Business Name Records”, Westlaw Database Directory, http://directory.westlaw.com/scope/default.asp?db=FBN-ALL&RS-W...&VR=2.0 as printed Dec. 17, 2009, pp. 5.
“Fighting the New Face of Fraud”, FinanceTech, http://www.financetech.com/showArticle.jhtml?articleID=167100405, Aug. 2, 2005.
“Financing Medical Procedures A Lucrative But Risky Business,” Credit Risk Management Report, vol. 10, Issue 15, 2 pgs., dated Aug. 7, 2000.
Financial Engines, http://corp.financialengines.com/ printed Oct. 12, 2012 in 1 page.
Fisher, Joseph, “Access to Fair Credit Reports: Current Practices and Proposed Legislation,” American Business Law Journal, Fall 1981, vol. 19, No. 3, p. 319.
Forrest, David, “Achieving Perfect Credit—Lesson 3: Assessing Your Situation,” https://web.archive.org/web/20140828173720/http://www.fool.com/seminars/ev/index.htm?sid=0029&lid=300, as archived Aug. 28, 2014, copyright 1995-2002, in 7 pages.
Frank, John, “Scoring Takes on a New Meaning,” Credit Card Management, Sep. 1996, vol. 9, No. 6, pp. 155-159.
“Fraud Alert | Learn How”. Fight Identity Theft, http://www.fightidentitytheft.com/flag.html, accessed on Nov. 5, 2009.
“FTC Testifies: Identity Theft on the Rise”, FTC News Release, Mar. 7, 2000, pp. 3.
“Fund Manager,” Portfolio Management Software website, indexed into Google on Jan. 7, 2005, Retrieved Oct. 24, 2014 http://www.fundmanagersoftware.com/, http://www.fundmanagersoftware.com/help/gph_tp_pieasset.html, http://www.fundmanagersoftware.com/demo2.html.
GAO-03-661, Best Practices: Improved Knowledge of DOD Service Contracts Could Reveal Significant Savings, GAO, Jun. 2003.
Gibbs, Adrienne; “Protecting Your Children from Identity Theft,” Nov. 25, 2008, http://www.creditcards.com/credit-card-news/identity-ID-theft-and-kids-children-1282.php, pp. 4.
Gilje, Shelby, “Credit Agency Moving Into Health Care,” NewsRoom, The Seattle Times, Section: SCENE, Mar. 22, 1995, pp. 3, http://web2.westlaw.com/result/documenttext.aspx?rs=WLW8.03&ss+CNT&rp=%2fWelc . . . .
Gilje, Shelby, “Keeping Tabs on Businesses That Keep Tabs on Us”, NewsRoom, The Seattle Times, Section: SCENE, Apr. 19, 1995, pp. 4.
Gionis et al., “Similarity Search in High Dimensions via Hashing”, Sep. 7, 1999, pp. 518-529.
Giudici, Paolo, “Bayesian Data Mining, with Application to Benchmarking and Credit Scoring,” Applied Stochastic Models in Business and Industry, 2001, vol. 17, pp. 69-81.
“GLBA Compliance and FFIEC Compliance” http://www.trustwave.com/financial-services.php printed Apr. 8, 2013 in 1 page.
Goldstein, Jacob, “The Newest Vital Sign: Your Credit Score,” The Wall Street Journal, Health Blog, as viewed at http://blogs.wsj.com/health/2008/03/18/the-newest-vital-sign-your-cr, Mar. 18, 2008, pp. 3.
Gopalan, R., “Panning for Sales-Force Gold”, Intelligent Enterprise, Dec. 21, 1999, vol. 2, No. 18, pp. 39-43.
“Green Tree Investors May Go to Court,” Mar. 4, 1998, http://web.archive.org/web/20001101080021/http://www.channel4000.com/news/stories/news-980304-120038.html.
“Groups Demand Government Action on Online Marketing to Children,” American Marketplace, Apr. 4, 1996, vol. 17, No. 7, p. 53.
Gualtieri et al., “The Forrester Wave™: Big Data Streaming Analytics, Q1 2016”, Forrester®, Mar. 30, 2016, pp. 14, https://www.sas.com/content/dam/SAS/en_us/doc/analystreport/forrester-big-data-streaming-analytics-108218.pdf.
Healy, Thomas J., “The New Science of Borrower Behavior,” Mortgage Banking, vol. 58, No. 5, pp. 26-35, Feb. 1, 1998.
Henry, M.D., Kimberly A., “The Face-Lift Sourcebook,” Oct. 11, 2000, 3 pgs. (p. 207).
Herron, Janna, “Social Media-Based Credit Score?”, http://www.bankrate.com/financing/credit-cards/social-media-based-credit-score/, posted Friday, Jan. 13, 2012, printed Nov. 22, 2013 in 2 pages.
Hill, Kerry, “Identity Theft Your Social Security Number Provides Avenue for Thieves”, NewsRoom, Wisconsin State Journal, Sep. 13, 1998, pp. 4.
ID Analytics, “ID Analytics® Consumer Notification Service” printed Apr. 16, 2013 in 2 pages.
ID Theft Assist, “Do You Know Where Your Child's Credit Is?”, Nov. 26, 2007, http://www.idtheftassist.com/pages/story14, pp. 3.
Ideon, Credit-Card Registry that Bellyflopped this Year, Is Drawing some Bottom-Fishers, The Wall Street Journal, Aug. 21, 1995, pp. C2.
“Impac Funding Introduces Enhanced Website for Static Pool Tracking of MBS Transactions,” Waltham, MA; Webpage printed out from http://www.lewtan.com/press/1208044_Impac-Lewtan.htm on Mar. 20, 2008.
“Improving the Implementation of State Children's Health Insurance Programs for Adolescents Report of an Invitational Conference Sponsored by the American Academy of Pediatrics, Section on Adolescent Health,” Pediatrics, Official Journal of the American Academy of Pediatrics, Section on Adolescent Health, Sep. 26-27, 1999, 9 pages.
IndiCareTM, On-Line Patient Assistant Program, Website Users Manual, JBI Associates, LLC, Jan. 1997, pp. 17.
Instant Access to Credit Reports Now Available Online with DMS' CreditBrowser-based system also Simplifies Credit Decisioning and Offers a Central Point of Control, Business Wire, Dallas, May 23, 2000, p. 0264.
Internal Revenue Service Data Book 2000, Issued Aug. 2001, Revised May 2003.
Jones, Yvonne, “Consumers Understood the Basics but Could Benefit from Targeted Educational Efforts,” Gao U.S. Government Accountability Office, Mar. 16, 2005, pp. 128, http://www.gao.gov/products/GAO-05-223.
“JPMorgan Worldwide Securities Services to Acquire Paloma's Middle and Back Office Operations,” Webpage printed from http://www.jpmorgan.com on Apr. 1, 2009.
“Judging Credit: Consumers Need Better Finance Tools”, News Journal, Daytona Beach, FL, Dec. 28, 2002.
Kauffman et al., “Research Directions on the Role an Impact of ICT in Microfinance”, Proceedings of the 43rd Hawaii International Conference on System Sciences, 2010, pp. 10.
Kent, Heather, “Huge declines in price as competition heats up in Vancouver's booming laser-surgery market,” CMAJ, Oct. 5, 1999; 161 (7), pp. 857-858.
Kulkosky, Edward, “Credit Scoring Appeal Transcends Underwriting,” American Banker, vol. 161, No. 93, p. 8, May 15, 1996.
Kuykendall, Lavonne, “Divergent Paths in Early Pacts with Credit Bureaus”, American Banker, May 30, 2002, vol. 167, No. 3, pp. 2.
Lan, Joe, “The Top Portfolio Management Software,” http://www.aaii.com/computerizedinvesting/article/the-top-portfolio-management-software, Includes Discussion thread, Fourth Quarter 2011, pp. 17.
Langer et al., “Creditor List Screening Practices: Certain Implications Under the Fair Credit Reporting Act and the Equal Credit Opportunity Act,” The Business Lawyer, May 1988, vol. 43, pp. 1123-1141.
Lanubile, et al., “Evaluating Empirical Models for the Detection of High-Risk Components: Some Lessons Learned”, 20th Annual Software Engineering Workshop, Nov. 29-30, 1995, Greenbelt, Maryland, pp. 1-6.
Lavelle, Marianne, “Health Plan Debate Turning to Privacy Some Call for Safeguards on Medical Disclosure. Is a Federal Law Necessary?,” The National Law Journal, vol. 16, No. 39, dated May 30, 1994, as downloaded from http://web2.westlaw.com/result/.
Lee, W.A., “Experian Eyes Payments, Mulls Deals” American Banker: The Financial Services Daily, 2pgs., New York, NY, May 30, 2003.
Lee, W.A.; “Fair Isaac Taps Institutions for Credit Score Distribution”, American Banker: The Financial Services Daily, New York, NY, Apr. 9, 2002, vol. 167, Issue 67, 1 Page.
Lee, W.A., “Money, Quicken, and the Value of Alliances”, American Banker: The Financial Services Daily, 2pgs., New York, NY, Jul. 28, 2003.
LendingTree.com, “Lender Ratings & Reviews,” http://web.archive.org/web/20091015043716/http://www.lendingtree.com/lender-reviews/, Oct. 15, 2009, in 21 pages.
Letter to Donald A. Robert from Carolyn B. Maloney, dated Oct. 31, 2007, pp. 2.
Letter to Donald A. Robert from Senator Charles E. Schumer, dated Oct. 11, 2007, pp. 2.
Letter to Harry C. Gambill from Carolyn B. Maloney, dated Oct. 31, 2007, pp. 2.
Letter to Harry C. Gambill from Senator Charles E. Schumer, dated Oct. 11, 2007, pp. 2.
Letter to Richard F. Smith from Carolyn B. Maloney, dated Oct. 31, 2007, pp. 2.
Letter to Richard F. Smith from Senator Charles E. Schumer, dated Oct. 11, 2007, pp. 2.
Li et al., “Automatic Verbal Information Verification for User Authentication”, IEEE Transactions on Speech and Audio Processing, vol. 8, No. 5, Sep. 2000, pp. 585-596.
LifeLock, “Identity Theft F.A.Q.” http://web.archive.org/web/20080215093614/http://www.identitytheftkiller.com/promo/faq.php, Feb. 15, 2008, pp. 8.
LifeLock, “LifeLock Launches First ID Theft Prevention Program for the Protection of Children,” Press Release, Oct. 14, 2005, http://www.lifelock.com/about-us/press-room/2005-press-releases/lifelock-protection-for-children.
LifeLock; “How Can LifeLock Protect My Kids and Family?” http://www.lifelock.com/lifelock-for-people/how-we-do-it/how-can-lifelock-protect-my-kids-and-family printed Mar. 14, 2008 in 1 page.
Lifelock, “Personal Identity Theft Protection & Identity Theft Products,” http://www.lifelock.com/lifelock-for-people, accessed Nov. 5, 2007.
LifeLock, Various Pages, www.lifelock.com/, Jan. 9, 2007, pp. 49.
Littwin, Angela, “Beyond Usury: A Study of Credit-Card Use and Preference Among Low-Income Consumers”, Texas Law Review, vol. 86, No. 3, pp. 451-506; Feb. 2008.
Longo, Tracey, “Managing Money: Your Family Finances”, Kiplinger's Personal Finance Magazine, Jun. 1, 1995, vol. 49, No. 6, pp. 4.
Lorette, Kristie, “How to Successfully Dispute Inaccuracies on Your Credit Report,” http://web.archive.org/web/20110531184149/http://www.quizzle.com/blog/2011/03/how-to-successfully-dispute-inaccuracies-on-your-credit-report/, Mar. 25, 2011, in * pages.
Lund, Graham, “Credit Bureau Data: Maximizing the Benefits,” Credit Management, May 2004, ProQuest Central, pp. 44-45.
Magid, Lawrence, J., Business Tools: When Selecting an ASP Ensure Data Mobility, Los Angeles Times, Los Angeles, CA, Feb. 26, 2001, vol. C, Issue 4, pp. 3.
Mathematica Policy Research, Inc., “1998 Health Care Survey of DoD Beneficiaries: Technical Manual,” Jul. 1999.
McGovern, Celeste, Jayhawk Medical Acceptance. (Brief Article), Alberta Report, 1 pg., dated Aug. 23, 1999.
McLaughlin, Nancy H., “Homeless, pregnant and alone Dana Sides knows her baby is likely to come in a month, but she has no idea where she will go after leaving the hospital,” NewsRoom, Greensboro News & Record (NC), Section: General News, dated Dec. 6, 2001.
“MediCredit Announces Major Investment from Medstone; Financing Will Enable Dramatic Expansion of Online Services,” Business Wire, pp. 2, dated May 12, 2000.
MediCredit, Patient Financing, “Thought you couldn't afford Cosmetic Surgery?,” 3 pgs., as downloaded from http://web.archive.org/web/19970601060333/http://www.medicredit.com/ (1 of 2) [Oct. 15, 2008 3:16:31 PM].
Medick et al., “German Agency to Mine Facebook to Assess Creditworthiness”, Jun. 7, 2012, http://www.spiegel.de/international/germany/german-credit-agency-plans-to-analyze-individual-facebook-pages-a-837539.html printed Nov. 22, 2013 in 2 pages.
Menge, Falko, “Enterprise Service Bus”, Free and Open Source Software Conference, 2007, pp. 6.
Merriam Webster's Collegiate Dictionary, 10th Edition, Jan. 1, 1993, p. 79.
MicroBilt, “PRBC Credit Reporting Agency—Payment Reporting Builds Credit,” retrieved from http://www.microbilt.com/nontraditional-credit-report.aspx and corresponding “Sample Report,” retrieved from http://www.microbilt.com/pdfs/PRBC%20Sample%20Report%20(complete).pdf printed Nov. 21, 2013 in 8 pages.
Microfinance Africa, “Philippines: Microfinance Players to get Their Own Credit Info Bureau,” Apr. 5, 2011, http://microfinanceafrica.net/microfinance-around-the-world/philippines-microfinance-players-to-get-their-own-credit-info-bureau/ printed Nov. 22, 2013 in 2 pages.
Miller, Margaret, “Credit Reporting Systems Around the Globe: The State of the Art in Public and Private Credit Registries”, Jun. 2000, pp. 32, http://siteresources.worldbank.org/INTRES/Resources/469232-1107449512766/Credit_Reporting_Systems_Around_The_Globe.pdf.
Mint.com, http://www.mint.com/ printed Sep. 18, 2008 in 2 pages.
Montgomery County Housing Report, Residential Market Report, Jan. 2004 in 6 pages.
MS Money Software by Microsoft http://www.microsoft.com/Money/default.mspx as retrieved on Sep. 17, 2008.
Myfico, http://www.myfico.com/products/ficoone/sample/sample_scoresimulator.aspx printed Oct. 12, 2012 in 3 pages.
My ID Alerts, “Why ID Alerts” http://www.myidalerts.com/why-id-alerts.jsps printed Apr. 3, 2012 in 2 pages.
My ID Alerts, “How it Works” http://www.myidalerts.com/how-it-works.jsps printed Apr. 3, 2012 in 3 pages.
MyReceipts, http://www.myreceipts.com/, printed Oct. 16, 2012 in 1 page.
MyReceipts—How it Works, http://www.myreceipts.com/howItWorks.do, printed Oct. 16, 2012 in 1 page.
“Name Availability Records”, Westlaw Database Directory, http://directory.westlaw.com/scope/default.asp?db=NA-ALL&RS=W...&VR=2.0 as printed Dec. 17, 2009, pp. 5.
National Alert Registry Launches RegisteredOffendersList.org to Provide Information on Registered Sex Offenders, May 16, 2005, pp. 2, http://www.prweb.com/printer/240437.htm accessed on Oct. 18, 2011.
National Alert Registry Offers Free Child Safety “Safe From Harm” DVD and Child Identification Kit, Oct. 24, 2006. pp. 2, http://www.prleap.com/pr/53170 accessed on Oct. 18, 2011.
National Alert Registry website titled, “Does a sexual offender live in your neighborhood”, Oct. 22, 2006, pp. 2, http://web.archive.org/wb/20061022204835/http://www.nationallertregistry.com/ accessed on Oct. 13, 2011.
“New Privista Product Provides Early Warning System to Combat Identity Theft”, PR Newswire, Oct. 24, 2000, PR Newswire Association, Inc., New York.
“NewsHound: NewsHound User Guide Internet E-Mail”, of record as early as May 2, 1997, pp. 11.
Newsroom, “CIGNA Report Withdrawn as Foe Sees Opening,” Insurance Regulator, State Survey, Sep. 9, 1996, vol. 8, Issue 34, pp. 4.
“New for Investors: Asset Allocation, Seasoned Returns and More,” Prosper, http://blog.prosper.com/2011/10/27/new-for-investors-asset-allocation-seasoned-returns-and-more/, Oct. 27, 2011, pp. 4.
Next Card: About Us, http://web.cba.neu.edu/˜awatson/NextCardCase/NextCardAboutUs.htm printed Oct. 23, 2009 in 10 pages.
“Normalize,” http://www.merriam-webster.com/dictionary/normalize printed Jun. 14, 2010.
Novack, Janet, “The Coming Fight over FICO,” Forbes, Dec. 18, 1995, vol. 156, No. 14, p. 96.
Occasional CF Newsletter; http://www.halhelms.com/index.cfm?fuseaction=newsletters.oct1999; Oct. 1999.
Office of Integrated Analysis and Forecasting, DOE/EIA-M065(2004), Model Documentation Report: Macroeconomic Activity Module (MAM) of the National Energy Modeling System, EIA, Washington DC, Feb. 2004.
Organizing Maniac's Blog—Online Receipts Provided by MyQuickReceipts.com, http://organizingmaniacs.wordpress.com/2011/01/12/online-receipts-provided-by-myquickreceipts.com/dated Jan. 12, 2011 printed Oct. 16, 2012 in 3 pages.
Pagano, et al., “Information Sharing in Credit Markets,” Dec. 1993, The Journal of Finance, vol. 48, No. 5, pp. 1693-1718.
Partnoy, Frank, Rethinking Regulation of Credit Rating Agencies: An Institutional Investor Perspective, Council of Institutional Investors, Apr. 2009, pp. 21.
Paustian, Chuck, “Every Cardholder a King Customers get the Full Treatment at Issuers' Web Sites,” Card Marketing, New York, Mar. 2001, vol. 5, No. 3, pp. 4.
Pennsylvania Law Weekly, “Discriminating Against Victims Admitting Domestic Abuse Can Lead to Denial of Insurance Coverage,” vol. XVIII, No. 26, dated Jun. 26, 1996, 2 pgs., as downloaded from http://web2.westlaw.com/result/documenttext.aspx?rs=WLW8.
Phinisee, Tamarind, “Banks, FTC Step Up Efforts to Address Identity Theft”, San Antonio Business Journal; San Antonio, Jul. 5, 2002, vol. 16, No. 24, pp. 5.
Planet Receipt—Home, http://www.planetreceipt.com/home printed Oct. 16, 2012 in 1 page.
Planet Receipt—Solutions & Features, http://www.planetreceipt.com/solutions-features printed Oct. 16, 2012 in 2 pages.
Powerforms: Declarative Client-Side for Field Validation, ISSN 1386-145x, Dec. 2000.
“ProClarity and Microsoft to Host Free Seminar Series on Retail Analytics with Independent Analyst Firm-ProClarity to Share Best Forrester Analysts to Discuss Trends and the Future of the Retail”; Business Wire; pp. 2; Aug. 13, 2003.
“Qualifying for Debt Settlement”, http://www.certifieddebt.com/debt/settlement-qualifications.shtml printed Jan. 9, 2013 in 2 pages.
Quantix Software, “Investment Account Manager,” available at https://www.youtube.com/watch?v=1UwNTEER1Kk, as published Mar. 21, 2012.
Quicken Online by Intuit http://www.quicken.intuit.com/, as retrieved on Sep. 17, 2008.
“Quicken Support”, http://web.archive.org/web/20071231040130/http://web.intuit.com/support/quicken/docs/d_qif.html as archived Dec. 31, 2007 in 6 pages.
Ralston et al., “Lending Procedures and the Viability-Social Objectives Conflict in Credit Unions”, The International Journal of Bank Marketing, 2003, vol. 21, No. 6/7, pp. 304-311 (14 pages).
Ramaswamy, Vinita M., Identity-Theft Toolkit, The CPA Journal, Oct. 1, 2006, vol. 76, Issue 10, pp. 66-70.
RAP Interactive, Inc. and Web Decisions: Proudly Presents Live Decisions, A Powerful New Information and Technology Resource that Revolutionizes Interactive Marketing, downloaded from www.webdecisions.com/pdf/LiveDecisions_Bro.pdf, as printed on Aug. 13, 2007.
Ratner, Juliana, “GMAC to Sell Risk-Management Advice; Target is 150 Biggest Home Loan Servicers,” American Banker, vol. 161, No. 53, p. 16, Mar. 19, 1996.
“Recognition and use by Appraisers of Energy-Performance Benchmarking Tools for Commercial Buildings,” prepared by the Institute for Market Transformation, NYSERDA, Feb. 2003, pp. 6.
Repici et al., “The Comma Separated Value (CSV) File Format”, http://creativyst.com/Doc/Articles/CSV/CSV01.htm, Creativyst, Inc., 2002, pp. 10.
“Resolve Debt for Less: With Help from Freedom Financial” http://www.debtsettlementusa.com/ printed Jan. 9, 2013 in 6 pages.
“RF/Spectrum to Offer Score,” National Mortgage News, Special Report; Credit Reporting & Scaring, Jun. 9, 1997, p. 40.
Risk Monitors, “New GMAC Unit Focuses on Portfolio Risk,” PR Newswire, Mar. 13, 1996, pp. 2. http://www.thefreelibrary.com/NEW+GMAC+UNIT+FOCUSES+ON+PORTFOLIO+RISK-a018092212.
Roth, Andrew, “CheckFree to Introduce E-Mail Billing Serving,” American Banker, New York, Mar. 13, 2001, vol. 166, No. 49, pp. 3.
Rubin, Rita, “Cosmetic Surgery on Credit, Finance plans let patients reconstruct now, pay later,” The Dallas Morning News, 2 pgs., dated Sep. 10, 1988.
Saunders, A., “Data Goldmine,” Management Today, London: Mar. 1, 2004, 6 pages.
Schmidt, David, “Environmental Impact: The Changing Credit Reporting Landscape,” Business Credit, Apr. 2003, vol. 105, No. 4, pp. 14 (electronic copy provided in 5 pages).
Screenshot for Investment Account Manager v.2.8.3, published at http://www.aaii.com/objects/get/1642.gif by at least Aug. 30, 2011 in 1 page.
Sealey, Geraldine, “Child ID Theft Can Go Unnoticed for Years”, http://abcnews.go.com/US/story?id=90257, Sep. 12, 2003 in 9 pages.
Searchamerica, “Payment Advisor Suite TM”, Solutions, 2009, pp. 2.
Selz, Michael, “Lenders Find Niche in Cosmetic Surgery That Isn't Insured—But Since You Can't Repossess a Nose Job, Risks Aren't Restricted to the Patients,” Wall Street Journal, New York, N.Y., Jan. 1997, pg. A.1, 3 pgs.
“Settling Your Debts—Part 1 in Our Debt Settlement Series”, http://www.creditinfocenter.com/debt/settle_debts.shtml printed Jan. 9, 2013 in 6 pages.
“Shareholders Sue Green Tree Financial,” Dated Dec. 4, 1997, http://web.archive.org/web/20000419070107/http://www.wcco.com/news/stories/news-971204-092238.html.
ShoeBoxed, https://www.shoeboxed.com/sbx-home/ printed Oct. 16, 2012 in 4 pages.
Simpson, Glyn, “Microsoft (MS) Money MSMoney FAQ, Help and Information Pages”, pp. 2, Copyright © Glyn Simpson 1998-2007, http://web.archive.org/web/20071018075531/http://money.mvps.org/faq/article/196.aspx.
Singletary, Michelle “Ratings for the Credit Raters”, The Washington Post, The Color of Money column, Mar. 24, 2002 in 1 page.
Singletary, Michelle, “Score One for Open Credit Ratings”, The Washington Post, Washington DC, Jun. 18, 2000, 3 pages.
Solapurkar, Prajakta, “Building Secure Healthcare Services Using OAuth 2.0 and JSON Web Token in IOT Cloud Scenario”, IEEE, 2nd International Conference on Contemporary Computing and Informatics (ic3i), 2016, pp. 99-104.
Stanton, T.H., “Credit Scoring and Loan Scoring as Tools for Improved Management of Federal Credit Programs”, Financier, Philadelphia, Summer 1999, vol. 6, 36 pages.
“StarNet Financial, Inc. Acquires Proprietary Rights to Sub-Prime Underwriting System Through Strategic Alliance With TRAkkER Corporation”, PR Newswire, Dallas, TX, Sep. 13, 1999.
State of Wisconsin, Division of Health Care Financing, Department of Health and Family Services: 1999-2001 Biennial Report, pp. 17-21.
Steele, Georgia, “Fair, Isaac Seeks Mortgage Tech Opportunities,” National Mortgage News, Special Report; B& C Lending, Mar. 23, 1998, p. 34.
Stein, Benchmarking Default Prediction Models: Pitfalls and Remedies in Model Validation, Moody's KMV, Revised Jun. 13, 2002, Technical Report #020305; New York.
Sullivan, Deidre, “Scoring Borrower Risk,” Mortgage Banking, Nov. 1994, vol. 55, No. 2, pp. 94-98.
Sumner, Anthony, “Tackling The Issue of Bust-Out Fraud”, Experian: Decision Analytics, Dec. 18, 2007, pp. 24.
Sumner, Anthony, “Tackling the Issue of Bust-Out Fraud”, e-News, Experian: Decision Analytics, pp. 4, [Originally Published in Retail Banker International Magazine Jul. 24, 2007].
Taylor, Marshall, “Loan-Level Pricing Draws Interest From Investors,” Real Estate Finance Today, Jul. 7, 1997, vol. 14, No. 14. p. 10.
Texas Department of Human Services, 1999 Annual Report, 60 Years of Progress, Medial Services 9P137, Publication No. DHS-600-FY99.
thatlook.com, Cosmetic Surgery Financing, 3 pgs, as downloaded from http://web.archive.org/web/200001214113900/www.thatlook.com/cosmetic_surgery_financing.cfm (1 of 2) [Oct. 15, 2008 4:11:47 PM].
“The Best of the Best,” Mortgage Technology, Nov. 1, 2003, vol. 10, No. 8, pp. 34-53.
TheMorningCall.Com, “Cheap Ways to Foil Identity Theft,” www.mcall.com/business/columnists/all-karp.5920748jul01,0 . . . , published Jul. 1, 2007.
Thomas, David, “Reporton Networks and Electronic Communications Newcourt Credit Turns to Extranet Services / A PC Connects to 1,200 Users at Once”, The Globe and Mail (Canada), Section: Report on Business Special Report, Nov. 12, 1996, pp. 2.
Todorova, Aleksandra, “Protecting Your Child's Identity”, Smart Money, Published Aug. 2, 2007, pp. 1-5.
TRAkkER Corporation website, trakkercorp.com, TRAkkER Software Description, May 26, 2000, available at http://web.archive.org/web/20000526234204/http://trakkercorp.com/page4.html.
“TransUnion—Child Identity Theft Inquiry”, TransUnion, http://www.transunion.com/corporate/personal/fraudldentityTheft/fraudPrevention/childIDInquiry.page as printed Nov. 5, 2009 in 4 pages.
TransUnion Consumer Credit Report http://www.transunion.com/, as retrieved on Sep. 17, 2008.
TransUnion: VantageScore®—Consistency in Credit Scoring, http://www.transunion.com/personal-credit/credit-reports/vantage-score.page printed Oct. 12, 2012 in 2 pages.
Trulia, “Trulia Estimates,” http://www.trulia.com/trulia_estimates/, printed Feb. 18, 2014 in 2 pages.
Tuman, Diane, “What is a Zestimate?” Mar. 2013, pp. 5, http://www.zillow.com/wikipages/What-is-a-Zestimate/.
US Legal, Description, http://www.uslegalforms.com/us/US-00708-LTR.htm printed Sep. 4, 2007 in 2 pages.
“Use of Alternative Data to Enhance Credit Reporting to Enable Access to Digital Financial Services by Individuals and SMEs Operating in the Informal Economy”, Guidance Note, International Committee on Credit Reporting (ICCR), Jun. 28, 2018, pp. 35.
Vamosi, Robert, “Howto Handle ID Fraud's Youngest Victims,” Nov. 21, 2008, http://news.cnet.com/8301-10789_3-10105303-57.html.
Van Collie, Shimon, “The Road to Better Credit-Card Marketing,” Bank Technology News, Sep. 1995, pp. 4.
Verstraeten, Geert, Ph.D.; Issues in predictive modeling of individual customer behavior: Applications in targeted marketing and consumer credit scoring; Universiteit Gent (Belgium), Dec. 2005.
Wahl, Martin, “The Stampede to Subprime,” Mortgage Banking, Oct. 1, 1997, vol. 58, No. 1, p. 26(7).
Washington State Office of Public Defense, “Criteria and Standards for Determining and Verifying Indigency,” dated Feb. 9, 2001.
Watts, Craig, “Consumers Now Can Know What Loan Rate Offers to Expect Based on Their FICO Credit Score at MyFICO.com,” San Rafael, CA, Mar. 6, 2002, pp. 2, http://www.myfico.com/PressRoom/PressReleases/2002_03_06.aspx.
Watts, Craig, “Fair, Isaac and Equifax Give Consumers New Score Power Tools Offering Greater Insights for Managing Their Credit Health,” May 21, 2002, pp. 3, http://www.myfico.com/PressRoom/PressReleases/2002_05_21.aspx.
Webpage printed from http://www.magnum.net/pdfs/RapUpBrochure.pdf as printed Mar. 3, 2008.
“We Eliminate Bad Debt”, as printed from http://www.webcreditbureau.com/start/, dated Aug. 22, 2012, 1 Page.
“Web Site Fuels Elective Surgery Trend; The Complete Resource to Paying for Cosmetic Surgery, Laser Vision Correction and Cosmetic Dentistry,” Business Wire, Apr. 7, 1999, pp. 2.
Wesabe.com http://www.wesabe.com/, as retrieved on Sep. 17, 2008.
West, David, “Neural Network Credit Scoring Models”, Computers & Operations Research, vol. 27, 2000, pp. 1131-1152.
White, Ron, “How Computers Work”, Special 10th Anniversary, Seventh Edition, Que Corporation, Indianapolis, IN, Oct. 2003, pp. 23.
Wilson, Andrea, “Escaping the Alcatraz of Collections and Charge-Offs”, http://www.transactionworld.net/articles/2003/october/riskMgmt1.asp, Oct. 2003.
Window on State Government, Susan Combs, Texas Comptroller of Public Accounts, Chapter 8: Health and Human Services, “Improve the Medicaid Eligibility Determination Process,” 9 pgs., as downloaded Apr. 9, 2008 from http://www.window.state.tx.us/etexas2001/recommend/ch08.
Wisconsin Department of Workforce Development, BadgerCare Medicaid Application Credit Report Authorization Form, dated Jun. 21, 2001, effective date, Jul. 1, 2001.
Wisconsin Department of Workforce Development, BadgerCare Medicaid Notification of Eligibility, dated Jul. 25, 2000, effective date, Jul. 1, 2000.
Wood, Greg, “Top Streaming Technologies for Data Lakes and Real-Time Data”, http://blog.zaloni.com/top-streaming-technologies-for-data-lakes-and-real-time-data, Sep. 20, 2016 in 3 pages.
Yang, et al., “An Analysis of the Ex Ante Probabilities of Mortgage Prepayment and Default”, Real Estate Economics, Dec. 1998, vol. 26, No. 4, pp. 651-676.
Yücesan et al., “Distributed Web-Based Simulation Experiments for Optimization”, Simulation Practice and Theory 9, Oct. 2001, pp. 73-90.
Zimmerman et al., “A Web-Based Platform for Experimental Investigation of Electric Power Auctions,” Decision Support Systems, Jan. 1999, vol. 24, pp. 193-205.
Zoot—Decision Engine, www.zootweb.com/decision_engine.html, as printed on Mar. 3, 2008.
Zoot—Instant Rules GUI, www.zootweb.com/instant_rules_GUI.html as printed Mar. 3, 2008.
Zoot—Pre-Built Standard Attributes, www.zootweb.com/credit_attributes.html as printed Mar. 3, 2008.
Zoot—Rules Management GUI, www.zootweb.com/business_rules_GUI.html as printed Mar. 3, 2008.
Official Communication in European Patent Application No. 12811546.6, dated Nov. 25, 2014.
Official Communication in Indian Patent Application No. 490/DELNP/2014, dated Jun. 20, 2019.
Official Communication in Russian Patent Application No. 2014101674/08, dated Dec. 15, 2014.
International Preliminary Report on Patentability and Written Opinion for Application No. PCT/US2012/046316, dated Jan. 14, 2014.
International Search Report and Written Opinion for Application No. PCT/US2013/072102, dated Apr. 18, 2014.
International Search Report and Written Opinion for Application No. PCT/US2014/019142, dated Jun. 20, 2014.
International Preliminary Report on Patentability in Application No. PCT/US2017/048265, dated Mar. 7, 2019.
Partial Supplementary European Search Report for Application No. EP12747205, dated May 14, 2020.
Extended European Search Report for Application No. EP12747205, dated Aug. 14, 2020.
International Search Report and Written Opinion for Application No. PCT/US2018/016258, dated May 16, 2018.
International Preliminary Report on Patentability in Application No. PCT/US2018/016258, dated Aug. 15, 2019.
International Search Report and Written Opinion for Application No. PCT/US2020/012976, dated May 6, 2020.
International Search Report and Written Opinion for Application No. PCT/US2018/061877, dated Mar. 8, 2019.
International Preliminary Report on Patentability in Application No. PCT/US2018/061877, dated Jun. 4, 2020.
International Search Report and Written Opinion for Application No. PCT/US2019/049377, dated Dec. 20, 2019.
Provisional Application as filed in U.S. Appl. No. 60/168,272, dated Dec. 1, 1999 in 14 pages.
Provisional Application as filed in U.S. Appl. No. 60/168,276, dated Dec. 1, 1999 in 82 pages.
Provisional Application as filed in U.S. Appl. No. 60/213,367, dated Jun. 23, 2000 in 20 pages.
Application as filed in U.S. Appl. No. 09/653,595, dated Aug. 31, 2000.
Extended European Search Report for Application No. EP12747205, dated Feb. 11, 2022.
International Preliminary Report on Patentability in Application No. PCT/US2020/012976, dated Jul. 22, 2021.
Nikravesh et al., “Fuzzy Queries, Search, and Decision Support System”, Soft Computing, Aug. 2002, vol. 6, No. 5, pp. 373-399.
Official Communication in Australian Patent Application No. 2018215082, dated Jan. 21, 2022.
Official Communication in Indian Patent Application No. 201917029540, dated Jan. 7, 2022.
Provisional Applications (1)
Number Date Country
62259548 Nov 2015 US
Continuations (2)
Number Date Country
Parent 16999686 Aug 2020 US
Child 17448500 US
Parent 15360496 Nov 2016 US
Child 16999686 US