Digital identity

Description

BACKGROUND

One valuable object that many people carry on a day-to-day basis is a wallet. The wallet contains items of financial value, such as cash, credit cards and other payment instruments. It additionally may include personal information, such as identification cards, which people use every day to verify their identities at various locations and/or establishments. However, the wallet has not caught up to the digital age. In particular, digital replacements of identification cards may in some cases be more susceptible to fraud if they are easy to counterfeit, copy, or duplicate, or may otherwise be more difficult to verify as authentic.

SUMMARY

Validated identification (“ID”) systems and methods as discussed in the present disclosure provide individuals with the ability to carry and present a validated digital ID for everyday use, for example as part of a digital wallet, much as one uses a driver's license or other form of ID in a physical wallet. In one embodiment, the validated ID system validates a digital form of ID (such as a scanned driver's license) for an individual, and provides a validated ID token to the individual for use, for example, with a mobile computing device (such as a smartphone). Thus, the digital form of ID, representing the actual ID of the individual, may be associated with the validated ID token, which indicates that the digital form of ID is validated (e.g., the digital form of ID is a validated digital ID). The validated ID token may then be provided or presented by the individual at various service providers/locations (such as retailers, restaurants, etc.) as a form of identification. The service providers/locations can request verification by the validated ID system of the individual's identity through use of the provided validated ID token. In some embodiments, the validated ID token may be refreshed, automatically or manually by request, on a periodic basis to increase security, prevent fraudulent use, and/or assure service providers of the validity of the individual's digital ID. In some embodiments, to provide greater security and trust, the validated ID system may provide the validated ID token to the individual over a first network, while providing verification of the validated ID token to the service provider/location over a second network (e.g., “out-of-band” verification or authentication).

An individual may find having a digital identification that is accepted at various participating service providers, establishments, and locations a convenient way to provide proof of her identity when asked or required. As an example, consider an individual asked to present a valid form of ID (e.g., to show proof of age) to gain entry into a nightclub with a minimum age requirement. The individual might carry, for example on a smartphone or other mobile computing device which the individual typically carries everywhere, a digital ID that has been validated by the validated ID system. The bouncer may have a computing device (such as a smartphone or a computer) available at the nightclub entry point, configured to read an ID token, and request verification of the ID token from the validated ID system. Thus, the individual can present her digital ID to the bouncer at the nightclub instead of a physical ID card (such as a driver's license). In some cases, the bouncer may visually inspect the digital ID and determine that the ID token is trustworthy (as might be indicated, for example, by a verification badge) and allow the individual to enter. However, for added security, the bouncer may use his computing device to read the individual's ID token, for example by scanning an image associated with the ID token or by wirelessly receiving some or all of the ID token (such as a unique code or digital certificate) from the individual's smartphone. The bouncer's computing device may then submit the ID token to the validated ID system for verification. In this example, the validated ID system may then determine whether the ID token is a validly issued and/or non-expired validated ID token, and provides a verification status to the bouncer's computing device. Depending on the verification status the bouncer may decide whether to allow the individual to enter.

As part of the “out-of-band” authentication process for even greater security, the validated ID system may communicate with (e.g. provide the validated ID token to) the individual's smartphone over a first network, and the bouncer's computing device may be configured to communicate with (e.g. send the validated ID token to and receive verification status from) the validated ID system over a second network distinct from the first network. Thus, among other benefits, a potential fraudster's attempt to commit fraud may be frustrated because the fraudster would have to intercept the validated ID token across two networks in communication with two separate computing devices.

One embodiment may include one or more computer processors and a storage device storing software instructions configured for execution by the one or more computer processors. In one embodiment, the software instructions are configured to cause the computing system to access an image of a driver license of a consumer, extract information regarding the consumer from the driver license image, the information including at least a name of the consumer and a photograph of the consumer, transmit the driver license image to a document authentication service with a request to validate authenticity of the driver license, receive from the document authentication service an indication of whether the driver license is valid, provide one or more authentication questions to the consumer, wherein responses to the one or more authentication questions are usable to determine whether the consumer is the consumer named in the driver license image, receive responses to the one or more authentication questions, and determine, based on the responses, whether the consumer is the consumer named in the driver license image. In one embodiment, in response to determining that both the driver license is valid and that the consumer is the consumer named in the driver license image, the computing system generates a digital identity including one or more images and/or user interfaces configured for display on a mobile computing device, the digital identity including the photograph of the consumer or another photograph of the consumer, at least some of the information extracted from the driver license image, an indication that the at least some of the information extracted from the driver license image was extracted from a validly issued driver license, and an indication that the identity of the consumer has been validated.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram which illustrates an exemplary data flow between one or more consumer devices (e.g., computing devices), service providers/retailers, and a validated identification system, according to one embodiment.

FIG. 2 illustrates an example user interface displaying a validated digital ID for an individual as used in one or more embodiments of the validated ID system.

FIGS. 3A, 3B and 3C illustrate an example use case scenario in which an individual may request validation of a digital ID by the validated ID system

FIGS. 4A, 4B and 4C illustrate an example use case scenario in which an individual may use a validated ID in conjunction with a service provider or retailer's receiving device.

FIG. 5 is a flowchart illustrating one embodiment of a process for an individual to initially validate his/her digital identification and receive a validated ID token to allow use of the digital ID at participating locations involving an embodiment of a validated ID system, such as the validated identification system of FIG. 1

FIG. 6 is a flowchart illustrating one embodiment of a process for verifying the identify of an individual using a validated ID token involving an embodiment of a validated ID system, such as the validated identification system of FIG. 1

FIG. 7 is a block diagram showing an embodiment in which a validated ID computing system is in communication with one or more networks, and various systems, are also in communication with the one or more networks.

FIG. 9 is a flow diagram illustrating example information components that may be combined in order to generate a digital identity of a consumer.

FIG. 11 is a block diagram illustrating one embodiment of a digital identity that is stored on a particular consumer's mobile device.

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 disclosure. Furthermore, embodiments of the disclosure may include several novel features, no single one of which is solely responsible for its desirable attributes or which is essential to practicing the embodiments of the disclosure herein described.

High Level Data Flows

FIG. 1 is a block diagram which illustrates an exemplary data flow between one or more consumer devices (e.g., computing devices) 162, service providers/retailers 164, and a validated identification system 100, according to one embodiment. The data flow of FIG. 1 illustrates how an individual may validate a digital ID, and provide the validated digital ID at participating service providers and/or retailers as proof of his or her identity.

Beginning at step (1), the individual can request validation of a digital ID, for example by providing the digital ID to the validated ID system. The digital ID may be provided in many different forms. For example, according to one embodiment, the individual may scan a physical form of identification (e.g., a driver's license, a passport, a government-issued form of ID, an identification card, or any other form of ID) into a digital data format (e.g., an image file, a document, etc.). Such scanning may be performed, for example, by a camera on the individual's computing device (e.g., a smartphone camera), or by any type of image scanning device capable of scanning the image of an object into a digital format. In other embodiments, the digital ID may comprise a form of ID already in a digital format (e.g., a form of ID issued or provided to the individual originally and/or only issued in digital format) or the individual may manually provide the digital ID information, such as by typing in a driver's license number and related information.

At step (2), the validated ID system validates the digital ID. The validated ID system may validate the digital ID by, for example, accessing one or more data sources (such as the data sources 166 as shown in FIG. 7) to retrieve consumer profile data associated with the individual. In order to validate the digital ID, the validated ID system can also use the consumer profile data associated with the individual to determine whether there is already a validated ID token that may be associated with the consumer profile for the individual. In some embodiments, the validated ID system may determine that no validated ID has been associated with the individual. In such cases, the validated ID system may extract personally identifying information (“PII”) such as the name, address, and other information associated with the individual from the digital ID provided by the individual. The validated ID system may then compare the extracted PII to the accessed consumer profile data to determine whether there is a match. If the PII extracted from the digital ID matches the consumer profile data, the validated ID system may generate a validated ID token for the digital ID for the individual.

In some embodiments, the validated ID system may validate information regarding the individual, such as the individual's date of birth (“DOB”), by referencing data such as the individual's credit report and/or public records, such as a birth certificate. Such age validation or authentication may be performed as part of the digital ID validation process, or as a separate process. Age validation may also be performed by the validated ID system as part of the verification process(es) described herein.

If the validated ID system determines that a validated ID token has already been generated and associated with the consumer profile data, the validated ID system may generate a new validated ID token (e.g. refresh the existing or previous validated ID token). Once generated and/or refreshed, the validated ID token may be associated with the consumer profile data associated with the individual, and stored, for example, in a validated identification data store for later use in the identity verification processes described herein.

The validated ID token may be provided by the validated ID system in myriad formats. In one embodiment, the validated ID token comprises a verification badge, such as a unique image generated dynamically and/or randomly by the validated ID system for the individual. In some embodiments, the validated ID token comprises an alphanumeric code (e.g., a data text string of characters). In some embodiments, the validated ID token comprises a cookie, a “super cookie,” a digital certificate, or other form of digital authentication which may be used to uniquely and securely identify and/or verify the individual's digital ID. In some embodiments, the validated ID token comprises a time stamp (e.g., a date and/or time) indicating when the validated ID token was issued and/or last validated. In some embodiments, the validated ID token comprises a geographic location indicator (e.g., Global Positioning System (“GPS”) coordinates, street, city, state, and/or any other information which provides an indication of geographic location) indicating a location from which the validated ID token was last validated. Such location information may reduce risk of a fraudster copying a digital ID (e.g., photographing or taking a screen shot of a digital ID on another user's device) since the fraudster likely isn't at the location at which the validated ID token was authenticated by the consumer (and which would be included in the photograph or screen shot of the consumers digital ID).

The validated ID token may also comprise any combination of the examples described herein (e.g., a verification badge and a digital certificate; or a verification badge and GPS coordinates; etc.). The validated ID token may also be encrypted. In some embodiments, some or all portions of the validated ID token (e.g., a verification badge) are configured for display via a user interface on the individual's computing device. In some embodiments, some or all portions of the validated ID token (e.g., a digital certificate) may additionally, or alternatively, be configured for digital transmission between one or more computing devices (e.g., via a wired or wireless connection including Ethernet connections, radio, infrared, Bluetooth, Wi-Fi, near field communication (“NFC”), text messaging, short message service (“SMS”), cellular networks, etc.). In some embodiments the validated ID token is refreshed or updated automatically on a periodic basis by the validated ID system, and the refreshed validated ID token is pushed to the individual's computing device. Alternatively or in combination with the above, the individual may manually trigger a refresh of the validated ID token.

In some embodiments, the validated ID token may be issued to or associated with the individual's computing device(s). The validated ID system may also be configured to track and record usage data related to the validated ID token (e.g. by logging or recording when a request to verify the validated ID token is received by the validated ID system). The usage data may be recorded, for example at the validated identification data store 108, and used by the validated ID system to determine and charge a periodic fee to the individual for use of the digital identification associated with the validated ID token.

Once the digital ID has been validated and the validated ID token has been generated, at step (3) the validated ID system may issue the validated ID token to the individual and/or the individual's computing device. In the event that the validated ID system is unable to determine a match of the personally identifying information of the digital ID to the accessed consumer profile data, the validated ID system may instead provide an indication to the individual that a digital ID could not be validated. In that case, the individual may attempt to submit a different form of digital ID, for example, by scanning a different identification card or rescanning the submitted digital ID and attempt to try again.

Continuing to step (4), the individual may present the validated digital ID at various service providers, retailers, locations, establishments, and the like. The individual may present or provide the validated ID in various different ways. For example, the individual may show an image of the validated digital ID to the service provider which may then visually inspect the validated digital ID to determine whether the digital ID of the individual is valid. For example, the validated digital ID may display a badge, an image, or a logo which provides a visual indication that the digital ID has been validated by the validated ID system. The badge, image, or logo may, for example, be a trusted or recognized image which may only displayed on a trusted device carrying the validated digital ID, or some other form of visual indication which participating service providers may recognize as an indication that the digital ID is valid for the individual. The digital ID may display, for example, a photograph of the individual (as typically shown in an identification card) as well as other personally identifying information in addition to the verification badge, image, or logo. One example of a validated digital ID is shown in an example user interface in FIG. 2 discussed herein.

In other embodiments, the individual may provide the validated digital ID to the service provider over a wireless or wired connection such as infrared, radio, Bluetooth, Wi-Fi, NFC, text messaging, SMS, cellular networks, etc., instead of, or in conjunction with, presenting a visual user interface of the digital ID. Thus, for example, the individual may simply digitally transmit the digital ID to a service provider's computing device (e.g., by placing his/her computing device in the proximity of the service provider's computing device, by “bumping” his/her computing device with the service provider's computing device, by docking, connecting, or plugging in his/her computing device to the service provider's computing device, and the like) to transmit some or all portions or components of the validated digital ID and/or validated ID token. The service provider's computing device may be configured to read or receive the validated ID token or a portion of the validated ID token, such as a digital certificate, over the wired or wireless connection. The service provider's computing device may also be configured to request the validated ID token from a nearby computing device, such as to enable the service provider to initiate the verification process manually and/or without further or direct action from the individual. Thus, in this example, the individual may not need to actually show the digital ID, but instead can simply provide the validated ID token to the service provider or retailer by proximity of their computing device which contains their digital wallet and/or validated digital ID.

At step (5), the service provider/retailer requests verification of the identity of the individual by using the ID token provided by the individual. The request may be sent, for example, over a network 170 (which in some embodiments may be separate and distinct from the network 160) to the validated identification system, which may use the ID token to determine whether the digital ID presented by the individual is valid.

At step (6), the validated ID system attempts to verify the identity of the individual using the ID token provided by the service provider/retailer. According to one embodiment, to verify the ID token, the validated ID system may access one or more validated ID tokens stored, for example, in a validated identification data store 108. Using the validated ID tokens, the validated ID system may determine whether the provided ID token is valid. If the provided ID token is determined to be invalid, the validated ID system may provide a verification status to the service provider/retailer indicating that the ID token could not be verified as valid.

If the validated ID system determines that the provided ID token is valid, then the validated ID system may provide a verification status to the service provider/retailer indicating that the ID token has been verified as valid. If the validated ID system determines that the provided ID token is not valid, then the validated ID system may provide an indication to the service provider/retailer that the ID token could not be verified as valid.

Once the service provider/retailer receives the verification status provided by the validated ID system, the service provider/retailer may take the appropriate action depending on the verification status. For example, if the verification status indicates that the identify of the individual could not be verified, the service provider/retailer may deny service or request further identification from the individual in order to verify their identity. In some embodiments, if the service provider/retailer receives a verification status from the validated ID system indicating that the ID token is valid, the service provider/retailer may provide the service accordingly.

Example of a Validated Digital ID User Interface for a Validated ID System

FIG. 2 illustrates an example user interface displaying a validated digital ID for an individual as used in one or more embodiments of the validated ID system. The sample user interface may be displayed, for example, via a web browser or standalone application. However, in some embodiments, the sample user interface shown in FIG. 2 may also be displayed on a suitable computer device, such as a cell/smart phone, tablet, portable computing device, desktop, laptop, or personal computer, and are not limited to the samples as described herein. The user interface includes examples of only certain features that a validated ID system may provide. In other embodiments, additional features may be provided, and they may be provided using various different user interfaces and software code. Depending on the embodiment, the user interface and functionality described with reference to FIG. 2 may be provided by software executing on the individual's computing device, by a validated ID system located remotely that is in communication with the computing device via one or more networks, and/or some combination of software executing on the computing device and the address verification system.

The user interface shown in FIG. 2 illustrates a digital ID for an individual which has been validated by the validated ID system. As shown in FIG. 2, the digital identification 200 may include various personally identifying information (“PII”) 205 associated with the digital ID of the individual. The PII 205 may include, for example, a photo of the individual, an ID number associated with the individual, an expiration date for the digital identification, a signature of the individual, the individual's name (e.g. last name, first name, middle name/initial), an address (e.g. residence or mailing) for the individual, a date of birth for the individual, and physically identifying information for the individual (e.g. hair color, eye color, height and weight). In other embodiments, additional PII not shown in FIG. 2 may be displayed. In some embodiments, not all PII associated with a digital ID may be displayed.

FIG. 2 also illustrates a validated ID token 210 indicating that the digital ID has been validated by the validated ID system. For example, the validated ID token 210 as shown in FIG. 2 includes a label 215 indicating that the ID is validated. In some embodiments, the digital ID 200 may also display an alphanumeric code 220 associated with the validated ID token 210, which may be uniquely and dynamically generated by the validated ID system. In some embodiments, the digital ID 200 may also display a validation status 225 such as a time stamp, date, and/or time indicating the last time the digital ID 200 was last validated by the validated ID system. Further, in some embodiments, the digital ID 200 may also display a location 230, such as GPS coordinates, street, city, and/or other geographical indicator, indicating the location from which the digital ID 200 was last validated by the validated ID system. Such information may be useful, for example, to assure service providers/retailers of the authenticity of the validated digital ID. Also, as illustrated in FIG. 2, in some embodiments the digital ID 200 may display an image 235 associated with the validated ID token 210, which may be, as pictured here, a badge or certificate indicating the digital ID has been validated. In some embodiments, the image 235 may also be displayed as an embedded code (such as a bar code, a Quick Response or “QR” code, etc.) or randomly generated image, which may be, for example, scanned by a computing device at a service provider/retailer to read the validated ID token from the digital ID of the individual. In some embodiments, the image 235 and/or the entire digital ID 200 may be an active user interface element (e.g. “clickable” or “selectable” such as via a touch screen interface or user interactive display element). For example, in response to an individual clicking on the image 235 and/or the digital ID 200, a request to validate the ID may be sent to the validated ID system which may then validate the ID and provide an updated validated ID token 210 for the digital ID 200.

