Identity verification through multisystem cooperation

Information

  • Patent Grant
  • 12021861
  • Patent Number
    12,021,861
  • Date Filed
    Monday, January 4, 2021
    3 years ago
  • Date Issued
    Tuesday, June 25, 2024
    6 months ago
Abstract
A system includes first and second subsystems. The first subsystem receives a validation number request, transmitted by a first device in response to the entry of an account number into a first field of a webpage. In response to receiving the request, the first subsystem randomly generates the validation number, stores a copy in memory, and transmits it to a second device. The second subsystem receives a transaction request that includes the validation number from the first device, and transmits the received number to the first subsystem. The first device transmitted the request in response to the second device receiving the validation number and its subsequent entry into a second field of the webpage displayed on the first device. In response to receiving the validation number, the first subsystem determines that it matches the stored copy and transmits a message to the second subsystem authorizing the transaction.
Description
TECHNICAL FIELD

The present disclosure relates generally to multisystem data transferring and, more specifically, to identity verification through multisystem cooperation.


BACKGROUND

The internet has enabled individuals to interact with organizations and other entities without ever stepping foot inside the physical buildings operated by the entities. For example, an individual may provide information to an entity simply by entering the information into a form displayed on a webpage belonging to the entity or otherwise transmitting the information electronically to the entity.


SUMMARY

This disclosure contemplates an identity verification system that may be used to help verify the identity of a user who is providing electronic information to an entity system. In particular, the disclosed system may be used to verify a user's identity when the user is attempting to engage in an electronic transaction with an entity system by using an internet-connected device to provide account information to the entity system. When the user enters an account number into a field displayed on a webpage of the entity, a system associated with the institution at which the user's account is held generates a validation number for the transaction. The institution system then transmits this validation number to a second device, which the user/account holder had previously registered with the system. After receiving the validation number on his/her second device, the user enters the validation number into the webpage displayed on his/her first device and transmits it to the entity system as part of the user's transaction request. The entity system then provides the validation number that it received from the user back to the institution system for authentication. If the validation number received by the institution system matches the validation number that the institution system originally transmitted to the second device, the institution system determines that the user who is attempting to conduct the transaction with the entity system is in fact the account holder (as opposed to an individual who has obtained the account holder's information and is attempting to impersonate the account holder), and instructs the entity system to approve the requested transaction. On the other hand, if the received validation number does not match the validation number originally transmitted by the institution system to the second device, the institution system instructs the entity system to decline the requested transaction. An embodiment of the identity verification system is described below.


According to one embodiment, a system includes a first subsystem associated with an institution and a second subsystem associated with an entity. The first subsystem includes a memory and a hardware processor communicatively coupled to the memory. The second subsystem includes a hardware processor. The hardware processor of the first subsystem receives, from a first user device, a request for a validation number. The first user device transmitted the request for the validation number in response to a determination that an account number had been entered into a first field of a webpage displayed on the first user device. The webpage is associated with the entity. The account number corresponds to an account held at the institution. In response to receiving the request for the validation number, the processor of the first subsystem randomly generates the validation number. The processor of the first subsystem also stores a copy of the validation number in the memory. The processor of the first subsystem additionally transmits the validation number to a second user device associated with the account. The hardware processor of the second subsystem receives, from the first user device, a request for a transaction. The request for the transaction includes the validation number. The first user device transmitted the request for the transaction in response to the second user device receiving the validation number and the validation number being entered into a second field of the webpage displayed on the first user device. The processor of the second subsystem also transmits the validation number received in the request for the transaction to the first subsystem. In response to receiving the validation number, the hardware processor of the first subsystem determines that the validation number received from the second subsystem matches the copy of the validation number stored in the memory. In response to determining that the validation number received from the second subsystem matches the copy of the validation number stored in the memory, the processor of the first subsystem transmits a message to the second subsystem authorizing the transaction.


Certain embodiments provide one or more technical advantages. As an example, an embodiment includes a mobile device application that, in response to the mobile device receiving a validation number, is configured to automatically display a pop-up notification of the validation number on the mobile device display. In this manner, the embodiment enables a user of the mobile device to efficiently access the validation number, and conserves processing resources that would otherwise be expended by the user using his/her mobile device to navigate to the mobile application and accessing the validation number within the mobile application. As another example, in certain embodiments, a user device is configured to determine when a user has entered an account number into a field displayed on a webpage and, in response, automatically replace the account verification fields traditionally displayed on the webpage with a field for input of a validation number. In this manner, certain embodiments conserve the processing and networking resources that would otherwise be expended by (1) the device transmitting the account number and the traditional account verification data to a merchant system, (2) the merchant system determining that the account number belongs to an institution for which the user should transmit a validation number to the merchant system, and (3) the merchant system transmitting a request to the user's device to display a field for input of the validation number. The system described in the present disclosure may particularly be integrated into a practical application of an identity verification system for use by an institution that conducts electronic transactions on behalf of its account holders, who initiate the transactions by providing account details to entities through webpages belonging to the entities.


Certain embodiments may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art form the figures, descriptions, and claims included herein.





BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:



FIG. 1 illustrates an example identity verification system; and



FIGS. 2A and 2B present a flowchart illustrating a method by which the first user device, second user device, institution system, and entity system of the identity verification system of FIG. 1 act cooperatively to verify the identity of a user who is attempting to engage in a transaction with the entity system.





DETAILED DESCRIPTION

Embodiments of the present disclosure and its advantages may be understood by referring to FIGS. 1 through 2B of the drawings, like numerals being used for like and corresponding parts of the various drawings.


I. System Overview



FIG. 1 illustrates an example identity verification system 100 that includes first device 102, user 104, second device 106, network 108, entity system 110, and institution system 112. Entity system 110 is associated with an entity with which user 104 may conduct a transaction. Institution system 112 is associated with an institution at which user 104 holds an account that user 104 may use to conduct the transaction. Generally, when user 104 attempts to engage in a transaction with entity system 110 using first device 102, institution system 112, entity system 110, first device 102, and second device 106 act cooperatively to verify the identify of user 104, with the aid of a validation number 130, generated by institution system 112 for the transaction. While described throughout this disclosure as being a number, validation number 130 may be any suitable sequence of characters. For example, in certain embodiments, validation number 130 may be an alphanumeric number, or any other suitable sequence of characters. Details of the manner by which validation number 130 is generated and subsequently used by first device 102, second device 106, entity system 110, and institution system 112 to confirm the identity of user 104 are presented below, and in the discussion of FIGS. 2A and 2B.


First device 102 and second device 106 are used by user 104 to communicate with components of system 100 over network 108. As illustrated in FIG. 1, in certain embodiments first device 102 and second device 106 are separate devices. In some embodiments, first device 102 and second device 106 are the same device. For example, first device 102 and second device 106 may both correspond to a smart phone operated by user 104.


First device 102 includes display 114. First device 102 is configured to display a webpage 116 belonging to entity system 110 on display 114. For example, user 104 may use first device 102 to access a web browser installed on first device 102 and use the web browser to navigate to webpage 116. Webpage 116 is an interactive webpage through which user 104 may initiate a transaction with entity system 110. For example, user 104 may use webpage 116 to purchase one or more goods from the entity associated with entity system 110. As illustrated in FIG. 1, webpage 116 may display one or more fields 140a/b. For example, webpage 116 may display a first field 140a for input of an account number 136, and a second field 140b for input of a validation number 130. While illustrated in FIG. 1 as including two fields 140a/b, webpage 116 may display any number of fields 140a/b. Furthermore, in certain embodiments, webpage 116 may be configured to adjust the number of displayed fields 140a/b in response to receiving input from user 104. For example, in certain embodiments, when webpage 116 first loads, webpage 116 may be configured to display a set of fields 140a/b that includes a field for input of a credit/bank card number, a field for input of an expiry date of the credit/bank card, and a field for input of a card verification value (CVV) number. Then, in response to user 104 entering a credit/bank card number that is associated with institution system 112, device 102 may be configured to replace the field for input of the expiry date of the credit/bank card and the field for input of the CVV number with a field 140b for input of a validation number 130.


In response to user 104 entering an account number 136 that is associated with institution system 112 into first field 140a, first device 102 is configured to transmit transaction initiation message 138 to institution system 112. As described in further detail below, and in the discussion of FIGS. 2A and 2B, transaction initiation message 138 is used by first device 102 to request that institution system 112 generate a validation number 130 for the transaction that user 104 is initiating. First device 102 may be configured to determine that user 104 has entered an account number 136 that is associated with institution system 112 into field 140a in any suitable manner. For example, in certain embodiments, device 102 is configured to make this determination based on the first four numbers of account number 136. In response to user 104 entering a validation number 130 into second field 140b, first device 102 is configured to transmit transaction request 144 to entity system 110. Transaction request 144 includes account number 136 and validation number 130. As described in further detail below, and in the discussion of FIGS. 2A and 2B, entity system 110 uses the information transmitted in transaction request 144 to verify user 104's identity and to process the requested transaction.


First device 102 includes any appropriate device for displaying webpage 116 and for communicating with components of system 100 over network 108. For example, first device 102 may be a mobile phone, a computer, a laptop, a tablet, an IoT device, and/or an automated assistant, among others. In addition to including display 114, first device 102 may include any other appropriate user interface, such as a microphone, keypad, or other appropriate terminal equipment usable by user 104. In some embodiments, an application executed by a processor of first device 102 may perform the functions described herein.


