Realtime access and control of secure regulated data

Description

BACKGROUND

Credit bureaus may provide users with the ability to limit access to the user's credit data, such as though completion of forms and manually providing identification information (e.g., birth certificate, passport, etc.). User's may have the ability to request access restrictions on credit data, such as via a lock or unlock, or freeze or unfreeze. When a credit file is unlocked, for example, information in the file can be accessed by third parties that have a permissible purpose to access the user's credit data, such as under the Fair Credit Reporting Act (FCRA) in the United States.

Typically, a user provides information to a credit bureau that confirms their identity, as well as possibly a lock/unlock identifier (e.g., a number or alphanumeric code) in order to initiate locking or unlocking of their credit file. Unfortunately, this can be a tedious, slow, and inconvenient process for many reasons. For example, the process may be quite slow as it may require human review of the authentication documents. There may also need to be several layers of security features to authenticate the user, such as providing original copies of documents (e.g., birth certificates, passports, etc.), biometric sensors, passwords and pins, and/or responding to questions. The user would also have to remember such passwords and pins, and responses to the answers. The forms or process of locking or unlocking may also be long and require a lot of information from the user. The forms may also require documents that may take time and effort to obtain (e.g. bank statement, utility bill, etc.). Furthermore, the lock or unlock feature may require a fee or payment from the user each and every time a lock or unlock request is sent. Also, sending and receiving information for such a request over the phone, via mail or electronically, may subject such information to security risks (e.g. hacking) and may lead to more identity theft or fraud. The rules for a freeze and unfreeze may also differ from state to state, further complicating the process of securing user data. Thus, when moving from one state to another, the rules for locking and unlocking your credit file may be quite different.

In view of these technological shortcomings, when a user wishes to provide a third party with access to credit data that is locked, they cannot do so. Additionally, users may forget that they locked their file and when applying for credit (or otherwise wanting to allow access to credit data), would simply be prevented from accessing their credit file until the arduous and time-consuming process of unlocking the credit data is performed. Users would have to identify what happened (e.g. whether the credit file was locked/frozen or some other reason such as incorrect information submitted) and take necessary steps to release the credit file that prolong the process and may dissuade a user from continuing.

Additionally, users have no control over their credit files once a lock is performed. For example, after a lock has been placed, the user is unaware of credit inquiries (requests by third parties to access credit data) received by the credit bureaus and, thus, cannot provide access to third parties that the user wishes to grant access to. For example, although the user may have locked their credit file for other security purposes (such as identify theft), the user may need to allow access their credit file for other purposes (such as applying for a credit card). However, based on the technological shortcomings noted above, the user may decide not to pursue the credit card. Moreover, after completing the arduous process of unlocking their credit file, the user may forget or just not be dedicated enough to spend the time on the similar process of re-locking their credit file.

Users may also find it inconvenient to have to memorize a separate identifier that is provided by the credit bureau for each credit bureau that maintains a credit file for the user. Moreover, the user may forget an identifier he or she may need to request a new identifier by, for example, phone or certified mail from the credit bureau, which can result in a delay in locking their file. Additionally, when the user wishes to unlock their file they may need to wait a specified period of time, often three days, for the file to be unlocked. Besides imposing risks to a user's credit file, these delays may cause lenders, such as those looking to provide instant credit, to lose out on credit opportunities. Furthermore, users may not want to reveal their identifiers in a public area at the point of sale.

In merchant environments, such as department stores, credit file locking and unlocking can be especially problematic. For example, a store may offer a credit card, debit card, or store loyalty card, for example, to a user at a point of sale. The user may decide that applying for the store card is not worthwhile because their credit file is locked and unlocking the file will take significant time and effort (e.g., the user may be required to call each of one or more credit bureaus and provide credit bureau specific credit file unlock codes to each credit bureau, pay a fee to each of the credit bureaus, etc., and waiting significant time periods for implementation by respective credit bureaus). Alternatively, a user may apply for the store card using the credit application process, only to discover that their credit file is locked. In this situation, the user may then decide not to proceed further with the application process because of the above-noted technological shortcomings in existing credit file control systems. As a result, merchants may lose out on significant sales and credit opportunities.

SUMMARY

The systems and methods described herein allow users to control access to regulated data of the user (stored in a secured third party database) through interaction on a mobile device (or other computing device), such as to provide a touch gesture on the mobile device that causes the users regulated data to be accessible to a third party. The regulated data may include credit data of the user, such as a credit report or credit file. Access rights to the regulated data may be provided in real-time (or near real-time) in response to a request for the data from a third party, for example. The system may allow a user to respond to an alert or notification that is automatically sent to the computing device of the user in response to a request for a secure regulated data of the user.

In one embodiment, the regulated data comprises credit data that is stored by one or more credit bureaus and the access control include locking and unlocking of credit data specific to a user. In some embodiments, systems and methods described herein allow users to unlock their credit files in real-time or near real-time. Upon receiving a request to access a credit file from a requesting entity, the system may determine whether the credit file is locked, frozen, or otherwise prevented from dissemination. In response to determining that the credit file is not locked, frozen, or otherwise prevented from dissemination, the system may proceed with the release of credit data. However, if the credit file cannot be sent to the requesting entity, the system may notify the user. The system may determine notification preferences of the user and transmit an alert according to such preferences. The alert may notify the user that an inquiry to the credit file has been sent.

In some embodiments, the system may authorize an unlock, unfreeze, thaw, or lift of the credit file. U.S. Pat. No. 9,256,904, titled “Multi-bureau credit file freeze and unfreeze,” issued Feb. 9, 2016, which is hereby incorporated by reference in its entirety, describes additional details and options in allowing users to lock or unlock their credit files, such as through use of a personal identifier. The features and details included in U.S. Pat. No. 9,256,904 may be applied to various embodiments discussed herein.

In some embodiments, the system performs credit file locking and unlocking based on user, system, or group defined preferences. For example, in some embodiments, the credit file may be unlocked for a particular period of time. The credit file may also be unlocked for a purpose or for a particular requesting entity. The unlock may be toward a portion or subset of the credit file while a lock remains on the remainder of the credit file. U.S. Pat. No. 8,744,956, titled “Systems and methods for permission arbitrated transaction services,” issued Jun. 3, 2014, describes additional details and options associated with selective sharing of credit data, such as sharing for a period of time or purpose. The features and details included in U.S. Pat. No. 8,744,956 may be applied to various of the embodiments discussed herein.

Embodiments of the present disclosure may be particularly advantageous in merchant environments. For example, in point of sale environments a user may apply for a credit card (debit card, store loyalty card, or other account that requires access to credit data by the merchant). However, the credit file may be locked. In response to the merchant's inquiry for credit information, the system can automatically and in real-time generate and transmit alert data to a mobile device of the user, notifying the user of the inquiry and possibly provided a link to additional information regarding the user's credit data, the requesting merchant, or other relevant information. Then the system can allow the user to authorize an unlock of the credit file. The unlock can be customized. For example, the credit file may be unlocked for a particular purpose (e.g. applying for a credit card or more generally for a line of credit). The unlock may be for a particular duration (such as an unlock for an hour) and then may automatically re-lock thereafter. The unlock may be for a particular requesting entity (e.g. a trusted merchant identified by the user). The unlock may be directed toward a portion of the credit data. For example, a portion of the credit data that is necessary for the purpose of the inquiry may be released. A less intrusive portion of the credit file may also be released (e.g. such as credit score without total debt). By providing users with a simplified interface and an expedient mechanism for customized unlocking of their credit files, the system can increase credit opportunities for both the user and the merchant, while reducing risk of identity theft by allowing the user to easily keep their credit file locked.