As described herein, in some embodiments, the various components of the validated ID token may be refreshed automatically by the validated ID system and provided or pushed to the individual's computing device on a periodic basis. Thus, for example, the code 215 and/or the image 235 may be randomly and dynamically updated, for example, every 30 seconds, so that at any given time the validated ID token represents a current status that the digital ID is valid. This auto-refresh feature may, for example, increase the security and/or trust associated with the validated digital ID, and help to prevent fraudulent use or copying by ensuring that the digital ID is validated on a recurring basis. Thus, for example, if an individual loses his/her computing device, he/she may be able to provide notice to the validated ID system that the computing device was lost or stolen. In response, the validated ID system may stop refreshing and/or pushing the validated ID token to the computing device, as a consequence, the validated ID token associated with the digital ID on the computing device may no longer be valid. This would prevent, for example, fraudulent use of the individual's computing device to verify their identity at various locations. It may also prevent a fraudster from intercepting or otherwise obtaining a copy of a validated ID token for use on another computing device, such as by taking a picture or screenshot of the validated ID token for use on the fraudster's own computing device. Thus, a validated ID token may only remain valid for a short, limited amount of time to reduce the possibility of fraudulent use. By the time the fraudster attempts to use the compromised or stolen validated ID token, the validated ID token most likely will have expired and the fraudster's attempt will be denied.

Although not shown in FIG. 2, in some embodiments, the individual may be presented with an option to manually refresh the validated ID token, in which case the validated ID system may issue a new validated ID token, for example, a new code 215 and/or a new image 235 to replace the existing code 215 and/or image 235. For example, if the individual suspected potentially fraudulent use of the validated ID token (e.g., if the individual left his/her computing device unattended for a period of time and was worried the computing device may have been compromised by a fraudster), the individual may wish to request a new validated ID token and thereby invalidate any previously issued validated ID tokens. Also, although not shown in FIG. 2, the digital ID user interface may provide an option to click on or touch the validated ID token or one of its components, such as the code 215 and/or image 235, in order to request verification of the digital ID. Thus, for example, a service provider wishing to verify the ID of the individual may click on or touch the validated ID token or one of its components to request verification of the individual's ID token. In such an embodiment, the validated ID system may perform the verification process and refresh or update the validated ID token to provide an indication that the digital ID of the individual is verified. As discussed herein, the request to verify the identity of the individual may be sent over a different network than the request to validate the digital ID. This may provide an extra layer of security because the validated ID token is generated and provided to the individual's computing device over a first network, while the validated ID token is provided by the service provider/retailer's computing device and verified over a second or “out of band” network connected to the validated ID system. By way of example, in some embodiments, the first network may be an online network (e.g. the Internet) while the second network may be a telecommunications network (e.g. a cellular network), and vice versa. Thus, for example, the individual may receive a validated ID token from the validated ID system over the Internet, while the service provider/retailer requests and/or receives verification over a cellular network. In other embodiments, other types of communications networks may be used in any combination to support a two-network, out-of-band architecture, including near-field networks, radio, infrared, Bluetooth, NFC, text message services, SMS, cellular networks, and the like.

Example Use Case Scenario for Validating a Digital ID

FIGS. 3A, 3B and 3C illustrate an example use case scenario in which an individual may request validation of a digital ID by the validated ID system. Beginning with FIG. 3A, the individual may be presented on a portable electronic device with a digital identification (“ID”) 300, including various personally identifying information (e.g. name, address, date of birth (“DOB”), etc.), and an option to “touch to validate” 305 by touching a user-selectable portion of the screen, for example, a pre-validation badge 310. Although FIG. 3A provides an example of “touch,” other user interactions may be possible, including but not limited to shaking, swiping, rotating, other touch and/or motion based interactions, voice commands (e.g. the individual may verbally request validation), etc.