Second device 106 is configured to receive validation number 130 from institution system 112 and present validation number 130 to user 104. Second device 106 may be configured to receive and present validation number 130 to user 104 in any suitable manner. As an example, in certain embodiments, an application installed on second device 106 is configured to receive validation number 130 from institution system 112 and to present validation number 130 to user 104. For example, the application may be configured to automatically generate a pop-up notification 142 that includes validation number 130 on the display 107 of second device 106. In some embodiments, second device 106 may automatically turn on display 107 in order to present pop-up notification 142 to user 104. In this manner, second device 106 may display validation number 130 to user 104 even though user 104 is not actively operating second device 106. In certain embodiments, second device 106 may be configured to display pop-up notification 142 to user 104 for a set amount of time, after which validation number 130 may no longer be available to user 104. In some embodiments, user 106 may be able to view validation number 130 even after pop-up notification 142 has disappeared from display 107. For example, in such embodiments, user 104 may view validation number 130 by navigating to the application that generated pop-up notification 142 and viewing validation number 130 within the application. As another example of the manner by which second device 106 may present validation number 130 to user 104, in certain embodiments, second device 106 may receive validation number 130 from institution system 112 in an SMS message or any other electronic message (e.g., email), and present the electronic message to user 104 on display 107. As a further example, in certain embodiments in which second device 106 is the same device as first device 102, in response to receiving validation number 130 from institution system 112, second device 106 may be configured to automatically populate second field 140b, displayed on webpage 116, with validation number 130.


Second device 106 includes any appropriate mobile device for displaying validation number 130 to user 104, and for communicating with components of system 100 over network 108. For example, second device 102 may be a mobile phone, a laptop, a tablet, an IoT device, and/or an automated assistant, among others. In addition to including display 107, second device 102 may include any other appropriate user interface, such as a microphone, keypad, or other appropriate terminal equipment usable by user 104. In some embodiments, an application executed by a processor of second device 106 may perform the functions described herein.


Network 108 facilitates communication between and amongst the various components of system 100. This disclosure contemplates network 108 being any suitable network operable to facilitate communication between such components. Network 108 may include any interconnecting system capable of transmitting audio, video, signals, data, messages, or any combination of the preceding. Network 108 may include all or a portion of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network, such as the Internet, a wireline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof, operable to facilitate communication between the components.


Entity system 110 is associated with a given entity with which user 104 is attempting to engage in a transaction. For example, entity system 110 may belong to a merchant with an online store, and/or any other entity with which user 104 may attempt to engage in a transaction. As illustrated in FIG. 1, entity system 110 includes a processor 118 and a memory 120. This disclosure contemplates processor 118 and memory 120 being configured to perform any of the functions of entity system 110 described herein. For example, processor 118 may execute instructions 122 stored in memory 120 to perform any of the functions described herein. Generally, entity system 110 is configured to: (1) receive a transaction request 144 from first device 102 that includes a validation number 130; (2) provide the received validation number 130 to institution system 112 for authentication; (3) receive an authentication result 148 back from institution system 112, indicating whether or not the validation number 130 received from first device 102 matches the validation number 130 stored by institution system 112; and (4) approve or decline transaction request 144 based on authentication result 148. These functions of entity system 110 are described in further detail below, in the discussion of FIGS. 2A and 2B.


Processor 118 is any electronic circuitry, including, but not limited to central processing units (CPUs), graphics processing units (GPUs), microprocessors, application specific integrated circuits (ASIC), application specific instruction set processor (ASIP), and/or state machines, that communicatively couples to memory 120 and controls the operation of entity system 110. Processor 118 may be 8-bit, 16-bit, 32-bit, 64-bit or of any other suitable architecture. Processor 118 may include an arithmetic logic unit (ALU) for performing arithmetic and logic operations, processor registers that supply operands to the ALU and store the results of ALU operations, and a control unit that fetches instructions from memory and executes them by directing the coordinated operations of the ALU, registers and other components. Processor 118 may include other hardware and software that operates to control and process information. Processor 118 executes software, such as instructions 122, stored on memory to perform any of the functions described herein. Processor 118 controls the operation and administration of entity system 110 by processing information received from first device 102, second device 106, network 108, and/or institution system 112. Processor 118 may be a programmable logic device, a microcontroller, a microprocessor, any suitable processing device, or any suitable combination of the preceding. Processor 118 is not limited to a single processing device and may encompass multiple processing devices. In certain embodiments in which processor 118 encompasses multiple processing devices, such devices may be located at geographically separate locations from one another and connected to one another by a network (e.g., network 108).


Memory 120 may store, either permanently or temporarily, data, operational software, or other information for processor 118, such as instructions 122. Memory 120 may include any one or a combination of volatile or non-volatile local or remote devices suitable for storing information. For example, memory 120 may include random access memory (RAM), read only memory (ROM), magnetic storage devices, optical storage devices, or any other suitable information storage device or a combination of these devices. The software represents any suitable set of instructions, logic, or code embodied in a computer-readable storage medium. For example, the software may be embodied in memory 120, a disk, a CD, or a flash drive. In particular embodiments, the software may include an application, such as instructions 122, executable by processor 118 to perform one or more of the functions described herein.


Institution system 112 is associated with a given institution at which user 104 holds an account that the user may use to complete a transaction with entity system 110. For example, institution system 112 may belong to a bank, a credit card company, and/or any other financial institution with which user 104 may hold an account. As illustrated in FIG. 1, institution system 112 includes a processor 124 and a memory 126. This disclosure contemplates processor 124 and memory 126 being configured to perform any of the functions of institution system 112 described herein. For example, processor 124 may execute instructions 128 stored in memory 126 to perform any of the functions described herein. Generally, institution system 112 is configured to: (1) receive transaction initiation message 138 from first device 102, indicating that user 104 is attempting to initiate a transaction with entity system 110; (2) in response to receiving transaction initiation message 138, randomly generate a validation number 130 for the transaction; (3) store a copy of validation number 130 in memory 126; (4) transmit validation number 130 to second device 106; (5) receive an authentication request 146 from entity system 110, which includes a validation number 130 received by entity system 110 from first device 102; (6) compare the received validation number 130 with the copy of the validation number 130 stored in memory 126; and (7) transmit a message 148 to entity system 110 instructing entity system 110 to approve or decline transaction request 144, based on the results of the comparison. These functions of institution system 112 are described in further detail below, in the discussion of FIGS. 2A and 2B.


Processor 124 is any electronic circuitry, including, but not limited to central processing units (CPUs), graphics processing units (GPUs), microprocessors, application specific integrated circuits (ASIC), application specific instruction set processor (ASIP), and/or state machines, that communicatively couples to memory 126 and controls the operation of institution system 112. Processor 124 may be 8-bit, 16-bit, 32-bit, 64-bit or of any other suitable architecture. Processor 124 may include an arithmetic logic unit (ALU) for performing arithmetic and logic operations, processor registers that supply operands to the ALU and store the results of ALU operations, and a control unit that fetches instructions from memory and executes them by directing the coordinated operations of the ALU, registers and other components. Processor 124 may include other hardware and software that operates to control and process information. Processor 124 executes software, such as instructions 128, stored on memory to perform any of the functions described herein. Processor 124 controls the operation and administration of institution system 112 by processing information received from first device 102, second device 106, network 108, and/or entity system 110. Processor 124 may be a programmable logic device, a microcontroller, a microprocessor, any suitable processing device, or any suitable combination of the preceding. Processor 124 is not limited to a single processing device and may encompass multiple processing devices. In certain embodiments in which processor 124 encompasses multiple processing devices, such devices may be located at geographically separate locations from one another and connected to one another by a network (e.g., network 108).


Memory 126 may store, either permanently or temporarily, data, operational software, or other information for processor 124, such as instructions 128. Memory 126 may include any one or a combination of volatile or non-volatile local or remote devices suitable for storing information. For example, memory 126 may include random access memory (RAM), read only memory (ROM), magnetic storage devices, optical storage devices, or any other suitable information storage device or a combination of these devices. The software represents any suitable set of instructions, logic, or code embodied in a computer-readable storage medium. For example, the software may be embodied in memory 126, a disk, a CD, or a flash drive. In particular embodiments, the software may include an application, such as instructions 128, executable by processor 124 to perform one or more of the functions described herein.


Memory 126 also stores copies of the validation numbers 130a through 130n that have been generated by institution system 112. In certain embodiments, memory 126 stores copies of the validation numbers that it has generated and that are outstanding. For example, memory 126 stores copies of the validation numbers that institution system 112 has not yet received back from entity system 110 in authentication requests 146. In some embodiments, memory 126 stores a full set of historical validation numbers 130a through 130n (e.g., copies of both the outstanding validation numbers 130 and those validation numbers 130 that institution system 112 has received back from entity system 110 in authentication requests 146). Institution system 112 may use this full set of historical validation numbers 130a through 130n to help ensure that any new validation numbers 130 that it generates have not previously been used for identity verification purposes, as described in further detail below, in the discussion of FIGS. 2A and 2B.


In certain embodiments, memory 126 also stores a set of times 132 and a set of account details 134. Each time of the set of times 132 is associated with a validation number 130, and corresponds to the time at which the validation number was generated by institution system 112. In certain embodiments, validation numbers 130 may expire after a certain amount of time. In such embodiments, institution system 112 uses set of times 132 to determine whether or not a validation number 130 received in an authentication request 146 has expired, as described in further detail below, in the discussion of FIGS. 2A and 2B. In certain embodiments, for each user 104 who holds an account with the institution associated with institution system 112, account details 134 stores information about the user and/or his/her account. For example, for a given user 104, account details 134 may store the account number 136 assigned to the user's account as well as an identification of second device 106, to which institution system 112 should send validation numbers 130, and/or any other information that institution system 112 may use to transmit validation numbers 130 to second device 106. For example, account details 134 may include a cell phone number assigned to second device 106, an email address belonging to user 104, and/or any other suitable identification information that may be used to transmit validation number 130 to second device 106.


Modifications, additions, or omissions may be made to the systems described herein without departing from the scope of the invention. For example, system 100 may include any number of users 104, first devices 102, second devices 106, entity system 110, and institution systems 112. The components may be integrated or separated. Moreover, the operations may be performed by more, fewer, or other components. Additionally, the operations may be performed using any suitable logic comprising software, hardware, and/or other logic.