Furthermore, the present disclosure is advantageous in security environments. For example, the user may apply a lock on their credit file. However, the user may want to know who is inquiring about their credit data while their account is locked. The user may be watching television at home when the user's mobile device notifies the user that a particular foreign company has tried to inquire about the user's credit data. The user may then keep the lock on their credit file and notify other third parties of the inquiry to begin an investigation. The same user can still unlock their credit files for other purposes (e.g. their trusted bank requested credit information to see if they can automatically increase the user's credit card limit).

In some embodiments, access exceptions may apply and thus credit data may nevertheless be released regardless of whether there is a lock or a freeze on the account. An access exception applies when credit data is provided regardless of whether the user's credit data is locked or frozen. For example, federal, state, and local government agencies have access to credit data in some circumstances (e.g. in support of a child support claim).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating one embodiment of a credit report access control system that is in communication with a user computing device and a plurality of credit bureaus via a network.

FIG. 2 is a block diagram illustrating an example configuration of a system that provides real-time user alerts in response to credit inquiry requests with unlock authorization.

FIG. 3 is a diagram illustrating one embodiment of a user lock status & preferences data structure.

FIG. 4 is a flowchart illustrating one embodiment of a method for providing a real-time inquiry alert to a user and unlock credit data.

FIGS. 5A-5F are user interfaces illustrating one embodiment for requesting an unlock of the credit file.

FIGS. 6A-6J are user interfaces illustrating one embodiment for requesting a lock and an unlock of the credit file.

FIGS. 7A-7B are user interfaces illustrating one embodiment for an alert on a mobile phone that allows the user to authorize an unlock.

FIGS. 8A-8C are user interfaces illustrating one embodiment for showing a history for a credit file.

FIGS. 9A-9D are portions of a user interface illustrating an example animation indicating lock status.

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

Embodiments of the disclosure will now be described with reference to the accompanying figures, wherein like numerals refer to like elements throughout. The terminology used in the description presented herein is not intended to be interpreted in any limited or restrictive manner, simply because it is being utilized in conjunction with a detailed description of certain specific embodiments of the invention. Furthermore, embodiments of the invention may include several novel features, no single one of which is solely responsible for its desirable attributes or which is essential to practicing the inventions herein described.

Definitions

In order to facilitate an understanding of the systems and methods discussed herein, a number of terms are defined below. The terms defined below, as well as other terms used herein, should be construed to include the provided definitions, the ordinary and customary meaning of the terms, and/or any other implied meaning for the respective terms. Thus, the definitions below do not limit the meaning of these terms, but only provide exemplary definitions.

The terms “user,” “individual,” “consumer,” and “customer” should be interpreted to include single persons, as well as groups of individuals, such as, for example, married couples or domestic partners, organizations, groups, and business entities. Additionally, the terms may be used interchangeably. In some embodiments, the terms refer to a computing device of a user rather than, or in addition to, an actual human operator of the computing device.

User Input (also referred to as “Input”) generally refers to any type of input provided by a user that is intended to be received and/or stored by one or more computing devices, to cause an update to data that is displayed, and/or to cause an update to the way that data is displayed. Non-limiting examples of such user input include keyboard inputs, mouse inputs, digital pen inputs, voice inputs, finger touch inputs (e.g., via touch sensitive display), gesture inputs (e.g., hand movements, finger movements, arm movements, movements of any other appendage, and/or body movements), and/or the like.

Credit data generally refers to user data that is collected and maintained by one or more credit bureaus (e.g., Experian, TransUnion, and Equifax) and is subject to regulatory requirements that limit, for example, sharing of credit data to requesting entities based on the Fair Credit Reporting Act (FCRA) regulations in the United States and/or other similar federal regulations. “Regulated data,” as used herein, often refers to credit data as an example of such regulated data. However, regulated data may include other types of data, such as HIPPA regulated medical data. Credit data can describe each individual data item associated with a user, e.g., an account balance, or any combination of the individual's data items. “Credit file” and “credit report” generally refer to a collection of credit data associated with a user, such as may be provided to the user, to a requesting entity that the user has authorized to access the user's credit data, or to a requesting entity that has a permissible purpose (e.g., under the FCRA) to access the users credit data without the user's authorization.

A credit report freeze (also referred to herein as a “credit freeze,” “report freeze,” a “freeze,” or the like) generally refers to blocking access to a user's credit data by third parties (e.g., someone or an entity other than the user associated with the credit data), such as credit data in a credit file or credit report. A credit report freeze is often executed in accordance with various security freeze laws. For example, a credit report freeze may be implemented in view of a single state's law to enact security freezes. A credit report freeze may require an individual to provide a personal identification (PIN) code and/or other authentication information (username and password, biometric data, etc.) to initiate the freeze. In some embodiments, state-regulated fees and or credit bureau fees may be charged to the user that requests a credit freeze. When a user's credit report is frozen, certain accesses to the user's credit data that are typically permissible, such as for pre-qualification of the user for a line of credit, may be blocked. In some embodiments, user initiated credit monitoring may or may not be allowed if the user's credit report is frozen. A credit freeze can prevent thieves and data hackers from accessing credit information

A credit report lock (also referred to herein as a “credit lock,” “report lock”, “lock,” or the like) generally refers to blocking access to credit data of a user associated with the credit data. A credit report unlock (also referred to herein as a “credit unlock lock,” “report unlock”, “unlock,” or the like) generally refers to allowing access to credit data that has previously been locked. A credit lock can allow customization beyond what is allowed with a credit freeze, such as to allow the user to proactively control accesses to their credit data, such as through authorizing access to only a particular entity, for a limited time period, etc., as discussed herein. A credit lock is generally implemented by one or more credit bureaus and, thus, may not be limited by government regulations, such as those that apply to a credit freeze. Advantageously, a credit report lock may prevent access to only particular items of credit data within a credit file of a user. The user's proactive controls may include blocking credit inquiry requests from only a certain entity or entities and, similarly, may allow access to credit data from only a certain entity or entities. A credit report lock may be for a particular period of time, such as a temporary lift (e.g., 1 hour) on the credit report lock, or purpose. While much of the description herein refers to a credit report lock and unlock, similar functionality and advantages can equally be applied to credit report freezes, lifts, and thaws, and vice versa.

An access exception generally refers to an exception for providing credit data of a user regardless of whether the user's credit data is locked and/or frozen. For example, federal, state, and local government agencies may receive an access exception such that their requests for credit data of a user are not blocked by the user's credit file being locked. Such government requests may be to retrieve user information in support of a child support claim, for example. Another access exception may be to companies requesting credit data for the purposes of employment of a user or to insurance companies for determining whether to insure a user. Companies that already have a pre-existing relationship with a user (e.g. the user has an open account with the company included on the user's credit report, collection agencies acting on behalf of those whom you owe for the purposes of reviewing the credit report) may also be allowed an access exception. Companies that may be able to offer prequalified offers of services may also have an access exception. In some embodiments, however, the user is able to specifically indicate to the access control system that such prequalification services are not to be provided access to the user's credit file and effectively override any access exceptions that such a prequalification service may otherwise have. Similar overrides to other access exceptions are also possible in various embodiments. Also, users requesting direct credit monitoring, credit reports, or credit scores from credit bureaus may also have an access exception. The examples are not meant to limit the definition but only to provide examples of the term.

In various embodiments discussed herein, alerts and/or notifications (which may be used interchangeably) are automatically transmitted to a device operated by the user whose credit data has been requested. The alert and/or notification can be transmitted at the time that the alert and/or notification is generated or at some determined time after generation of the alert and/or notification. When received by the user's device, the alert and/or notification can cause the device to display the alert and/or notification via the activation of an application on the device (e.g., a browser, a mobile application, etc.). For example, receipt of the alert and/or notification may automatically activate an application on the device, such as a messaging application (e.g., SMS or MMS messaging application), a standalone application (e.g., a credit monitoring application provided to the user by the credit report access control system), or a browser, for example, and display information included in the alert and/or notification. If the device is offline when the alert and/or notification is transmitted, the application may be automatically activated when the device is online such that the alert and/or notification is displayed. As another example, receipt of the alert and/or notification may cause a browser to open and be redirected to a login page generated by the system so that the user can log in to the system and view the alert and/or notification. Alternatively, the alert and/or notification may include a URL of a webpage (or other online information) associated with the alert and/or notification, such that when the device (e.g., a mobile device) receives the alert, a browser (or other application) is automatically activated and the URL included in the alert and/or notification is accessed via the Internet. The alert and/or notification may be determined based on preferences stored in a data store. For example, a user may sign up for a publish/subscribe service or a credit monitoring service that may be configured to identify changes to credit data. Upon enrollment, the individual may additionally select an option to be notified of credit data inquiries and a selection of preferences for receiving alerts/notifications (e.g., as discussed with reference to block 425 of FIG. 4 below).

A module generally 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, 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. Software modules may include, by way of example, components, such as class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, tables, arrays, and variables. 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 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. When executed by the credit report access control system 100, modules may allow the credit report access control system 100 to perform operations, such as storing data, accessing stored data, modifying stored data, communicating with other computing devices and systems, and other operations described herein. For ease of explanation, the modules may be referred to as performing an operation or a method, even though other systems and/or components of the credit report access control system 100 may actually perform the operation or method in response to executing software of a module, for example.

Example Workflow and Advantages

The present disclosure generally relates to credit file locking and unlocking. The service may allow a user to respond to an alert sent in response to a request for a locked credit file. The system may authorize an unlock, unfreeze, thaw, or lift of the credit file. In one embodiment, a system that implements a credit file locking service is disclosed. In contrast to existing frameworks where credit files of users are locked or unlocked through a laborious process, not providing the user with the various proactive controls noted herein, the systems and methods described herein allow users to selectively authorize access to their credit data even after the credit file has been locked or frozen. Additionally, the user access controls and customizations discussed herein with reference to credit locking and unlocking may also be used with a fraud alert. In one embodiment, if a fraud alert is placed on a user's credit file, each time a third party, for example a merchant, requests access to the user's locked credit file, a credit bureau sends notice to the requesting third party that the third party should take steps to verify the identity of the party requesting credit prior to extending credit in the name of the user on the requested credit report. For example, the user may be contacted with a request for permission to allow the third party to access the credit file for purposes of determining eligibility for a credit account, for example.

In an illustrative embodiment, a user may provide one or more personal identifier (also referred to herein as “PID”) to a report access control system, for example over a computer network. As used herein, a PID may comprise any personal identifier, including without limitation a login ID and password, a name, an address, a phone number, a date of birth, a maiden name, a social security number, an account number, a driver's license number, a password, a RFID tag or token, biometric data, such as a fingerprint, and/or a personal identification number (also referred to herein as a “PIN” or a PIN code”), which may comprise a sequence of numerals, a sequence of alphanumeric characters, or any combination of personal identifiers. A user selected PID may indicate that the user has selected the type of data in the PID (e.g., a user selects a PID that is a password, a PIN, or a fingerprint) and/or that the user has selected the content of the PID (e.g., the user selects the particular password or PIN or provides a fingerprint). A user selected PID may advantageously be easier for the user to remember and/or provide to a requesting entity or device.

A user may provide the PID using a computing device, such as, for example, a mobile device, a keypad, a card reader, or a biometric data reader. A report access control system may then validate the identity of the user using the PID provided. After verifying the identity of the user, the report access control system may initiate unlocking or locking of the user's credit files at each of a plurality of credit bureaus. In one embodiment, the credit files may be unlocked or locked for a predetermined period of time, and the predetermined period of time may be specified by the user.

Some embodiments of the systems and methods described herein may allow merchants to increase credit opportunities, especially in point of sale environments. For example, a merchant can request a user to enter a PID, such as a PIN code, into a keypad (e.g., a credit card reader keypad). After the user enters a PID, the merchant can request a credit file. In other embodiments, the PID is sent directly to the credit bureau, access control system, or the like such that the merchant does not have access to the PIDs, preserving security of the PID. For example, a user interface and API from the access control system may be provided via the merchants POS terminal (e.g. a card reader and keypad at checkout) so that information provided by the user to unlock the user's credit file, such as a PID, is transmitted directly to the access control system without allowing the merchant to store the PID.

If a user's credit file is locked when a merchant requests access, the merchant will be denied access to the credit file. Advantageously, in response to such an access request, the access control system discussed herein can send a real-time alert to the user allowing the user to unlock the credit file and/or a user's preferences may allow the credit file to unlock. The user may be able to quickly and easily lock or unlock their credit files after the desired credit pulls have occurred by entry of their PID. Thus, the system may increase credit opportunities for merchants and other financial service providers of mortgages, automobile loans, credit card accounts, and the like by allowing them to access credit files quickly.

Various embodiments discussed herein include details regarding specific implementations of an access control system, including interactive user interfaces that improve the functioning of the basic display function of the computer itself. These interactive user interfaces improve the ability of the computer to display information and interact with the user, such as by allowing a user to quickly and easily provide access to credit data. Design of computer user interfaces “that are useable and easily learned by humans is a non-trivial problem for software developers.” (Dillon, A. (2003) User Interface Design. MacMillan Encyclopedia of Cognitive Science, Vol. 4, London: MacMillan, 453-458.) The present disclosure describes various embodiments of interactive and dynamic user interfaces that are the result of significant development. This non-trivial development has resulted in the user interfaces described herein which may provide significant cognitive and ergonomic efficiencies and advantages over previous systems. The interactive and dynamic user interfaces include improved human-computer interactions that may provide reduced mental workloads, improved decision-making, reduced work stress, and/or the like, for a user. For example, user interaction with the interactive user interface via the inputs described herein may provide an optimized display of, and interaction with, a credit report access control system.

Example System Architecture

FIG. 1 is a block diagram illustrating one embodiment of a credit report access control system 100 that is in communication with a user computing device 162 and a plurality of credit bureaus 164 (including credit bureaus 164A, 164B, 164N that are representative of any quantity of credit bureaus) via a network 160. Generally, the credit bureaus 164 comprise one or more computing systems that gather and make available information about how users use credit, such as a credit score or credit report, for example.

The computing device 162 may be associated with any user, such as an individual consumer, a retailer, an account provider, etc. The user computing device 162 may comprise one or more computing system, mobile device, keypad, card reader, biometric data reader, or other device that allows a user, such as a user, merchant, bank, etc., to exchange information with the credit report access control system 100. In particular, the user computing device 162 may allow the user to interface with the system 100 in managing access to the user's credit data. In addition, the user computing device 162 may allow the user to unlock or lock credit files at multiple credit bureaus by communicating with the credit report access control system 100. In a merchant environment, such as a department store, the computing device 162 may include a keypad, such as a keypad associated with a credit card reader at a store checkout, that allows a user to enter in information to unlock (or lock) their credit files at the plurality of credit bureaus 164 nearly instantaneously and using a simplified process.

The credit report access control system 100 may be used to implement certain systems and methods described herein. For example, in one embodiment the credit report access control system 100 may be configured to implement a credit file freeze or lock and/or a credit file thaw or unlock process. The functionality provided for in the components and modules of the credit report access control system 100 may be combined into fewer components and modules or further separated into additional components and modules. The various computing components and functionality described herein with reference to the system 100 may also be included in any of the discussed user computing devices 162.

The credit report access control system 100 may include, for example, a computing system, such as a computing device that is IBM, Macintosh, or Linux/Unix compatible. In one embodiment, the computing device comprises one or more servers, desktop computers, laptop computers, cell phones, personal digital assistants, and/or kiosks, for example. In one embodiment, the credit report access control system 100 include a central processing unit (“CPU”) 105, which may include one or more conventional microprocessors. The credit report access control system 100 may further include a memory 130, such as random access memory (“RAM”), a flash memory, and/or a read only memory (“ROM”), and a mass storage device 120, such as one or more hard drives, diskettes, and/or optical media storage devices. Typically, the components and modules of the credit report access control system 100 are connected using a standards based bus system. In different embodiments, the standards based bus system could be Peripheral Component Interconnect (PCI), Microchannel, Small Computer System Interface (SCSI), Industrial Standard Architecture (ISA) and Extended ISA (EISA) architectures, for example.

The credit report access control system 100 is generally controlled and coordinated by operating system software, such as Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, Windows Vista, Windows 7, 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 credit report access control system 100 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, and I/O services, and provide a user interface, such as a graphical user interface (“GUI”), among other things.

The illustrative credit report access control system 100 may include one or more commonly available input/output (I/O) devices and interfaces 110, such as a keyboard, mouse, touchpad, and printer. In one embodiment, the I/O devices and interfaces 110 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. The credit report access control system 100 may also include one or more multimedia devices 140, such as speakers, video cards, graphics accelerators, and microphones, for example.

In the embodiments of FIG. 1, the I/O devices and interfaces 110 provide a communication interface to various external devices. In the embodiments of FIG. 1, the credit report access control system 100 is coupled to a network 160 that comprises any combination of one or more of a LAN, WAN, or the Internet, for example, via a wired, wireless, or combination of wired and wireless, communication link 115. The network 160 communicates with various computing devices and/or other electronic devices via wired or wireless communication links.

In the illustrative embodiments of FIG. 1, the credit report access control system 100 includes, or may be coupled to, for example via a network connection, a device that includes a user lock status & preferences data structure 161. The user lock status & preferences data structure 161 may include lock or unlock information that associates users with respective access codes for locking and/or unlocking the user's credit files at each of a plurality of credit bureaus. The user lock status & preferences data structure 161 may be implemented in any suitable format, including objects, tables, arrays, hash tables, linked lists, and/or trees. The user lock status & preferences data structure 161 may be implemented and stored in a database. As used herein, a database may comprise 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, an object-oriented database, and/or a record-based database. The data structure 161 may be stored in any computer readable medium, including a hard drive, a random-access memory, an optical disc, a tape drive, and/or a diskette.

The information stored by the user lock status & preferences data structure 161 may include a user personal identifier (“PID”) that may be selected by a user. In one embodiment, the user PID is associated with multiple credit bureau specific access codes that are associated with the user's credit file at respective credit bureaus and that are configured to initiate locking or unlocking (and/or other access control operations) of the user's credit files at the respective credit bureaus 164. In addition to the components and devices that are illustrated in FIG. 1, the credit report access control system 100 may be connected to other data structures that store access codes for user credit files and/or other computing devices through a bus or network 160.

The user lock status & preferences data structure 161 may include user lock status of the credit file. For example, the data structure 161 may include data identifying whether a credit file is frozen, unfrozen, locked, unlocked, thawed, and/or other access controls that the user has requested for the user's credit file. As noted above, a “credit file” and/or “credit data” may refer to an entire credit file of a user, a portion of the credit file, credit data, financial or transactional data, personal data, and/or other data related to an individual.

In some embodiments, the user lock status & preferences data structure 161 may store preferences. A user preference may include a preference on actions to take upon an inquiry for a credit file while the credit file is locked. For example, preferences may include whether an alert is sent to the user regarding a credit data request. Preferences may also include the type of information to include in such an alert. Preferences may also include whether an option to unlock the credit data should be included in the alert, and/or may include an automatic unlock of the credit file. The unlock may be customized (e.g. for a particular period of time, for a particular requesting entity, for a portion of the credit file). The preferences may be a default preference, may be inputted by the user, or may be determined based on other relevant circumstances. FIG. 3, discussed in further detail below, includes an example of a portion of such as user lock status & preferences data structure 161.

In the embodiment of FIG. 1, the credit report access control system 100 also include application modules that may be executed by the CPU 105. In the example embodiment of FIG. 1, the application modules include the registration module 150 and the access control module 155, which are discussed in further detail below. In the embodiments described herein, the credit report access control system 100 is configured to execute the registration module 150, among other modules, to create a single point of service for users to lock, unlock, or apply further custom access controls on their credit files at multiple credit bureaus 164A-N. For example, in one embodiment, the registration module 150 allows a user to set up the file locking service by creating an account. The registration module 150 may request a user to provide enrollment information, including information that verifies their identity, such as a name, driver's license number, address, social security number, birth date, phone number, account number, and the like. The registration module 150 may then request the user to select a user PID. When the user PID is later provided to the credit report access control system 100, the credit report access control system 100 may initiate locking or unlocking of credit files of the user at a plurality of credit bureaus 164A-N using access codes associated with the user's credit files at respective credit bureaus.

The registration module 150 may further be configured to send requests to the plurality of credit bureaus 164 to obtain access codes and/or other information about unlocking or locking credit files of a registering user. In one embodiment, the registration module 150 may automatically register the user at the plurality of credit bureaus 164 and receive the respective access codes for locking/unlocking the user's credit files at those credit bureaus 164. In one embodiment, an access code authenticates the identity of the user at a particular credit bureau for credit file locking or unlocking. The registration module 150 may store these credit bureau specific access codes in the user lock status & preference data structure 161 and associate some or all of the credit bureau specific access codes of a user with the user PID of the user.

The credit report access control system 100 may also execute the access control module 155 to provide a simplified mechanism or interface to lock or unlock credit files at the plurality of credit bureaus 164A-N. In one embodiment, the access control module 155 can receive a user PID that is inputted by a user from user computing device 162, or other device. After receiving the user PID, the access control module 155 may access the user lock status & preferences data structure 161 to translate the received user PID into access codes corresponding to multiple respective credit bureaus. The access codes may then be sent over the network 160 to corresponding respective credit bureaus 164 to lock or unlock one or more credit files of the user.

In some embodiments, when the credit report access control system 100 is operated or associated with one or more of the credit bureaus 164, the user PID may be used to lock or unlock credit files without any translation. This may be particularly advantageous in reducing processing time that may otherwise be expended to translate a user PID into lock or unlock information.

FIG. 2 is a block diagram illustrating an example configuration of a system that provides real-time user alerts in response to credit inquiry requests when the user's credit file is locked. In the embodiment illustrated, credit data is shown being received by a credit bureau 164 from various entities, such as a bank 230, a credit card company 231 and an account provider 232. Credit data may additionally be received from lenders and/or other financial institutions (not illustrated). The credit bureau includes a processing queue 242 for receiving and routing the incoming credit data. Tradeline data, e.g., information regarding credit and debit accounts of the user, may be transmitted to the credit data store 222. For example, a credit module operated by the credit bureau 164 may determine appropriate credit data and other user information to be stored in credit data store 222 based at least in part on the data received from the various entities 230-232.

The credit data store 222 may be monitored periodically, such as via a batch process, to identify changes to credit data stored by the credit bureau. For example, the credit bureau may nightly scan the credit data store for changes to user credit files. In one embodiment, the batch monitor 206 looks for changes to credit files of users that are enrolled in a credit monitoring service of one or more affiliates of the credit bureau. A credit monitoring service may generally include a service with which individuals maintain an account in order to be alerted when a change posts to the individual's credit data or credit report, which may include an inquiry being noted in the individual's credit data. In the embodiment of FIG. 2, a user credit monitoring service performs and/or requests that the batch monitor 206 perform a batch process to identify changes to credit data associated with customers of the user credit monitoring service. For example, the credit monitoring service may periodically pull identified credit changes and determine which alerts correspond to customers of the credit monitoring service. Once customers for particular changes are identified, information regarding the change may be transmitted to the user. A few hours to a few days may pass between the credit data being received by the credit bureau and the provision of notifications to users regarding changes to the affected user.

Also shown in FIG. 2 are requests for user credit data that might be received by the credit report access control system 100. Depending on the embodiment, the credit report access control system 100 may be operated and/or controlled by the credit bureau 164 or may be operated and/or controlled by a separate entity, such that communications between the system 100 and the credit bureau 164 are via one or more network connections. Credit requesting entities, such as credit requesting entity 202, may include lenders, car dealers, brokers, retailers, landlords, and/or any other entity that is interested in user credit data. Requests for credit data are generally referred to herein as inquiries, inquiry requests or credit inquiry requests. In addition to providing the requested credit data (such as a credit report regarding the user) to the credit requester, inquiry requests may be recorded in the credit file of the user, which may be stored in credit data store 222. Thus, inquiry requests can be monitored by the batch monitoring processes that are performed by the credit bureau 164 (such as by batch monitor 206) and/or an affiliate of the credit bureau (such as by credit monitoring service), which may include a credit data reseller or a third-party credit monitoring service. However, providing alerts in this manner may result in the customer of a credit monitoring service receiving notification of an inquiry request days after the inquiry request was made. If the inquiry request was fraudulent (e.g., made by someone that was not authorized to receive credit data associated with the customer and/or to open a credit account in the name of the customer), the customer would be better served to receive the notification earlier, such that action may be taken to minimize damage to the customer's identity, finances and/or credit file. Additionally, if the user's credit file is locked, such that the credit file of the user is not provided to the requesting entity 202, a change (e.g., a soft or hard inquiry) in the credit data of the user may not be recorded and, thus, the user would not receive any indication of the received credit inquiry. As discussed below, the system 100 addresses this technological problem by providing a system and user interfaces that allow a user to receive alerts of credit inquiries, even when the user's credit file is locked, and determine desired actions to be taken in response to the credit inquiry.

In the embodiment of FIG. 2, the credit report access control system 100 provides users with real-time notifications of inquiry requests. In this embodiment, the credit report access control system 100, which initially receives the inquiry request from the credit requesting entity 202, provides inquiry request notices upon receipt of a new inquiry alert from a credit requesting entity 202. For example, the credit bureau may provide the inquiry request notices to the credit report access control system 100 regardless of whether the credit file of the user is locked. Additionally, in cases where credit data of the user would be provided to the requesting entity 202, an inquiry request notice may be provided to the user prior to providing the requested credit data to the credit requesting entity 202 and/or recording the inquiry request in the user's credit data (e.g., prior to storing data associated with the inquiry request in credit data store 222). In other embodiments, the credit report access control system 100 may provide the inquiry request notices substantially contemporaneously with recording the inquiry request in the user's credit data and/or retrieving credit data to provide to the credit requesting entity.

Credit inquiry alerts may be provided to the user in various manners, as described further below. For example, as illustrated in the example of FIG. 2, inquiry alerts generated by the credit report access control system 100 may be sent to a user device 162. Similarly, the user may access alert details by requesting additional information from the credit report access control system 100. The credit report access control system 100 may retrieve contact information for the user from an account data store operated by a credit monitoring service, for example, which may include an email address, telephone number, account user name, etc. The credit report access control system 100 may send or otherwise provide an alert to the user and/or a user device 162 associated with the user based on the retrieved contact information. Alerts may be delivered via any medium, such as, for example, an online portal that is accessible to alert members (e.g., a credit monitoring website), SMS text message, push notification to a mobile device (e.g., to a credit monitoring mobile application), email, printed digests, a mobile application, automated or personal telephone call, etc. In some embodiments, the alert may include detailed information associated with the inquiry, such as information identifying the credit requesting entity 202, the time of the inquiry, the data requested (e.g., whether a full credit report was requested), etc. In other embodiments, the alert may not include any specific information regarding the inquiry, but may notify the user that he should access his account with the credit monitoring service and/or review his credit data with credit bureau 164 in order to obtain further details.

In some embodiments, the user device 162 may transmit an unlock authorization. The unlock authorization may be sent to the credit report access control system 100, to the credit bureau 164, or any other entity that may perform or process an unlock action on a credit file. The user device 162 may display a user interface allowing the user to select an unlock authorization, which then would send an unlock authorization. Example of user interfaces that may be provided to the user to allow easy, yet secure, access to the user's credit data are provided in FIGS. 6 and 7.

The user device 162 may automatically send an unlock authorization based on a user's predetermined preferences (e.g. preferences stored in the user lock status & preferences data structure 161). In other embodiments, an unlock authorization may not need to be sent, but may automatically be determined (e.g. within the credit report access control system 100) based on the user preferences. For example, an unlock authorization may be initiated in response to the inquiry request of the credit requesting entity 202 and the preconfigured preferences for the credit file stored in the user lock status & preferences data store 161. The unlock authorization may be for a particular credit requesting entity 202, for a particular time period, and/or include other variations specific to the user and/or requesting entity 202. In a similar manner, the user may provide a lock authorization, such as of all of the user's credit data, for the particular credit requesting entity 202, for a portion of the credit data, and/or based on other preferences of the user.

Example User Preferences

FIG. 3 is a diagram illustrating a portion of an example user lock status & preferences data structure, for example the user lock status & preferences data structure 161 of FIG. 2. As shown, the data structure 161 may include enrollment information 310 associated with a user, such as a name, address, phone number, email address, and the like. The user lock status & preferences data structure may also include various personal identifiers 320 associated with the enrollment information of respective users that authenticate a user's identity to the credit report access control system 100. In the illustrated embodiment, a user personal identifier may comprise a user-selected PID, e.g., a PIN, a username/password combination, biometric data (e.g. fingerprint or eye scanner), and/or other information that can be used to authenticate a user.

In addition, the user lock status & preferences data structure 161 further includes access codes 330 that can be used to lock or unlock credit files of the associated user at respective credit bureaus, including access code 330A that is usable to apply access restrictions for Joe Smith at a first credit bureau and access code 330B that is usable to apply access restrictions for Joe Smith at a second credit bureau. In the embodiment shown in FIG. 3, the access codes include numerical codes or identifiers, but could include any other form of data, such as alphanumeric, encrypted, hashed, etc. data. In the embodiment shown in FIG. 3, once a particular user is identified in the user lock status & preferences data structure, e.g., by locating a user PID (or other personal identifier 320) received from a merchant POS device or user computing device in the data structure, the access codes for each of multiple credit bureaus are identified and may be used to initiate the requested access controls, such as locking or unlocking the user's credit file, without further involvement from the user.

The user lock status & preferences data structure 161 may also include user preferences 340 for additional access controls of the user's credit data. User preferences may indicate, for example, actions for the system 100 to take upon a credit inquiry request, including actions when the credit file is locked. For example, the user preferences 340 may include a toggle that indicates whether inquiry alerts received when the credit file is locked are to be sent to the user. The user may also indicate one or more other entities (such as a credit bureau, the credit requesting entity, or other third parties) to which alerts should be sent. The user preference may include the type of information included in the alert (such as whether information on the requesting entity should be added to the alert). The user preference may also include an unlock or lock time period that allows the credit file to be unlocked for a particular period of time (e.g. 5 minutes) allowing for the requesting entity to access the credit file. The user preferences may also include indications of access rights associated with particular purposes of inquiry alerts. The user preferences may also include preferences for providing only portions of the user's credit data to particular entities, for particular purposes, and/or based on other criteria. In some embodiments, user preferences may include any other rules for controlling access to the user's credit data.

Example Real-Time Alert and Selective Credit Access Process

FIG. 4 is a flowchart illustrating one embodiment of a method for providing a real-time inquiry alert to a user with an active lock on the user's credit data, with an option for the user to unlock the credit file for immediate access. Depending on the embodiment, the method of FIG. 4 may include additional or fewer blocks and/or the blocks may be performed in a different order than is illustrated. For ease of discussion, the method of FIG. 4 is described below as being completed by the credit report access control system 100. However, the method may be implemented by any other device, or combination of devices, such as computing devices associated with a credit bureau, an affiliate or credit reseller associated with a credit bureau, and/or a credit monitoring service.

The illustrative method begins at block 405, where the credit report access control system 100 receives an inquiry request requesting credit data associated with an individual. The inquiry request may include, for example, a request for a credit report, a credit score, and/or specific portions or fields of credit data associated with the individual. In some embodiments, the credit inquiry may be sent by a computing system associated with the requesting entity 202 to a credit bureau or credit reseller, which may in turn provide the inquiry or notification of the inquiry to the credit report access control system 100. For example, the credit bureau or credit reseller may operate in a manner in which notification of a credit inquiry is automatically sent or otherwise provided to the access control module when the inquiry is received, such that the credit report access control system 100 may process the inquiry notification for alert purposes in parallel with, prior to, or otherwise without regard to the credit bureau's processing of the request for credit data. In other embodiments, the credit report access control system 100 may receive the credit inquiry directly from the credit requesting entity.

At block 410, the credit report access control system 100 analyzes the inquiry request to identify user identity information associated with the inquiry request. In some embodiments, analyzing the inquiry request may include parsing the request to extract user identity information, such as a name, social security number, address, employer, etc. In some embodiments, the system 100 receives the user information from a third party, such as directly from a credit bureau or a credit monitoring service provider.

Next, in block 415 the credit report access control system 100 identifies any access control restrictions associated with the user's credit data, such as determining whether the credit file of the user is locked, unlocked, frozen, unfrozen, thawed, or other condition. In the example process of FIG. 4, if the credit file is unlocked (or unfrozen or in another condition that would allow release of the credit data in some embodiments), then at block 420 the system 100 proceeds with the release of the credit data. In some embodiments, the release of credit data is subject to one or more regulations, such as FCRA regulations in the United States, such that credit data may only be releases if there is a “permissible purpose” for the release. The system 100 may determine whether the credit data of the user should be released pursuant to any such regulations or another entity may make the determination. Returning to decision block 415, if the credit file of the user is locked (or frozen or in another condition that would disallow release of the credit data in some embodiments), then the method proceeds to block 425.

At block 425, the system 100 retrieves user preference information associated with the user. In some embodiments, the user preference information may be retrieved from a data store associated with members of a notification service (e.g., a credit monitoring service), such that the user preference information includes details provided by the individual when signing up for the service. For example, a user may sign up for a credit monitoring service, and during enrollment, may have an option to select receiving an alert upon a credit inquiry and/or other user preferences for the content, delivery channel, etc. of any alerts/notifications. In other embodiments, the user preference information may alternatively or additionally be retrieved from one or more other data sources, such as the user lock status & preferences data structure 161 discussed above, or from profile data or account data maintained by a third-party service with which the individual maintains contact information and/or other personal information. The retrieved contact information may include, for example, a phone number, email address, mailing address, account name or user name, IP address, or device identifier. In some embodiments, the system 100 may additionally retrieve notification preferences associated with the individual, such as information identifying the method of notification, the amount of information in the notification, the frequency or timing of the notification, or the like.

Next, at block 430, the system 100 generates an alert for delivery to the user. Advantageously, the alert may be generated even if the user's credit file is locked, or without regard to any other access restrictions associated with the user's credit data or how the credit bureaus may or may not indicate the inquiry request in the user's credit data. In some embodiments, generation of the alert may be based on the inquiry being received without requiring the credit file to be unlocked, and not dependent on a change to stored credit data of the user. In some embodiments, generating an alert may include storing information indicating that an alert associated with the individual is available, such that the individual will be notified of the alert at a later time, such as during a batch process. In other embodiments, the generated alert may be delivered or otherwise provided to the user immediately after the alert is generated. The information included in the generated alert may be limited, in some embodiments, to an indication that an inquiry has been received regarding the individual. In other embodiments, the generated alert may include details regarding the inquiry, such as information identifying the requesting entity (such as a financial institution or other entity described above), a third party associated with the requesting entity (such as a retail store associated with a credit card issuer that submitted the inquiry), a time and date of the inquiry, the data requested (e.g., whether a full credit report was requested), and/or a geographic location associated with the inquiry.

Once the alert has been generated, the system 100 delivers or sends the generated alert to the individual (such as to a user computing device associated with the individual) based on the notification preferences information retrieved at block 425. As will be appreciated, the alert may be provided in a variety of ways depending on the contact information, contact preferences and/or the embodiment. For example, providing the alert may include, but is not limited to, sending a notification to a mobile application on the user computing device (e.g., a smart phone), causing activation of the mobile application on the user computing device without any user interaction, and displaying the alert message on the user mobile device. In some embodiments the alert may be transmitted by sending a text message, sending an email, making a phone call, leaving a voicemail, sending a letter, providing alert information when the user logs into an account or launches an application, etc. In some embodiments, an alert may be delivered to the individual regardless of whether the inquiry is a hard inquiry of soft inquiry. In other embodiments, alerts may only be provided to the user for hard inquiries. In embodiments in which an individual may receive an alert associated with a soft inquiry, the alert may notify the user that there “may” be a change to the user's credit report, since a soft inquiry might never post to the individual's credit report.

In some embodiments, the system 100 may communicate with the credit bureau 164 and/or credit requesting entity 202 to operate in a closed loop manner. For example, in one embodiment the credit bureau may wait for confirmation from the user that credit information may be released to the credit requesting entity 202 before providing the user's credit information to the credit requesting entity. For example, the inquiry alert may request that the user respond within a specified time period indicating whether the credit data should be released to the credit requesting entity 202, and may default to either releasing or not releasing the data if no response is received, depending on the embodiment. In some embodiments, the time period may be included in the user lock status and preferences data structure 161, for example.

In block 435, in some embodiments, alerts may provide the receiving users the ability to unlock credit data, allowing a particular requesting entity (or all requesting entities in some embodiments) to access the user's credit data. If the user selects the option to unlock the credit data, the method continues to block 440 where the credit data is unlocked. The credit data may also be unlocked based on user preferences stored in the user lock status and preferences data store 161. For example, the credit data of the user may be unlocking according to particular time limit, requesting entity, requested purpose, or other preferences established by the user and/or default unlock preferences (such as user preferences 340 discussed above). Thus, if the user has indicated that unlocks are to be for 15 minutes and only to the particular requesting entity associated with the alert, credit data of the user is available to only the particular requesting entity for 15 minutes.

As an example of the real-time alert and unlock option that may be provided by the system 100, a user may receive an alert indicating that credit information for the user has been requested by a given entity that is transmitted immediately after the credit inquiry is received by the system 100 and/or a credit bureau, such as within seconds or minutes of a merchant requesting credit data of the user. In some embodiments, the alert includes information regarding the requesting entity, such as identifying a name of the requesting entity (e.g., “Big Box Department Store”). If the user is not familiar with the requesting entity, the user can respond to the alert requesting credit information remains locked. The response, or a subsequent response, may indicate that the requesting entity should be provided with an indication that the request may be associated with actions of an identity thief. Additionally, the response, or a subsequent response, may request one or more protective actions, such as putting additional access restrictions on the user's credit file, for example, extending the lock to all requesting entities if it is currently for only certain requesting entities or adding a lock for the particular requesting entity. These actions may be selected individually or collectively based on the user's preferences, for example. In other embodiments, fewer or additional actions may be taken in response to a user indicating that a received alert is not a result of activity by the user. In some embodiments, an electronic alert may include a link or button that the user can select in order to allow the credit data to be provided in response to the inquiry and another link or button that the user can select in order to prevent the credit data from being provided.

Depending on the embodiment, the determination at block 435 may be performed based on various data, inputs, and/or criteria. For example, the authorization to unlock the user's credit file may be received from the user (e.g., via a mobile application into which the user provides an unlock input), determined by circumstances of the situation (e.g., rules that may automatically unlock the user's credit file based on the particular requester, purpose of the request, etc.), determined based on user or system preferences in a data store, or the like.

If at block 435 authorization is not given to unlock the credit file, the method continues to block 445 where the system 100 determines if an access exception applies. An access exception applies when credit data is provided regardless of whether the user's credit data is locked. For example, federal, state, and local government agencies have access to credit data in some circumstances (e.g. in support of a child support claim). In this case, regardless of whether the user authorizes unlocking of credit data at block 435, the credit data of the user would be released at block 420. If an access exception does not apply, then the method would proceed to block 450 where access to the credit data is blocked so that the requesting entity does not obtain any of the user's credit data. In some embodiments, block 445 is performed concurrently or before block 435, where if an access exception applies, then the credit data is provided to the requesting entity without having to determine if authorization to unlock the credit file has been received from the user.

Example User Interfaces & Additional Embodiments

FIGS. 5A-5F are user interfaces illustrating example embodiments for providing an alert and allowing the user to quickly and easily unlock the credit file. The user interfaces in FIGS. 5-8 are adapted for display on a mobile device, but similar user interfaces may be provided on any other computer display, such as in a browser on a display screen. In FIG. 5A, an example dashboard for a user's credit monitoring account, for example, is illustrated. In this example, the dashboard includes various statistics, such as outstanding debt, balance on accounts, an option to access a full credit report, and a credit score (e.g. FICO score). The user can swipe left (or right, or provide another input in other embodiments) to access the user interface of FIG. 5B, where the user account is shown to be “unlocked.” In this example embodiment, the user is notified of this “new feature” to lock and unlock the user's credit file via the application, and is given the option to click “What is this feature?” that will allow the user to access the user interface of FIG. 5C. The user interface of FIG. 5C provides a description of the locking feature and related advantages. The description explains that a credit file can be protected using biometric scanners (e.g. a finger print) to protect credit information, to prevent unauthorized activity on a credit report, ease of locking and unlocking, and preventing third parties from accessing a report. The user interface also allows the user to select user registration which enables the user to register to use the lock/unlock feature of the application, such as using a user interface similar to FIG. 5F. In some embodiments, the user is not required to separately register to use the lock/unlock feature. For example, the lock/unlock functionality discussed herein may be providing to users of a credit monitoring service, whether a free or paid service. In some embodiments, a user may be enrolled in a credit monitoring service that is free, and may be provided with an offer to upgrade the free account to a paid account in order to access the real-time locking/unlocking features discussed herein.

Alternatively in FIG. 5A, the user can select an option to see the full credit report, which would present a user interface similar to the example of FIG. 5D. The user interface can show details on account information (e.g. total open or closed accounts), credit inquiries (e.g. reported inquiries by requesting entities), public records, a status on the credit report (e.g. locked, unfrozen, thawed), personal information of the user, and summary statistics (e.g. debt, credit available). The user can select the lock/unlock option which can transition to a user interface similar to the example in FIG. 5E. In this example, the user interface includes a description of a lock and an option to register for the lock/unlock option (similar to that of FIG. 5C). FIG. 5E can also be accessed by clicking the option in FIG. 5B to lock/unlock their credit report. Then, the user can select an option to register for the lock/unlock option, which would transition the user interface to the one in FIG. 5F, where the user can register for the lock/unlock feature.

FIGS. 6A-6J are user interfaces illustrating another embodiment for displaying various credit data of a user and providing lock and unlock functionality. FIG. 6A illustrates an example dashboard for an account of a user showing various statistics. The dashboard can include aspects of a user's credit file, e.g. FICO score over a period of time, a score simulator, outstanding debt, suggestions on how to improve a credit score, viewing the full credit file, and a lock/unlock function. The user may have the option to view the full credit file, which would transition the user interface to that of FIG. 6B. The user interface of FIG. 6B can show particular details of a credit file, such as the total number of accounts, FICO scores and factors that can help or hurt such a score, inquiries of credit data, public records, an option to lock or unlock, and information on the user such as personal information or other statistics (debt or credit available). The user can click the lock/unlock option transitioning the user interface to that of FIG. 6C. Alternatively, the user can click the lock/unlock option at the user interface of FIG. 6A to directly transition to the user interface of FIG. 6C. FIG. 6C shows that the credit report is “unlocked,” and provides a description on what it means to lock a credit file (similar to that of FIG. 5C). The user can lock the credit report via a user interaction input. For example, the user can press and hold to lock the credit report, as shown in FIG. 6D where while holding the lock button, the user interface shows that the credit report is locking, and will do so as a security measure over a period of time. After the period of time elapses, the credit report is shown to be locked in FIG. 6E.

FIG. 6F illustrates an example dashboard (similar to that of FIG. 6A) illustrating a credit file that is locked. The user can select to view the full credit report which is shown in FIG. 6G (similar to that of FIG. 6B) while showing that the credit report is locked. The user can select the lock/unlock option in FIG. 6F or 6G to transition the user interface to the lock/unlock screen where an option is available to unlock the credit file and a description is provided describing what locking/unlocking means (similar to that of FIG. 6C). The user can unlock the credit report via a user interaction input.

In some embodiments, such as in example user interfaces FIGS. 6C-6E, a user can lock their credit file through a “press and hold” gesture on an “unlock” icon displayed on the display. In some embodiments, the press and hold gesture requires the user to touch the icon for at least a predetermined time, such as 3 seconds, before unlocking of the user's credit file is initiated. Thus, if the user touches the icon (intentionally or unintentionally) for only 2 seconds, the credit unlock will not be initiated. In some embodiments, while the unlock icon is pressed the user interface is updated as the time pressed increases towards the predetermined time. For example, when the unlock icon is initially touched, the “Unlocked” indication may change to a “Locking” indication, then as the icon continues to be pressed, dots on either side of “Locking” appear, such as 1 dot on each side after 1 second pressing, 2 dots after 2 seconds pressing, etc., with the dots and “Locking” indication replaced by “Unlocked” in the user interface. In other embodiments, other visual indications may be used to indicate a time period that the user must press the icon to initiate locking of the credit file and/or a dynamically updating visualization of the current time pressed. Other visualization may indicate dials, bars, numerical counters, etc. As shown in FIGS. 6H-6J, similar user interface interactions may be performed to initiate unlocking of a locked credit file. Other visualizations and/or user inputs may be required for locking/unlocking of credit files, such as, for example, a pin or code, a simple click, a puzzle, other biometric sensors.

FIGS. 7A-7B are user interfaces illustrating one embodiment for a credit inquiry alert on a mobile phone that allows the user to authorize an unlock. FIG. 7A illustrates an example alert 705 displayed on a mobile phone notifying the user that a request for credit data has been received by a requesting entity, and also confirming that the credit file of the user is locked. Alert 705 may be displayed at block 430 of FIG. 4, for example. In this example, the alert 705 is a push notification that automatically displays on the mobile device regardless of the applications opened or active on the mobile device. Thus, the alert advantageously provides the user with information regarding the inquiry immediately after the credit request is made by the requesting entity. As discussed above, the alert can activate an application on the mobile device, be delivered via SMS, or in any other format.

In the example of FIG. 7A, the user can select the alert to cause information to be presented to the user, such as the information shown by the user interface in FIG. 7B. Depending on the embodiment, the alert can provide various information on the requesting entity, explanation on certain options for the user, and buttons enabling a user to respond. For example, the alert may provide the name, address, or other information on the requesting entity. The explanation may provide options, such as unlocking the report for only the requesting entity, continue the lock on the requesting entity, unlocking for a period of time or particular purpose, unlocking portions of the credit data, or the like. The user can then press and hold the unlock icon for a period of time (e.g. 3 seconds) to unlock the credit file for the requesting entity (here, “XYZ Car Company”), such as via the various user interface interactions or gestures discussed above.

FIGS. 8A-8C are example user interfaces illustrating additional credit-related information that may be provided to a user, such as credit history. FIG. 8A illustrates an example user interface summarizing alerts and history. For example, the first entry 802 shows the credit file as locked, the second entry 804 shows the credit file as unlocked, and the third entry 806 shows a specific credit inquiry that was blocked in view of the user's credit file being locked. FIG. 8B shows more information on the credit lock of the first entry 802 with a description on the lock feature of the credit file and an option to “change status,” which would enable the user to unlock the credit file. FIG. 8C provides detail on the blocked inquiry request in the third entry 806. For example, the additional information in third entry 806 can provide information on when the request was made, information on the requesting entity, the purpose of the inquiry, the type of information requested, and/or the credit bureau (or other third party) that the request was made to.

FIGS. 9A-9D are portions of a user interface illustrating example animations indicating lock/unlock status of a consumers regulated data (e.g., credit data). The illustrated user interface portions may be part of an alert provided to the user, such as in response to an inquiry request being received, part of a mobile application (e.g., a credit monitoring application), part of a desktop application, part of a website that may be displayed in a browser, or any other user interface that may be provided to the user to indicate lock/unlock status and allow easy updating of that status. In this particular example, FIG. 9A includes an icon of an open physical lock with the text “Report Unlocked” shown. This figure further indicates that the user may “Press and Hold to Lock Experian Credit Report.” Thus, in this embodiment when the user touches the blue circular icon, the icon is updated to indicate a locking process has been initiated. For example, FIG. 9B shows concentric circles around the central icon (which is now updated to show the physical lock image in a locked position and in red rather than blue). In some embodiments, the concentric circles are animated such that they each begins small immediately around the central lock icon and is animated as diameter increases, causing an effect similar to ripples moving outward after dropping a stone in water. In this embodiment, the colors are adjusted as the credit data lock/unlock status changes, here from blue when in the unlock state to red when in the locked or locking state. FIG. 9C illustrates an example of how this particular user interface may be updated after the locking process is completed, such as when the user maintains touch on the lock icon of FIG. 9B for a predetermined time, such as three seconds, five seconds, 10 seconds, etc. Thus, the illustration in FIG. 9C indicates to the user that the credit data is now locked.

FIG. 9D illustrates an example visualization that may be provided when the user unlocks the credit data. Thus, from the locked state (e.g., FIG. 9C), the user may press the lock icon for a predetermined time to unlock the credit file. During this predetermined time, concentric circles similar to those in FIG. 9B may be displayed, such as in an animated pattern similar to discussed above (e.g., concentric circles that enlarge like ripples around a stone dropped in water). In some embodiments, the animation may be mirrored between the locking and unlocking actions. For example, during the locking action (e.g., FIG. 9 B), the circles may move outward from the central lock icon, while during the unlocking action (e.g., FIG. 9D), the circles may move inward towards the central lock icon. In other embodiments, other visualizations that indicate lock/unlock status, as well as animations or other indications of user interactions that cause changes of the lock/unlock state, may be used in conjunction with any of the processes or systems discussed herein.

Variations and Other Embodiments

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.

All publications and patent applications mentioned in this specification are herein incorporated by reference in their entirety to the same extent as if each individual publication or patent application was specifically and individually indicated to be incorporated by reference.

Claims

1. A system comprising: a secured and regulated data store that stores regulated user credit information associated with a plurality of consumers, wherein the regulated user credit information is associated with member information indicating respective users enrolled in a fraud notification service, wherein the respective users enrolled in the fraud notification service comprise a subset of the plurality of consumers, wherein the secured and regulated data store is configured to be controlled by an access control system, wherein data stored in the secured and regulated data store indicates that a first subset of the plurality of consumers have locked credit files and a second subset of the plurality of consumers do not have locked credit files;a computing device in communication with the secured and regulated data store and that is configured to prevent access to locked credit data of the first subset of a plurality of users and in response to an unlock request from a corresponding user, to override access preventions for one or more requesting entities but otherwise maintain the access preventions, the computing device further configured to: receive, from a user, a request to lock credit data associated with the user;execute a locking module of the access control system that causes the access control system to lock the credit data associated with the user in the secured and regulated data store;receive an inquiry request from a requesting entity, wherein the inquiry request includes a request for the credit data associated with the user, wherein the inquiry request is transmitted by the requesting entity in response to an online loan application initiated by the user;determine that the user is enrolled in the fraud notification service based at least in part by comparing inquiry information associated with the inquiry request and member information associated with the user, wherein the member information compared includes at least one of a name, a social security number or an address; andin response to receiving the inquiry request and determining that the user is enrolled in the fraud notification service: retrieve contact information associated with the user, wherein the retrieved contact information includes at least one of a phone number, an IP address, or a device identifier associated with a mobile device of the user;determine that the credit data of the user is locked;in response to determining that the credit data of the user is locked, generate an alert for delivery to the user before processing, by a credit bureau, credit data of the user responsive to the request, the alert including: at least a portion of the inquiry information identifying the requesting entity; anda user interface element enabling the user to unlock the credit data, the user interface element responsive to touch input of the user of touching the user interface element;electronically provide the alert to the user based on the retrieved contact information, wherein electronically providing the alert to the user comprises sending the alert to the mobile device of the user as a push notification to an application operating on the mobile device, the alert configured for display of the at least a portion of the inquiry information identifying the requesting entity, wherein the application is configured to transmit an unlock request to the computing device based at least in part on user selection of the user interface element; andin response to receiving the unlock request from the mobile device: automatically execute an access exception module of the access control system that causes the application of an override, to the access prevention that has been previously set on the credit data of the user, for the requesting entity in accordance with user-defined access preferences for the loan application, andsubsequent to access of the credit data of the user from the secured and regulated data store in accordance with the application of the override, automatically removing the override and maintaining the access prevention, wherein maintaining the access prevention prevents the requesting entity from accessing the credit data of the user after the override has been removed.
2. The system of claim 1, wherein the user interface element includes a central icon, and wherein in response to a user's selection of the central icon to unlock the credit data, the alert displays one or more concentric circles around the central icon.
3. The system of claim 1, wherein the user-defined access preferences indicate one or more of an unlock time period or set of entities.
4. The system of claim 1, wherein the application transmits an unlock request to the computing device based at least in further part on a determination that the user touched the user interface element for a threshold time period.
5. The system of claim 1, wherein the application transmits an unlock request to the computing device further based on a user preference.
6. The system of claim 1, wherein the application of the override comprises allowing access to a first subset of the credit data and preventing access to a second subset of the credit data.
7. The system of claim 1, wherein the application of the override comprises allowing access only for the requesting entity.
8. The system of claim 1, wherein the application of the override comprises allowing access only for a particular purpose, wherein the purpose is associated with a reason for the inquiry request.
9. The system of claim 1, wherein the application of the override comprises allowing access only for a particular period of time.
10. A method comprising: receiving, from a user, a request to lock regulated credit data associated with the user;executing a locking module of an access control system that causes the access control system to lock the credit data associated with the user in a secured and regulated data store, wherein the regulated user credit information is associated with member information indicating respective users enrolled in a fraud notification service, wherein the respective users enrolled in the fraud notification service comprise a subset of the plurality of consumers, wherein the secured and regulated data store is configured to be controlled by the access control system, wherein data stored in the secured and regulated data store indicates that a first subset of the plurality of consumers have locked credit files and a second subset of the plurality of consumers do not have locked credit files;receiving an inquiry request from a requesting entity, wherein the inquiry request includes a request for the credit data associated with the user, wherein the inquiry request is transmitted by the requesting entity in response to a loan application initiated by the user;determining that the user is enrolled in a fraud notification service based at least in part by comparing inquiry information associated with the inquiry request and member information associated with the user, wherein the member information compared includes at least one of a name, a social security number or an address; andin response to receiving the inquiry request and determining that the user is enrolled in the fraud notification service: retrieving contact information associated with the user, wherein the retrieved contact information includes at least one of a phone number, an IP address, or a device identifier associated with a mobile device of the user;determine that the credit data of the user is locked;in response to determining that the credit data of the user is locked, generating an alert for delivery to the user before processing, by a credit bureau, credit data of the user responsive to the request, the alert including: at least a portion of the inquiry information identifying the requesting entity; anda user interface element enabling the user to unlock the credit data, the user interface element responsive to touch input of the user with respect to the user interface element;electronically providing the alert to the user based on the retrieved contact information, wherein electronically providing the alert to the user comprises sending the alert to the mobile device of the user as a push notification to an application operating on the mobile device, the alert configured for display of the at least a portion of the inquiry information identifying the requesting entity, wherein the application is configured to transmit an unlock request based at least in part on user selection of the user interface element; andin response to receiving the unlock request from the mobile device: automatically executing an access exception module of the access control system that causes the application of an override, to the access prevention that has bene previously set on the credit data of the user, for the requesting entity in accordance with user-defined access preferences for the loan application, andsubsequent to access of the credit data of the user from the secured and regulated data store in accordance with the application of the override, automatically removing the override and maintaining the access prevention, wherein maintaining the access prevention prevents the requesting entity from accessing the credit data of the user after the override has been removed.
11. The method of claim 10, wherein the user interface element includes a central icon, and wherein in response to a user's selection of the central icon to unlock the credit data, the alert displays one or more concentric circles around the central icon.
12. The method of claim 10, wherein the user-defined preferences indicate one or more of an unlock time period or set of entities.
13. The method of claim 10, wherein the application transmits an unlock request in response to a time period of the user touching reaching a threshold time.
14. The method of claim 10, wherein the application transmits an unlock request further based on a user preference.
15. The method of claim 10, wherein the application of the override comprises allowing access to a first subset of the credit data and preventing access to a second subset of the credit data.
16. The method of claim 10, wherein the application of the override comprises allowing access only for the requesting entity.
17. The method of claim 10, wherein the application of the override comprises allowing access only for a particular purpose, wherein the purpose is tied to a reason for the inquiry request.
18. The method of claim 10, wherein the application of the override comprises allowing access only for a particular period of time.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority under 35 U.S.C. § 119(e) of U.S. Provisional Application No. 62/256,634, filed on Nov. 17, 2015 and titled COMPUTER SYSTEM AND INTERACTIVE USER INTERFACES FOR REAL TIME ACCESS AND CONTROL OF REMOTE DATA, the entirety of which is incorporated herein by reference.

US Referenced Citations (695)

Number	Name	Date	Kind
3316395	Lavin et al.	Apr 1967	A
4305059	Benton	Dec 1981	A
4578530	Zeidler	Mar 1986	A
4736294	Gill	Apr 1988	A
4774664	Campbell et al.	Sep 1988	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
5317636	Vizcaino	May 1994	A
5317733	Murdock	May 1994	A
5336870	Hughes et al.	Aug 1994	A
5361201	Jost et al.	Nov 1994	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
5659725	Levy et al.	Aug 1997	A
5696907	Tom	Dec 1997	A
5699527	Davidson	Dec 1997	A
5704029	Wright, Jr.	Dec 1997	A
5708422	Blonder et al.	Jan 1998	A
5732400	Mandler	Mar 1998	A
5745654	Titan	Apr 1998	A
5745706	Wolfberg et al.	Apr 1998	A
5748098	Grace	May 1998	A
5774883	Andersen	Jun 1998	A
5793972	Shane	Aug 1998	A
5802142	Browne	Sep 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
5914472	Foladare et al.	Jun 1999	A
5918217	Maggioncalda et al.	Jun 1999	A
5924082	Silverman et al.	Jul 1999	A
5930764	Melchione et al.	Jul 1999	A
5930776	Dykstra et al.	Jul 1999	A
5940812	Tengel et al.	Aug 1999	A
5950172	Klingman	Sep 1999	A
5953710	Fleming	Sep 1999	A
5956693	Geerlings	Sep 1999	A
5966695	Melchione et al.	Oct 1999	A
5978780	Watson	Nov 1999	A
5991411	Kaufman et al.	Nov 1999	A
5995947	Fraser et al.	Nov 1999	A
6012044	Maggioncalda et al.	Jan 2000	A
6014645	Cunningham	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
6055570	Nielsen	Apr 2000	A
6064987	Walker	May 2000	A
6070141	Houvener	May 2000	A
6070147	Harms et al.	May 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
6115690	Wong	Sep 2000	A
6115694	Cheetham et al.	Sep 2000	A
6119103	Basch et al.	Sep 2000	A
6128599	Walker	Oct 2000	A
6128603	Dent	Oct 2000	A
6154729	Cannon et al.	Nov 2000	A
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
6249770	Erwin et al.	Jun 2001	B1
6253203	O'Flaherty et al.	Jun 2001	B1
6269325	Lee et al.	Jul 2001	B1
6275824	O'Flaherty et al.	Aug 2001	B1
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
6324524	Lent et al.	Nov 2001	B1
6330546	Gopinathan et al.	Dec 2001	B1
6330575	Moore	Dec 2001	B1
6339790	Inoue	Jan 2002	B1
6374264	Bohannon et al.	Apr 2002	B1
6384844	Stewart et al.	May 2002	B1
6385594	Lebda et al.	May 2002	B1
6397224	Zubeldia et al.	May 2002	B1
6405173	Honarvar	Jun 2002	B1
6405181	Lent et al.	Jun 2002	B2
6430539	Lazarus et al.	Aug 2002	B1
6487540	Smith et al.	Nov 2002	B1
6529880	McKeen et al.	Mar 2003	B1
6532450	Brown et al.	Mar 2003	B1
6542894	Lee et al.	Apr 2003	B1
6567791	Lent et al.	May 2003	B2
6581075	Guturu et al.	Jun 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
6658393	Basch et al.	Dec 2003	B1
6782390	Lee et al.	Aug 2004	B2
6804346	Mewhinney	Oct 2004	B1
6805287	Bishop et al.	Oct 2004	B2
6823319	Lynch et al.	Nov 2004	B1
6832229	Reed	Dec 2004	B2
6839690	Foth et al.	Jan 2005	B1
6842782	Malik et al.	Jan 2005	B1
6873972	Marcial et al.	Mar 2005	B1
6901406	Nabe et al.	May 2005	B2
6910624	Natsuno	Jun 2005	B1
6912483	Frederick	Jun 2005	B2
6950807	Brock	Sep 2005	B2
6962336	Glass	Nov 2005	B2
6985887	Sunstein et al.	Jan 2006	B1
6988085	Hedy	Jan 2006	B2
7003476	Samra et al.	Feb 2006	B1
7013310	Messing et al.	Mar 2006	B2
7016870	Jones et al.	Mar 2006	B1
7028052	Chapman et al.	Apr 2006	B2
7058817	Ellmore	Jun 2006	B1
7062458	Maggioncalda et al.	Jun 2006	B2
7065566	Menard et al.	Jun 2006	B2
7069249	Stolfo et al.	Jun 2006	B2
7076462	Nelson et al.	Jul 2006	B1
7076475	Honarvar et al.	Jul 2006	B2
7083087	Gangi	Aug 2006	B1
7107249	Dively et al.	Sep 2006	B2
7117172	Black	Oct 2006	B1
7120599	Keyes	Oct 2006	B2
7143063	Lent	Nov 2006	B2
7165037	Lazarus et al.	Jan 2007	B2
7213064	Smith et al.	May 2007	B2
7229006	Babbi et al.	Jun 2007	B2
7243075	Shaffer et al.	Jul 2007	B1
7249076	Pendleton et al.	Jul 2007	B1
7254558	Hinkle et al.	Aug 2007	B2
7263497	Wiser et al.	Aug 2007	B1
7280980	Hoadley et al.	Oct 2007	B1
7280983	Kuroda et al.	Oct 2007	B2
7296734	Pliha	Nov 2007	B2
7302420	Aggarwal et al.	Nov 2007	B2
7308417	Nathan	Dec 2007	B1
7314166	Anderson et al.	Jan 2008	B2
7318224	Honarvar et al.	Jan 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
7366694	Lazerson	Apr 2008	B2
7376603	Mayr et al.	May 2008	B1
7383215	Navarro et al.	Jun 2008	B1
7383988	Slonecker, Jr.	Jun 2008	B2
7386466	McLean et al.	Jun 2008	B2
7395232	Pilato	Jul 2008	B1
7403919	Chacko et al.	Jul 2008	B2
7409369	Homuth et al.	Aug 2008	B1
7418417	Chacko et al.	Aug 2008	B2
7451095	Bradley et al.	Nov 2008	B1
7464067	Chestnut	Dec 2008	B2
7479949	Jobs et al.	Jan 2009	B2
7480631	Merced et al.	Jan 2009	B1
7505939	Lent et al.	Mar 2009	B2
7529698	Joao	May 2009	B2
7542993	Satterfield et al.	Jun 2009	B2
7546266	Beirne et al.	Jun 2009	B2
7552086	Rajasekar et al.	Jun 2009	B1
7559217	Bass	Jul 2009	B2
7580884	Cook	Aug 2009	B2
7584146	Duhon	Sep 2009	B1
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
7610229	Kornegay	Oct 2009	B1
7620592	O'Mara et al.	Nov 2009	B2
7624068	Heasley et al.	Nov 2009	B1
7630932	Danaher et al.	Dec 2009	B2
7653592	Flaxman et al.	Jan 2010	B1
7653593	Zarikian et al.	Jan 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
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
7729983	Ellis	Jun 2010	B1
7734522	Johnson et al.	Jun 2010	B2
7756789	Welker et al.	Jul 2010	B2
7769657	Chacko et al.	Aug 2010	B2
7774257	Maggioncalda et al.	Aug 2010	B2
7774270	MacCloskey	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
7797734	Babi et al.	Sep 2010	B2
7801812	Conlin 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
7835983	Lefner et al.	Nov 2010	B2
7836111	Shan	Nov 2010	B1
7840484	Haggerty et al.	Nov 2010	B2
7849004	Choudhuri et al.	Dec 2010	B2
7853998	Blaisdell et al.	Dec 2010	B2
7860782	Cash et al.	Dec 2010	B2
7873677	Messing et al.	Jan 2011	B2
7877304	Coulter	Jan 2011	B1
7890420	Haggerty et al.	Feb 2011	B2
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
7930252	Bender et al.	Apr 2011	B2
7937416	Hossfeld 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
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
7983975	Jones et al.	Jul 2011	B2
7987124	Holden et al.	Jul 2011	B1
8001034	Chung et al.	Aug 2011	B2
8001041	Hoadley 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
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
8073768	Haggerty et al.	Dec 2011	B2
8078524	Crawford et al.	Dec 2011	B2
8078527	Cerise et al.	Dec 2011	B2
8086523	Palmer	Dec 2011	B1
8095458	Peterson et al.	Jan 2012	B2
8099356	Feinstein et al.	Jan 2012	B2
8131614	Haggerty et al.	Mar 2012	B2
8160960	Fei et al.	Apr 2012	B1
8165940	Meimes et al.	Apr 2012	B2
8195549	Kasower	Jun 2012	B2
8204774	Chwast et al.	Jun 2012	B2
8204812	Stewart et al.	Jun 2012	B2
8225395	Atwood et al.	Jul 2012	B2
8234498	Britti et al.	Jul 2012	B2
8255971	Webb et al.	Aug 2012	B1
8260699	Smith et al.	Sep 2012	B2
8285613	Coulter	Oct 2012	B1
8290840	Kasower	Oct 2012	B2
8311936	Haggerty et al.	Nov 2012	B2
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
8347364	Babi et al.	Jan 2013	B2
8359278	Domenikos et al.	Jan 2013	B2
8386377	Xiong et al.	Feb 2013	B1
8392334	Hirtenstein et al.	Mar 2013	B2
8463595	Rehling et al.	Jun 2013	B1
8473353	Matsuda 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
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
8571971	Brown et al.	Oct 2013	B1
8572083	Snell et al.	Oct 2013	B1
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
8660919	Kasower	Feb 2014	B2
8694420	Oliai	Apr 2014	B1
8725613	Celka et al.	May 2014	B1
8732004	Ramos et al.	May 2014	B1
8738516	Dean et al.	May 2014	B1
8744956	DiChiara	Jun 2014	B1
8760417	Haug	Jun 2014	B2
8762243	Jenkins et al.	Jun 2014	B2
8775299	Achanta et al.	Jul 2014	B2
8781951	Lewis et al.	Jul 2014	B2
8781953	Kasower	Jul 2014	B2
8856894	Dean et al.	Oct 2014	B1
8930216	Johnson et al.	Jan 2015	B1
8930263	Mahacek et al.	Jan 2015	B1
8983867	Stibel et al.	Mar 2015	B2
9015171	Bayliss	Apr 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
9213461	Eraker et al.	Dec 2015	B2
9256904	Haller	Feb 2016	B1
9443268	Kapczynski et al.	Sep 2016	B1
9449346	Hockey et al.	Sep 2016	B1
9558519	Burger	Jan 2017	B1
9569797	Rohn et al.	Feb 2017	B1
9595023	Hockey et al.	Mar 2017	B1
9607336	Dean et al.	Mar 2017	B1
9690820	Girulat, Jr.	Jun 2017	B1
9710852	Olson et al.	Jul 2017	B1
9892457	Kapczynski	Feb 2018	B1
10003591	Hockey et al.	Jun 2018	B2
10104059	Hockey et al.	Oct 2018	B2
10319029	Hockey et al.	Jun 2019	B1
10380654	Hirtenstein et al.	Aug 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
10586279	Ramos et al.	Mar 2020	B1
10614463	Hockey et al.	Apr 2020	B1
10671749	Felice-Steele et al.	Jun 2020	B2
10726491	Hockey et al.	Jul 2020	B1
10757154	Jacobs et al.	Aug 2020	B1
10880313	Manna et al.	Dec 2020	B2
10937090	Debie et al.	Mar 2021	B1
10949428	Poirel et al.	Mar 2021	B2
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
20010011247	O'Flaherty et al.	Aug 2001	A1
20010027413	Bhutta	Oct 2001	A1
20010039523	Iwamoto	Nov 2001	A1
20010042785	Walker et al.	Nov 2001	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
20020049624	Raveis, Jr.	Apr 2002	A1
20020052836	Galperin et al.	May 2002	A1
20020069122	Yun et al.	Jun 2002	A1
20020077964	Brody et al.	Jun 2002	A1
20020091650	Ellis	Jul 2002	A1
20020099641	Mills et al.	Jul 2002	A1
20020099824	Bender et al.	Jul 2002	A1
20020107765	Walker	Aug 2002	A1
20020111890	Sloan et al.	Aug 2002	A1
20020128962	Kasower	Sep 2002	A1
20020147669	Taylor et al.	Oct 2002	A1
20020147695	Khedkar et al.	Oct 2002	A1
20020165757	Lisser	Nov 2002	A1
20020165839	Taylor et al.	Nov 2002	A1
20020169747	Chapman et al.	Nov 2002	A1
20020174124	Haas et al.	Nov 2002	A1
20020178146	Akella et al.	Nov 2002	A1
20020194117	Nabe et al.	Dec 2002	A1
20020198736	Harrison	Dec 2002	A1
20020198806	Blagg et al.	Dec 2002	A1
20020198824	Cook	Dec 2002	A1
20030009415	Lutnick et al.	Jan 2003	A1
20030009418	Green et al.	Jan 2003	A1
20030018549	Fei et al.	Jan 2003	A1
20030028477	Stevenson et al.	Feb 2003	A1
20030041031	Hedy	Feb 2003	A1
20030046222	Bard et al.	Mar 2003	A1
20030064705	Desierio	Apr 2003	A1
20030065563	Elliott et al.	Apr 2003	A1
20030078897	Florance et al.	Apr 2003	A1
20030101111	Dang et al.	May 2003	A1
20030115122	Slater et al.	Jun 2003	A1
20030154162	Danaher et al.	Aug 2003	A1
20030158960	Engberg	Aug 2003	A1
20030163435	Payone	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
20030204752	Garrison	Oct 2003	A1
20030212618	Keyes et al.	Nov 2003	A1
20030229580	Gass et al.	Dec 2003	A1
20030236738	Lange et al.	Dec 2003	A1
20040006536	Kawashima et al.	Jan 2004	A1
20040023637	Johnson 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
20040044615	Xue et al.	Mar 2004	A1
20040044617	Lu	Mar 2004	A1
20040111292	Hutchins	Jun 2004	A1
20040111358	Lange et al.	Jun 2004	A1
20040111359	Hudock	Jun 2004	A1
20040111363	Trench et al.	Jun 2004	A1
20040117302	Weichert et al.	Jun 2004	A1
20040133493	Ford et al.	Jul 2004	A1
20040138995	Hershkowitz et al.	Jul 2004	A1
20040143546	Wood et al.	Jul 2004	A1
20040153437	Buchan	Aug 2004	A1
20040158521	Newton	Aug 2004	A1
20040158723	Root	Aug 2004	A1
20040159700	Khan et al.	Aug 2004	A1
20040186807	Nathans et al.	Sep 2004	A1
20040193535	Barazesh	Sep 2004	A1
20040199456	Flint et al.	Oct 2004	A1
20040215584	Yao	Oct 2004	A1
20040243450	Bernard, Jr. et al.	Dec 2004	A1
20040243506	Das	Dec 2004	A1
20040249532	Kelly et al.	Dec 2004	A1
20040255127	Arnouse	Dec 2004	A1
20050004855	Jenson et al.	Jan 2005	A1
20050010513	Duckworth et al.	Jan 2005	A1
20050027633	Fortuna et al.	Feb 2005	A1
20050055275	Newman et al.	Mar 2005	A1
20050080697	Foss et al.	Apr 2005	A1
20050080716	Belyi et al.	Apr 2005	A1
20050080821	Breil et al.	Apr 2005	A1
20050086126	Patterson	Apr 2005	A1
20050086176	Dahlgren	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
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
20050130704	McFarland et al.	Jun 2005	A1
20050137963	Ricketts et al.	Jun 2005	A1
20050154617	Ruggieri et al.	Jul 2005	A1
20050154664	Guy et al.	Jul 2005	A1
20050154769	Eckart et al.	Jul 2005	A1
20050159996	Lazaraus et al.	Jul 2005	A1
20050203768	Florance	Sep 2005	A1
20050267840	Holm-Blagg et al.	Dec 2005	A1
20050273431	Abel et al.	Dec 2005	A1
20060014129	Coleman et al.	Jan 2006	A1
20060031158	Orman	Feb 2006	A1
20060059073	Walzak	Mar 2006	A1
20060080251	Fried et al.	Apr 2006	A1
20060095363	May	May 2006	A1
20060100954	Schoen	May 2006	A1
20060123461	Lunt et al.	Jun 2006	A1
20060131390	Kim	Jun 2006	A1
20060149674	Cook et al.	Jul 2006	A1
20060155639	Lynch et al.	Jul 2006	A1
20060163347	Foss et al.	Jul 2006	A1
20060173772	Hayes et al.	Aug 2006	A1
20060178971	Owen et al.	Aug 2006	A1
20060178983	Nice et al.	Aug 2006	A1
20060184410	Ramamurthy et al.	Aug 2006	A1
20060195351	Bayburtian	Aug 2006	A1
20060195391	Stanelle	Aug 2006	A1
20060212386	Willey et al.	Sep 2006	A1
20060229799	Nimmo et al.	Oct 2006	A1
20060229996	Ley et al.	Oct 2006	A1
20060233332	Toms	Oct 2006	A1
20060241923	Xu 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
20060271633	Adler	Nov 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
20070016500	Chatterji et al.	Jan 2007	A1
20070016501	Chatterji et al.	Jan 2007	A1
20070016518	Atkinson et al.	Jan 2007	A1
20070038568	Greene et al.	Feb 2007	A1
20070078741	Haggerty et al.	Apr 2007	A1
20070083463	Kraft	Apr 2007	A1
20070093234	Willis et al.	Apr 2007	A1
20070112668	Celano et al.	May 2007	A1
20070156718	Hossfeld et al.	Jul 2007	A1
20070168267	Zimmerman et al.	Jul 2007	A1
20070179798	Inbarajan	Aug 2007	A1
20070208640	Banasiak et al.	Sep 2007	A1
20070214000	Shahrabi et al.	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
20070260539	Delinsky	Nov 2007	A1
20070266439	Kraft	Nov 2007	A1
20070282736	Conlin et al.	Dec 2007	A1
20070288338	Hoadley	Dec 2007	A1
20070288490	Longshaw	Dec 2007	A1
20070299770	Delinsky	Dec 2007	A1
20070299771	Brody	Dec 2007	A1
20080010203	Grant	Jan 2008	A1
20080027841	Eder	Jan 2008	A1
20080027859	Nathans et al.	Jan 2008	A1
20080052224	Parker	Feb 2008	A1
20080059317	Chandran et al.	Mar 2008	A1
20080059364	Tidwell et al.	Mar 2008	A1
20080065530	Talbert et al.	Mar 2008	A1
20080103799	Domenikos et al.	May 2008	A1
20080109740	Prinsen et al.	May 2008	A1
20080133322	Kalla 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
20080195548	Chu et al.	Aug 2008	A1
20080201257	Lewis et al.	Aug 2008	A1
20080205774	Brinker et al.	Aug 2008	A1
20080222015	Megdal et al.	Sep 2008	A1
20080222027	Megdal et al.	Sep 2008	A1
20080222706	Renaud et al.	Sep 2008	A1
20080270209	Mauseth et al.	Oct 2008	A1
20080270294	Lent et al.	Oct 2008	A1
20080270295	Lent et al.	Oct 2008	A1
20080294996	Hunt et al.	Nov 2008	A1
20080312969	Raines et al.	Dec 2008	A1
20090007231	Kaiser et al.	Jan 2009	A1
20090012889	Finch	Jan 2009	A1
20090018996	Hunt et al.	Jan 2009	A1
20090055322	Bykov et al.	Feb 2009	A1
20090089190	Girulat	Apr 2009	A1
20090099960	Robida et al.	Apr 2009	A1
20090106846	Dupray et al.	Apr 2009	A1
20090119199	Salahi	May 2009	A1
20090119299	Rhodes	May 2009	A1
20090132347	Anderson et al.	May 2009	A1
20090144160	Haggerty et al.	Jun 2009	A1
20090158030	Rasti	Jun 2009	A1
20090171723	Jenkins	Jul 2009	A1
20090210886	Bhojwani et al.	Aug 2009	A1
20090222375	Choudhuri et al.	Sep 2009	A1
20090222377	Choudhuri et al.	Sep 2009	A1
20090222379	Choudhuri et al.	Sep 2009	A1
20090240624	James et al.	Sep 2009	A1
20090271248	Sherman et al.	Oct 2009	A1
20090289110	Regen et al.	Nov 2009	A1
20090299911	Abrahams et al.	Dec 2009	A1
20090327120	Eze et al.	Dec 2009	A1
20100009320	Wilkelis	Jan 2010	A1
20100010935	Shelton	Jan 2010	A1
20100023434	Bond	Jan 2010	A1
20100082476	Bowman	Apr 2010	A1
20100114744	Gonen	May 2010	A1
20100122316	Lyon	May 2010	A1
20100174638	Debie et al.	Jul 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
20100253686	Alsbury et al.	Oct 2010	A1
20100257102	Perlman	Oct 2010	A1
20100268660	Ekdahl	Oct 2010	A1
20100299251	Thomas	Nov 2010	A1
20100299252	Thomas	Nov 2010	A1
20100299260	Thomas	Nov 2010	A1
20100324986	Thomas	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
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
20110137924	Hunt et al.	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
20110282779	Megdal et al.	Nov 2011	A1
20110295733	Megdal et al.	Dec 2011	A1
20120005070	McFall et al.	Jan 2012	A1
20120066106	Papadimitriou	Mar 2012	A1
20120101938	Sower	Apr 2012	A1
20120101939	Sower	Apr 2012	A1
20120116951	Chung et al.	May 2012	A1
20120123931	Megdal et al.	May 2012	A1
20120136774	Imrey et al.	May 2012	A1
20120191596	Kremen et al.	Jul 2012	A1
20120246048	Cohen et al.	Sep 2012	A1
20120253852	Pourfallah et al.	Oct 2012	A1
20120254018	Davies et al.	Oct 2012	A1
20120265661	Megdal et al.	Oct 2012	A1
20120271660	Harris et al.	Oct 2012	A1
20120278767	Stibel et al.	Nov 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
20130103571	Chung et al.	Apr 2013	A1
20130110565	Means et al.	May 2013	A1
20130117087	Coppinger	May 2013	A1
20130173451	Kornegay et al.	Jul 2013	A1
20130173481	Hirtenstein et al.	Jul 2013	A1
20130191261	Chandler et al.	Jul 2013	A1
20130205135	Lutz	Aug 2013	A1
20130317954	Psota et al.	Nov 2013	A1
20130332338	Yan et al.	Dec 2013	A1
20130332341	Papadimitriou	Dec 2013	A1
20130339249	Weller et al.	Dec 2013	A1
20140012734	Megdal et al.	Jan 2014	A1
20140019333	Morris 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
20140110477	Hammad	Apr 2014	A1
20140156501	Howe	Jun 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
20160125412	Cannon	May 2016	A1
20160224996	Hunt et al.	Aug 2016	A1
20170161486	Jeon et al.	Jun 2017	A1
20170228820	Rohn	Aug 2017	A1
20170262758	Boyapalle et al.	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
20180082371	Chandler	Mar 2018	A1
20180176267	Malatesha et al.	Jun 2018	A1
20180204279	Painter et al.	Jul 2018	A1
20180218069	Rege et al.	Aug 2018	A1
20180218448	Thomas et al.	Aug 2018	A1
20180285886	Yan et al.	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
20190318122	Hockey et al.	Oct 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
20200201878	Putnam et al.	Jun 2020	A1
20200202425	Taylor-Shoff et al.	Jun 2020	A1
20200211099	Smith et al.	Jul 2020	A1
20200213206	Bracken et al.	Jul 2020	A1
20200233850	Girulat, Jr.	Jul 2020	A1
20200327610	Rohn et al.	Oct 2020	A1
20200372506	Billman et al.	Nov 2020	A1
20200389461	Felice-Steele et al.	Dec 2020	A1
20210194885	Manna	Jun 2021	A1

Foreign Referenced Citations (47)

Number	Date	Country
2 611 595	Dec 2006	CA
1290373	Apr 2001	CN
0 350 907	Jan 1990	EP
0 468 440	Jan 1992	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
2001-282957	Oct 2001	JP
2002-163449	Jun 2002	JP
2003-016261	Jan 2003	JP
2003-316950	Nov 2003	JP
10-0638324	Oct 2006	KR
2007-015510	Apr 2008	MX
I256569	Jun 2006	TW
WO 97022073	Jun 1997	WO
WO 99046710	Sep 1999	WO
WO 00011574	Mar 2000	WO
WO 01016896	Mar 2001	WO
WO 01039090	May 2001	WO
WO 01039589	Jun 2001	WO
WO 01041083	Jun 2001	WO
WO 01057720	Aug 2001	WO
WO 01080053	Oct 2001	WO
WO 01084281	Nov 2001	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 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 2009061342	May 2009	WO
WO 2009064840	May 2009	WO
WO 2009099448	Aug 2009	WO
WO 2010129257	Nov 2010	WO
WO 2016070096	May 2016	WO
WO 2018144612	Aug 2018	WO
WO 2019103979	May 2019	WO
WO 2020051154	Mar 2020	WO
WO 2020132026	Jun 2020	WO

Non-Patent Literature Citations (197)

Entry
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.
AISG's National Underwriting Database, A-PLUS, is Now the Largest in the Industry, Business Wire, Aug. 7, 1997.
Announcing TrueProfiler, http://web.archive.org/web/20021201123646/http://www.truecredit.com/index.asp, dated Dec. 1, 2002, 2 pages.
“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, 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.
Bilotta, Caryn, “Understanding Credit Scores,” Pittsburgh Post—Gazette, May 9, 2010.
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.
Cantor, R. and Packer, F., “The Credit Rating Industry,” FRBNY Quarterly Review, Summer-Fall, 1994, pp. 1-24.
“Chase Gets Positive,” Bank Technology News, May 6, 2000, vol. 14, No. 5, pp. 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.
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.
CreditAnalyst, Digital Matrix Systems, as printed out Mar. 4, 2008, pp. 2.
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.
Credit Card Management, “Neural Nets Shoot for Jackpot,” Dec. 1995, pp. 1-6.
Credit Risk Management Report, Potomac, Mar. 9, 1998, vol. 8, No. 4.
CreditXpert Inc., CreditXpert 3-Bureau Comparison™, 2002, pp. 5, 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, http://web.archive.org/web/20030630132914/http://creditxpert.com/CreditXpert%20What-If%20Simulator(TM)%20sample.pdf.
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.
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.
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.
Dillon et al., “Good Science”, Marketing Research: A Magazine of Management & Applications TM, Winter 1997, vol. 9, No. 4; pp. 11.
Downing, Jr.; Richard, “Changes to the Credit Reporting Act,” Mortgage Banking, Apr. 1, 1998, vol. 58, No. 7, pp. 82-85.
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.
Equifax: Consumer Bureau, http://www.equifax.co.in/financial-services/consumer_bureau/en_in#RiskScore printed Oct. 12, 2012 in 3 pages.
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.
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 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, 2000, in 2 pages.
Experian Information Solutions, Inc., Credit Trends: Access Credit Trending Information Instantly, http://kewaneecreditbureau.com/Credit.Trends.pdf, Aug. 2000, pp. 4.
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.
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.
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,” http://www.fool.com/seminars/ev/index.htm?sid=0029&lid=300, 2002, 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.
“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, “Keeping Tabs on Businesses That Keep Tabs on Us”, NewsRoom, The Seattle Times, Section: Scene, Apr. 19, 1995, pp. 4.
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.
“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, QI 2016”, Forrester®, Mar. 30, 2016, p. 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.
Hill, Kerry, “Identity Theft Your Social Security Number Provides Avenue For Thieves”, NewsRoom, Wisconsin State Journal, Sep. 13, 1998, pp. 4.
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.
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.
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.
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.
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; “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.
Longo, Tracey, “Managing Money: Your Family Finances”, Kiplinger's Personal Finance Magazine, Jun. 1, 1995, vol. 49, No. 6, pp. 4.
Lund, Graham, “Credit Bureau Data: Maximizing the Benefits,” Credit Management, May 2004, ProQuest Central, pp. 44-45.
Merriam Webster's Collegiate Dictionary, 10th Edition, 1999, p. 79.
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.
Montgomery County Housing Report, Residential Market Report, Jan. 2004 in 6 pages.
MyFico, http://www.myfico.com/products/ficoone/sample/sample_scoresimulator.aspx printed Oct. 12, 2012 in 3 pages.
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.
“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/, pp. 4.
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.
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.
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; p. 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=1UwNTEERlKk, as published Mar. 21, 2012.
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.
“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.
Saunders, A., “Data Goldmine,” Management Today, London: Mar. 1, 2004, 6 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.
“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.
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.
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.
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.
Taylor, Marshall, “Loan-Level Pricing Draws Interest From Investors,” Real Estate Finance Today, Jul. 7, 1997, vol. 14, No. 14. p. 10.
“The Best of the Best,” Mortgage Technology, Nov. 1, 2003, vol. 10, No. 8, pp. 34-53.
“TransUnion—Child Identity Theft Inquiry”, TransUnion, http://www.transunion.com/corporate/personal/fraudIdentityTheft/fraudPrevention/childIDInquiry.page as printed Nov. 5, 2009 in 4 pages.
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/.
Vamosi, Robert, “How to 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; Unversiteit Gent (Belgium) 2005.
Wahl, Martin, “The Stampede to Subprime,” Mortgage Banking, Oct. 1, 1997, vol. 58, No. 1, p. 26(7).
Watts, Craig, “Consumers Now Can Know What Loan Rate Offers to Expect Based on Their FICO Credit Score at MyFICO.com,” 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.
West, David, “Neural Network Credit Scoring Models”, Computers & Operations Research, vol. 27, 2000, pp. 1131-1152.
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, 2001, pp. 73-90.
Zimmerman et al., “A Web-Based Platform for Experimental Investigation of Electric Power Auctions,” Decision Support Systems, 1999, vol. 24, pp. 193-205.
Zoot—Instant Rules GUI, www.zootweb.com/instant_rules_GUI.html as printed Mar. 3, 2008.
Zoot—Rules Management GUI, www.zootweb.com/business_rules_GUI.html as printed Mar. 3, 2008.
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.
Apte, et al., “A Probabilistic Estimation Framework for Predictive Modeling Analytics,” IBM Systems Journal, 2002, vol. 41, No. 3, pp. 438-448.
“Fraud Alert \| Learn How”. Fight Identity Theft. http://www.fightidentitytheft.com/flag.html, accessed on Nov. 5, 2009.
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.
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-pressreleases/lifelock-protection-for-children.
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/, 2007.
“NewsHound: NewsHound User Guide Internet E-Mail”, of record as early as May 2, 1997, pp. 11.
“Normalize,” http://www.merriam-webster.com/dictionary/normalize printed Jun. 14, 2010.
Sealey, Geraldine, “Child ID Theft Can Go Unnoticed for Years”, http://abcnews.com/US/story?id:90257, Sep. 12, 2003 in 9 pages.
TheMorningCall.Com, “Cheap Ways to Foil Identity Theft,” www.mcall.com/business/columnists/all-karp.5920748jul01.0 . . . , published Jul. 1, 2007.
Todorova, Aleksandra, “Protecting Your Child's Identity”, Smart Money, Published Aug. 2, 2007, pp. 1-5.
“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.
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/US2018/061877, dated Mar. 8, 2019.
Gopalan, R., “Panning for Sales-Force Gold”, Intelligent Enterprise, Dec. 21, 1999, vol. 2, No. 18, pp. 39-43.
International Search Report and Written Opinion for Application No. PCT/US2019/049377, dated Dec. 20, 2019.
Menge, Falko, “Enterprise Service Bus”, Free and Open Source Software Conference, 2007, pp. 6.
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).
International Preliminary Report on Patentability in Application No. PCT/US2018/061877, dated Jun. 4, 2020.
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).
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.
Nikravesh et al., “Fuzzy Queries, Search, and Decision Support System”, Soft Computing, Aug. 2002, vol. 6, No. 5, pp. 373-399.
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).
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.

Provisional Applications (1)

	Number	Date	Country
	62256634	Nov 2015	US

Realtime access and control of secure regulated data

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Term Extension