FIG. 3B continues the touch example by illustrating the individual touching the pre-validation badge to initiate the request to validate the digital ID. Once a request to validate has been detected by the device, the request may be submitted to the validated ID system, which may then attempt to validate the ID for example, in conjunction with the process described with reference to FIG. 5 herein. If the validated ID system successfully validates the digital ID, it may provide a validated ID token to the individual's device for display as illustrated in FIG. 3C. In some embodiments the digital ID may display some or all of the validation status information as described herein (e.g. validation ID, time stamp, location, and/or certification badge). As shown in the example of FIG. 3C, the request to validate the digital ID was a success, and the pre-validation badge 310 has been replaced with a validation badge 315 along with other validation status information received from the validated ID system. In some embodiments, if the digital ID could not validated by the validated ID system, the device may instead show a message indicating that the digital ID could not be validated. In this use case, the validation process may be performed by the user and/or by another entity that requires validation of the ID. For example, a security agent at an event may want to see the active validation of the user's ID before trusting that the ID is valid and, thus, may actually be handed the mobile device (in a similar way as a paper ID would be) and press the validate icon to initiate the validation process (e.g., rather than shining a black light on or looking for holograms in a printed driver's license).

Example Use Case Scenario for a Validated ID

FIGS. 4A, 4B and 4C illustrate an example use case scenario in which an individual may use a validated ID in conjunction with a service provider or retailer's receiving device 405. In the example scenario illustrated, the individual may transfer a digital copy of some of all his/her digital ID (e.g. the entire digital ID, or a portion of the validated ID token, or any variation thereof), for example to a service provider's system, via a receiving device (such as a tablet PC or similar). FIG. 4A illustrates the individual's digital ID (e.g. on a mobile device) 400 displaying a message 410 indicating the individual may shake the device or touch a receiving device (e.g. receiving device 405), to transfer the digital ID from the individual's device 400 to the receiving device 405. Thus, the individual may perform the desired action (e.g. shake, touch, or other gesture) to wirelessly transfer a digital copy of the digital ID to the receiving device 405. FIG. 4B illustrates the receiving device 405 with a copy of the digital ID after receiving the digital ID from the individual's device 400. In some embodiments, after receiving the digital ID on the receiving device 405, the service provider may request validation of the digital ID in accordance with the processes described herein (see, e.g., FIG. 6). Thus, the validated ID system may receive the digital ID from the service provider's receiving device 405, validate the digital ID, and provide a verification status back to the service provider's receiving device 405.

FIG. 4C illustrates a variation on FIG. 4B in which instead of displaying and/or receiving the individual's digital ID, the receiving device 405 may alternatively display information about the digital ID's validation status (e.g., the individual's name, a validation ID, a time stamp (e.g., a date and/or time) indicating when the validated ID token was issued and/or last validated, a geographic location indicator (e.g., Global Positioning System (“GPS”) coordinates, street, city, state, and/or any other information which provides an indication of geographic location) indicating a location from which the validated ID token was last validated, and/or a validation badge. The abbreviated validation status information shown in FIG. 4C may be displayed after receiving the digital ID from the individual's device 400, or after receiving a verification status from the validated ID system in response to a request to verify the digital ID received from the individual's device 400.

Examples of Methods Performed by a Validated Identification System

FIG. 5 is a logical flow diagram of a process 300 for an individual to initially validate his/her digital identification and receive a validated ID token to allow use of the digital ID at participating locations involving an embodiment of a validated ID system, such as the validated identification system 100 of FIG. 1. The method of FIG. 5 will be described herein as being performed by the validated ID system 100, but in other embodiments the method may be performed by one or more other computing systems, possibly in cooperation with the validated ID system 100.

Beginning at block 305, the validated ID system receives a request to validate the digital ID of an individual. The request may be received from an individual wishing to validate their digital ID for use in, for example, a digital wallet. The request may include, for example, a digitized form of a physical ID card (such as a scanned image of a driver's license). In some embodiments the request may also include additional personally identifying information or “out-of-wallet” information that may only be known by the individual (such as the individual's make and model of their first car, the name of their first boy/girlfriend, where they were born, where they went to high school, the name of their favorite teacher in high school, and other types of personally identifying information.) Such out-of-wallet information may be extracted from credit data or other public/private data associated with the individual, or may have been previously provided by the individual to the validated ID system, such that the validated ID system can use the out-of-wallet information to further verify the individual's digital identification. This information may also be useful to, for example, prevent a fraudster from stealing a physical ID card and attempting to validate the stolen physical ID card for fraudulent purposes, as the fraudster is less likely to have the out-of-wallet information necessary to validate the ID.

At block 310, the validated ID system may access consumer profile data, for example from data sources 166 storing, e.g., credit bureau and/or consumer data as shown in FIG. 7, associated with the individual. Additionally, the validated ID system may access a validated identification data store 108 which may be included as part of a validated ID system. The validated identification data store 108 may include, for example, consumer profile data previously accessed from the data sources 166, out-of-wallet information provided by the individual, and/or previously generated validated ID tokens (current and expired) which may be associated with the individual.

At block 315, the validated ID system determines if there is a validated ID token associated with the consumer profile data. In response to a determination that that no validated ID token is associated with the consumer profile data associated with the individual, the process 300 may proceed to block 320. At block 320, the validated ID system extracts personally identifying information (“PII”) from the received digital identification of the individual. At block 325, the validated ID system compares the extracted PII and/or out-of-wallet information provided by the individual (e.g., in response to questions asked by the validated ID system) to the accessed consumer profile data. For example, the PII may include a last name, first name, and an address which may be compared to the name and address information associated with the consumer profile data to determine if the PII is a match.

At block 330, the validated ID system determines whether the PII matches the consumer profile data. In response to a determination that the PII does match consumer profile data associated with the individual, the process 300 may proceed to block 335.

At block 335, the validated ID system may generate a validated ID token for the digital ID of the individual. Once the validated ID token has been generated, the process 300 may proceed to block 340 where the validated ID token may be associated with the consumer profile data associated with the individual. For example, the validated ID token may be stored in the validated identification data store 108 for retrieval in a later process for verifying the identity of the individual. Finally, moving to block 345, the validated ID system may push or provide the validated ID token for the digital ID of the individual to the requesting entity.

Returning to block 330, if the validated ID system determines that the PII does not match the consumer profile data (e.g., if the address on the digital ID does not match any address(es) in the consumer profile data for the individual, or the individual-provided out-of-wallet information does not match out-of-wallet information in the consumer profile data for the individual, etc.), the process 300 can proceed to block 350 where the validated ID system may provide an indication that the digital identification could not be validated. In some embodiments, along with the indication that the digital ID could not be validated, the validated ID system may provide information indicating one or more reasons why the digital ID could not be validated. For example, the validated ID system may suggest that the digital ID could not be validated because the address did not match an address known in the consumer profile data, or the digital ID could not be validated because the name or other personally identifying information, such as the individual's physical information, could not be matched, or that the out-of-wallet information provided was incorrect, etc.

Returning to block 315, if the validated ID system determines that a validated ID token has already been associated with the consumer profile associated with the individual, then the process may proceed directly to block 335 where the validated ID system may refresh the validated ID token associated with the individual's digital ID. For example, this process may be performed as part of an automatic or periodic batch process for refreshing the validated ID associated with an individual's digital ID which may be performed as described herein automatically or manually in response to a request from the individual to refresh the validated ID token. From block 335 the process 300 may proceed to blocks 340-345 as described above, and the process 300 may then end.

FIG. 6 is a logical flow diagram of a process 400 for verifying the identify of an individual using a validated ID token involving an embodiment of a validated ID system, such as the validated identification system 100 of FIG. 1. The method of FIG. 6 will be described herein as being performed by the validated ID system 100, but in other embodiments the method may be performed by one or more other computing systems, possibly in cooperation with the validated ID system 100.

Beginning at block 405, the validated ID system receives a request to verify the identity of an individual using an ID token. For example, the request may be received from a service provider/retailer wishing to verify the identity of the individual using an ID token provided by the individual. The request may include, for example, some or all portions, in any combination, of the ID token to be verified. Thus, for example, in some embodiments, the request may include a digital certificate associated with the ID token; or the request may include a validation code, such as text-based alphanumeric code or a code read from a QR image or bar code, associated with the ID token; and/or the request may include any other data element associated with the ID token.

At block 410, the validated ID system accesses validated identification data for example, from the validated identification data store 108. At block 415, the validated ID system uses the validated identification data to determine if the provided ID token is a valid ID token, e.g. based on data included in the validated identification data. For example, in some embodiments, the validated ID system may attempt to match the provided ID token (or an element of the provided ID token, such as a code) to one or more known validated ID tokens (or an element of the validated ID tokens, such as a code) included in the validated identification data. If the provided ID token does not match any known validated ID tokens, the validated ID system may determine that the provided ID token is not valid. In another example, the validated ID system may find a match of the provided ID token to one of the known validated ID tokens, but determine that the known validated ID token has expired or is otherwise no longer valid.

If the validated ID system determines that the provided ID token is not valid, then the process 400 may proceed to block 420, where the validated ID system may provide to the requesting party a verification status indicating that the ID token is not valid. In some embodiments the validated ID system may also provide with the verification status additional information related to why the ID token is not valid. For example, the verification status may indicate that the provided ID token has expired, or that the provided ID token did not match any known validated ID tokens, etc.

In some embodiments, along with the verification status, the validated ID system may also provide out-of-wallet information (e.g. questions and answers) which the requesting party (e.g. service provider/retailer) may use to further verify the individual's identity, where the out-of-wallet information is information typically only known to the individual. For example, after scanning an individual's digital ID and/or ID token and sending a request for verification to the validated ID system, the nightclub bouncer may receive a response indicating that the digital ID and/or ID token is valid along with an additional out-of-wallet question and answer which the nightclub bouncer may ask the individual for further verification. In some embodiments of the validated ID system, when the individual initially validates her digital ID, she may have be given an option, or preference, to enable or disable this type of extra “out-of-wallet” verification when the digital ID is used. The individual may also be given options to decide where (e.g. particular service providers/retailers) and/or when (e.g. particular time, day, or period of time, such as for example when the individual may be traveling) out-of-wallet type verification may be used. For example, the individual may desire out-of-wallet verification as an added security measure when using the digital ID at a financial institution such as bank (where) or during a trip abroad (when), but may not want out-of-wallet verification enabled at other locations such as supermarkets or restaurants (where) or during everyday use (when). Some of all of these features may also be provided or enabled in some embodiments via one or more user interfaces provided by the validated ID system.

As mentioned above, the validated ID system may also validate the individual's date of birth (and/or other data associated with the individual), separately as a standalone process or as part of the process 400. Thus, in some embodiments the provided ID token may include age or date or birth information, which the validated ID system may compare to accessed consumer profile data (e.g. credit report or public records, such as a birth certificate) to validate the individual's age or date of birth. The validated ID system may then provide this information to the requesting party with the verification status. This information may be useful, for example, to ensure that the individual meets a certain age requirement, such as to enter an age-prohibitive establishment (e.g. a bar or a nightclub) or to purchase age-prohibitive products (e.g. alcohol, cigarettes).

If the validated ID system determines that the provided ID token is valid, then the process 400 may proceed to block 425, where the validated ID system may provide to the requesting party a verification status indicating that the ID token is valid.

Once the validated ID system has determined whether the provided ID token is valid and provided the verification status at block 440 or block 435, the process 400 may end.

Example System Implementation and Architecture

FIG. 7 is a block diagram showing an embodiment in which a validated ID computing system 100 (or simply “computing system 100”) is in communication with a network 160 and an optional network 170, and various systems, such as user computing device(s) 162 and service provider(s)/retailer(s) 164, are also in communication with the networks 160 and 170. The computing system 100 may be used to implement systems and methods described herein. In some embodiments the network 170 may be separate and distinct from the network 160, wherein the network 170 is used to provide out-of-band verification of a validated ID token.

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

In the embodiment of FIG. 7, the computing system 100 includes a digital identification validation module 150 and/or validated identification data store 108. The digital identification validation module 150 may be configured to validate a digital ID for an individual and/or verify or authenticate a validated ID token associated with the individual, for example in response to a request for verification from a service provider 164. The validated identification data 108 may be, for example, a database configured to store consumer profile data, personally identifying or out-of-wallet information for individuals, and/or validated ID tokens (current and expired) associated with an individual. Also shown in the embodiment of FIG. 7, the computing device(s) 162 may include a validated id module 162A which may be configured to send digital IDs to the computing system 100 and/or service provider(s)/retailer(s) 164, receive validated ID tokens from the computing system 100, and display validated ID tokens on the computing device 162. The validated ID module 162A may also be configured to periodically request a new or refreshed validated ID token in accordance with the processes described herein. These and other modules in the computing system 100 and/or computing device(s) 162 may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.

The computing system 100 is generally controlled and coordinated by operating system software, such as Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, 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 computing 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, I/O services, and provide a user interface, such as a graphical user interface (“GUI”), among other things.

The exemplary computing 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 computing system 100 may also include one or more multimedia devices 140, such as speakers, video cards, graphics accelerators, and microphones, for example.

In the embodiment of FIG. 7, the I/O devices and interfaces 110 provide a communication interface to various external devices. In the embodiment of FIG. 7, the computing system 100 is electronically coupled to networks 160 and 170, which comprises one or more of a LAN, WAN, and/or the Internet, for example, via a wired, wireless, or combination of wired and wireless, communication link 115. The networks 160 and 170 communicate with various computing devices and/or other electronic devices via wired or wireless communication links.

According to FIG. 7, in some embodiments, information may be provided to the computing system 100 over the network 160 from one or more data sources 166. The data sources 166 may include one or more internal and/or external data sources. The data sources 166 may include internal and external data sources which store, for example, credit bureau data (for example, credit bureau data from File One℠) and/or other consumer data. In some embodiments, one or more of the databases or data sources may be implemented using a relational database, such as Sybase, Oracle, CodeBase and Microsoft® SQL Server as well as other types of databases such as, for example, a flat file database, an entity-relationship database, and object-oriented database, and/or a record-based database.

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

Digital Identity

A digital identity service may be configured to compile digital identity information regarding a consumer and to make that digital identity information available to multiple data sources. For example, a digital identity service may be configured to obtain information regarding a consumer's identity from a physical ID (e.g., a driver's license, a birth certificate, a Social Security card, etc.), validate the authenticity of the provided physical ID (or more particularly, a photograph of the physical ID), and combine the consumer information from the authenticated physical ID with authentication information of the consumer (e.g., authenticating that the consumer really is who they say they are, such as via one or more out of wallet questions, and/or that the consumer is who is identified in the physical ID). Thus, the digital identity service can generate a digital identity of the consumer that is populated with information with minimal effort from the consumer, but that is validated in multiple ways so that the information can be trusted by various entities, including the various validation methods discussed above with reference to FIGS. 1-7.

FIG. 8 is a flowchart illustrating an example process of generating a digital identity for a consumer, such as may be initiated when a consumer attempts to register for an online service (e.g., a credit monitoring service). In the embodiment of FIG. 8, the method is divided into two columns, with the left column indicating actions that a consumer and/or consumer mobile device may perform, while the right-hand column indicates actions that a digital identity service and/or related computing systems may perform. Depending on the embodiment, the blocks may be performed by different entities. Additionally, the blocks may be performed in an order different than is illustrated and/or the method may contain additional or fewer blocks.

Beginning at block 810, a consumer accesses a registration site or application on a mobile device (or a non-mobile device). For example, a consumer may access a sign-up page for a free (or paid) credit monitoring service, which requires personal identification information of the consumer in order to register for the credit monitoring service. In other embodiments, the consumer may visit a site or app of the digital identity service directly, such that the process begins with a consumer requesting establishment of a digital identity (e.g., without initiating registration with any other service).

Next, at block 820, the consumer provides a photograph of the consumer's driver's license and/or other identification document, such as a passport, birth certificate, Social Security card, school identification, etc. Depending on the embodiment, the consumer may provide images of both a front and back of the identification document because, for example, the back of certain identification documents includes valuable identification information and/or information that is usable to validate the authenticity of the identification document.

Moving to block 830, the digital identity service scans the driver's license for identification information of the consumer. For example, the digital identity service may perform OCR on the driver's license and then parse information on the driver's license according to regular expression logic configured to identify various pieces of identification information. In one embodiment, the digital identity service uses technology provided by another party to extract information from the identification document. Alternatively, the digital identity service may forward the driver's license images to another entity so that the information extraction may be performed by that other entity and returned to the digital identity service.

In block 840, the consumer information extracted from the driver's license is provided to the enrollment service. For example, the consumer information may be used to pre-populate registration fields provided by the enrollment service so that the consumer is not required to manually provide such information. In some embodiments, the consumer information is provided later in the process, such as after the authenticity of the identification document is validated. In some embodiments, such as where the consumer is not enrolling in a service, block 840 may not be performed.

Next, at block 850, authenticity of the driver's license (or other form of identification) is validated, either using technology provided by the digital identity service itself and/or using document validation technology of one or more other entities. For example, in one embodiment the digital identity service provides the identification document images to a company such as 192 Business to perform a document validity check. In such an embodiment, the results of a validity check (e.g., a confirmation that the document is valid or an indication that the document may be invalid, and/or a confidence level of authenticity) may be returned to the digital identity service. In some embodiments, the information extraction at block 830 and/or the authenticity validation of block 850 are performed by a single entity, such as the digital identity service or another entity.

Moving to block 860, the identity of the individual is authenticated, such as to obtain a confidence level that the consumer really is the consumer identified in the driver's license information. Depending on the embodiment, various authentication techniques may be performed, such as by using out of wallet questions that are obtained from a consumer's credit data (e.g. questions regarding previous mortgage accounts, residence addresses, etc., that it is unlikely know by others besides the consumer). In some embodiments, the authentication is performed by a separate service, such as Experian's PreciseID service, and results of the authentication are provided back to the digital identity service.

At block 870, the consumer receives and responds to out of wallet questions and/or other authentication questions in order to authenticate the identity of the consumer. As noted above, various authentication methods may be used in order to arrive at a confidence level that the consumer is who is identified in the provided identification document photographs.

Moving to block 880, in some embodiments once the consumer is authenticated the consumer is asked to provide a current photograph (and/or other biometric) to be included in the consumer's digital identity. For example, the consumer may obtain a photograph on the consumer's mobile device that is transmitted to the digital identity service. In other embodiments, a photograph is not obtained at block 880 and, instead, an existing photograph of the consumer is used in the digital identity of the consumer (or no photograph of the consumer is used in certain embodiments). For example, the photograph of the consumer from the driver's license (or other ID) may be used in the digital identity service and/or a photograph of the consumer may be obtained from one or more other data sources, such as a social network that has a profile picture of the consumer.

Next, at block 890 the digital identity service generates a digital identity for the consumer. Depending on the embodiment, the digital identity may include various data, such as a copy of the driver's license photograph(s), extracted information from the driver's license, authenticity information regarding the driver's license, authentication information regarding the individual identified in the driver's license, one or more photographs of the individual, device information associated with one or more devices from which the identification information was received (e.g., a device identifier for the mobile device of the consumer) and/or any other information relevant to the consumer's identity. In some embodiments additional data sources are accessed in order to obtain further information regarding the consumer, such as demographic data sources, publicly available data sources, marketing data sources, etc.

At block 895, the digital identity is made available for various applications. For example, with reference to the example registration process noted above, the digital identity may be provided to the registration site and used in registration of the consumer for the associated service. In some embodiments, the digital identity may be stored on a server of the digital identity service and made available to third parties (e.g., online websites) via an API and/or other exchange protocol. In some embodiments, the digital identity may be stored on the consumers device, e.g., a mobile device of the consumer, such that information from the digital identity may be provided directly to requesting entities (e.g. a financial institution that requires the identity information) from the consumers mobile device, such as using one or more of the methods discussed above, for example.

FIG. 9 is a flow diagram illustrating example information components that may be combined in order to generate a digital identity of a consumer. Depending on the embodiment, fewer and/or additional information may be combined in a consumer's digital identity.

In the embodiment of FIG. 9, a state driver's license, authenticated identity information, and a current photo are each received (or generated or accessed) by the digital identity system. Also shown in FIG. 9 are other data regarding the individual, which may include any other type of data, such as demographic, psychographic, etc. In this embodiment, the digital identity system combines the received information (or at least portions of the information) in order to generate a digital identity of the consumer, such as the example digital identity illustrated.

The example digital entity is in the form of a user interface that may be provided to any interested party to provide consumer information, as well as information regarding the validity of the information and authentication of the individual. In other embodiments, the information may be in any other format, such as in a database or other data structure. The example digital identity of FIG. 9 illustrates information extracted from the consumers driver's license, and also indicates that the driver's license was validated on a particular date (Aug. 23, 2012 in this example), and that the identity of the indicated individual (e.g., John Doe in this example), was authenticated on May 22, 2013. In this example, a validation stamp (e.g. the logo in the lower right corner of the digital identity) indicates a source of the digital identity, such that the information provided therein may be more trustworthy. In some embodiments additional or less information regarding the validity of the provided consumer information may be included, such as a date and/or location where the consumer was last authenticated. In some embodiments, the consumer is required to re-authenticate periodically (as discussed in certain embodiments discussed above). In some embodiments, the digital identity may be shown to an interested party and authentication of the digital identity may occur in real time, such as based on a device identifier, location information of the device, authentication questions asked of the consumer, and/or other information available to the digital identity system.

FIG. 10 is a block diagram illustrating one embodiment of a digital identity system in communication with various services that access digital identities of consumers that are stored by the digital identity system. In the example of FIG. 10, an online service, a mobile service, a digital wallet service, and one or more other services, may each communicate with the digital identity service in order to access one or more digital identities of consumers via an API that is configured to allow such communication. Thus, the various services may easily access digital identity information of consumers (e.g., possibly after receiving authorization to do so from the consumer) in order to provide services to consumers, validate the consumer's identity, etc. In other embodiments, the services may communicate with the digital identity system (and the digital identities stored therein) in any other manner.

FIG. 11 is a block diagram illustrating one embodiment of a digital identity that is stored on a particular consumer's mobile device. As noted above, the digital identity may be a valuable information item that is usable by a consumer to quickly and reliably provide information to various entities. Examples of services to which the digital identity may be provided via the mobile device are an online service, a mobile service, and a brick-and-mortar service, as well as any other service. The digital ID may be transmitted to the online service via any available protocol, such as via an Internet connection or near field communication, for example. In one embodiment, the digital ID is displayed to an individual representing the brick and mortar service (e.g., a nightclub bouncer or cashier at a restaurant or store) in order to allow the individual to view the authenticated ID of the consumer.

In one embodiment, a digital identity may be used in conjunction with other services, such as a payment service, to streamline a payment process by providing identification and payment information concurrently, for example. In some embodiments, the digital identity may be used in conjunction with alerts that are provided to consumers. For example, a consumer may be provided an alert when the consumer approaches a business establishment of interest in view of a portion of the digital identity of the consumer being accessible to the business.

Other

Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The code modules may be stored on any type of non-transitory computer-readable medium or computer storage device, such as hard drives, solid state memory, optical disc, and/or the like. The systems and modules may also be transmitted as generated data signals (for example, as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and may take a variety of forms (for example, as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage such as, for example, volatile or non-volatile storage.

The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example 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. For example, the methods described herein may be performed by the address verification computing system 100 and/or any other suitable computing device. The methods may be executed on the computing devices in response to execution of software instructions or other executable code read from a tangible 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.

It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.

Claims

1. A computing system for managing a digital identity of an individual, the computer system comprising: one or more processors in communication with one or more non-transitory computer-readable media comprising computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to: obtain a result of a comparison between (a) a set of personally identifying information associated with a form of identification (“ID”) of an individual and (b) information in consumer profile data for the individual;generate a validated ID token based at least in part on the result of the comparison between the set of personally identifying information and the consumer profile data, wherein the validated ID token is specific to the individual and is usable to authenticate the individual;associate the validated ID token and the consumer profile data in a validated ID data store;receive a request for the validated ID token for the individual; andtransmit a response to the request that includes the validated ID token.
2. The computing system of claim 1, wherein the validated ID token is generated in response to a determination that the consumer profile data was not associated with a pre-existing ID token.
3. The computing system of claim 1, wherein the computer-executable instructions further cause the one or more processors to: retrieve a digital image of the form of ID of the individual from a camera of a mobile device of the individual; andextract the set of personally identifying information associated with the ID of the individual from the digital image.
4. The computing system of claim 1, wherein the request is sent by a third party merchant.
5. The computing system of claim 1, wherein the computer-executable instructions further cause the one or more processors to: generate a new validated ID token periodically for the individual.
6. The computing system of claim 1, wherein the computer-executable instructions further cause the one or more processors to: provide the validated ID token to the individual over a first network, wherein transmitting the response to the request that includes the validated ID token includes transmitting the response over a second network.
7. The computing system of claim 1, wherein the validated ID token is valid for use only for a predetermined period of time.
8. The computing system of claim 1, wherein the validated ID token is associated with a particular computing device of a user.
9. The computing system of claim 8, wherein the validated ID token tracks the usage of the data of the computing device.
10. The computing system of claim 1, wherein the request for the validated ID token is from a point of sale device of a third party merchant.
11. The computing system of claim 1, wherein the computer-executable instructions further cause the one or more processors to: provide a user interface to the individual, wherein the user interface includes a selectable interface element configured to, upon selection by the individual, invalidate the validated ID token.
12. A method of managing a digital ID of an individual, the method implemented by one or more computing devices configured with specific computer-executable instructions and comprising: obtaining a result of a comparison between (a) a set of personally identifying information associated with a form of identification (“ID”) of an individual and (b) information in consumer profile data for the individual;generating a validated ID token based at least in part on the result of the comparison between the set of personally identifying information and the consumer profile data, wherein the validated ID token is specific to the individual and is usable to authenticate the individual;associating the validated ID token and the consumer profile data in a validated ID data store;receiving a request for the validated ID token for the individual; andtransmitting a response to the request that includes at last a portion of the validated ID token.
13. The method of claim 12, wherein the form of ID corresponds to at least one of a driver's license, a passport, or a government-issued form of ID.
14. The method of claim 12, wherein receiving the request comprises receiving a scan of the form of ID.
15. The method of claim 12, wherein the method further comprises: identifying a photograph of the individual from a social media site corresponding to the individual; andcomparing the photograph to another photograph of the individual,wherein generating the validated ID token is further based at least in part on a determination that at least a portion of the another photograph corresponds to at least a portion of the photograph of the individual.
16. The method of claim 12, wherein the validated ID token comprises an indication that the form of ID is valid, wherein the indication that the form of ID is valid indicates that the form of ID was issued by an issuing entity.
17. The method of claim 12, wherein the validated ID token comprises an indication that an identity of the individual has been validated.
18. The method of claim 12, wherein the accessed consumer profile data comprises credit data.
19. The method of claim 12 further comprising storing the validated ID token on a network-accessible server and providing an application programming interface to one or more online services, wherein the application programming interface is configured to allow the one or more online services to access the validated ID token.
20. The method of claim 12, wherein the response to the request includes the entire validated ID token.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation U.S. patent application Ser. No. 16/657,174, filed Oct. 18, 2019, titled “Digital Identity”, which is a continuation U.S. patent application Ser. No. 15/662,712, filed Jul. 28, 2017, titled “Digital Identity”, which is a continuation of U.S. patent application Ser. No. 14/276,540, filed on May 13, 2014, titled “Digital Identity”, which claims priority benefit to U.S. Provisional Application No. 61/826,925, titled “DIGITAL IDENTITY”, filed on May 23, 2013, each of which is hereby incorporated by reference in its entirety herein.

US Referenced Citations (1271)

Number	Name	Date	Kind
3752904	Waterbury	Aug 1973	A
4795890	Goldman	Jan 1989	A
4891503	Jewell	Jan 1990	A
4977595	Ohta et al.	Dec 1990	A
4989141	Lyons et al.	Jan 1991	A
5126936	Champion et al.	Jun 1992	A
5351293	Michener et al.	Sep 1994	A
5590038	Pitroda	Dec 1996	A
5640577	Scharmer	Jun 1997	A
5659725	Levy et al.	Aug 1997	A
5659731	Gustafson	Aug 1997	A
5715314	Payne et al.	Feb 1998	A
5719941	Swift et al.	Feb 1998	A
5748098	Grace	May 1998	A
5754632	Smith	May 1998	A
5828840	Cowan et al.	Oct 1998	A
5832068	Smith	Nov 1998	A
5844218	Kawan et al.	Dec 1998	A
5866889	Weiss et al.	Feb 1999	A
5881131	Farris et al.	Mar 1999	A
5903830	Joao et al.	May 1999	A
5913196	Talmor et al.	Jun 1999	A
5956693	Geerlings	Sep 1999	A
5966695	Melchione et al.	Oct 1999	A
5999596	Walker et al.	Dec 1999	A
6021397	Jones et al.	Feb 2000	A
6021943	Chastain	Feb 2000	A
6026440	Shrader et al.	Feb 2000	A
6038551	Barlow et al.	Mar 2000	A
6055570	Nielsen	Apr 2000	A
6069941	Byrd et al.	May 2000	A
6072894	Payne	Jun 2000	A
6073106	Rozen et al.	Jun 2000	A
6073140	Morgan et al.	Jun 2000	A
6085242	Chandra	Jul 2000	A
6119103	Basch et al.	Sep 2000	A
6128602	Northington et al.	Oct 2000	A
6157707	Baulier et al.	Dec 2000	A
6161139	Win et al.	Dec 2000	A
6182068	Culliss	Jan 2001	B1
6182219	Feldbau et al.	Jan 2001	B1
6182229	Nielsen	Jan 2001	B1
6196460	Shin	Mar 2001	B1
6233588	Marchoili et al.	May 2001	B1
6247000	Hawkins et al.	Jun 2001	B1
6253202	Gilmour	Jun 2001	B1
6254000	Degen et al.	Jul 2001	B1
6263447	French et al.	Jul 2001	B1
6269369	Robertson	Jul 2001	B1
6282658	French et al.	Aug 2001	B2
6292795	Peters et al.	Sep 2001	B1
6311169	Duhon	Oct 2001	B2
6321339	French et al.	Nov 2001	B1
6327578	Linehan	Dec 2001	B1
6343279	Bissonette et al.	Jan 2002	B1
6356937	Montville et al.	Mar 2002	B1
6397212	Biffar	May 2002	B1
6453353	Win et al.	Sep 2002	B1
6457012	Jatkowski	Sep 2002	B1
6463533	Calamera et al.	Oct 2002	B1
6473740	Cockril et al.	Oct 2002	B2
6496936	French et al.	Dec 2002	B1
6510415	Talmor et al.	Jan 2003	B1
6523021	Monberg et al.	Feb 2003	B1
6523041	Morgan et al.	Feb 2003	B1
6539377	Culliss	Mar 2003	B1
6564210	Korda et al.	May 2003	B1
6571334	Feldbau et al.	May 2003	B1
6574736	Andrews	Jun 2003	B1
6581059	Barrett et al.	Jun 2003	B1
6601173	Mohler	Jul 2003	B1
6607136	Atsmon et al.	Aug 2003	B1
6622131	Brown et al.	Sep 2003	B1
6629245	Stone et al.	Sep 2003	B1
6647383	August et al.	Nov 2003	B1
6654786	Fox et al.	Nov 2003	B1
6658393	Basch et al.	Dec 2003	B1
6679425	Sheppard et al.	Jan 2004	B1
6714944	Shapiro et al.	Mar 2004	B1
6725381	Smith et al.	Apr 2004	B1
6734886	Hagan et al.	May 2004	B1
6750985	Rhoads	Jun 2004	B2
6754665	Futagami et al.	Jun 2004	B1
6766327	Morgan, Jr. et al.	Jul 2004	B2
6766946	Iida et al.	Jul 2004	B2
6782379	Lee	Aug 2004	B2
6795812	Lent et al.	Sep 2004	B1
6796497	Benkert et al.	Sep 2004	B2
6804346	Mewhinney	Oct 2004	B1
6805287	Bishop et al.	Oct 2004	B2
6816850	Culliss	Nov 2004	B2
6816871	Lee	Nov 2004	B2
6823319	Lynch et al.	Nov 2004	B1
6829711	Kwok et al.	Dec 2004	B1
6845448	Chaganti et al.	Jan 2005	B1
6857073	French et al.	Feb 2005	B2
6871287	Ellingson	Mar 2005	B1
6892307	Wood et al.	May 2005	B1
6900731	Kreiner et al.	May 2005	B2
6907408	Angel	Jun 2005	B2
6908030	Rajasekaran et al.	Jun 2005	B2
6910624	Natsuno	Jun 2005	B1
6920435	Hoffman et al.	Jul 2005	B2
6928487	Eggebraaten et al.	Aug 2005	B2
6934714	Meinig	Aug 2005	B2
6934849	Kramer et al.	Aug 2005	B2
6934858	Woodhill	Aug 2005	B2
6947989	Gullotta et al.	Sep 2005	B2
6950807	Brock	Sep 2005	B2
6950809	Dahan et al.	Sep 2005	B2
6950858	Ogami	Sep 2005	B2
6965881	Brickell et al.	Nov 2005	B1
6968319	Remington et al.	Nov 2005	B1
6973462	Dattero et al.	Dec 2005	B2
6983381	Jerdonek	Jan 2006	B2
6985887	Sunstein et al.	Jan 2006	B1
6986461	Geoghegan et al.	Jan 2006	B1
6988085	Hedy	Jan 2006	B2
6993596	Hinton et al.	Jan 2006	B2
6999941	Agarwal	Feb 2006	B1
7016907	Boreham et al.	Mar 2006	B2
7028013	Saeki	Apr 2006	B2
7028052	Chapman et al.	Apr 2006	B2
7039607	Watarai et al.	May 2006	B2
7043476	Robson	May 2006	B2
7058817	Ellmore	Jun 2006	B1
7059531	Beenau et al.	Jun 2006	B2
7062475	Szabo et al.	Jun 2006	B1
7076462	Nelson et al.	Jul 2006	B1
7085727	VanOrman	Aug 2006	B2
7089584	Sharma	Aug 2006	B1
7107241	Pinto	Sep 2006	B1
7117172	Black	Oct 2006	B1
7121471	Beenau et al.	Oct 2006	B2
7124144	Christianson et al.	Oct 2006	B2
7154375	Beenau et al.	Dec 2006	B2
7155739	Bari et al.	Dec 2006	B2
7174454	Roskind	Feb 2007	B2
7177846	Moenickheim et al.	Feb 2007	B2
7194416	Provost et al.	Mar 2007	B1
7200602	Jonas	Apr 2007	B2
7203653	McIntosh	Apr 2007	B1
7209895	Kundtz et al.	Apr 2007	B2
7219107	Beringer	May 2007	B2
7222369	Vering et al.	May 2007	B2
7225464	Satyavolu et al.	May 2007	B2
7231657	Honarvar et al.	Jun 2007	B2
7234156	French et al.	Jun 2007	B2
7234160	Vogel et al.	Jun 2007	B2
7237267	Rayes et al.	Jun 2007	B2
7240199	Tomkow	Jul 2007	B2
7240363	Ellingson	Jul 2007	B1
7243369	Bhat et al.	Jul 2007	B2
7246067	Austin et al.	Jul 2007	B2
7246740	Swift et al.	Jul 2007	B2
7249096	Lasater et al.	Jul 2007	B1
7249113	Continelli et al.	Jul 2007	B1
7251347	Smith	Jul 2007	B2
7263497	Wiser et al.	Aug 2007	B1
7289971	O'Neil et al.	Oct 2007	B1
7303120	Beenau et al.	Dec 2007	B2
7310611	Shibuya et al.	Dec 2007	B2
7314167	Kiliccote	Jan 2008	B1
7328233	Salim et al.	Feb 2008	B2
7330871	Barber	Feb 2008	B2
7333635	Tsantes et al.	Feb 2008	B2
7337468	Metzger	Feb 2008	B2
7340042	Cluff et al.	Mar 2008	B2
7340679	Botscheck et al.	Mar 2008	B2
7343149	Benco	Mar 2008	B2
7343295	Pomerance	Mar 2008	B2
7356503	Johnson et al.	Apr 2008	B1
7356506	Watson et al.	Apr 2008	B2
7356516	Richey et al.	Apr 2008	B2
7370044	Mulhern et al.	May 2008	B2
7370351	Ramachandran et al.	May 2008	B1
7383988	Slonecker, Jr.	Jun 2008	B2
7386448	Poss et al.	Jun 2008	B1
7389913	Starrs	Jun 2008	B2
7403942	Bayliss	Jul 2008	B1
7421732	Costa-Requena et al.	Sep 2008	B2
7433864	Malik	Oct 2008	B2
7437679	Uemura et al.	Oct 2008	B2
7438226	Helsper et al.	Oct 2008	B2
7444414	Foster et al.	Oct 2008	B2
7444518	Dharmarajan et al.	Oct 2008	B1
7451113	Kasower	Nov 2008	B1
7458508	Shao et al.	Dec 2008	B1
7460857	Roach, Jr.	Dec 2008	B2
7467401	Cicchitto	Dec 2008	B2
7478157	Bohrer et al.	Jan 2009	B2
7480631	Merced et al.	Jan 2009	B1
7490356	Lieblich et al.	Feb 2009	B2
7503489	Heffez	Mar 2009	B2
7509117	Yum	Mar 2009	B2
7509278	Jones	Mar 2009	B2
7512221	Toms	Mar 2009	B2
7519558	Ballard et al.	Apr 2009	B2
7526796	Lulich et al.	Apr 2009	B2
7529698	Joao	May 2009	B2
7530097	Casco-Arias et al.	May 2009	B2
7542993	Satterfield et al.	Jun 2009	B2
7543739	Brown et al.	Jun 2009	B2
7546271	Chmielewski et al.	Jun 2009	B1
7548886	Kirkland et al.	Jun 2009	B2
7552080	Willard et al.	Jun 2009	B1
7552123	Wade et al.	Jun 2009	B2
7552467	Lindsay	Jun 2009	B2
7555459	Dhar et al.	Jun 2009	B2
7562184	Henmi et al.	Jul 2009	B2
7562814	Shao et al.	Jul 2009	B1
7566002	Love et al.	Jul 2009	B2
7571473	Boydstun et al.	Aug 2009	B1
7575157	Barnhardt et al.	Aug 2009	B2
7577665	Ramer et al.	Aug 2009	B2
7577934	Anonsen et al.	Aug 2009	B2
7580884	Cook	Aug 2009	B2
7581112	Brown et al.	Aug 2009	B2
7584126	White	Sep 2009	B1
7584146	Duhon	Sep 2009	B1
7587366	Grim, III et al.	Sep 2009	B2
7587368	Felsher	Sep 2009	B2
7603701	Gaucas	Oct 2009	B2
7606401	Hoffman et al.	Oct 2009	B2
7606725	Robertson et al.	Oct 2009	B2
7610216	May et al.	Oct 2009	B1
7613600	Krane	Nov 2009	B2
7620596	Knudson et al.	Nov 2009	B2
7623844	Herrmann et al.	Nov 2009	B2
7630932	Danaher et al.	Dec 2009	B2
7634737	Beringer et al.	Dec 2009	B2
7636941	Blinn et al.	Dec 2009	B2
7641113	Alvarez et al.	Jan 2010	B1
7647344	Skurtovich, Jr. et al.	Jan 2010	B2
7653592	Flaxman et al.	Jan 2010	B1
7653600	Gustin	Jan 2010	B2
7653688	Bittner	Jan 2010	B2
7657431	Hayakawa	Feb 2010	B2
7660989	Tomkow	Feb 2010	B2
7672833	Blume et al.	Mar 2010	B2
7676834	Camaisa et al.	Mar 2010	B2
7685096	Margolus et al.	Mar 2010	B2
7685209	Norton et al.	Mar 2010	B1
7685279	Miltonberger et al.	Mar 2010	B2
7686214	Shao et al.	Mar 2010	B1
7689487	Britto et al.	Mar 2010	B1
7689505	Kasower	Mar 2010	B2
7689563	Jacobson	Mar 2010	B1
7690032	Peirce	Mar 2010	B1
7698214	Lindgren	Apr 2010	B1
7698217	Phillips et al.	Apr 2010	B1
7698445	Fitzpatrick et al.	Apr 2010	B2
7698558	Tomkow	Apr 2010	B2
7707271	Rudkin et al.	Apr 2010	B2
7707624	Tomkow	Apr 2010	B2
7708190	Brandt et al.	May 2010	B2
7711635	Steele et al.	May 2010	B2
7725385	Royer et al.	May 2010	B2
7730078	Schwabe et al.	Jun 2010	B2
7739139	Robertson et al.	Jun 2010	B2
7747494	Kothari et al.	Jun 2010	B1
7747520	Livermore et al.	Jun 2010	B2
7747521	Serio	Jun 2010	B2
7747542	Morley et al.	Jun 2010	B2
7761384	Madhogarhia	Jul 2010	B2
7761568	Levi et al.	Jul 2010	B1
7765166	Beringer et al.	Jul 2010	B2
7765311	Itabashi et al.	Jul 2010	B2
7769696	Yoda	Aug 2010	B2
7769697	Fieschi et al.	Aug 2010	B2
7769998	Lynch et al.	Aug 2010	B2
7774270	MacCloskey	Aug 2010	B1
7788040	Haskell et al.	Aug 2010	B2
7792715	Kasower	Sep 2010	B1
7792725	Booraem et al.	Sep 2010	B2
7793835	Coggeshall et al.	Sep 2010	B1
7797725	Lunt et al.	Sep 2010	B2
7801828	Candella et al.	Sep 2010	B2
7801956	Cumberbatch et al.	Sep 2010	B1
7802104	Dickinson	Sep 2010	B2
7810036	Bales et al.	Oct 2010	B2
7818228	Coulter	Oct 2010	B1
7827115	Weller et al.	Nov 2010	B2
7841004	Balducci et al.	Nov 2010	B1
7841008	Cole et al.	Nov 2010	B1
7844520	Franklin	Nov 2010	B1
7849014	Erikson	Dec 2010	B2
7849624	Holt et al.	Dec 2010	B2
7853493	DeBie et al.	Dec 2010	B2
7853533	Eisen	Dec 2010	B2
7853984	Antell et al.	Dec 2010	B2
7865557	Tomkow	Jan 2011	B2
7865958	Lieblich et al.	Jan 2011	B2
7870078	Clark et al.	Jan 2011	B2
7877304	Coulter	Jan 2011	B1
7877784	Chow et al.	Jan 2011	B2
7880728	de los Reyes et al.	Feb 2011	B2
7886008	Tomkow et al.	Feb 2011	B2
7908242	Achanta	Mar 2011	B1
7909246	Hogg et al.	Mar 2011	B2
7912865	Akerman et al.	Mar 2011	B2
7930285	Abraham et al.	Apr 2011	B2
7930411	Hayward	Apr 2011	B1
7941324	Sholtis	May 2011	B1
7958046	Doerner et al.	Jun 2011	B2
7966192	Pagliari et al.	Jun 2011	B2
7966372	Tomkow	Jun 2011	B1
7970679	Kasower	Jun 2011	B2
7975299	Balducci et al.	Jul 2011	B1
7979908	Millwee	Jul 2011	B2
7983932	Kane	Jul 2011	B2
7983979	Holland, IV	Jul 2011	B2
7991688	Phelan et al.	Aug 2011	B2
8001153	Skurtovich, Jr. et al.	Aug 2011	B2
8001235	Russ et al.	Aug 2011	B2
8005155	Lee et al.	Aug 2011	B1
8011582	Ghafarzadeh	Sep 2011	B2
8032932	Speyer et al.	Oct 2011	B2
8037097	Guo et al.	Oct 2011	B2
8041956	White et al.	Oct 2011	B1
8055904	Cato et al.	Nov 2011	B1
8060424	Kasower	Nov 2011	B2
8060916	Bajaj et al.	Nov 2011	B2
8065233	Lee et al.	Nov 2011	B2
8073785	Candella et al.	Dec 2011	B1
8078453	Shaw	Dec 2011	B2
8078524	Crawford et al.	Dec 2011	B2
8078881	Liu	Dec 2011	B1
8079070	Camaisa et al.	Dec 2011	B2
8099341	Varghese	Jan 2012	B2
8104679	Brown	Jan 2012	B2
8116731	Buhrmann et al.	Feb 2012	B2
8116751	Aaron	Feb 2012	B2
8127982	Casey et al.	Mar 2012	B1
8127986	Taylor et al.	Mar 2012	B1
8131777	McCullouch	Mar 2012	B2
8144368	Rodriguez	Mar 2012	B2
8151327	Eisen	Apr 2012	B2
8161104	Tomkow	Apr 2012	B2
8172132	Love et al.	May 2012	B2
8175889	Girulat et al.	May 2012	B1
8185747	Wood et al.	May 2012	B2
8190513	Felger	May 2012	B2
8195549	Kasower	Jun 2012	B2
8209389	Tomkow	Jun 2012	B2
8219771	Le Neel	Jul 2012	B2
8219822	Camaisa et al.	Jul 2012	B2
8224723	Bosch et al.	Jul 2012	B2
8224913	Tomkow	Jul 2012	B2
8225395	Atwood et al.	Jul 2012	B2
8229810	Butera et al.	Jul 2012	B2
8229844	Felger	Jul 2012	B2
8234498	Britti et al.	Jul 2012	B2
8239677	Colson	Aug 2012	B2
8239929	Kwan et al.	Aug 2012	B2
8241369	Stevens	Aug 2012	B2
8244629	Lewis et al.	Aug 2012	B2
8244848	Narayanan et al.	Aug 2012	B1
8255452	Piliouras	Aug 2012	B2
8255971	Webb et al.	Aug 2012	B1
8255978	Dick	Aug 2012	B2
8260706	Freishtat et al.	Sep 2012	B2
8261334	Hazlehurst et al.	Sep 2012	B2
8266065	Dilip et al.	Sep 2012	B2
8275845	Tomkow	Sep 2012	B2
8280348	Snyder et al.	Oct 2012	B2
8281372	Vidal	Oct 2012	B1
8285613	Coulter	Oct 2012	B1
8285656	Chang et al.	Oct 2012	B1
8291218	Garcia et al.	Oct 2012	B2
8291477	Lunt	Oct 2012	B2
8295898	Ashfield et al.	Oct 2012	B2
8296562	Williams et al.	Oct 2012	B2
8302164	Lunt	Oct 2012	B2
8312033	McMillan	Nov 2012	B1
8315940	Winbom et al.	Nov 2012	B2
8327429	Speyer et al.	Dec 2012	B2
8359278	Domenikos et al.	Jan 2013	B2
8359393	Metzger	Jan 2013	B2
8374634	Dankar et al.	Feb 2013	B2
8374973	Herbrich et al.	Feb 2013	B2
8406736	Das et al.	Mar 2013	B2
8423648	Ferguson et al.	Apr 2013	B2
8442886	Haggerty et al.	May 2013	B1
8442910	Morris et al.	May 2013	B2
8443202	White et al.	May 2013	B2
8447016	Kugler et al.	May 2013	B1
8456293	Trundle et al.	Jun 2013	B1
8464939	Taylor et al.	Jun 2013	B1
8468090	Lesandro et al.	Jun 2013	B2
8468198	Tomkow	Jun 2013	B2
8468199	Tomkow	Jun 2013	B2
8478674	Kapczynski et al.	Jul 2013	B1
8478981	Khan et al.	Jul 2013	B2
8484186	Kapczynski et al.	Jul 2013	B1
8484706	Tomkow	Jul 2013	B2
8504628	Tomkow	Aug 2013	B2
8515828	Wolf et al.	Aug 2013	B1
8515844	Kasower	Aug 2013	B2
8527357	Ganesan	Sep 2013	B1
8527417	Telle et al.	Sep 2013	B2
8527773	Metzger	Sep 2013	B1
8528078	Camaisa et al.	Sep 2013	B2
8533118	Weller et al.	Sep 2013	B2
8533791	Samuelsson et al.	Sep 2013	B2
8549590	de Villiers Prichard et al.	Oct 2013	B1
8560381	Green et al.	Oct 2013	B2
8572391	Golan et al.	Oct 2013	B2
8578496	Krishnappa	Nov 2013	B1
8588748	Buhrman et al.	Nov 2013	B2
8600886	Ramavarjula et al.	Dec 2013	B2
8601602	Zheng	Dec 2013	B1
8606234	Pei et al.	Dec 2013	B2
8606694	Campbell et al.	Dec 2013	B2
8620942	Hoffman et al.	Dec 2013	B1
8630938	Cheng et al.	Jan 2014	B2
8645275	Seifert et al.	Feb 2014	B2
8646051	Paden et al.	Feb 2014	B2
8656504	Lurey et al.	Feb 2014	B2
8671115	Skurtovich, Jr. et al.	Mar 2014	B2
8688543	Dominquez	Apr 2014	B2
8689311	Blinn et al.	Apr 2014	B2
8695105	Mahendrakar et al.	Apr 2014	B2
8701199	Dotan et al.	Apr 2014	B1
8705718	Baniak et al.	Apr 2014	B2
8706599	Koenig et al.	Apr 2014	B1
8725613	Celka et al.	May 2014	B1
8738934	Lurey et al.	May 2014	B2
8744956	DiChiara et al.	Jun 2014	B1
8751388	Chapa	Jun 2014	B1
8762287	Morley et al.	Jun 2014	B2
8768914	Scriffignano et al.	Jul 2014	B2
8769614	Knox et al.	Jul 2014	B1
8781882	Arboletti et al.	Jul 2014	B1
8781953	Kasower	Jul 2014	B2
8781975	Bennett et al.	Jul 2014	B2
8782154	Tomkow	Jul 2014	B2
8782217	Arone et al.	Jul 2014	B1
8782753	Lunt	Jul 2014	B2
8793166	Mizhen	Jul 2014	B2
8793509	Nelson et al.	Jul 2014	B1
8793777	Colson	Jul 2014	B2
8800005	Lunt	Aug 2014	B2
8806584	Lunt	Aug 2014	B2
8818888	Kapczynski et al.	Aug 2014	B1
8819793	Gottschalk, Jr.	Aug 2014	B2
8826371	Webb et al.	Sep 2014	B2
8826393	Eisen	Sep 2014	B2
8831564	Ferguson et al.	Sep 2014	B2
8839394	Dennis et al.	Sep 2014	B2
8856894	Dean et al.	Oct 2014	B1
8862514	Eisen	Oct 2014	B2
8868932	Lurey et al.	Oct 2014	B2
D717332	Nies et al.	Nov 2014	S
8931058	DiChiara et al.	Jan 2015	B2
8938399	Herman	Jan 2015	B1
8954459	McMillan et al.	Feb 2015	B1
8972400	Kapczynski et al.	Mar 2015	B1
9010627	Prasad et al.	Apr 2015	B1
9043886	Srinivasan et al.	May 2015	B2
9047473	Samuelsson et al.	Jun 2015	B2
9100400	Lunt	Aug 2015	B2
9106691	Burger et al.	Aug 2015	B1
9124606	Metzger	Sep 2015	B2
9147042	Haller et al.	Sep 2015	B1
9147117	Madhu et al.	Sep 2015	B1
9154482	Dudziak et al.	Oct 2015	B2
9158903	Metzger	Oct 2015	B2
9185123	Dennis et al.	Nov 2015	B2
9195984	Spector et al.	Nov 2015	B1
9195985	Domenica et al.	Nov 2015	B2
9196004	Eisen	Nov 2015	B2
9203819	Fenton et al.	Dec 2015	B2
9215223	Kirsch	Dec 2015	B2
9235728	Gottschalk, Jr. et al.	Jan 2016	B2
9246899	Durney et al.	Jan 2016	B1
9256624	Skurtovich, Jr. et al.	Feb 2016	B2
9269085	Webb et al.	Feb 2016	B2
9294476	Lurey et al.	Mar 2016	B1
9344413	Kirsch	May 2016	B2
9361597	Britton et al.	Jun 2016	B2
9380057	Knauss	Jun 2016	B2
9390384	Eisen	Jul 2016	B2
9391971	Lunt	Jul 2016	B2
9412141	Prichard et al.	Aug 2016	B2
9420448	Dankar et al.	Aug 2016	B2
9462044	Preibisch et al.	Oct 2016	B1
9465786	Lurey et al.	Oct 2016	B2
9467445	Egan et al.	Oct 2016	B2
9491160	Livesay et al.	Nov 2016	B2
9578014	Sondhi et al.	Feb 2017	B2
9600651	Ryan et al.	Mar 2017	B1
9607336	Dean et al.	Mar 2017	B1
9626680	Ryan et al.	Apr 2017	B1
9633322	Burger	Apr 2017	B1
9641521	Egan et al.	May 2017	B2
9665854	Burger et al.	May 2017	B1
9684905	Haller et al.	Jun 2017	B1
9697521	Webb et al.	Jul 2017	B2
9706402	Kueh	Jul 2017	B2
9710523	Skurtovich, Jr. et al.	Jul 2017	B2
9721147	Kapczynski	Aug 2017	B1
9734501	Durney et al.	Aug 2017	B2
9754256	Britton et al.	Sep 2017	B2
9754311	Eisen	Sep 2017	B2
9760885	Ramalingam et al.	Sep 2017	B1
9779392	Prasad et al.	Oct 2017	B1
9818121	Snyder et al.	Nov 2017	B2
9843582	Mahendrakar et al.	Dec 2017	B2
9876796	Egan et al.	Jan 2018	B2
9892389	Domenica et al.	Feb 2018	B2
10075446	McMillan et al.	Sep 2018	B2
10089679	Eisen	Oct 2018	B2
10097551	Chan et al.	Oct 2018	B2
10115079	Burger et al.	Oct 2018	B1
10169761	Burger	Jan 2019	B1
10284548	Williams et al.	May 2019	B2
10356079	Lurey et al.	Jul 2019	B2
10373240	Ross et al.	Aug 2019	B1
10380565	Prasad	Aug 2019	B1
10395053	Samid	Aug 2019	B2
10438308	Prichard et al.	Oct 2019	B2
10453159	Kapczynski	Oct 2019	B2
10616196	Khitrenovich et al.	Apr 2020	B1
10637646	Krishnamacharya et al.	Apr 2020	B2
10652227	Spektor et al.	May 2020	B2
10664936	Chapa et al.	May 2020	B2
10685336	Burger et al.	Jun 2020	B1
10719873	Dean et al.	Jul 2020	B1
10740762	Burger	Aug 2020	B2
10771463	Berezin et al.	Sep 2020	B2
10783542	Walz et al.	Sep 2020	B2
10798093	Kaliski, Jr. et al.	Oct 2020	B2
10798096	Touati et al.	Oct 2020	B2
10863359	Talwar	Dec 2020	B2
10891618	Kinch et al.	Jan 2021	B2
10911234	Jain et al.	Feb 2021	B2
10999298	Eisen	May 2021	B2
11012240	Kirsch	May 2021	B1
11074641	Ross et al.	Jul 2021	B1
11095643	Huffman et al.	Aug 2021	B2
11120519	Kapczynski	Sep 2021	B2
11146676	Sena, Jr. et al.	Oct 2021	B2
11157872	McMillan et al.	Oct 2021	B2
11164178	Anderson et al.	Nov 2021	B2
11164271	Chapa et al.	Nov 2021	B2
11178128	Poschel et al.	Nov 2021	B2
11206246	Krishnamacharya	Dec 2021	B2
11232413	Burger et al.	Jan 2022	B1
11277439	Knopf	Mar 2022	B2
11288677	Burger	Mar 2022	B1
11290255	Krishnamacharya et al.	Mar 2022	B2
11310227	Hamburg et al.	Apr 2022	B2
11356460	Bondugula et al.	Jun 2022	B2
11361317	Billman et al.	Jun 2022	B2
11363015	Yeddula et al.	Jun 2022	B2
11431729	Bloomquist et al.	Aug 2022	B2
11449630	Talwar	Sep 2022	B2
11470069	Gillespie	Oct 2022	B2
11526884	Chilaka et al.	Dec 2022	B2
11532030	Smith	Dec 2022	B1
11544363	Deore et al.	Jan 2023	B2
11551226	Kumar	Jan 2023	B2
11587150	Ross et al.	Feb 2023	B1
11588639	Jain et al.	Feb 2023	B2
20010029482	Tealdi et al.	Oct 2001	A1
20010039532	Coleman, Jr. et al.	Nov 2001	A1
20010042785	Walker et al.	Nov 2001	A1
20010044729	Pomerance	Nov 2001	A1
20010044756	Watkins et al.	Nov 2001	A1
20010049274	Degraeve	Dec 2001	A1
20020004736	Roundtree et al.	Jan 2002	A1
20020013827	Edstrom et al.	Jan 2002	A1
20020013899	Faul	Jan 2002	A1
20020026519	Itabashi et al.	Feb 2002	A1
20020032635	Harris et al.	Mar 2002	A1
20020033846	Balasubramanian et al.	Mar 2002	A1
20020045154	Wood et al.	Apr 2002	A1
20020052754	Joyce et al.	May 2002	A1
20020059201	Work	May 2002	A1
20020059521	Tasler	May 2002	A1
20020069122	Yun et al.	Jun 2002	A1
20020077964	Brody et al.	Jun 2002	A1
20020087460	Hornung	Jul 2002	A1
20020091544	Middeljans et al.	Jul 2002	A1
20020091635	Dilip et al.	Jul 2002	A1
20020099635	Guiragosian	Jul 2002	A1
20020103933	Garon et al.	Aug 2002	A1
20020111816	Lortscher et al.	Aug 2002	A1
20020116247	Tucker et al.	Aug 2002	A1
20020120537	Morea et al.	Aug 2002	A1
20020120757	Sutherland et al.	Aug 2002	A1
20020120846	Stewart et al.	Aug 2002	A1
20020128962	Kasower	Sep 2002	A1
20020133365	Grey et al.	Sep 2002	A1
20020133462	Shteyn	Sep 2002	A1
20020138470	Zhou	Sep 2002	A1
20020143943	Lee et al.	Oct 2002	A1
20020147801	Gullotta et al.	Oct 2002	A1
20020157029	French et al.	Oct 2002	A1
20020169747	Chapman et al.	Nov 2002	A1
20020173994	Ferguson, III	Nov 2002	A1
20020174048	Dheer et al.	Nov 2002	A1
20020184509	Scheidt et al.	Dec 2002	A1
20020198800	Shamrakov	Dec 2002	A1
20020198806	Blagg et al.	Dec 2002	A1
20020198824	Cook	Dec 2002	A1
20020198830	Randell et al.	Dec 2002	A1
20030002671	Inchalik et al.	Jan 2003	A1
20030009418	Green et al.	Jan 2003	A1
20030009426	Ruiz-Sanchez	Jan 2003	A1
20030023531	Fergusson	Jan 2003	A1
20030036995	Lazerson	Feb 2003	A1
20030041031	Hedy	Feb 2003	A1
20030046311	Baidya et al.	Mar 2003	A1
20030046554	Leydier et al.	Mar 2003	A1
20030048904	Wang et al.	Mar 2003	A1
20030061163	Durfield	Mar 2003	A1
20030069839	Whittington et al.	Apr 2003	A1
20030069943	Bahrs et al.	Apr 2003	A1
20030097342	Whittingtom	May 2003	A1
20030097380	Mulhern et al.	May 2003	A1
20030105710	Barbara et al.	Jun 2003	A1
20030105733	Boreham	Jun 2003	A1
20030105742	Boreham et al.	Jun 2003	A1
20030115133	Bian	Jun 2003	A1
20030131102	Umbreit	Jul 2003	A1
20030154162	Danaher et al.	Aug 2003	A1
20030158960	Engberg	Aug 2003	A1
20030163513	Schaeck et al.	Aug 2003	A1
20030163733	Barriga-Caceres et al.	Aug 2003	A1
20030171942	Gaito	Sep 2003	A1
20030177028	Cooper et al.	Sep 2003	A1
20030182214	Taylor	Sep 2003	A1
20030187837	Culliss	Oct 2003	A1
20030188193	Venkataramappa	Oct 2003	A1
20030195859	Lawrence	Oct 2003	A1
20030200447	Sjoblom	Oct 2003	A1
20030204429	Botscheck et al.	Oct 2003	A1
20030204752	Garrison	Oct 2003	A1
20030208412	Hillestad et al.	Nov 2003	A1
20030220858	Lam et al.	Nov 2003	A1
20040002878	Hinton	Jan 2004	A1
20040006488	Fitall et al.	Jan 2004	A1
20040010458	Friedman	Jan 2004	A1
20040010698	Rolfe	Jan 2004	A1
20040015714	Abraham et al.	Jan 2004	A1
20040015715	Brown	Jan 2004	A1
20040019518	Abraham et al.	Jan 2004	A1
20040019549	Gulbrandsen	Jan 2004	A1
20040019799	Vering et al.	Jan 2004	A1
20040024671	Freund	Feb 2004	A1
20040024709	Yu et al.	Feb 2004	A1
20040030649	Nelson et al.	Feb 2004	A1
20040039586	Garvey et al.	Feb 2004	A1
20040044628	Mathew et al.	Mar 2004	A1
20040044673	Brady et al.	Mar 2004	A1
20040044739	Ziegler	Mar 2004	A1
20040078324	Lonnberg et al.	Apr 2004	A1
20040083159	Crosby et al.	Apr 2004	A1
20040088237	Moenickheim et al.	May 2004	A1
20040088255	Zielke et al.	May 2004	A1
20040107250	Marciano	Jun 2004	A1
20040110119	Riconda et al.	Jun 2004	A1
20040111359	Hudock	Jun 2004	A1
20040111375	Johnson	Jun 2004	A1
20040117302	Weichert et al.	Jun 2004	A1
20040122681	Ruvolo et al.	Jun 2004	A1
20040122696	Beringer	Jun 2004	A1
20040128150	Lundegren	Jul 2004	A1
20040128156	Beringer et al.	Jul 2004	A1
20040133440	Carolan et al.	Jul 2004	A1
20040133509	McCoy et al.	Jul 2004	A1
20040133513	McCoy et al.	Jul 2004	A1
20040133515	McCoy et al.	Jul 2004	A1
20040138994	DeFrancesco et al.	Jul 2004	A1
20040141005	Banatwala et al.	Jul 2004	A1
20040143546	Wood et al.	Jul 2004	A1
20040143596	Sirkin	Jul 2004	A1
20040153521	Kogo	Aug 2004	A1
20040158523	Dort	Aug 2004	A1
20040158723	Root	Aug 2004	A1
20040159700	Khan et al.	Aug 2004	A1
20040167793	Masuoka et al.	Aug 2004	A1
20040193891	Ollila	Sep 2004	A1
20040199789	Shaw et al.	Oct 2004	A1
20040210661	Thompson	Oct 2004	A1
20040220865	Lozowski et al.	Nov 2004	A1
20040220918	Scriffignano et al.	Nov 2004	A1
20040225643	Alpha et al.	Nov 2004	A1
20040230527	Hansen et al.	Nov 2004	A1
20040243514	Wankmueller	Dec 2004	A1
20040243518	Clifton et al.	Dec 2004	A1
20040243588	Tanner et al.	Dec 2004	A1
20040243832	Wilf et al.	Dec 2004	A1
20040249811	Shostack	Dec 2004	A1
20040250085	Tattan et al.	Dec 2004	A1
20040250107	Guo	Dec 2004	A1
20040254935	Chagoly et al.	Dec 2004	A1
20040255127	Arnouse	Dec 2004	A1
20040267714	Frid et al.	Dec 2004	A1
20050005168	Dick	Jan 2005	A1
20050010513	Duckworth et al.	Jan 2005	A1
20050021476	Candella et al.	Jan 2005	A1
20050021551	Silva et al.	Jan 2005	A1
20050027983	Klawon	Feb 2005	A1
20050027995	Menschik et al.	Feb 2005	A1
20050055231	Lee	Mar 2005	A1
20050058262	Timmins et al.	Mar 2005	A1
20050060332	Bernstein et al.	Mar 2005	A1
20050071328	Lawrence	Mar 2005	A1
20050075985	Cartmell	Apr 2005	A1
20050086126	Patterson	Apr 2005	A1
20050091164	Varble	Apr 2005	A1
20050097017	Hanratty	May 2005	A1
20050097039	Kulcsar et al.	May 2005	A1
20050097320	Golan et al.	May 2005	A1
20050102180	Gailey et al.	May 2005	A1
20050105719	Huda	May 2005	A1
20050108396	Bittner	May 2005	A1
20050108631	Amorin et al.	May 2005	A1
20050114335	Wesinger, Jr. et al.	May 2005	A1
20050114344	Wesinger, Jr. et al.	May 2005	A1
20050114345	Wesinger, Jr. et al.	May 2005	A1
20050119978	Ates	Jun 2005	A1
20050125291	Demkiw Grayson et al.	Jun 2005	A1
20050125397	Gross et al.	Jun 2005	A1
20050125686	Brandt	Jun 2005	A1
20050137899	Davies et al.	Jun 2005	A1
20050138391	Mandalia et al.	Jun 2005	A1
20050144133	Hoffman et al.	Jun 2005	A1
20050144452	Lynch et al.	Jun 2005	A1
20050154664	Guy et al.	Jul 2005	A1
20050154665	Kerr	Jul 2005	A1
20050154769	Eckart et al.	Jul 2005	A1
20050166262	Beattie et al.	Jul 2005	A1
20050171884	Arnott	Aug 2005	A1
20050181765	Mark	Aug 2005	A1
20050208461	Krebs et al.	Sep 2005	A1
20050216434	Haveliwala et al.	Sep 2005	A1
20050216582	Toomey et al.	Sep 2005	A1
20050216953	Ellingson	Sep 2005	A1
20050216955	Wilkins et al.	Sep 2005	A1
20050226224	Lee et al.	Oct 2005	A1
20050240578	Biederman et al.	Oct 2005	A1
20050256809	Sadri	Nov 2005	A1
20050267840	Holm-Blagg et al.	Dec 2005	A1
20050273431	Abel et al.	Dec 2005	A1
20050273442	Bennett et al.	Dec 2005	A1
20050288998	Verma et al.	Dec 2005	A1
20060004623	Jasti	Jan 2006	A1
20060004626	Holmen et al.	Jan 2006	A1
20060010072	Eisen	Jan 2006	A1
20060010391	Uemura et al.	Jan 2006	A1
20060010487	Fierer et al.	Jan 2006	A1
20060016107	Davis	Jan 2006	A1
20060032909	Seegar	Feb 2006	A1
20060036543	Blagg et al.	Feb 2006	A1
20060036748	Nusbaum et al.	Feb 2006	A1
20060036870	Dasari et al.	Feb 2006	A1
20060041464	Powers et al.	Feb 2006	A1
20060041670	Musseleck et al.	Feb 2006	A1
20060059110	Madhok et al.	Mar 2006	A1
20060059362	Paden et al.	Mar 2006	A1
20060069635	Ram et al.	Mar 2006	A1
20060074986	Mallalieu et al.	Apr 2006	A1
20060074991	Lussier et al.	Apr 2006	A1
20060079211	Degraeve	Apr 2006	A1
20060080230	Freiberg	Apr 2006	A1
20060080251	Fried et al.	Apr 2006	A1
20060080263	Willis et al.	Apr 2006	A1
20060085361	Hoerle et al.	Apr 2006	A1
20060101508	Taylor	May 2006	A1
20060129419	Flaxer et al.	Jun 2006	A1
20060129481	Bhatt et al.	Jun 2006	A1
20060129533	Purvis	Jun 2006	A1
20060131390	Kim	Jun 2006	A1
20060136595	Satyavolu	Jun 2006	A1
20060140460	Coutts	Jun 2006	A1
20060155573	Hartunian	Jul 2006	A1
20060155780	Sakairi et al.	Jul 2006	A1
20060161435	Atef et al.	Jul 2006	A1
20060161554	Lucovsky et al.	Jul 2006	A1
20060173776	Shalley et al.	Aug 2006	A1
20060173792	Glass	Aug 2006	A1
20060178971	Owen et al.	Aug 2006	A1
20060179050	Giang et al.	Aug 2006	A1
20060184585	Grear et al.	Aug 2006	A1
20060195351	Bayburtian	Aug 2006	A1
20060204051	Holland, IV	Sep 2006	A1
20060212407	Lyon	Sep 2006	A1
20060218407	Toms	Sep 2006	A1
20060229943	Mathias et al.	Oct 2006	A1
20060229961	Lyftogt et al.	Oct 2006	A1
20060235935	Ng	Oct 2006	A1
20060239512	Petrillo	Oct 2006	A1
20060253358	Delgrosso et al.	Nov 2006	A1
20060262929	Vatanen et al.	Nov 2006	A1
20060265243	Racho et al.	Nov 2006	A1
20060271456	Romain et al.	Nov 2006	A1
20060271457	Romain et al.	Nov 2006	A1
20060271633	Adler	Nov 2006	A1
20060277089	Hubbard et al.	Dec 2006	A1
20060282429	Hernandez-Sherrington et al.	Dec 2006	A1
20060282660	Varghese et al.	Dec 2006	A1
20060282819	Graham et al.	Dec 2006	A1
20060287764	Kraft	Dec 2006	A1
20060287765	Kraft	Dec 2006	A1
20060287766	Kraft	Dec 2006	A1
20060287767	Kraft	Dec 2006	A1
20060288090	Kraft	Dec 2006	A1
20060294199	Bertholf	Dec 2006	A1
20070005508	Chiang	Jan 2007	A1
20070005984	Florencio et al.	Jan 2007	A1
20070022141	Singleton et al.	Jan 2007	A1
20070027816	Writer	Feb 2007	A1
20070032240	Finnegan et al.	Feb 2007	A1
20070038568	Greene et al.	Feb 2007	A1
20070043577	Kasower	Feb 2007	A1
20070047714	Baniak et al.	Mar 2007	A1
20070067297	Kublickis	Mar 2007	A1
20070072190	Aggarwal	Mar 2007	A1
20070073889	Morris	Mar 2007	A1
20070078908	Rohatgi et al.	Apr 2007	A1
20070078985	Shao et al.	Apr 2007	A1
20070083460	Bachenheimer	Apr 2007	A1
20070083463	Kraft	Apr 2007	A1
20070093234	Willis et al.	Apr 2007	A1
20070094230	Subramaniam et al.	Apr 2007	A1
20070094241	M. Blackwell et al.	Apr 2007	A1
20070106517	Cluff et al.	May 2007	A1
20070112667	Rucker	May 2007	A1
20070112668	Celano et al.	May 2007	A1
20070121843	Atazky et al.	May 2007	A1
20070124256	Crooks et al.	May 2007	A1
20070143825	Goffin	Jun 2007	A1
20070156692	Rosewarne	Jul 2007	A1
20070162307	Austin et al.	Jul 2007	A1
20070174186	Hokland	Jul 2007	A1
20070174448	Ahuja et al.	Jul 2007	A1
20070174903	Greff	Jul 2007	A1
20070192121	Routson et al.	Aug 2007	A1
20070192853	Shraim et al.	Aug 2007	A1
20070198432	Pitroda et al.	Aug 2007	A1
20070204338	Aiello et al.	Aug 2007	A1
20070205266	Carr et al.	Sep 2007	A1
20070226122	Burrell et al.	Sep 2007	A1
20070240206	Wu et al.	Oct 2007	A1
20070244807	Andringa et al.	Oct 2007	A1
20070245245	Blue et al.	Oct 2007	A1
20070250441	Paulsen et al.	Oct 2007	A1
20070250459	Schwarz et al.	Oct 2007	A1
20070261108	Lee et al.	Nov 2007	A1
20070261114	Pomerantsev	Nov 2007	A1
20070266439	Kraft	Nov 2007	A1
20070282743	Lovelett	Dec 2007	A1
20070282959	Stern	Dec 2007	A1
20070288355	Roland et al.	Dec 2007	A1
20070288360	Seeklus	Dec 2007	A1
20070294195	Curry et al.	Dec 2007	A1
20080010203	Grant	Jan 2008	A1
20080010206	Coleman	Jan 2008	A1
20080010687	Gonen et al.	Jan 2008	A1
20080028446	Burgoyne	Jan 2008	A1
20080033742	Bernasconi	Feb 2008	A1
20080033956	Saha et al.	Feb 2008	A1
20080040610	Fergusson	Feb 2008	A1
20080047017	Renaud	Feb 2008	A1
20080052182	Marshall	Feb 2008	A1
20080052244	Tsuei et al.	Feb 2008	A1
20080059364	Tidwell et al.	Mar 2008	A1
20080066188	Kwak	Mar 2008	A1
20080071682	Dominguez	Mar 2008	A1
20080072316	Chang et al.	Mar 2008	A1
20080077526	Arumugam	Mar 2008	A1
20080082536	Schwabe et al.	Apr 2008	A1
20080083021	Doane et al.	Apr 2008	A1
20080086431	Robinson et al.	Apr 2008	A1
20080091530	Egnatios et al.	Apr 2008	A1
20080103800	Domenikos et al.	May 2008	A1
20080103972	Lanc	May 2008	A1
20080104672	Lunde et al.	May 2008	A1
20080109422	Dedhia	May 2008	A1
20080109875	Kraft	May 2008	A1
20080114670	Friesen	May 2008	A1
20080115191	Kim et al.	May 2008	A1
20080115226	Welingkar et al.	May 2008	A1
20080120569	Mann et al.	May 2008	A1
20080120716	Hall et al.	May 2008	A1
20080126233	Hogan	May 2008	A1
20080141346	Kay et al.	Jun 2008	A1
20080148368	Zurko et al.	Jun 2008	A1
20080154758	Schattmaier et al.	Jun 2008	A1
20080155686	McNair	Jun 2008	A1
20080162317	Banaugh et al.	Jul 2008	A1
20080162350	Allen-Rouman et al.	Jul 2008	A1
20080162383	Kraft	Jul 2008	A1
20080175360	Schwarz et al.	Jul 2008	A1
20080183480	Carlson et al.	Jul 2008	A1
20080183585	Vianello	Jul 2008	A1
20080195548	Chu et al.	Aug 2008	A1
20080201401	Pugh et al.	Aug 2008	A1
20080205655	Wilkins et al.	Aug 2008	A1
20080208726	Tsantes et al.	Aug 2008	A1
20080208735	Balet et al.	Aug 2008	A1
20080208752	Gottlieb et al.	Aug 2008	A1
20080208873	Boehmer	Aug 2008	A1
20080212845	Lund	Sep 2008	A1
20080216156	Kosaka	Sep 2008	A1
20080222706	Renaud et al.	Sep 2008	A1
20080222722	Navratil et al.	Sep 2008	A1
20080229415	Kapoor et al.	Sep 2008	A1
20080249869	Angell et al.	Oct 2008	A1
20080255992	Lin	Oct 2008	A1
20080256613	Grover	Oct 2008	A1
20080263058	Peden	Oct 2008	A1
20080270295	Lent et al.	Oct 2008	A1
20080270299	Peng	Oct 2008	A1
20080281737	Fajardo	Nov 2008	A1
20080288283	Baldwin, Jr. et al.	Nov 2008	A1
20080288299	Schultz	Nov 2008	A1
20080301016	Durvasula et al.	Dec 2008	A1
20080306750	Wunder et al.	Dec 2008	A1
20080314977	Domenica et al.	Dec 2008	A1
20080319889	Hammad	Dec 2008	A1
20090006230	Lyda et al.	Jan 2009	A1
20090018986	Alcorn et al.	Jan 2009	A1
20090031426	Dal Lago et al.	Jan 2009	A1
20090037332	Cheung et al.	Feb 2009	A1
20090043691	Kasower	Feb 2009	A1
20090055322	Bykov et al.	Feb 2009	A1
20090055894	Lorsch	Feb 2009	A1
20090064297	Selgas et al.	Mar 2009	A1
20090094237	Churi et al.	Apr 2009	A1
20090094674	Schwartz et al.	Apr 2009	A1
20090100047	Jones et al.	Apr 2009	A1
20090106141	Becker	Apr 2009	A1
20090106150	Pelegero et al.	Apr 2009	A1
20090106846	Dupray et al.	Apr 2009	A1
20090119299	Rhodes	May 2009	A1
20090125369	Kloostra et al.	May 2009	A1
20090125972	Hinton et al.	May 2009	A1
20090132347	Anderson et al.	May 2009	A1
20090138335	Lieberman	May 2009	A1
20090144166	Dickelman	Jun 2009	A1
20090150166	Leite et al.	Jun 2009	A1
20090150238	Marsh et al.	Jun 2009	A1
20090157564	Cross	Jun 2009	A1
20090157693	Palahnuk	Jun 2009	A1
20090158030	Rasti	Jun 2009	A1
20090164232	Chmielewski et al.	Jun 2009	A1
20090164380	Brown	Jun 2009	A1
20090172788	Veldula et al.	Jul 2009	A1
20090172795	Ritari et al.	Jul 2009	A1
20090177529	Hadi	Jul 2009	A1
20090177562	Peace et al.	Jul 2009	A1
20090183259	Rinek et al.	Jul 2009	A1
20090199264	Lang	Aug 2009	A1
20090199294	Schneider	Aug 2009	A1
20090204514	Bhogal et al.	Aug 2009	A1
20090204599	Morris et al.	Aug 2009	A1
20090210241	Calloway	Aug 2009	A1
20090210807	Xiao et al.	Aug 2009	A1
20090215431	Koraichi	Aug 2009	A1
20090216640	Masi	Aug 2009	A1
20090222449	Hom et al.	Sep 2009	A1
20090228918	Rolff et al.	Sep 2009	A1
20090234665	Conkel	Sep 2009	A1
20090234775	Whitney et al.	Sep 2009	A1
20090234876	Schigel et al.	Sep 2009	A1
20090240624	James et al.	Sep 2009	A1
20090247122	Fitzgerald et al.	Oct 2009	A1
20090254375	Martinez et al.	Oct 2009	A1
20090254476	Sharma et al.	Oct 2009	A1
20090254572	Redlich et al.	Oct 2009	A1
20090254656	Vignisson et al.	Oct 2009	A1
20090254971	Herz et al.	Oct 2009	A1
20090260064	Mcdowell et al.	Oct 2009	A1
20090271847	Karjala et al.	Oct 2009	A1
20090307778	Mardikar	Dec 2009	A1
20090313134	Faith et al.	Dec 2009	A1
20090313562	Appleyard et al.	Dec 2009	A1
20090319638	Faith et al.	Dec 2009	A1
20090327270	Teevan et al.	Dec 2009	A1
20090328173	Jakobson et al.	Dec 2009	A1
20100011428	Atwood et al.	Jan 2010	A1
20100030578	Siddique et al.	Feb 2010	A1
20100030677	Melik-Aslanian et al.	Feb 2010	A1
20100042542	Rose et al.	Feb 2010	A1
20100043055	Baumgart	Feb 2010	A1
20100049803	Ogilvie et al.	Feb 2010	A1
20100058404	Rouse	Mar 2010	A1
20100063942	Arnott et al.	Mar 2010	A1
20100063993	Higgins et al.	Mar 2010	A1
20100076836	Giordano et al.	Mar 2010	A1
20100077351	Kaulgud et al.	Mar 2010	A1
20100077483	Stolfo et al.	Mar 2010	A1
20100083371	Bennetts et al.	Apr 2010	A1
20100088233	Tattan et al.	Apr 2010	A1
20100094768	Miltonberger	Apr 2010	A1
20100094910	Bayliss	Apr 2010	A1
20100100945	Ozzie et al.	Apr 2010	A1
20100114744	Gonen	May 2010	A1
20100114776	Weller et al.	May 2010	A1
20100121767	Coulter et al.	May 2010	A1
20100122305	Moloney	May 2010	A1
20100122324	Welingkar et al.	May 2010	A1
20100122333	Noe et al.	May 2010	A1
20100130172	Vendrow et al.	May 2010	A1
20100136956	Drachev et al.	Jun 2010	A1
20100138298	Fitzherald et al.	Jun 2010	A1
20100145836	Baker et al.	Jun 2010	A1
20100153278	Farsedakis	Jun 2010	A1
20100153290	Duggan	Jun 2010	A1
20100161816	Kraft et al.	Jun 2010	A1
20100169159	Rose et al.	Jul 2010	A1
20100174638	Debie et al.	Jul 2010	A1
20100174813	Hildreth et al.	Jul 2010	A1
20100175119	Vitaletti	Jul 2010	A1
20100179906	Hawkes	Jul 2010	A1
20100185546	Pollard	Jul 2010	A1
20100205076	Parson et al.	Aug 2010	A1
20100205662	Ibrahim et al.	Aug 2010	A1
20100211445	Bodington	Aug 2010	A1
20100211636	Starkenburg et al.	Aug 2010	A1
20100212004	Fu	Aug 2010	A1
20100217837	Ansari et al.	Aug 2010	A1
20100217969	Tomkow	Aug 2010	A1
20100223192	Levine et al.	Sep 2010	A1
20100229245	Singhal	Sep 2010	A1
20100241493	Onischuk	Sep 2010	A1
20100241535	Nightengale et al.	Sep 2010	A1
20100250338	Banerjee et al.	Sep 2010	A1
20100250410	Song et al.	Sep 2010	A1
20100250411	Ogrodski	Sep 2010	A1
20100250955	Trevithick et al.	Sep 2010	A1
20100257102	Perlman	Oct 2010	A1
20100258623	Beemer et al.	Oct 2010	A1
20100262932	Pan	Oct 2010	A1
20100280914	Carlson	Nov 2010	A1
20100281020	Drubner	Nov 2010	A1
20100293049	Maher et al.	Nov 2010	A1
20100293050	Maher et al.	Nov 2010	A1
20100293058	Maher et al.	Nov 2010	A1
20100293090	Domenikos et al.	Nov 2010	A1
20100299262	Handler	Nov 2010	A1
20100325442	Petrone et al.	Dec 2010	A1
20100325694	Bhagavatula et al.	Dec 2010	A1
20100332393	Weller et al.	Dec 2010	A1
20110004498	Readshaw	Jan 2011	A1
20110016533	Zeigler et al.	Jan 2011	A1
20110023115	Wright	Jan 2011	A1
20110029388	Kendall et al.	Feb 2011	A1
20110035788	White et al.	Feb 2011	A1
20110040736	Kalaboukis	Feb 2011	A1
20110071950	Ivanovic	Mar 2011	A1
20110082768	Eisen	Apr 2011	A1
20110083181	Nazarov	Apr 2011	A1
20110113084	Ramnani	May 2011	A1
20110119155	Hammad et al.	May 2011	A1
20110126024	Beatson et al.	May 2011	A1
20110126275	Anderson et al.	May 2011	A1
20110131096	Frew et al.	Jun 2011	A1
20110131123	Griffin et al.	Jun 2011	A1
20110137760	Rudie et al.	Jun 2011	A1
20110142213	Baniak et al.	Jun 2011	A1
20110145899	Cao et al.	Jun 2011	A1
20110148625	Velusamy	Jun 2011	A1
20110161218	Swift	Jun 2011	A1
20110166988	Coulter	Jul 2011	A1
20110167011	Paltenghe et al.	Jul 2011	A1
20110173681	Qureshi et al.	Jul 2011	A1
20110179139	Starkenburg et al.	Jul 2011	A1
20110184780	Alderson et al.	Jul 2011	A1
20110184838	Winters et al.	Jul 2011	A1
20110196791	Dominguez	Aug 2011	A1
20110208601	Ferguson et al.	Aug 2011	A1
20110211445	Chen	Sep 2011	A1
20110260832	Ross et al.	Oct 2011	A1
20110264566	Brown	Oct 2011	A1
20110270754	Kelly et al.	Nov 2011	A1
20110307397	Benmbarek	Dec 2011	A1
20110307957	Barcelo et al.	Dec 2011	A1
20120011158	Avner et al.	Jan 2012	A1
20120016948	Sinha	Jan 2012	A1
20120018506	Hammad et al.	Jan 2012	A1
20120030216	Churi et al.	Feb 2012	A1
20120030771	Pierson et al.	Feb 2012	A1
20120047219	Feng et al.	Feb 2012	A1
20120047423	Tomkow	Feb 2012	A1
20120054592	Jaffe et al.	Mar 2012	A1
20120072382	Pearson et al.	Mar 2012	A1
20120079585	Chan et al.	Mar 2012	A1
20120084866	Stolfo	Apr 2012	A1
20120089438	Tavares et al.	Apr 2012	A1
20120096557	Britton et al.	Apr 2012	A1
20120108274	Acebo Ruiz et al.	May 2012	A1
20120110467	Blake et al.	May 2012	A1
20120110677	Abendroth et al.	May 2012	A1
20120117629	Miyazawa et al.	May 2012	A1
20120124498	Santoro et al.	May 2012	A1
20120130898	Snyder et al.	May 2012	A1
20120136763	Megdal et al.	May 2012	A1
20120151045	Anakata et al.	Jun 2012	A1
20120173339	Flynt et al.	Jul 2012	A1
20120173563	Griffin et al.	Jul 2012	A1
20120191610	Prasad	Jul 2012	A1
20120215682	Lent et al.	Aug 2012	A1
20120215719	Verlander	Aug 2012	A1
20120216125	Pierce	Aug 2012	A1
20120235897	Hirota	Sep 2012	A1
20120239497	Nuzzi	Sep 2012	A1
20120246060	Conyack, Jr. et al.	Sep 2012	A1
20120246730	Raad	Sep 2012	A1
20120253852	Pourfallah et al.	Oct 2012	A1
20120290660	Rao et al.	Nov 2012	A1
20120297484	Srivastava	Nov 2012	A1
20120323717	Kirsch	Dec 2012	A1
20120331557	Washington	Dec 2012	A1
20130004033	Trugenberger et al.	Jan 2013	A1
20130006843	Tralvex	Jan 2013	A1
20130018811	Britti et al.	Jan 2013	A1
20130031109	Roulson et al.	Jan 2013	A1
20130031624	Britti et al.	Jan 2013	A1
20130041701	Roth	Feb 2013	A1
20130066775	Milam	Mar 2013	A1
20130080467	Carson et al.	Mar 2013	A1
20130085804	Leff et al.	Apr 2013	A1
20130085939	Colak et al.	Apr 2013	A1
20130086186	Tomkow	Apr 2013	A1
20130086654	Tomkow	Apr 2013	A1
20130110678	Vigier et al.	May 2013	A1
20130117087	Coppinger	May 2013	A1
20130117387	Tomkow	May 2013	A1
20130125010	Strandell	May 2013	A1
20130132151	Stibel et al.	May 2013	A1
20130139229	Fried et al.	May 2013	A1
20130173449	Ng et al.	Jul 2013	A1
20130179955	Bekker et al.	Jul 2013	A1
20130198525	Spies et al.	Aug 2013	A1
20130205135	Lutz	Aug 2013	A1
20130212661	Neafsey et al.	Aug 2013	A1
20130246150	Ovick et al.	Sep 2013	A1
20130246273	Ovick et al.	Sep 2013	A1
20130246528	Ogura	Sep 2013	A1
20130254008	Ovick et al.	Sep 2013	A1
20130254096	Serio et al.	Sep 2013	A1
20130268333	Ovick et al.	Oct 2013	A1
20130271272	Dhesi et al.	Oct 2013	A1
20130275762	Tomkow	Oct 2013	A1
20130279676	Baniak et al.	Oct 2013	A1
20130282461	Ovick et al.	Oct 2013	A1
20130290097	Balestrieri et al.	Oct 2013	A1
20130293363	Plymouth	Nov 2013	A1
20130298238	Shah et al.	Nov 2013	A1
20130318569	Canning et al.	Nov 2013	A1
20130332342	Kasower	Dec 2013	A1
20130339217	Breslow et al.	Dec 2013	A1
20130339249	Weller et al.	Dec 2013	A1
20130346331	Giovannetti et al.	Dec 2013	A1
20140012733	Vidal	Jan 2014	A1
20140013396	Field-Eliot et al.	Jan 2014	A1
20140025475	Burke	Jan 2014	A1
20140032723	Nema	Jan 2014	A1
20140033280	Nimashakavi et al.	Jan 2014	A1
20140040051	Ovick et al.	Feb 2014	A1
20140040135	Ovick et al.	Feb 2014	A1
20140046872	Arnott et al.	Feb 2014	A1
20140051464	Ryan et al.	Feb 2014	A1
20140061302	Hammad	Mar 2014	A1
20140089167	Kasower	Mar 2014	A1
20140110477	Hammad	Apr 2014	A1
20140162611	Mezhibovsky et al.	Jun 2014	A1
20140164112	Kala	Jun 2014	A1
20140164398	Smith et al.	Jun 2014	A1
20140164519	Shah	Jun 2014	A1
20140201100	Rellas	Jul 2014	A1
20140258083	Achanta et al.	Sep 2014	A1
20140279467	Chapa et al.	Sep 2014	A1
20140280945	Lunt	Sep 2014	A1
20140283123	Lonstein et al.	Sep 2014	A1
20140289812	Wang et al.	Sep 2014	A1
20140298485	Gardner	Oct 2014	A1
20140317023	Kim	Oct 2014	A1
20140317716	Chao et al.	Oct 2014	A1
20140331282	Tkachev	Nov 2014	A1
20140379600	Chapa et al.	Dec 2014	A1
20150067341	Deen et al.	Mar 2015	A1
20150089569	Sondhi et al.	Mar 2015	A1
20150142595	Acuña-Rohter	May 2015	A1
20150180870	Zhang et al.	Jun 2015	A1
20150199667	Fernando et al.	Jul 2015	A1
20150199668	Fernando et al.	Jul 2015	A1
20150249655	Lunt	Sep 2015	A1
20150254658	Bondesen et al.	Sep 2015	A1
20150278277	Agrawal et al.	Oct 2015	A1
20150326580	McMillan et al.	Nov 2015	A1
20150350186	Chan et al.	Dec 2015	A1
20160005020	Fernando et al.	Jan 2016	A1
20160027008	John	Jan 2016	A1
20160050198	Thibadeau, Sr. et al.	Feb 2016	A1
20160065563	Broadbent et al.	Mar 2016	A1
20160088465	Golla	Mar 2016	A1
20160142532	Bostick	May 2016	A1
20160217444	Martin	Jul 2016	A1
20160217445	Martin	Jul 2016	A1
20160226879	Chan et al.	Aug 2016	A1
20160275476	Artman et al.	Sep 2016	A1
20160283740	Roundtree	Sep 2016	A1
20160337369	Sanso	Nov 2016	A1
20170061436	Liu et al.	Mar 2017	A1
20170186012	McNeal	Jun 2017	A1
20170200223	Kasower	Jul 2017	A1
20170324749	Bhargava et al.	Nov 2017	A1
20170331832	Lander et al.	Nov 2017	A1
20170337549	Wong	Nov 2017	A1
20170337557	Durney et al.	Nov 2017	A1
20170357971	Pitz et al.	Dec 2017	A1
20180041336	Keshava et al.	Feb 2018	A1
20180046856	Kapczynski	Feb 2018	A1
20180077142	Thakkar	Mar 2018	A1
20180083915	Medam et al.	Mar 2018	A1
20180227292	Golshan et al.	Aug 2018	A1
20180232433	Kanvinde	Aug 2018	A1
20180285549	Sonkar et al.	Oct 2018	A1
20180337914	Mohamad Abdul et al.	Nov 2018	A1
20180343265	McMillan et al.	Nov 2018	A1
20180365690	Ovick et al.	Dec 2018	A1
20180375791	Kaladgi et al.	Dec 2018	A1
20190073676	Wang	Mar 2019	A1
20190095516	Srinivasan et al.	Mar 2019	A1
20190164173	Liu et al.	May 2019	A1
20190228173	Gupta et al.	Jul 2019	A1
20190228178	Sharma et al.	Jul 2019	A1
20190259030	Burger	Aug 2019	A1
20190349360	Yeddula et al.	Nov 2019	A1
20200104834	Pontious et al.	Apr 2020	A1
20200118127	Miller et al.	Apr 2020	A1
20200137080	Bloomquist et al.	Apr 2020	A1
20200162443	Poschel et al.	May 2020	A1
20200205002	Talwar	Jun 2020	A1
20200228321	Krishnamacharya et al.	Jul 2020	A1
20200293684	Harris et al.	Sep 2020	A1
20200304501	Fan	Sep 2020	A1
20200314088	Feijoo et al.	Oct 2020	A1
20200320511	Anderson et al.	Oct 2020	A1
20200334349	Billman et al.	Oct 2020	A1
20200342557	Chapa et al.	Oct 2020	A1
20200372535	Walz et al.	Nov 2020	A1
20200380112	Allen	Dec 2020	A1
20200380509	Billman et al.	Dec 2020	A1
20200394331	Talwar	Dec 2020	A1
20200403992	Huffman et al.	Dec 2020	A1
20210012312	Bradstreet	Jan 2021	A1
20210117969	Chilaka et al.	Apr 2021	A1
20210144131	Krishnamacharya	May 2021	A1
20210203667	Bondugula et al.	Jul 2021	A1
20210240808	Sadhwani et al.	Aug 2021	A1
20210241120	Chen et al.	Aug 2021	A1
20210288948	Joffe et al.	Sep 2021	A1
20220027853	McMillan et al.	Jan 2022	A1
20220027891	Anderson et al.	Jan 2022	A1
20220044343	Chapa et al.	Feb 2022	A1
20220070169	Cano et al.	Mar 2022	A1
20220109578	Kirsch	Apr 2022	A1
20220173887	Krishnamacharya et al.	Jun 2022	A1
20220182487	Sharma et al.	Jun 2022	A1
20220239665	Bondugula et al.	Jul 2022	A1
20220261461	Bondugula et al.	Aug 2022	A1
20220279067	Sena, Jr. et al.	Sep 2022	A1
20220345460	Alden et al.	Oct 2022	A1

Foreign Referenced Citations (75)

Number	Date	Country
3 076 931	Oct 2020	CA
3 052 415	Jul 2021	CA
2 896 503	Aug 2021	CA
104877993	Sep 2015	CN
1 028 401	Aug 2000	EP
1 239 378	Sep 2002	EP
1 301 887	Apr 2003	EP
1 850 278	Oct 2007	EP
2 425 583	Mar 2012	EP
2 074 513	Feb 2016	EP
2 939 364	Jun 2020	EP
3 577 850	Jul 2021	EP
3 862 897	Aug 2021	EP
4 060 941	Sep 2022	EP
2 811 070	Mar 2021	ES
2 518 099	Mar 2015	GB
201917040928	Nov 2019	IN
2005-135431	May 2005	JP
2005-208945	Aug 2005	JP
4202314	Dec 2008	JP
2012-113696	Jun 2012	JP
10-2000-0063313	Nov 2000	KR
10-2002-0039203	May 2002	KR
10-2007-0081504	Aug 2007	KR
I256569	Jun 2006	TW
WO 99054803	Oct 1999	WO
WO 99060481	Nov 1999	WO
WO 00030045	May 2000	WO
WO 01009752	Feb 2001	WO
WO 01009792	Feb 2001	WO
WO 01010090	Feb 2001	WO
WO 01084281	Nov 2001	WO
WO 02011025	Feb 2002	WO
WO 02029636	Apr 2002	WO
WO 03073711	Sep 2003	WO
WO 2004031986	Apr 2004	WO
WO 2004049654	Jun 2004	WO
WO 2005033979	Apr 2005	WO
WO 2006019752	Feb 2006	WO
WO 2006050278	May 2006	WO
WO 2006069199	Jun 2006	WO
WO 2006099081	Sep 2006	WO
WO 2007001394	Jan 2007	WO
WO 2007050156	May 2007	WO
WO 2008042614	Apr 2008	WO
WO 2008054849	May 2008	WO
WO 2009064694	May 2009	WO
WO 2009102391	Aug 2009	WO
WO 2009108901	Sep 2009	WO
WO 2009117468	Sep 2009	WO
WO 2010001406	Jan 2010	WO
WO 2010062537	Jun 2010	WO
WO 2010077989	Jul 2010	WO
WO 2010150251	Dec 2010	WO
WO 2011005876	Jan 2011	WO
WO 2011014878	Feb 2011	WO
WO 2012054646	Apr 2012	WO
WO 2013126281	Aug 2013	WO
WO 2013140410	Sep 2013	WO
WO 2014008079	Jan 2014	WO
WO 2014150987	Sep 2014	WO
WO 2015038520	Mar 2015	WO
WO 2018129373	Jul 2018	WO
WO 2018191638	Oct 2018	WO
WO 2018199992	Nov 2018	WO
WO 2019006144	Jan 2019	WO
WO 2019152592	Aug 2019	WO
WO 2019209857	Oct 2019	WO
WO 2019245998	Dec 2019	WO
WO 2020206305	Oct 2020	WO
WO 2021011308	Jan 2021	WO
WO 2021067446	Apr 2021	WO
WO 2021097090	May 2021	WO
WO 2021138263	Jul 2021	WO
WO 2021155053	Aug 2021	WO

Non-Patent Literature Citations (145)

Entry
U.S. Appl. No. 12/705,489, filed Feb. 12, 2010, Bargoli et al.
U.S. Appl. No. 12/705,511, filed Feb. 12, 2010, Bargoli et al.
Aad et al., “NRC Data Collection and the Privacy by Design Principles”, IEEE, Nov. 2010, pp. 5.
Actuate, “Delivering Enterprise Information for Corporate Portals”, White Paper, 2004, pp. 1-7.
“Aggregate and Analyze Social Media Content: Gain Faster and Broader Insight to Market Sentiment,” SAP Partner, Mantis Technology Group, Apr. 2011, pp. 4.
Aharony et al., “Social Area Networks: Data Networking of the People, by the People, for the People,” 2009 International Conference on Computational Science and Engineering, May 2009, pp. 1148-1155.
Aktas et al., “Personalizing PageRank Based on Domain Profiles”, WEBKDD workshop: Webmining and Web Usage Analysis, Aug. 22, 2004, pp. 83-90.
Aktas et al., “Using Hyperlink Features to Personalize Web Search”, WEBKDD workshop: Webmining and Web Usage Analysis, Aug. 2004.
“Arizona Company Has Found Key in Stopping ID Theft,” PR Newswire, New York, Aug. 10, 2005 http://proquest.umi.com/pqdweb?did=880104711&sid=1&Fmt=3&clientId=19649&RQT=309&Vname=PQD.
ABC News Now:Money Matters, as broadcasted Nov. 15, 2005 with guest Todd Davis (CEO of Lifelock), pp. 6.
Anonymous, “Credit-Report Disputes Await Electronic Resolution,” Credit Card News, Chicago, Jan. 15, 1993, vol. 5, No. 19, p. 5.
Anonymous, “MBNA Offers Resolution of Credit Card Disputes,” Hempstead, Feb. 2002, vol. 68, No. 2, p. 47.
Anonymous, “Feedback”, Credit Management, ABI/Inform Global, Sep. 2006, pp. 6.
Bacon, Chris, “OAuth id_token missing information on refresh #1141”, <https://github.com/googleapis/google-api-dotnet-client/issues/1141>, Jan. 1, 2018, pp. 9.
Bielski, Lauren, “Will you Spend to Thwart ID Theft?” ABA Banking Journal, Apr. 2005, pp. 54, 56-57, 60.
BlueCava, “What We Do”, http://www.bluecava.com/what-we-do/, printed Nov. 5, 2012 in 3 pages.
Buxfer, http://www.buxfer.com/ printed Feb. 5, 2014 in 1 page.
Check, http://check.me/ printed Feb. 5, 2014 in 3 pages.
Cheng, Fred, “Security Attack Safe Mobile and Cloud-based One-time Password Tokens Using Rubbing Encryption Algorithm”, Monet, 2011, vol. 16, pp. 304-336.
Chores & Allowances, “Do Kids Have Credit Reports?” Oct. 15, 2007, http://choresandallowances.blogspot.com/2007/10/do-kids-have-credit-reports.html, pp. 5.
Comlounge.net, “plonesocial.auth.rpx” http://web.archive.org/web/20101026041841/http://comlounge.net/rpx as captured Oct. 26, 2010 in 9 pages.
“Consumers Gain Immediate and Full Access to Credit Score Used by Majority of U.S. Lenders”, PR Newswire, ProQuest Copy, Mar. 19, 2001, p. 1.
“CreditCheck Monitoring Services,” Dec. 11, 2000, pp. 1, lines 21-23.
Cullen, Terri; “The Wall Street Journal Complete Identity Theft Guidebook:How to Protect Yourself from the Most Pervasive Crime in America”; Chapter 3, pp. 59-79; Jul. 10, 2007.
“D&B Corporate Family Linkage”, D&B Internet Access for U.S. Contract Customers, https://www.dnb.com/ecomp/help/linkage.htm as printed Dec. 17, 2009, pp. 1.
Day, Jo and Kevin; “ID-ology: A Planner's Guide to Identity Theft”; Journal of Financial Planning:Tech Talk; pp. 36-38; Sep. 2004.
Equifax, “InstaTouch ID: Separate Fact from Friction.” http://equifax.uberflip.eom/i/791148-mobile-consumer-identity-service-product-sheet/1, 2016, pp. 2.
Equifax; “Equifax Credit Watch”; https://www.econsumer.equifax.co.uk/consumer/uk/sitepage.ehtml, dated Jun. 27, 2007 on www.archive.org.
Ettorre, “Paul Kahn on Exceptional Marketing,” Management Review, vol. 83, No. 11, Nov. 1994, pp. 48-51.
Facebook, “Facebook helps you connect and share with the people in your life,” www.facebook.com printed Nov. 16, 2010 in 1 page.
FamilySecure.com, “Frequently Asked Questions”, http://www.familysecure.com/FAQ.aspx as archived Jul. 15, 2007 in 3 pages.
FamilySecure.com; “Identity Theft Protection for the Whole Family \| FamilySecure.com” http://www.familysecure.com/, as retrieved on Nov. 5, 2009.
Fenner, Peter, “Mobile Address Management and Billing for Personal Communications”, 1st International Conference on Universal Personal Communications, 1992, ICUPC '92 Proceedings, pp. 253-257.
“Fictitious Business Name Records”, Westlaw Database Directory, http://directory.westlaw.com/scope/default.asp?db=FBN-ALL&RS-W...&VR=2.0 as printed Dec. 17, 2009, pp. 5.
Fisher, Joseph, “Access to Fair Credit Reports: Current Practices and Proposed Legislation,” American Business Law Journal, Fall 1981, vol. 19, No. 3, p. 319.
Franks et al., “HTTP Authentication: Basic and Digest Access Authentication”, Network Working Group, Standards Track, Jun. 1999, pp. 34.
“Fraud Alert \| Learn How”. Fight Identity Theft. http://www.fightidentitytheft.com/flag.html, accessed on Nov. 5, 2009.
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.
Gordon et al., “Identity Fraud: A Critical National and Global Threat,” LexisNexis, Oct. 28, 2003, pp. 1-48.
Gordon et al., “Using Identity Authentication and Eligibility Assessment to Mitigate the Risk of Improper Payments”, LexisNexis, Jan. 28, 2008, pp. 18. https://risk.lexisnexis.com/-/media/files/government/white-paper/identity_authentication-pdf.pdf.
Haglund, Christoffer, “Two-Factor Authentication with a Mobile Phone”, Fox Technologies, Uppsala, Department of Information Technology, Nov. 2, 2007, pp. 62.
Harrington et al., “iOS 4 in Action”, Chapter 17, Local and Push Notification Services, Manning Publications Co., Jun. 2011, pp. 347-353.
Herzberg, Amir, “Payments and Banking with Mobile Personal Devices,” Communications of the ACM, May 2003, vol. 46, No. 5, pp. 53-58.
Hoofnagle, Chris Jay, “Identity Theft: Making the Known Unknowns Known,” Harvard Journal of Law & Technology, Fall 2007, vol. 21, No. 1, pp. 98-122.
ID Analytics, “ID Analytics® Consumer Notification Service” printed Apr. 16, 2013 in 2 pages.
ID Theft Assist, “Do You Know Where Your Child's Credit Is?”, Nov. 26, 2007, http://www.idtheftassist.com/pages/story14, pp. 3.
“ID Thieves These Days Want Your Number, Not Your Name”, The Columbus Dispatch, Columbus, Ohio, http://www.dispatch.com/content/stories/business/2014/08/03/id-thieves-these-days-want-your-number-not-your-name.html, Aug. 3, 2014 in 2 pages.
Identity Theft Resource Center; Fact Sheet 120 A—To Order a Credit Report for a Child; Fact Sheets, Victim Resources; Apr. 30, 2007.
“Identity Thieves Beware: Lifelock Introduces Nation's First Guaranteed Proactive Solution to Identity Theft Protection,” PR Newswire, New York, Jun. 13, 2005 http://proquest.umi.com/pqdweb?did=852869731&sid=1&Fmt=3&clientId=19649&RQT=309&Vname=PQD.
Ideon, Credit-Card Registry that Bellyflopped this Year, Is Drawing some Bottom-Fishers, The Wall Street Journal, Aug. 21, 1995, pp. C2.
Information Brokers of America, “Information Brokers of America Child Identity Theft Protection” http://web.archive.org/web/20080706135451/http://iboainfo.com/child-order.html as archived Jul. 6, 2008 in 1 page.
Information Brokers of America, “Safeguard Your Child's Credit”, http://web.archive.org/web/20071215210406/http://www.iboainfo.com/child-id-protect.html as archived Dec. 15, 2007 in 1 page.
Intelius, “People Search—Updated Daily, Accurate and Fast!” http://www.intelius.com/people-search.html?=&gclid=CJqZIZP7paUCFYK5KgodbCUJJQ printed Nov. 16, 2010 in 1 page.
Iovation, Device Identification & Device Fingerprinting, http://www.iovation.com/risk-management/device-identification printed Nov. 5, 2012 in 6 pages.
Jones et al., “JSON Web Signature (JWS)”, Internet Engineering Task Force (IETF), ISSN: 2070-1721, Standards Track, May 2015, pp. 59.
Khan, Muhammad Khurram, PhD., “An Efficient and Secure Remote Mutual Authentication Scheme with Smart Cards” IEEE International Symposium on Biometrics & Security Technologies (ISBAST), Apr. 23-24, 2008, pp. 1-6.
Lanubile, et al., “Evaluating Empirical Models for the Detection of High-Risk Components: Some Lessons Learned”, 20th Annual Software Engineering Workshop, Nov. 29-30, 1995, Greenbelt, Maryland, pp. 1-6.
Lee, W.A.; “Experian, on Deal Hunt, Nets Identity Theft Insurer”, American Banker: The Financial Services Daily, Jun. 4, 2003, New York, NY, 1 page.
Lefebvre et al., “A Robust Soft Hash Algorithm for Digital Image Signature”, International Conference on Image Processing 2:11 (ICIP), vol. 3, Oct. 2003, pp. 495-498.
Leskovec, Jure, “Social Media Analytics: Tracking, Modeling and Predicting the Flow of Information through Networks”, WWW 2011-Tutorial, Mar. 28-Apr. 1, 2011, Hyderabad, India, pp. 277-278.
Letter to Donald A. Robert from Carolyn B. Maloney, dated Oct. 31, 2007, pp. 2.
Letter to Donald A. Robert from Senator Charles E. Schumer, dated Oct. 11, 2007, pp. 2.
Letter to Harry C. Gambill from Carolyn B. Maloney, dated Oct. 31, 2007, pp. 2.
Letter to Harry C. Gambill from Senator Charles E. Schumer, dated Oct. 11, 2007, pp. 2.
Letter to Richard F. Smith from Carolyn B. Maloney, dated Oct. 31, 2007, pp. 2.
Letter to Richard F. Smith from Senator Charles E. Schumer, dated Oct. 11, 2007, pp. 2.
Li et al., “Automatic Verbal Information Verification for User Authentication”, IEEE Transactions on Speech and Audio Processing, vol. 8, No. 5, Sep. 2000, pp. 585-596.
LifeLock, “How LifeLock Works,” http://www.lifelock.com/lifelock-for-people printed Mar. 14, 2008 in 1 page.
LifeLock, “LifeLock Launches First ID Theft Prevention Program for the Protection of Children,” Press Release, Oct. 14, 2005, http://www.lifelock.com/about-us/press-room/2005-press-releases/lifelock-protection-for-children.
LifeLock; “How Can LifeLock Protect My Kids and Family?” http://www.lifelock.com/lifelock-for-people/how-we-do-it/how-can-lifelock-protect-my-kids-and-family printed Mar. 14, 2008 in 1 page.
LifeLock, “Personal Identity Theft Protection & Identity Theft Products,” http://www.lifelock.com/lifelock-for-people, accessed Nov. 5, 2007.
LifeLock, Various Pages, www.lifelock.com/, Jan. 9, 2007, pp. 49.
Lobo, Jude, “MySAP.com Enterprise Portal Cookbook,” SAP Technical Delivery, Feb. 2002, vol. 1, pp. 1-13.
Lodderstedt et al., “OAuth 2.0 token Revocation”, Internet Engineering Task Force (IETF), Standards Track, Aug. 2013, pp. 11.
Magid, Lawrence, J., Business Tools: When Selecting an ASP Ensure Data Mobility, Los Angeles Times, Los Angeles, CA, Feb. 26, 2001, vol. C, Issue 4, pp. 3.
Manilla, http://www.manilla.com/how-it-works/ printed Feb. 5, 2014 in 1 page.
Meyers et al., “Using Your Social Networking Accounts to Log Into NPR.org,” NPR.org, Jun. 24, 2010, http://web.archive.org/web/20100627034054/http://www.npr.org/blogs/inside/2010/06/24/128079309/using-your-social-networking-accounts-to-log-into-npr-org in 3 pages.
Micarelli et al., “Personalized Search on the World Wide Web,” The Adaptive Web, LNCS 4321, 2007, pp. 195-230.
Microsoft, “Expand the Reach of Your Business,” Microsoft Business Solutions, 2004, in 16 pages.
Mint.com, http://www.mint.com/how-it-works/ printed Feb. 5, 2013 in 2 pages.
Mvelopes, http://www.mvelopes.com/ printed Feb. 5, 2014 in 2 pages.
My Call Credit http://www.mycallcredit.com/products.asp?product=ALR dated Dec. 10, 2005 on www.archive.org.
My Call Credit http://www.mycallcredit.com/rewrite.asp?display=faq dated Dec. 10, 2005 on www.archive.org.
My ID Alerts, “Why ID Alerts” http://www.myidalerts.com/why-id-alerts.jsps printed Apr. 3, 2012 in 2 pages.
My ID Alerts, “How it Works” http://www.myidalerts.com/how-it-works.jsps printed Apr. 3, 2012 in 3 pages.
“Name Availability Records”, Westlaw Database Directory, http://directory.westlaw.com/scope/default.asp?db=NA-ALL&RS=W...&VR=2.0 as printed Dec. 17, 2009, pp. 5.
National Alert Registry Launches RegisteredOffendersList.org to Provide Information on Registered Sex Offenders, May 16, 2005, pp. 2, http://www.prweb.com/printer/240437.htm accessed on Oct. 18, 2011.
National Alert Registry Offers Free Child Safety “Safe From Harm” DVD and Child Identification Kit, Oct. 24, 2006. pp. 2, http://www.prleap.com/pr/53170 accessed on Oct. 18, 2011.
National Alert Registry website titled, “Does a sexual offender live in your neighborhood”, Oct. 22, 2006, pp. 2, http://web.archive.org/wb/20061022204835/http://www.nationallertregistry.com/ accessed on Oct. 13, 2011.
Next Card: About Us, http://web.cba.neu.edu/˜awatson/NextCardCase/NextCardAboutUs.htm printed Oct. 23, 2009 in 10 pages.
Ogg, Erica, “Apple Cracks Down on UDID Use”, http://gigaom.com/apple/apple-cracks-down-on-udid-use/printed Nov. 5, 2012 in 5 Pages.
Pagano, et al., “Information Sharing in Credit Markets,” Dec. 1993, The Journal of Finance, vol. 48, No. 5, pp. 1693-1718.
Partnoy, Frank, Rethinking Regulation of Credit Rating Agencies: An Institutional Investor Perspective, Council of Institutional Investors, Apr. 2009, pp. 21.
Paustian, Chuck, “Every Cardholder a King Customers get the Full Treatment at Issuers' Web Sites,” Card Marketing, New York, Mar. 2001, vol. 5, No. 3, pp. 4.
People Finders, http://www.peoplefinders.com/?CMP=Google&utm_source=google&utm_medium=cpc printed Nov. 16, 2010 in 1 page.
People Lookup, “Your Source for Locating Anyone!” www.peoplelookup.com/people-search.html printed Nov. 16, 2010 in 1 page.
People Search, “The Leading Premium People Search Site on the Web,” http://www.peoplesearch.com printed Nov. 16, 2010 in 2 pages.
PersonalCapital.com, http://www.personalcapital.com/how-it-works printed Feb. 5, 2014 in 5 pages.
Phinisee, Tamarind, “Banks, FTC Step Up Efforts to Address Identity Theft”, San Antonio Business Journal; San Antonio, Jul. 5, 2002, vol. 16, No. 24, pp. 5.
Press Release—“Helping Families Protect Against Identity Theft—Experian Announces FamilySecure.com; Parents and guardians are alerted for signs of potential identity theft for them and their children; product features an industry-leading $2 million guarantee”; PR Newswire; Irvine, CA; Oct. 1, 2007.
Privacy Rights Clearinghouse, “Identity Theft: What to do if it Happens to You,” http://web.archive.org/web/19990218180542/http://privacyrights.org/fs/fs17a.htm printed Feb. 18, 1999.
Ramaswamy, Vinita M., Identity-Theft Toolkit, The CPA Journal, Oct. 1, 2006, vol. 76, Issue 10, pp. 66-70.
Rawe, Julie; “Identity Thieves”, Time Bonus Section, Inside Business, Feb. 2002, pp. 2.
Roth, Andrew, “CheckFree to Introduce E-Mail Billing Serving,” American Banker, New York, Mar. 13, 2001, vol. 166, No. 49, pp. 3.
Sakimura et al., “OpenID Connect Core 1.0 Incorporating Errata Set 1”, <https://openid.net/specs/openid-connect-core-1_0.html>, Nov. 8, 2014, pp.
SAS, “SAS® Information Delivery Portal”, Fact Sheet, 2008, in 4 pages.
Scholastic Inc.:Parent's Request for Information http://web.archive.org/web/20070210091055/http://www.scholastic.com/inforequest/index.htm as archived Feb. 10, 2007 in 1 page.
Scholastic Inc.:Privacy Policy http://web.archive.org/web/20070127214753/http://www.scholastic.com/privacy.htm as archived Jan. 27, 2007 in 3 pages.
Securities and Futures Commission, “Guideline on Anti-Money Laundering and Counter-Terrorist Financing”, Jul. 2012, pp. 135.
Singletary, Michelle, “The Littlest Victims of ID Theft”, The Washington Post, The Color of Money, Oct. 4, 2007.
Sun, Hung-Min, “An Efficient Remote Use Authentication Scheme Using Smart Cards”, IEEE Transactions on Consumer Electronics, Nov. 2000, vol. 46, No. 4, pp. 958-961.
Target, “Free Credit Monitoring and Identity Theft Protection with Experian's ProtectMyID Now Available”, Jan. 13, 2014, pp. 2. http://corporate.target.com.
TheMorningCall.Com, “Cheap Ways to Foil Identity Theft,” www.mcall.com/business/columnists/all-karp.5920748jul01,0 . . . , published Jul. 1, 2007.
“TransUnion—Child Identity Theft Inquiry”, TransUnion, http://www.transunion.com/corporate/personal/fraudIdentityTheft/fraudPrevention/childIDInquiry.page as printed Nov. 5, 2009 in 4 pages.
Truston, “Checking if your Child is an ID Theft Victim can be Stressful,” as posted by Michelle Pastor on Jan. 22, 2007 at http://www.mytruston.com/blog/credit/checking_if_your_child_is_an_id_theft_vi.html.
US Legal, Description, http://www.uslegalforms.com/us/US-00708-LTR.htm printed Sep. 4, 2007 in 2 pages.
Vamosi, Robert, “How to Handle ID Fraud's Youngest Victims,” Nov. 21, 2008, http://news.cnet.com/8301-10789_3-10105303-57.html.
Waggoner, Darren J., “Having a Global Identity Crisis,” Collections & Credit Risk, Aug. 2001, vol. vol. 6, No. 8, pp. 6.
Wang et al., “User Identification Based on Finger-vein Patterns for Consumer Electronics Devices”, IEEE Transactions on Consumer Electronics, May 2010, vol. 56, No. 2, pp. 799-804.
Weaver et al., “Federated, Secure Trust Networks for Distributed Healthcare IT Services”, IEEE International Conference on Industrial Informatics, 2003. INDIN 2003. Proceedings, 2003, pp. 162-169.
WhatIs.com, “Risk-Based Authentication (RBA)”, https://web.archive.org/web/20121025033106/http://whatis.techtarget.com/definition/risk-based-authentication-RBA, Oct. 23, 2012, pp. 1.
Yahoo! Search, “People Search,” http://people.yahoo/com printed Nov. 16, 2010 in 1 page.
Yodlee \| Money Center, https://yodleemoneycenter.com/ printed Feb. 5, 2014 in 2 pages.
You Need a Budget, http://www.youneedabudget.com/features printed Feb. 5, 2014 in 3 pages.
Official Communication in Australian Patent Application No. 2014318966, dated Apr. 6, 2019.
Official Communication in Australian Patent Application No. 2019261724, dated Sep. 1, 2020.
Official Communication in Canadian Patent Application No. 2,923,697, dated Oct. 9, 2019.
Extended European Search Report for Application No. EP14843372.5, dated May 2, 2017.
Official Communication in European Application No. EP14843372.5 dated Nov. 29, 2018.
Extended European Search Report for Application No. EP19203040.1, dated Jan. 29, 2020.
International Search Report and Written Opinion for Application No. PCT/US2014/054713, dated Dec. 15, 2014.
International Preliminary Report on Patentability in Application No. PCT/US2014/054713, dated Mar. 24, 2016.
Official Communication in Australian Patent Application No. 2006306790, dated Apr. 29, 2010.
Official Communication in Australian Patent Application No. 2006306790, dated May 19, 2011.
International Search Report and Written Opinion for Application No. PCT/US2006/028006, dated Jul. 27, 2007.
International Preliminary Report on Patentability in Application No. PCT/US2006/028006, dated Apr. 23, 2008.
International Search Report and Written Opinion for Application No. PCT/US2019/037547, dated Oct. 4, 2019.
International Preliminary Report on Patentability in Application No. PCT/US2019/037547, dated Dec. 30, 2020.
International Search Report and Written Opinion for Application No. PCT/US2021/015566, dated May 11, 2021.
Extended European Search Report for Application No. EP21183630.9, dated Oct. 15, 2021.
International Preliminary Report on Patentability in Application No. PCT/US2021/015566, dated Aug. 11, 2022.
Willems et al., “On the Security and Privacy of Interac e-Transfers”, School of Electrical Engineering and Computer Science, Faculty of Engineering, University of Ottawa, Extended Version, Dec. 10, 2019, pp. 47.
U.S. Appl. No. 14/276,540, U.S. Pat. No. 9,721,147, Digital Identity, filed May 13, 2014.
U.S. Appl. No. 15/662,712, U.S. Pat. No. 10,453,159, Digital Identity, filed Jul. 28, 2017.
U.S. Appl. No. 16/657,174, 2020/0160472, Digital Identity, filed Oct. 18, 2019.

Provisional Applications (1)

	Number	Date	Country
	61826925	May 2013	US

Continuations (3)

	Number	Date	Country
Parent	16657174	Oct 2019	US
Child	17444849		US
Parent	15662712	Jul 2017	US
Child	16657174		US
Parent	14276540	May 2014	US
Child	15662712		US

Digital identity

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

International Classifications

Disclaimer

Abstract