FIGS. 2A and 2B present a flowchart (described in conjunction with elements of FIG. 1) illustrating an example method 200 by which first device 102, second device 106, institution system 112, and entity system 110 act cooperatively to verify the identify of a user 104 who is attempted to engage in a transaction with entity system 110.


In step 202 first device 102 determines whether or not user 104 has entered an account number 136 into a field 140a of a webpage 116 associated with entity system 110. If, in step 202 first device 102 determines that user 104 has entered an account number 136 into field 140a, in step 204 first device 102 transmits a message 138 to institutions system 112 requesting that institution system 112 generate a validation number 130. In step 206 institution system 112 randomly generates a validation number 130. Institution system 112 may randomly generate validation number 130 in any suitable manner. As an example, in certain embodiments in which validation number 130 corresponds to a sequence of numerical digits, institution system 112 may generate validation number 130 using a random number generator stored in memory 126. For example, institution system 112 may use the random number generator to generate a validation number 130 that is 5 digits in length, 10 digits in length, or any other suitable length. In some embodiments, institution system 112 may use the random number generator to randomly generate a length for the validation number as well as to randomly generate the digits that make up the validation number. In certain embodiments in which validation number 130 is an alphanumeric number, institution system 112 may use the random number generator to: (1) randomly determine a length for the validation number; (2) randomly determine a number of letters to include in the validation number, randomly determine those letters, and randomly assign each of those letters to a position within the validation number; (3) randomly determine a number of digits to include in the validation number, randomly determine those digits, and randomly assign each of those digits to a position within the validation number; and/or (4) randomly determine a number of wildcard characters to include in the validation number, randomly determine those wildcard characters, and randomly assign each of those wildcard characters to a position within the validation number.


In step 208 institution system 112 compares the randomly generated validation number 130 to historical validation numbers 130a through 130n stored in memory 120 to determine whether or not the validation number 130 already exists. If, in step 208 institution system 112 determines that validation number 130 already exists in memory 126, method 200 returns to step 206, where institution system 112 randomly generates a new validation number 130. If, in step 208 institution system 112 determines that validation number 130 does not already exist in memory 126, in step 210 institution system 112 transmit validation number 130 to second device 106. In step 212 second device 106 displays validation number 130 to user 104 on display 107. In response to second device 106 displaying validation number 130, user 104 may enter validation number 130 into a second field 140b of the webpage 116 that is displayed on first device 102.


In step 214 first device 102 determines whether user 104 has entered validation number 130 into second field 140b of webpage 116. If, in step 214 first device 102 determines that user 104 has entered validation number 130 into second field 140b, in step 216 first device 102 transmits validation number 130 to entity system 110 in transaction request 144. In step 218 entity system 110 determines whether or not it has received validation number 130. If, in step 218 entity system 100 determine that it has received validation number 130, in step 220 entity system 110 transmits the received validation number 130 to institution system 112 for authentication.


In step 222 institution system 112 determines whether or not the validation number 130 received from entity system 110 matches the copy of the original validation number 130 that institution system 112 transmitted to second device 106. In certain embodiments, institution system 112 additionally determines whether or not it has received the validation number within a threshold amount of time since it first generated the validation number (e.g., whether or not the validation number has expired). If, in step 222 institution system 112 determines that the validation number 130 received from entity system 110 does not match the copy of the validation number 130 stored in memory 126 and/or that the validation number 130 has been received after the threshold amount of time since it was first generated, in step 226 institution system 112 generates message 148 instructing entity system 110 to decline user 104's transaction request 144. If, in step 222 institution system 112 determines that the validation number 130 received from entity system 110 matches the copy of the validation number 130 stored in memory 126 and, in certain embodiments, that the validation number 130 was received within the threshold time since its creation, in step 224 institution system generates message 148 instructing entity system 110 to approve user 104's transaction request 144. In step 228 institution system 112 transmits message 148 to entity system 110. In certain embodiments, in step 230 institution system 112 also sends instructions to second device 106 to delete any copies of validation number 130, such that validation number 130 is no longer available on second device 106. In response to receiving such instructions, second device 102 deletes validation number 130, in step 232. In step 234 entity system 110 transmits transaction result message 142 to first device 102. Transaction result message 142 may include any suitable information. As an example, in certain embodiments in which institution system 112 transmitted an authentication result message 148 to entity system 110 instructing entity system 110 to deny the requested transaction, transaction result message 142 may indicate that entity system 110 has denied the transaction. As another example, in certain embodiments in which institution system 112 transmitted an authentication result message 148 to entity system 110 instructing entity system 110 to approve the transaction request 144, entity system 110 may have used account number 136 to process the transaction. In such embodiments, transaction result message 142 may indicate that entity system has processed the transaction, and may include information such as a confirmation number. In step 236, in response to receiving transaction result message 142, first device 102 displays the contents of transaction result message 142 on display 114. For example, first device 102 may display a message to user 104 on display 114 indicating that entity system 110 has approved or declined the transaction.


Modifications, additions, or omissions may be made to method 200 depicted in FIGS. 2A and 2B. Method 200 may include more, fewer, or other steps. For example, steps may be performed in parallel or in any suitable order. While discussed as first device 102, second device 106, institution system 112, and entity system 110 (or components thereof) performing certain steps, any suitable components of system 100, may perform one or more steps of the method.


Although the present disclosure includes several embodiments, a myriad of changes, variations, alterations, transformations, and modifications may be suggested to one skilled in the art, and it is intended that the present disclosure encompass such changes, variations, alterations, transformations, and modifications as falling within the scope of the appended claims.

Claims
  • 1. A system comprising: a first subsystem associated with an institution, the first subsystem comprising: a memory; anda hardware processor communicatively coupled to the memory, the hardware processor configured to:receive, from a first user device, a request for a first validation number, wherein: a webpage is displayed on the first user device comprising a first field configured to receive an account number, a second field configured to receive an expiry date and a third field configured to receive a card verification value number;the first user device transmitted the request for the first validation number in response to a determination that the account number is entered into the first field;in response to the determination that the account number is entered into the first field, the second field and the third field are automatically replaced with a fourth field configured to receive the first validation number;the webpage is associated with an entity; andthe account number corresponds to an account held at the institution; andin response to receiving the request for the first validation number: randomly generate the first validation number;store a copy of the first validation number in the memory;determine whether the first validation number already exists in the memory;in response to determining that the first validation number already exists in the memory, randomly generate a new validation number; andin response to determining that the first validation number is not in the memory, transmit the first validation number to a second user device associated with the account, the second user device being different from the first user device; anda second subsystem associated with the entity, the second subsystem comprising a hardware processor configured to: receive, from the first user device, a request for a transaction, the request for the transaction comprising the first validation number, wherein the first user device transmitted the request for the transaction in response to: the second user device receiving the first validation number; andthe first validation number being entered into the fourth field of the webpage displayed on the first user device; andtransmit the first validation number received in the request for the transaction to the first subsystem, wherein, in response to receiving the first validation number, the hardware processor of the first subsystem is further configured to: determine that the first validation number received from the second subsystem matches the copy of the first validation number stored in the memory;in response to determining that the first validation number received from the second subsystem matches the copy of the first validation number stored in the memory, transmit a message to the second subsystem authorizing the transaction; andin response to determining that the first validation number received from the second subsystem matches the copy of the first validation number stored in the memory, transmit a message to the second user device instructing the second user device to delete the first validation number.
  • 2. The system of claim 1, wherein the hardware processor of the second subsystem is further configured to: receive, from a third user device, a request for a second transaction, the request for the second transaction comprising a second validation number; andin response to receiving the request for the second transaction, transmit the second validation number to the first subsystem, wherein, in response to receiving the second validation number, the hardware processor of the first subsystem is further configured to: determine that the second validation number does not match any validation numbers stored in the memory; andin response to determining that the second validation number does not match any validation numbers stored in the memory, transmit a second message to the second subsystem instructing the second subsystem to decline the second transaction.
  • 3. The system of claim 1, wherein the second user device is configured to receive the first validation number from the first subsystem in at least one of: an SMS message;an email message; anda pop-up message generated by an application installed on the second user device.
  • 4. The system of claim 1, wherein: the first validation number is an alphanumeric number; andrandomly generating the first validation number comprises at least one of: randomly determining a length of the first validation number;randomly determining a number of letters to include in the first validation number;randomly determining a number of digits to include in the first validation number;randomly determining a number of wildcard characters to include in the first validation number;randomly determining a digit and a position of the digit within the first validation number;randomly determining a letter and a position of the letter within the first validation number; andrandomly determining a wildcard character and a position of the wildcard character within the first validation number.
  • 5. The system of claim 1, wherein: the first user device is the same as the second user device; andin response to receiving the first validation number from the first subsystem, the first user device is configured to automatically populate the fourth field of the webpage with the first validation number.
  • 6. The system of claim 1, wherein: in response to receiving the first validation number, the hardware processor of the first subsystem is further configured to determine that an amount of time since the first validation number was generated is less than a threshold length of time; andtransmitting the message to the second subsystem authorizing the transaction is further performed in response to determining that the amount of time since the first validation number was generated is less than the threshold length of time.
  • 7. A method comprising: receiving, from a first user device, a request for a first validation number, wherein: a webpage is displayed on the first user device comprising a first field configured to receive an account number, a second field configured to receive an expiry date and a third field configured to receive a card verification value number;the first user device transmitted the request for the first validation number in response to a determination that the account number is entered into the first field;in response to the determination that the account number is entered into the first field, the second field and the third field are automatically replaced with a fourth field configured to receive the first validation number;the webpage is associated with an entity; andthe account number corresponds to an account held at an institution;in response to receiving the request for the first validation number: randomly generating the first validation number;storing a copy of the first validation number in a storage location;determine whether the first validation number already exists in a memory;in response to determining that the first validation number already exists in the memory, randomly generate a new validation number; andin response to determining that the first validation number is not in the memory, transmitting the first validation number to a second user device associated with the account, the second user device being different from the first user device;receiving the first validation number from a system associated with the entity, the first validation number received by the system as part of a request for a transaction transmitted by the first user device, wherein the first user device transmitted the request for the transaction in response to: the second user device receiving the first validation number; andthe first validation number being entered into the fourth field of the webpage displayed on the first user device;determining that the first validation number received from the system matches the copy of the first validation number stored in the storage location;in response to determining that the first validation number received from the system matches the copy of the first validation number stored in the storage location, transmitting a message to the system authorizing the transaction; andin response to determining that the first validation number received from the system matches the copy of the first validation number stored in the storage location, transmitting a message to the second user device instructing the second user device to delete the first validation number.
  • 8. The method of claim 7, further comprising: receiving a second validation number from the system, the second validation number received by the system as part of a request for a second transaction transmitted by a third user device;determining that the second validation number does not match any validation numbers stored in the storage location; andin response to determining that the second validation number does not match any validation numbers stored in the storage location, transmitting a second message to the system instructing the system to decline the second transaction.
  • 9. The method of claim 7, wherein transmitting the first validation number to the second user device comprises at least one of: transmitting an SMS message to the second user device;transmitting an email message to an email account of a user of the second user device; andtransmitting the first validation number to an application installed on the second user device, wherein, in response to receiving the first validation number, the application is configured to generate a pop-up message on a display of the second user device, the pop-up message comprising the first validation number.
  • 10. The method of claim 7, wherein: the first validation number is an alphanumeric number; andrandomly generating the first validation number comprises at least one of: randomly determining a length of the first validation number;randomly determining a number of letters to include in the first validation number;randomly determining a number of digits to include in the first validation number;randomly determining a number of wildcard characters to include in the first validation number;randomly determining a digit and a position of the digit within the first validation number;randomly determining a letter and a position of the letter within the first validation number; andrandomly determining a wildcard character and a position of the wildcard character within the first validation number.
  • 11. The method of claim 7, wherein: the first user device is the same as the second user device; andthe first validation number being entered into the fourth field of the webpage displayed on the first user device comprises the first user device automatically populating the fourth field of the webpage with the first validation number.
  • 12. The method of claim 7, further comprising, in response to receiving the first validation number, determining that an amount of time since the first validation number was generated is less than a threshold length of time, wherein transmitting the message to the system authorizing the transaction is further performed in response to determining that the amount of time since the first validation number was generated is less than the threshold length of time.
  • 13. An apparatus associated with an institution, the apparatus comprising: a memory; anda hardware processor communicatively coupled to the memory, the hardware processor configured to: receive, from a first user device, a request for a first validation number, wherein: a webpage is displayed on the first user device comprising a first field configured to receive an account number, a second field configured to receive an expiry date and a third field configured to receive a card verification value number;the first user device transmitted the request for the first validation number in response to a determination that the account number is entered into the first field;in response to the determination that the account number is entered into the first field, the second field and the third field are automatically replaced with a fourth field configured to receive the first validation number;the webpage is associated with an entity; andthe account number corresponds to an account held at the institution;in response to receiving the request for the first validation number: randomly generate the first validation number;store a copy of the first validation number in the memory;determine whether the first validation number already exists in the memory;in response to determining that the first validation number already exists in the memory, randomly generate a new validation number; andin response to determining that the first validation number is not in the memory, transmit the first validation number to a second user device associated with the account, the second user device being different from the first user device;receive, from a system associated with the entity, the first validation number, wherein the system received the first validation number from the first user device as part of a request for a transaction, the request for the transaction transmitted by the first user device in response to: the second user device receiving the first validation number; andthe first validation number being entered into the fourth field of the webpage displayed on the first user device;determine that the first validation number received from the system matches the copy of the first validation number stored in the memory;in response to determining that the first validation number received from the system matches the copy of the first validation number stored in the memory, transmit a message to the system authorizing the transaction; andin response to determining that the first validation number received from the system matches the copy of the first validation number stored in the memory, transmit a message to the second user device instructing the second user device to delete the first validation number.
  • 14. The apparatus of claim 13, wherein the hardware processor is further configured to: receive a second validation number from the system, the second validation number received by the system as part of a request for a second transaction transmitted by a third user device;determine that the second validation number does not match any validation numbers stored in the memory; andin response to determining that the second validation number does not match any validation numbers stored in the memory, transmit a second message to the system instructing the system to decline the second transaction.
  • 15. The apparatus of claim 13, wherein transmitting the first validation number to the second user device comprises at least one of: transmitting an SMS message to the second user device;transmitting an email message to an email account of a user of the second user device; andtransmitting the first validation number to an application installed on the second user device, wherein, in response to receiving the first validation number, the application is configured to generate a pop-up message on a display of the second user device, the pop-up message comprising the first validation number.
  • 16. The apparatus of claim 13, wherein: the first validation number is an alphanumeric number; andrandomly generating the first validation number comprises at least one of: randomly determining a length of the first validation number;randomly determining a number of letters to include in the first validation number;randomly determining a number of digits to include in the first validation number;randomly determining a number of wildcard characters to include in the first validation number;randomly determining a digit and a position of the digit within the first validation number;randomly determining a letter and a position of the letter within the first validation number; andrandomly determining a wildcard character and a position of the wildcard character within the first validation number.
  • 17. The apparatus of claim 13, wherein: in response to receiving the first validation number, the hardware processor is further configured to determine that an amount of time since the first validation number was generated is less than a threshold length of time; andtransmitting the message to the system authorizing the transaction is further performed in response to determining that the amount of time since the first validation number was generated is less than the threshold length of time.
US Referenced Citations (889)
Number Name Date Kind
5148481 Abraham Sep 1992 A
5307483 Knipfer Apr 1994 A
5604791 Lee Feb 1997 A
5613012 Hoffman Mar 1997 A
5615277 Hoffman Mar 1997 A
5649462 Cucchi Jul 1997 A
5678046 Cahill Oct 1997 A
5764789 Pare, Jr. Jun 1998 A
5802199 Pare, Jr. Sep 1998 A
5805719 Pare, Jr. Sep 1998 A
5870723 Pare, Jr. Feb 1999 A
5903721 Sixtus May 1999 A
5913196 Talmor Jun 1999 A
6017765 Yamada Jan 2000 A
6134326 Micali Oct 2000 A
6137884 Micali Oct 2000 A
6141750 Micali Oct 2000 A
6154879 Pare, Jr. Nov 2000 A
6185683 Ginter Feb 2001 B1
6289513 Bentwich Sep 2001 B1
6317783 Freishtat Nov 2001 B1
6335927 Elliott Jan 2002 B1
6343361 Nendell Jan 2002 B1
6363358 Palmer Mar 2002 B1
6366682 Hoffman Apr 2002 B1
6396482 Griffin May 2002 B1
6434379 Despres Aug 2002 B1
6438550 Doyle Aug 2002 B1
6557168 Czajkowski Apr 2003 B1
6567974 Czajkowski May 2003 B1
6587853 LaRue Jul 2003 B1
6609125 Layne Aug 2003 B1
6690930 Dupre Feb 2004 B1
6705517 Zajkowski Mar 2004 B1
6851114 Czajkowski Feb 2005 B1
6901586 Czajkowski May 2005 B1
7020658 Hill Mar 2006 B1
7113962 Kee Sep 2006 B1
7202773 Oba Apr 2007 B1
7209903 Mamdani Apr 2007 B1
7240036 Mamdani Jul 2007 B1
7379921 Kiliccote May 2008 B1
7533335 Sawicki May 2009 B1
7933589 Mamdani Apr 2011 B1
7941197 Jain May 2011 B2
8024235 Mathew Sep 2011 B2
8109444 Jain Feb 2012 B2
8161527 Curren Apr 2012 B2
8341083 Jain Dec 2012 B1
8370911 Mallard Feb 2013 B1
8381999 Jain Feb 2013 B2
8407768 Hayter Mar 2013 B1
8423476 Bishop et al. Apr 2013 B2
8538863 Saunders Sep 2013 B1
8548540 Jain Oct 2013 B2
8561142 Sobel Oct 2013 B1
8561892 Hayhow et al. Oct 2013 B2
8660955 Ledbetter et al. Feb 2014 B2
8689296 Shewchuk Apr 2014 B2
8739260 Damm-Goossens May 2014 B1
8745718 Dufel Jun 2014 B1
8762279 Weller et al. Jun 2014 B2
8762529 Payne Jun 2014 B1
8781966 Blair et al. Jul 2014 B2
8793184 Lakshminarayanan Jul 2014 B2
8806582 Dietrich Aug 2014 B2
8818983 Truong Aug 2014 B1
8851366 Modi Oct 2014 B2
8885894 Rowen et al. Nov 2014 B2
8918854 Giobbi Dec 2014 B1
9016589 Jain Apr 2015 B2
9032498 Ben Ayed May 2015 B1
9038157 Santiago, Jr. May 2015 B1
9077713 Zheng Jul 2015 B1
9110679 Chan Aug 2015 B1
9191217 Martell Nov 2015 B2
9210156 Little Dec 2015 B1
9231925 Lundström Jan 2016 B1
9240992 Dietrich Jan 2016 B2
9251538 Shakkarwar Feb 2016 B1
9277049 Danis Mar 2016 B1
9294475 Hoyos Mar 2016 B2
9336634 Beenau et al. May 2016 B2
9384480 Jain Jul 2016 B2
9406067 Robinson et al. Aug 2016 B1
9420097 Perotti Aug 2016 B2
9471913 Kaptcan Oct 2016 B1
9501774 Ashfield Nov 2016 B2
9519901 Dorogusker Dec 2016 B1
9569775 Fisher et al. Feb 2017 B2
9594740 Reddy Mar 2017 B1
9674700 John Archibald Jun 2017 B2
9736147 Mead Aug 2017 B1
9736180 Baldwin Aug 2017 B2
9818112 Pirzadeh et al. Nov 2017 B2
9846689 Perelman Dec 2017 B2
9847990 de Boursetty Dec 2017 B1
9853977 Laucius Dec 2017 B1
9858781 Campero Jan 2018 B1
9888377 McCorkendale Feb 2018 B1
10037526 Campos Jul 2018 B2
10044647 Karp Aug 2018 B1
10068220 Perlman Sep 2018 B2
10109159 Shoemaker, Jr. Oct 2018 B1
10182048 Sabanayagam Jan 2019 B1
10200380 Belz Feb 2019 B2
10230725 Peterson Mar 2019 B2
10270771 Tamanini Apr 2019 B1
10290000 Kenderov May 2019 B2
10296897 Wu May 2019 B1
10304054 McNeal May 2019 B2
10332191 Eckel Jun 2019 B1
10362169 Sanderlin Jul 2019 B1
10395244 Mossler Aug 2019 B1
10411894 Yavnilovich Sep 2019 B1
10432618 Poder Oct 2019 B1
10462080 Jones Oct 2019 B1
10523708 Ilincic Dec 2019 B1
10524429 Tvetene Jan 2020 B1
10541996 Choi Jan 2020 B1
10552833 Godard et al. Feb 2020 B2
10560845 Manepalli Feb 2020 B1
10574689 Hoyos Feb 2020 B1
10580009 Snyder et al. Mar 2020 B2
10614442 Gupta et al. Apr 2020 B2
10623403 Gupta Apr 2020 B1
10623961 Manepalli Apr 2020 B1
10642715 Simca May 2020 B1
10645075 Rafferty May 2020 B1
10652739 Lilley May 2020 B1
10657754 Osborn May 2020 B1
10665244 Gupta May 2020 B1
10666793 Gardner May 2020 B1
10671984 Hayhow et al. Jun 2020 B2
10679453 Dominguez et al. Jun 2020 B2
10686781 Kaditz Jun 2020 B1
10701067 Ziraknejad Jun 2020 B1
10713661 Song et al. Jul 2020 B2
10721226 Kurani Jul 2020 B1
10721242 Jones Jul 2020 B1
10733601 Osborn Aug 2020 B1
10755277 Shakkarwar Aug 2020 B2
10783576 Van Os Sep 2020 B1
10785303 Ghabour Sep 2020 B2
10796017 Azaroff Oct 2020 B1
10810816 Kocher Oct 2020 B1
10853795 Capurso Dec 2020 B1
10873575 Herget Dec 2020 B2
10891610 Powell Jan 2021 B2
10915891 Winklevoss Feb 2021 B1
10932403 Tvetene Mar 2021 B1
10993387 Tvetene May 2021 B1
10997592 Kurani May 2021 B1
11006154 McSchooler May 2021 B2
11017464 Harris May 2021 B1
11023968 Arnold Jun 2021 B2
11044246 Freeling Jun 2021 B1
11051163 Smith Jun 2021 B1
11063931 Johri Jul 2021 B2
11070532 Choi Jul 2021 B1
11074562 Phillips Jul 2021 B1
11093309 Katzer Aug 2021 B1
11093912 Fakhraie Aug 2021 B1
11093944 Tesser Aug 2021 B1
11106515 Fakhraie Aug 2021 B1
11153307 Davey Oct 2021 B1
11232518 Mcwain Jan 2022 B1
11245690 Yoon Feb 2022 B1
11251975 Wahla Feb 2022 B1
11257057 Asmi Feb 2022 B1
11288660 Kurani Mar 2022 B1
11316849 Anzaldua Apr 2022 B1
11323434 Vali May 2022 B1
11354673 Brock Jun 2022 B1
11381652 Ranjan Jul 2022 B2
11386887 Teng Jul 2022 B1
11410161 Kurani Aug 2022 B1
11489842 Russell Nov 2022 B1
11546461 Jiron Jan 2023 B1
11587058 Kurani Feb 2023 B1
11593789 Kurani Feb 2023 B1
11615401 Kurani Mar 2023 B1
11632366 Shemesh Apr 2023 B1
11710179 Kaditz Jul 2023 B1
11740853 Eidam Aug 2023 B1
11762972 Singhal Sep 2023 B1
20010031457 Pfenninger Oct 2001 A1
20010032878 Tsiounis Oct 2001 A1
20020010693 Palmer Jan 2002 A1
20020016750 Attia Feb 2002 A1
20020032874 Hagen Mar 2002 A1
20020064149 Elliott May 2002 A1
20020067409 Harari Jun 2002 A1
20020069129 Akutsu Jun 2002 A1
20020091646 Lake Jul 2002 A1
20020112177 Voltmer Aug 2002 A1
20020149567 Griffin Oct 2002 A1
20030033146 Morin Feb 2003 A1
20030046589 Gregg Mar 2003 A1
20030051138 Maeda Mar 2003 A1
20030105648 Schurenberg Jun 2003 A1
20030105725 Hoffman Jun 2003 A1
20030115142 Brickell Jun 2003 A1
20030126080 Ogmen Jul 2003 A1
20030154371 Filipi-Martin Aug 2003 A1
20030154405 Harrison Aug 2003 A1
20030173408 Mosher, Jr. Sep 2003 A1
20030200184 Dominguez Oct 2003 A1
20030208406 Okamoto Nov 2003 A1
20030221125 Rolfe Nov 2003 A1
20030235092 Micheloni Dec 2003 A1
20030236991 Letsinger Dec 2003 A1
20040030935 Kai Feb 2004 A1
20040039930 Ohmori Feb 2004 A1
20040044739 Ziegler Mar 2004 A1
20040066278 Hughes Apr 2004 A1
20040088551 Dor May 2004 A1
20040093419 Weihl May 2004 A1
20040117662 Ong Jun 2004 A1
20040128249 Hoffman Jul 2004 A1
20040153655 Rolfe Aug 2004 A1
20040236964 Haverinen Nov 2004 A1
20040243517 Hansen Dec 2004 A1
20040257196 Kotzin Dec 2004 A1
20050035200 Hendrick Feb 2005 A1
20050038741 Bonalle Feb 2005 A1
20050048951 Saito Mar 2005 A1
20050077348 Hendrick Apr 2005 A1
20050077349 Bonalle Apr 2005 A1
20050097049 Writer et al. May 2005 A1
20050125686 Brandt Jun 2005 A1
20050133589 Chou Jun 2005 A1
20050154877 Trench Jul 2005 A1
20050162575 Harvie Jul 2005 A1
20050182956 Ginter Aug 2005 A1
20050194438 Ziegler Sep 2005 A1
20050195975 Kawakita Sep 2005 A1
20050198534 Matta Sep 2005 A1
20050209974 Okunseinde Sep 2005 A1
20050226318 Shepherd Oct 2005 A1
20050240528 Hendrick Oct 2005 A1
20050268107 Harris Dec 2005 A1
20060005024 Law Jan 2006 A1
20060005124 Speicher Jan 2006 A1
20060006226 Fitzgerald Jan 2006 A1
20060031096 Buttner Feb 2006 A1
20060054682 de la Huerga Mar 2006 A1
20060074798 Din Apr 2006 A1
20060109844 Bomhoff May 2006 A1
20060121895 Zou Jun 2006 A1
20060136739 Brock Jun 2006 A1
20060149962 Fountain Jul 2006 A1
20060206709 Labrou Sep 2006 A1
20060208066 Finn Sep 2006 A1
20060242693 Kussmaul Oct 2006 A1
20060265648 Rainisto Nov 2006 A1
20060265668 Rainisto Nov 2006 A1
20060282662 Whitcomb Dec 2006 A1
20060288405 Albisu Dec 2006 A1
20070011724 Gonzalez Jan 2007 A1
20070033150 Nwosu Feb 2007 A1
20070038867 Verbauwhede Feb 2007 A1
20070040017 Kozlay Feb 2007 A1
20070042755 Singhal Feb 2007 A1
20070050456 Vuong Mar 2007 A1
20070055439 Denker Mar 2007 A1
20070094512 Nomiya Apr 2007 A1
20070118745 Buer May 2007 A1
20070130504 Betancourt Jun 2007 A1
20070178883 Nandagopal Aug 2007 A1
20070186099 Beck Aug 2007 A1
20070214492 Gopi Sep 2007 A1
20070214493 Davis Sep 2007 A1
20070220275 Heitzeberg Sep 2007 A1
20070226495 Kim Sep 2007 A1
20070242824 Vishik Oct 2007 A1
20070250920 Lindsay Oct 2007 A1
20070257101 Alderucci Nov 2007 A1
20070277032 Relyea Nov 2007 A1
20070284433 Domenica Dec 2007 A1
20070294749 Nice Dec 2007 A1
20070300057 Corcoran Dec 2007 A1
20080005578 Shafir Jan 2008 A1
20080015013 Gelman Jan 2008 A1
20080046520 Jager Feb 2008 A1
20080046723 Weber Feb 2008 A1
20080046984 Bohmer Feb 2008 A1
20080070503 Bang Mar 2008 A1
20080085691 Harvey Apr 2008 A1
20080098464 Mizrah Apr 2008 A1
20080120707 Ramia May 2008 A1
20080141353 Brown Jun 2008 A1
20080144787 Gantman Jun 2008 A1
20080185429 Saville Aug 2008 A1
20080212771 Hauser Sep 2008 A1
20080300020 Nishizawa Dec 2008 A1
20080301460 Miller Dec 2008 A1
20080314977 Domenica Dec 2008 A1
20090025071 Mumm Jan 2009 A1
20090037285 Murphy Feb 2009 A1
20090037340 Hitchen Feb 2009 A1
20090045253 Han Feb 2009 A1
20090055924 Trotter Feb 2009 A1
20090064296 Aikawa Mar 2009 A1
20090065571 Jain Mar 2009 A1
20090069049 Jain Mar 2009 A1
20090069050 Jain Mar 2009 A1
20090069052 Jain Mar 2009 A1
20090070272 Jain Mar 2009 A1
20090070691 Jain Mar 2009 A1
20090073186 Caniglia Mar 2009 A1
20090076962 Hitchen Mar 2009 A1
20090088217 Chung Apr 2009 A1
20090100265 Tadokoro Apr 2009 A1
20090104888 Cox Apr 2009 A1
20090118997 Truitt May 2009 A1
20090126002 Vail May 2009 A1
20090132417 Scipioni May 2009 A1
20090144513 Pierce Jun 2009 A1
20090150989 Hoey Jun 2009 A1
20090190802 Adams Jul 2009 A1
20090200371 Kean Aug 2009 A1
20090205036 Slaton Aug 2009 A1
20090207004 Ziska Aug 2009 A1
20090235339 Mennes Sep 2009 A1
20090249475 Ohaka Oct 2009 A1
20090287921 Zhu Nov 2009 A1
20090300744 Guo Dec 2009 A1
20090305670 DeBoer Dec 2009 A1
20090320118 Muller Dec 2009 A1
20090328165 Cook Dec 2009 A1
20100005386 Verma Jan 2010 A1
20100017334 Itoi Jan 2010 A1
20100030743 Lim Feb 2010 A1
20100034385 Gantman Feb 2010 A1
20100042583 Gervais Feb 2010 A1
20100042846 Trotter Feb 2010 A1
20100091995 Chen Apr 2010 A1
20100125510 Smith May 2010 A1
20100174914 Shafir Jul 2010 A1
20100218249 Wilson Aug 2010 A1
20100223461 Drader Sep 2010 A1
20100241571 McDonald Sep 2010 A1
20100257359 Currie Oct 2010 A1
20100258625 Stanfield Oct 2010 A1
20100293382 Hammad Nov 2010 A1
20100312539 Yamagajo Dec 2010 A1
20100318801 Roberge Dec 2010 A1
20100319064 Warrier Dec 2010 A1
20110047606 Blomquist Feb 2011 A1
20110053560 Jain Mar 2011 A1
20110113477 Miyabayashi May 2011 A1
20110117966 Coppinger May 2011 A1
20110119155 Hammad May 2011 A1
20110154459 Kuang Jun 2011 A1
20110177852 Jain Jul 2011 A1
20110179478 Flick Jul 2011 A1
20110201121 Kaartinen Aug 2011 A1
20110202991 Paquin Aug 2011 A1
20110221568 Giobbi Sep 2011 A1
20110237223 Coppinger Sep 2011 A1
20110237224 Coppinger Sep 2011 A1
20110237296 Coppinger Sep 2011 A1
20110238579 Coppinger Sep 2011 A1
20110238580 Coppinger Sep 2011 A1
20110242286 Pace Oct 2011 A1
20110244920 Coppinger Oct 2011 A1
20110246317 Coppinger Oct 2011 A1
20110289563 Evenden Nov 2011 A1
20110307939 Okashita Dec 2011 A1
20110313547 Hernandez Dec 2011 A1
20110317824 Kim Dec 2011 A1
20120018506 Hammad Jan 2012 A1
20120023207 Gandhewar Jan 2012 A1
20120031969 Hammad Feb 2012 A1
20120089514 Kraemling Apr 2012 A1
20120102324 McNeely Apr 2012 A1
20120133605 Tanaka May 2012 A1
20120136734 Jain May 2012 A1
20120144201 Anantha Jun 2012 A1
20120166338 Agnelli Jun 2012 A1
20120179761 Fuhrmann Jul 2012 A1
20120185692 Hamlin Jul 2012 A1
20120191615 Schibuk Jul 2012 A1
20120198005 DeLuca Aug 2012 A1
20120198491 O'Connell Aug 2012 A1
20120206365 Wangsness Aug 2012 A1
20120210448 Vrancken Aug 2012 A1
20120221998 Rowley Aug 2012 A1
20120226582 Hammad Sep 2012 A1
20120239571 Boot Sep 2012 A1
20120311684 Paulsen Dec 2012 A1
20120321084 Le Saint Dec 2012 A1
20130023241 Lim Jan 2013 A1
20130024577 Krishnaswamy Jan 2013 A1
20130031260 Jones Jan 2013 A1
20130054457 Strickland Feb 2013 A1
20130055356 Gafni Feb 2013 A1
20130090059 Edwards Apr 2013 A1
20130097526 Stovicek Apr 2013 A1
20130110729 Mcalear May 2013 A1
20130117832 Gandhi May 2013 A1
20130124135 Chang May 2013 A1
20130138570 Ross May 2013 A1
20130151629 DeLuca Jun 2013 A1
20130152184 Wang Jun 2013 A1
20130166450 Pama Jun 2013 A1
20130166913 Lenon Jun 2013 A1
20130200999 Spodak Aug 2013 A1
20130205380 Avni Aug 2013 A1
20130246261 Purves Sep 2013 A1
20130263242 Jain Oct 2013 A1
20130275303 Fiore Oct 2013 A1
20130276082 Kuang Oct 2013 A1
20130292479 Jain Nov 2013 A1
20130297933 Fiducia Nov 2013 A1
20130305287 Wong Nov 2013 A1
20130346302 Purves Dec 2013 A1
20140013108 Pellikka Jan 2014 A1
20140013116 Smith Jan 2014 A1
20140020108 John Jan 2014 A1
20140032110 Simring Jan 2014 A1
20140040147 Varadarajan Feb 2014 A1
20140041009 Kousaka Feb 2014 A1
20140045586 Allen Feb 2014 A1
20140052995 Hu Feb 2014 A1
20140053196 Selim Feb 2014 A1
20140062853 Chaudhri Mar 2014 A1
20140074713 Neuwirth Mar 2014 A1
20140101721 Nagase Apr 2014 A1
20140123224 Nosrati May 2014 A1
20140129356 Jain May 2014 A1
20140136309 Goldman May 2014 A1
20140136353 Goldman May 2014 A1
20140149263 Denton May 2014 A1
20140157381 Disraeli Jun 2014 A1
20140161258 Yang Jun 2014 A1
20140164244 Wilson Jun 2014 A1
20140189808 Mahaffey Jul 2014 A1
20140207479 Noland Jul 2014 A1
20140223531 Outwater Aug 2014 A1
20140229387 Chow Aug 2014 A1
20140245389 Oberheide Aug 2014 A1
20140245396 Oberheide Aug 2014 A1
20140257956 Durbha Sep 2014 A1
20140279514 Sharp Sep 2014 A1
20140282885 Mechaley, Jr. Sep 2014 A1
20140282964 Stubblefield Sep 2014 A1
20140282993 Van Till Sep 2014 A1
20140287725 Lee Sep 2014 A1
20140317713 Gadotti Oct 2014 A1
20140331286 Davis Nov 2014 A1
20140351126 Priebatsch Nov 2014 A1
20150019944 Kalgi Jan 2015 A1
20150026049 Theurer Jan 2015 A1
20150040193 Clemons Feb 2015 A1
20150040203 Qian Feb 2015 A1
20150074408 Oberheide Mar 2015 A1
20150074774 Nema Mar 2015 A1
20150081552 Stewart Mar 2015 A1
20150089568 Sprague Mar 2015 A1
20150095999 Toth Apr 2015 A1
20150102899 Kim Apr 2015 A1
20150109428 Mechaley, Jr. Apr 2015 A1
20150113621 Glickfield Apr 2015 A1
20150120471 Cooke Apr 2015 A1
20150142623 Ferguson May 2015 A1
20150150108 Asai May 2015 A1
20150154588 Purves Jun 2015 A1
20150161616 Brunet Jun 2015 A1
20150172292 Kuang Jun 2015 A1
20150186632 Liu Jul 2015 A1
20150200934 Naguib Jul 2015 A1
20150200936 Kim Jul 2015 A1
20150206147 Stanfield Jul 2015 A1
20150207790 Lu Jul 2015 A1
20150208238 Jiang Jul 2015 A1
20150215312 Cesnik Jul 2015 A1
20150215455 Perotti Jul 2015 A1
20150220892 Allen Aug 2015 A1
20150220914 Purves Aug 2015 A1
20150242602 Skygebjerg Aug 2015 A1
20150242852 Goldstone Aug 2015 A1
20150254661 Lanc Sep 2015 A1
20150257010 Salonen Sep 2015 A1
20150269369 Hamid Sep 2015 A1
20150271164 Hamid Sep 2015 A1
20150271200 Brady Sep 2015 A1
20150281225 Schoen Oct 2015 A1
20150288668 Kupper Oct 2015 A1
20150312251 Genestier Oct 2015 A1
20150326559 Kuang Nov 2015 A1
20150326565 Kuang Nov 2015 A1
20150356316 Thompson Dec 2015 A1
20150356560 Shastry et al. Dec 2015 A1
20150365283 Ronca Dec 2015 A1
20150379888 Hill Dec 2015 A1
20160012430 Chandrasekaran Jan 2016 A1
20160012441 Goldberg Jan 2016 A1
20160019543 Taylor, III Jan 2016 A1
20160019547 Gurnani Jan 2016 A1
20160021691 Lee Jan 2016 A1
20160026996 Jain Jan 2016 A1
20160036790 Shastry Feb 2016 A1
20160036803 Li Feb 2016 A1
20160036805 Lin Feb 2016 A1
20160044033 Hsiang Feb 2016 A1
20160048705 Yang Feb 2016 A1
20160048846 Douglas Feb 2016 A1
20160057125 Li Feb 2016 A1
20160080157 Lundström Mar 2016 A1
20160080364 Karimzadeh Mar 2016 A1
20160094525 Lin Mar 2016 A1
20160104161 Butler Apr 2016 A1
20160112778 Wang Apr 2016 A1
20160112870 Pathuri Apr 2016 A1
20160125180 Smith May 2016 A1
20160142398 Lin May 2016 A1
20160142439 Goutal May 2016 A1
20160142894 Papakonstantinou May 2016 A1
20160147990 Schneider May 2016 A1
20160149870 Chou May 2016 A1
20160173483 Wong Jun 2016 A1
20160180136 Meier Jun 2016 A1
20160189127 Amarnath Jun 2016 A1
20160191514 Talmor Jun 2016 A1
20160191540 Fuka Jun 2016 A1
20160198223 Maluk Jul 2016 A1
20160205098 Han Jul 2016 A1
20160219034 Hintermeister Jul 2016 A1
20160232381 Ju Aug 2016 A1
20160239657 Loughlin-Mchugh Aug 2016 A1
20160260098 Landrock Sep 2016 A1
20160261585 Ito Sep 2016 A1
20160267486 Mitra Sep 2016 A1
20160267493 Liu Sep 2016 A1
20160269379 Livesay Sep 2016 A1
20160269415 Dykeman Sep 2016 A1
20160269908 Richards Sep 2016 A1
20160277930 Li Sep 2016 A1
20160283839 Ye Sep 2016 A1
20160286396 Tuukkanen Sep 2016 A1
20160300224 Liu Oct 2016 A1
20160307179 Zou Oct 2016 A1
20160337334 Murr Nov 2016 A1
20160344728 Jeon Nov 2016 A1
20160364716 Bakshi Dec 2016 A1
20160371736 Turner Dec 2016 A1
20160379220 Tunnell Dec 2016 A1
20170006471 Kim Jan 2017 A1
20170019396 Bettenburg Jan 2017 A1
20170019400 Drolshagen Jan 2017 A1
20170024728 Bull Jan 2017 A1
20170024729 Huxham Jan 2017 A1
20170039566 Schipperheijn Feb 2017 A1
20170041296 Ford Feb 2017 A1
20170053286 Bhagat Feb 2017 A1
20170054561 Schleiff Feb 2017 A1
20170063848 Collinge Mar 2017 A1
20170070484 Kruse Mar 2017 A1
20170075894 Poornachandran Mar 2017 A1
20170078270 Tang Mar 2017 A1
20170078322 Seiver Mar 2017 A1
20170085561 Han Mar 2017 A1
20170085568 Rolfe Mar 2017 A1
20170086041 Bao Mar 2017 A1
20170086069 Liu Mar 2017 A1
20170086070 Henderson Mar 2017 A1
20170109752 Hubbard Apr 2017 A1
20170132200 Noland May 2017 A1
20170142589 Park May 2017 A1
20170148009 Perez Lafuente May 2017 A1
20170169427 Sikljovan et al. Jun 2017 A1
20170171216 Chhabra Jun 2017 A1
20170177808 Irwin Jun 2017 A1
20170177809 Bull Jun 2017 A1
20170178093 Bull Jun 2017 A1
20170178135 Bull Jun 2017 A1
20170178245 Rodkey Jun 2017 A1
20170186012 McNeal Jun 2017 A1
20170187701 Bonnell Jun 2017 A1
20170199713 Clark Jul 2017 A1
20170228405 Ward Aug 2017 A1
20170228738 Beenau et al. Aug 2017 A1
20170243219 Wong et al. Aug 2017 A1
20170244730 Sancheti Aug 2017 A1
20170250816 Popa Aug 2017 A1
20170250938 Dahl Aug 2017 A1
20170272418 Kim Sep 2017 A1
20170279798 Reynolds Sep 2017 A1
20170286711 Negrea Oct 2017 A1
20170286768 Livesay Oct 2017 A1
20170289127 Hendrick Oct 2017 A1
20170289168 Bar Oct 2017 A1
20170289181 Wang Oct 2017 A1
20170295155 Wong Oct 2017 A1
20170295175 Guo Oct 2017 A1
20170308906 McCauley Oct 2017 A1
20170316493 Numata Nov 2017 A1
20170318001 Eggers Nov 2017 A1
20170323354 Martell Nov 2017 A1
20170324750 Khan Nov 2017 A1
20170330165 Banerjee Nov 2017 A1
20170346802 Gruskin Nov 2017 A1
20170346815 Andrews Nov 2017 A1
20170346851 Drake Nov 2017 A1
20170359339 Hevizi Dec 2017 A1
20170359342 Magyar Dec 2017 A1
20170359723 Pal Dec 2017 A1
20170366530 Dominguez et al. Dec 2017 A1
20170372056 Narasimhan Dec 2017 A1
20170372310 Narasimhan Dec 2017 A1
20180025442 Isaacson Jan 2018 A1
20180026968 Canavor Jan 2018 A1
20180028905 Shoemaker, Jr. Feb 2018 A1
20180032712 Oh Feb 2018 A1
20180032750 Hammel Feb 2018 A1
20180032759 Radocchia Feb 2018 A1
20180034822 Mistry Feb 2018 A1
20180041479 Wang Feb 2018 A1
20180053160 Schwartz Feb 2018 A1
20180060867 Hagan Mar 2018 A1
20180068105 Shapiro Mar 2018 A1
20180068290 Xia Mar 2018 A1
20180069704 Dray, Jr. Mar 2018 A1
20180075452 Weller et al. Mar 2018 A1
20180077133 Matute Mar 2018 A1
20180082304 Summerlin Mar 2018 A1
20180091498 Kekicheff Mar 2018 A1
20180103019 Chen Apr 2018 A1
20180103341 Moiyallah, Jr. Apr 2018 A1
20180109378 Fu Apr 2018 A1
20180121683 Goldberg May 2018 A1
20180122256 Smith May 2018 A1
20180123804 Smith May 2018 A1
20180124047 Fisher May 2018 A1
20180143958 Kakkad May 2018 A1
20180145827 Pitel May 2018 A1
20180146363 Liu May 2018 A1
20180150836 Kumar May 2018 A1
20180158057 Kirch Jun 2018 A1
20180158061 Edelstein Jun 2018 A1
20180159839 Citron Jun 2018 A1
20180167386 Bhatt Jun 2018 A1
20180173871 Toth Jun 2018 A1
20180176212 Nair Jun 2018 A1
20180181958 Locke Jun 2018 A1
20180189788 Lacoss-Arnold Jul 2018 A1
20180191695 Lindemann Jul 2018 A1
20180198621 Senyuk Jul 2018 A1
20180198781 Bhogal Jul 2018 A1
20180205557 Sun Jul 2018 A1
20180205725 Cronkright Jul 2018 A1
20180211258 Buis Jul 2018 A1
20180212957 Lee Jul 2018 A1
20180219917 Chiang Aug 2018 A1
20180234420 Mattes Aug 2018 A1
20180240107 Andrade Aug 2018 A1
20180255460 Hammad et al. Sep 2018 A1
20180288060 Jackson Oct 2018 A1
20180308086 Shan Oct 2018 A1
20180308095 Hammad Oct 2018 A1
20180316665 Caldera Nov 2018 A1
20180322501 Eisen Nov 2018 A1
20180322571 Vea Nov 2018 A1
20180331837 Uhr Nov 2018 A1
20180332033 Lakhani Nov 2018 A1
20180332065 Gupta Nov 2018 A1
20180349880 Steele Dec 2018 A1
20180349881 Steele Dec 2018 A1
20180351949 Scott Dec 2018 A1
20180359227 Trantham Dec 2018 A1
20180359811 Verzun Dec 2018 A1
20180373849 Gidley Dec 2018 A1
20180375864 Kano Dec 2018 A1
20190005491 Grassadonia Jan 2019 A1
20190007397 Goldberg Jan 2019 A1
20190014108 Rothschild Jan 2019 A1
20190020476 Kats Jan 2019 A1
20190026234 Harnik Jan 2019 A1
20190026577 Hall Jan 2019 A1
20190026579 Hall Jan 2019 A1
20190034929 Tang Jan 2019 A1
20190036906 Biyani Jan 2019 A1
20190036913 Tzur-David Jan 2019 A1
20190036914 Tzur-David Jan 2019 A1
20190042719 Miu Feb 2019 A1
20190052629 Manepalli Feb 2019 A1
20190068587 Zhao Feb 2019 A1
20190068608 Boland Feb 2019 A1
20190075094 Clarke Mar 2019 A1
20190075101 Wang Mar 2019 A1
20190080326 Trivedi Mar 2019 A1
20190089538 Park Mar 2019 A1
20190102778 Lebovic Apr 2019 A1
20190104121 Khandani Apr 2019 A1
20190116051 Rome Apr 2019 A1
20190122213 Chen Apr 2019 A1
20190124066 Peddada Apr 2019 A1
20190130386 Bhat May 2019 A1
20190132304 Overby May 2019 A1
20190139024 Bakshi May 2019 A1
20190140844 Brown May 2019 A1
20190149540 Shimazu May 2019 A1
20190158496 Hallock May 2019 A1
20190158655 DeLuca May 2019 A1
20190163931 Wolverton May 2019 A1
20190166128 Kurian May 2019 A1
20190182044 Mullen Jun 2019 A1
20190190907 Panus Jun 2019 A1
20190197815 Kamal Jun 2019 A1
20190199755 Larionov Jun 2019 A1
20190231160 Lu Aug 2019 A1
20190236559 Padmanabhan Aug 2019 A1
20190236562 Padmanabhan Aug 2019 A1
20190236598 Padmanabhan Aug 2019 A1
20190236606 Padmanabhan Aug 2019 A1
20190236866 Leonard Aug 2019 A1
20190238316 Padmanabhan Aug 2019 A1
20190238525 Padmanabhan Aug 2019 A1
20190253413 Wang Aug 2019 A1
20190253434 Biyani Aug 2019 A1
20190270118 Araujo-Simon Sep 2019 A1
20190281048 Dong Sep 2019 A1
20190289008 Serban Sep 2019 A1
20190295054 Purves Sep 2019 A1
20190303915 Hammad Oct 2019 A1
20190303929 Brown Oct 2019 A1
20190304336 DeLand Oct 2019 A1
20190311145 Baskaran Oct 2019 A1
20190318122 Hockey Oct 2019 A1
20190318361 Hurst Oct 2019 A1
20190327245 Holton Oct 2019 A1
20190332691 Beadles Oct 2019 A1
20190333048 DiCross Oct 2019 A1
20190333054 Cona Oct 2019 A1
20190340610 Song et al. Nov 2019 A1
20190347669 Satpute Nov 2019 A1
20190354720 Tucker Nov 2019 A1
20190357050 Kennedy-Foster Nov 2019 A1
20190370804 Perry Dec 2019 A1
20190385396 Jothipandian Dec 2019 A1
20190386826 Kato Dec 2019 A1
20190386984 Thakkar Dec 2019 A1
20190394189 Thirumalai Dec 2019 A1
20200013250 Jakubek Jan 2020 A1
20200051675 Nelson Feb 2020 A1
20200055243 Zhou Feb 2020 A1
20200058002 Patanaik Feb 2020 A1
20200058021 Mittal Feb 2020 A1
20200068389 Rothkopf Feb 2020 A1
20200068399 Brown Feb 2020 A1
20200076813 Felice-Steele Mar 2020 A1
20200082396 Chow Mar 2020 A1
20200082401 Arora Mar 2020 A1
20200089700 Ericson Mar 2020 A1
20200089760 Ericson Mar 2020 A1
20200090168 Mossler Mar 2020 A1
20200092282 Childress Mar 2020 A1
20200092283 Parkinson Mar 2020 A1
20200092284 Zhu Mar 2020 A1
20200097971 Church Mar 2020 A1
20200106608 Lo Apr 2020 A1
20200111091 Ellingson Apr 2020 A1
20200122931 Chen Apr 2020 A1
20200127858 Stöhr Apr 2020 A1
20200134600 Koeppel Apr 2020 A1
20200137038 Endler Apr 2020 A1
20200137096 Endler Apr 2020 A1
20200137109 Endler Apr 2020 A1
20200145220 Chang May 2020 A1
20200167793 Muralidharan May 2020 A1
20200167862 Manepalli May 2020 A1
20200169568 Kurian May 2020 A1
20200195636 Landrock Jun 2020 A1
20200201443 Huang Jun 2020 A1
20200213119 Schat Jul 2020 A1
20200213293 Zhou Jul 2020 A1
20200213298 Ericson Jul 2020 A1
20200213310 Ju Jul 2020 A1
20200220862 Chan Jul 2020 A1
20200234283 Greiche Jul 2020 A1
20200244656 Manepalli Jul 2020 A1
20200245142 Manepalli Jul 2020 A1
20200250413 Lu Aug 2020 A1
20200250651 Lee Aug 2020 A1
20200250666 Carri Aug 2020 A1
20200259827 Shaffer Aug 2020 A1
20200259828 Shaffer Aug 2020 A1
20200259829 Shaffer Aug 2020 A1
20200259830 Shaffer Aug 2020 A1
20200267283 Tong Aug 2020 A1
20200279255 Douglas Sep 2020 A1
20200296082 Killoran, Jr. Sep 2020 A1
20200296585 Bolotin Sep 2020 A1
20200304310 Rule Sep 2020 A1
20200313881 Feng Oct 2020 A1
20200320292 Chawda Oct 2020 A1
20200327513 Salama et al. Oct 2020 A1
20200328880 Bolotin Oct 2020 A1
20200336597 Haltom Oct 2020 A1
20200342088 Jorgensen Oct 2020 A1
20200342394 Moore Oct 2020 A1
20200342445 Yoo Oct 2020 A1
20200344058 Wang Oct 2020 A1
20200344224 Hochman Oct 2020 A1
20200366665 Vasudevan Nov 2020 A1
20200366704 Vasudevan Nov 2020 A1
20200374286 Agarwal Nov 2020 A1
20200374287 Bowie Nov 2020 A1
20200380426 Schlank Dec 2020 A1
20200389450 Levitt Dec 2020 A1
20200402052 Sloane Dec 2020 A1
20200403992 Huffman Dec 2020 A1
20210004454 Chester Jan 2021 A1
20210004803 Rule Jan 2021 A1
20210014229 Beveridge Jan 2021 A1
20210027295 Raquepaw Jan 2021 A1
20210029107 Parkinson Jan 2021 A1
20210036859 Sukhomlinov Feb 2021 A1
20210042764 Rungta Feb 2021 A1
20210051159 Kesanupalli Feb 2021 A1
20210058392 Leddy, III Feb 2021 A1
20210064780 Riedel Mar 2021 A1
20210067201 Wang Mar 2021 A1
20210073365 Boussard Mar 2021 A1
20210081937 Yaqub Mar 2021 A1
20210084024 Sadayoshi Mar 2021 A1
20210090068 Merino Gonzalez Mar 2021 A1
20210105267 Brown Apr 2021 A1
20210112098 Lillie Apr 2021 A1
20210117524 McKell-Redwood Apr 2021 A1
20210120003 Rothschild Apr 2021 A1
20210126904 Kakugwa Apr 2021 A1
20210133736 Kavanagh May 2021 A1
20210141888 Hires May 2021 A1
20210146883 Ha May 2021 A1
20210168455 Campbell Jun 2021 A1
20210176234 Silverstein Jun 2021 A1
20210192039 Pihur Jun 2021 A1
20210192508 Edwards Jun 2021 A1
20210194703 Queralt Jun 2021 A1
20210208952 Jain Jul 2021 A1
20210216612 Wojcik Jul 2021 A1
20210233078 Vittimberga Jul 2021 A1
20210250765 Vargas Aug 2021 A1
20210256500 Kuchenski Aug 2021 A1
20210271766 Yoho Sep 2021 A1
20210281559 Valecha Sep 2021 A1
20210297411 Keselman Sep 2021 A1
20210303630 Atkinson Sep 2021 A1
20210314282 Sharma Oct 2021 A1
20210320922 Furhmann Oct 2021 A1
20210326432 Kaidi Oct 2021 A1
20210336962 Mulampaka Oct 2021 A1
20210357897 Phillips Nov 2021 A1
20210374709 Suresh Dec 2021 A1
20210383387 Ratica Dec 2021 A1
20210385183 Henao Mota Dec 2021 A1
20210385216 Khalil Dec 2021 A1
20210398141 Benkreira Dec 2021 A1
20210398145 Hare Dec 2021 A1
20210406861 Edmiston Dec 2021 A1
20220003040 Capitaine Jan 2022 A1
20220006812 Rodriguez Bravo Jan 2022 A1
20220009039 Korematsu Jan 2022 A1
20220021706 Jubilee Jan 2022 A1
20220027887 Palanisamy Jan 2022 A1
20220050890 Karantzis Feb 2022 A1
20220052997 Kim Feb 2022 A1
20220060471 Wilson Feb 2022 A1
20220076258 Tax Mar 2022 A1
20220086131 Kinai Mar 2022 A1
20220092604 Kwatra Mar 2022 A1
20220092928 Piazza Mar 2022 A1
20220108314 Mehta Apr 2022 A1
20220109986 Jogand-Coulomb Apr 2022 A1
20220129872 Guggarigoudar Apr 2022 A1
20220129900 Naujok Apr 2022 A1
20220174043 Mihatsch Jun 2022 A1
20220198394 Chandra Jun 2022 A1
20220311617 Lundberg Sep 2022 A1
20220343319 Murao Oct 2022 A1
20220405357 King Dec 2022 A1
20230009385 Naccache Jan 2023 A1
20230020193 Williams Jan 2023 A1
20230032549 Ciarniello Feb 2023 A1
20230035507 Mohammed Feb 2023 A1
20230043031 Watanabe Feb 2023 A1
Non-Patent Literature Citations (7)
Entry
Ren et al “Potential Identity Resolution Systems for the Industrial Internet of Things: A Survey,” IEEE Communications Surveys & Tutorials, vol. 23, No. 1, First Quarter, pp. 391-430 (Year: 2020).
Carretero et al “Federated Identity Architecture of the European eID System,” IEEE Access, pp. 75302-75326, (Year: 2018).
Sood et al “An Empirical Study of HTTP-based Financial Botnets,” IEEE Transactions on Dependable and Secure Computing, vol. 13, No. 2, Mar./Apr. 2016, pp. 236-251 (Year: 2016).
Krawiecka et al “SafeKeeper: Protecting Web Passwords using Trusted Execution Environments,” Track: Security and Privacy on the Web, Apr. 23-27, 2018, Lyon, France, pp. 349-358 (Year: 2018).
Hsu et al “An Online Fraud-Resistant Technology for Credit Card E-Transactions,” IEEE, pp. 1-4 (Year: 2007).
Guo et al “Aggregated Privacy-Preserving Identity Verification for Composite Web Services,” 2011 IEEE International Conference on Web Services, IEEE Computer Society, pp. 692-693 (Year: 2011).
Copeland et al Independently Verifiable Identity Scheme (IVIS), IEEE, pp. 196-198 (Year: 2017).
Related Publications (1)
Number Date Country
20220217136 A1 Jul 2022 US