Patent Grant
11915243
Conventional tokenization processes could be improved. While typical tokenization processes can utilize tokens to hide sensitive information of user during transaction, they can have vulnerabilities. For example, a token may be transmitted to several entities involved in a transaction process allowing the token to be stolen at any point during the transaction (e.g., intercepted by a man-in-the-middle), and in their final form. Upon retrieving the token, a malicious party can carry out a fraudulent transaction. In some cases, a token can be dynamically generated at the time of a transaction to reduce risk. However, such dynamic tokens are still at risk of being stolen.
Additionally, conventional payment tokenization processes could be more efficient. For example, a user conducting a transaction may still need to present a payment device (e.g., payment card, etc.) during a transaction. This can be cumbersome as the user has to take out their payment device and conduct extra actions (e.g., swipe, dip, touch, etc.) during the transaction. Further, the user may be required to provide manual input, such as a physical signature, for verification during the transaction. These extra steps can be time-consuming and inefficient. Thus, the use of tokens in typical payment tokenization processes does not provide sufficient security and efficiency.
Embodiments of the invention address these and other problems, individually and collectively.
Embodiments of the invention are related to systems and methods for enabling tokenization processes that increase security and efficiency of transactions. Embodiments of the invention enable transactions that reduce the vulnerability of tokens to being stolen and utilized by a fraudulent party. In embodiments of the invention, several pieces of information that may be utilized to generate a token can be distributed to multiple entities, such that no single entity stores all information utilized to generate the token. This mitigates the risk of a whole token being intercepted by an intermediary, which reduces the risk of fraudulent transactions. Additionally, these transactions can be conducted without the use of a payment device. Thus, embodiments of the invention enable transactions that have increased security and efficiency.
One embodiment of the invention is a method. The method may comprise generating a request message comprising identification data of the user. The method may further comprise transmitting the request message comprising the identification data to a plurality of remote server computers including an authorization computer. The server computers may respectively comprise validation keys that are used to form at least part of a validation identity token. The method may also comprise receiving a response message comprising the validation keys from the authorization computer and generating the validation identity token using at least the validation keys. In some cases, the validation identity token is formed using the validation keys and a validation identity token precursor.
Further, the method may comprise authenticating the user based upon the generated validation identity token. In some embodiments, authenticating may comprise comparing the generated validation identity token with another validation identity token previously provided by the user, determining a value associated with the difference between the generated validation identity token and the validation identity token previously provided by the user, and determining that the value is within a threshold.
In some embodiments, the identification data may be of different forms. For example, in some cases, the identification data may comprise the validation identity token precursor. In some cases, the identification data may comprise biometric data. In some cases, the identification data may comprise an account identifier. In some embodiments, the validation keys are chromatic keys and the validation identity token is a chromatic identity token. In some cases, the validation identity token precursor is a chromatic identity token precursor.
Another embodiment of the invention is an access device. The access device may comprise a process and a computer-readable medium coupled to the processor, the computer-readable medium comprising code, executable by the processor, for performing the above-described method.
Another embodiment of the invention is a method. The method may comprise receiving a request message comprising identification data of a user and retrieving a validation key, wherein the validation key is used to form at least part of a validation identity token. The method may further comprise including the validation key in the request message and sending the request message to one or more remote server computers including an authorization computer. The one or more remote server computers may respectively comprise validation keys that are used to form at least part of the validation identity token. The method may further comprise receiving a response message including the validation keys in the request message and sending the response message to an access device, wherein the user is authenticated based upon the validation identity token.
Another embodiment of the invention is a server computer. The server computer may comprise a processor and a computer-readable medium coupled to the processor, the computer-readable medium comprising code, executable by the processor, for performing the above described method.
These and other embodiments of the invention are described in further detail below.
Embodiments of the invention are related to systems and methods for enabling tokenization processes that mitigate the risk of tokens being compromised. Certain elements utilized to generate a token may be dispersed to multiple entities (e.g., remote server computers) such that no single entity stores all the elements utilized to generate the token. Each distributed element may be used to form at least part of the token. Upon collection of all the distributed elements, the token be completed and utilized to authenticate a user conducting a transaction.
Conventional systems include tokenization processes that are vulnerable to fraud. For example, conventional systems may transmit a token to multiple entities involved in the transaction process. This presents the risk the token be stolen by an intermediary at any point during the transaction.
Embodiments of the invention provide direct benefits, such as increased security and transaction efficiency. Forgoing transmission of a whole token during a transaction can reduce risk of fraud, since it cannot be obtained by a man-in-the-middle. In embodiments of the invention, information that may be utilized to generate the token may be distributed to several entities. Consequently, the risk of that the entire token will be stolen by an intermediary is reduced. Additionally, some embodiments of the invention enable conducting transactions that are convenient and simple, such as by not requiring a device (e.g., payment device) and physical signature to be provided by a user. Thus, typical cumbersome processes associated with conducting transactions may be eliminated without compromising security of the transactions.
Prior to discussing embodiments of the invention, description of some terms may be helpful in understanding embodiments of the invention.
“Identification data” may be any information that can be utilized to identify a user. Some examples of identification data may include biometric information. The biometric information may be in any suitable form, such as facial images, facial recognition data (e.g., digital 3D models, topographic maps, etc.), iris scans, voice prints, voice samples, fingerprint data, and other information. Other examples of identification data may include a name, a driver's license number, a birth date, an account number (e.g., personal account number (PAN)), a card verification value (CVV), an account number expiration date, and other information associated with the user. In some embodiments, identification data may comprise a validation identity token precursor.
A “validation identity token” may be data that indicates that an entity is authentic and valid. In some embodiments, the validation identity token may comprise digital data that may be used to validate a transaction. A validation identity token may be in any suitable form including a numerical value, a color, an image, a picture, etc. In some embodiments, the validation identity token may be generated using at least a plurality of validation keys. In some embodiments, the validation identity token may be generated using the plurality of validation keys and a validation identity token precursor.
A “validation identity token precursor” may be data that can be used to create a validation entity token. The validation identity token precursor may be unique to a user and may be utilized to identify the user. In some cases, the validation identity token precursor may be generated using identification data associated with the user. In an exemplary case, the validation identity token precursor may be a trigonometric identity value generated based on a facial image of the user.
A “validation key” may include data which, in combination with a validation identity token precursor or other validation keys, may form a validation identity token. In some cases, the validation key may be a numerical value. The validation key may be of a different value that the validation identity token precursor and may be stored at a remote server computer. In some implementations, the validation key may be generated based on a portion of identification data associated with a user. In an exemplary case, a validation key may be generated based on a certain portion of a facial image of the user. For example, the validation key may be digital image data corresponding to the portion of the image, a numerical representation of a physical position on the face in the portion of the image, or a numerical representation of a combination (e.g., summation, average, etc.) of multiple physical positions on the face in the portion of the image.
A “chromatic identity token” may be a validation identity token that can be represented by color. The chromatic identity token may be associated with a color indicating whether a user may be authenticated for a transaction. In some embodiments, the chromatic identity token may be a numerical value associated with a color, such as a 24-bit color representation in the RGB color space (e.g., hexadecimal value #00FF00). However, any suitable representation may be utilized. The chromatic identity token may be generated utilizing at least chromatic keys. In some cases, the chromatic identity token may be generated also utilizing a chromatic identity token precursor.
A “chromatic identity token precursor” may be a validation identity token precursor that can be represented by a color. In some embodiments, the chromatic identity token precursor may be a numerical value associated with a color, such as a 24-bit color representation in the RGB color space. However, any suitable representation may be utilized. The chromatic identity token precursor may be unique to a user and in some cases, may be utilized to identity a user. The chromatic identity token precursor may be generated based on identification data of a user. In an exemplary case, the chromatic identify token precursor may be a numerical value associated with a color mapped from a trigonometric identity value generated based on a facial image of the user.
A “chromatic key” may be a validation key that can be represented by a color. In some embodiments, the chromatic key may be numerical value associated with a color, such as a 24-bit color representation in the RGB color space. However, any suitable representation may be utilized. The validation key may be of a different value that of the chromatic identity token precursor and may be stored at a remote server computer. The chromatic key may be generated based on identification data of a user.
An “account identifier” may be any information that may be associated with a user's account. In some embodiments, the account identifier may be a personal account number (PAN), an email address, a name, a driver's license number, or other identifier. The account identifier may be any suitable identifier that may be associated with the user and may be utilized to identity an account of the user.
A “request message” may be any suitable message that includes information associated with a request. In some embodiments, the request message may be sent during a transaction from an access device and may include a request to authenticate a user for a transaction and/or may seek approval for a transaction. In the latter case, a “request message” may be an “authorization request message.” In some cases, the request message may comprise identification data of the user. In some embodiments, the request message may also include instructions to server computers that handle the request message to retrieve validation keys. The request message may or may not include a validation identity token precursor.
A “server computer” may typically be a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. A server computer may be associated with an entity such as a processing network, a resource provider computer, a transport computer, or an authorization computer.
An “authorization request message” may be an electronic message that requests authorization. For example, the authorization request message may be sent to a processing network (e.g., payment processing network) and/or an authorization computer (e.g., issuer) of a payment card to request authorization for a transaction. An authorization request message according to some embodiments may comply with (International Organization of Standardization) ISO 8583, which is a standard for systems that exchange electronic transaction information associated with a payment made by a user using a payment device or payment account. The authorization request message may include an issuer account identifier that may be associated with a payment device or payment account. An authorization request message may also comprise additional data elements corresponding to “identification information” including, by way of example only: a service code, a CVV (card verification value), a dCVV (dynamic card verification value), an expiration date, and the like. An authorization request message may also comprise “transaction information,” such as any information associated with a current transaction, such as the transaction amount, merchant identifier, merchant location, etc., as well as any other information that may be utilized in determining whether to identify and/or authorize a transaction.
An “authorization response message” may be an electronic message reply that indicates authorization status. For example, the authorization response message may be a reply to an authorization request message generated by an issuing financial institution or a processing network (e.g., payment processing network). The authorization response message may include, by way of example only, one or more of the following status indicators: Approval—transaction was approved; Decline—transaction was not approved; or Call Center—response pending more information, merchant must call the toll-free authorization phone number. The authorization response message may also include an authorization code, which may be a code that a credit card issuing bank returns in response to an authorization request message in an electronic message (either directly or through the processing network) to the access device (e.g. POS equipment), associated with a resource provider computer (e.g., merchant) that indicates approval of the transaction. The code may serve as proof of authorization. As noted above, in some embodiments, a processing network may generate or forward the authorization response message to the resource provider computer (e.g., merchant computer).
A “resource providing entity” may be an entity that may make resources available to a user. A resource providing entity may also be known as a resource provider. Examples of resource providing entities include merchants, vendors, suppliers, owners, traders, and the like. In some embodiments, such entities may be a single individual, small groups of individuals, or larger groups of individuals (e.g., companies). Resource providing entities may be associated with one or more physical locations (e.g., supermarkets, malls, stores, buildings, etc.) and online platforms (e.g., e-commerce websites, online companies, etc.). At the physical locations, the resource providing entity may host an access device for conducting transactions with a user's payment device. In some embodiments, resource providing entities may make available physical items (e.g., goods, products, etc.) to the user. In other embodiments, resource providing entities may make available digital resources (e.g., electronic documents, electronic files, etc.) or services to the user. In other embodiments, resource providing entities may manage access to certain resources by the user.
An “acquirer” may typically be a business entity (e.g., a commercial bank) that has a business relationship with a particular merchant or other entity. Some entities can perform both issuer and acquirer functions. Some embodiments may encompass such single entity issuer-acquirers. The acquirer may operate an acquirer computer, which can also be generically referred to as a “transport computer.”
A “payment processing network” may include data processing subsystems, networks, and operations used to support and deliver authorization services, and clearing and settlement services. For example, the payment processing network may comprise a server computer, coupled to a network interface, and a database of information. The payment processing network may include wired or wireless network, including the internet. An exemplary payment processing network includes VisaNet®, operated by Visa®. Payment processing networks such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, includes a VIP system (Visa Integrated Payments system), which processes authorization requests and a Base II system which performs clearing and settlement services. The payment processing network may also be generically referred to as a “processing network.”
An “authorizing entity” may be an entity that authorizes a request. Examples of an authorizing entity may be an issuer, a governmental agency, a document repository, an access administrator, etc. An authorizing entity may be associated with an authorization computer.
An “issuer” may typically refer to a business entity (e.g., a bank) that maintains an account for a user. An issuer may also issue payment (credit/debit) card, account numbers or payment tokens stored on a user device, such as a cellular telephone, smart card, tablet, or laptop to the user. Some issuer systems can perform both issuer computer and acquirer computer functions. When a transaction involves a payment account associated with the issuer, the issuer may verify the account and respond with an authorization response message to the acquirer that may be forwarded to the corresponding access device, if applicable.
A “computing device” may be any suitable electronic device that can process and communicate information to other electronic devices. The computing device may include a processor and a computer readable medium coupled to the processor, the computer readable medium comprising code, executable by the processor. The computing device may also each include an external communication interface for communicating with each other and other entities. A mobile device, a cardholder device, a user device, a consumer device, a server computing device, and any computer may be exemplary types of computing devices.
Embodiments of the invention provide several advantages over conventional systems and methods for performing tokenization processes for transactions. A prior system is shown in
A transaction may be conducted between client computer 101 and remote authentication computer 103. Upon receiving a transaction request message from client computer 101, remote authentication computer 103 may initiate an authentication process to verify a user associated with client computer 101. In some cases, the transaction request message may include an authentication token. Remote authentication computer 103 may communicate with authentication database 104 to retrieve authentication information associated with the authentication token. Remote authentication computer 103 may then verify the user based on the authentication information and then complete the transaction.
While the typical system shown in
In contrast, embodiments of the invention reduce the risk of the token being utilized for fraud. This is because portions of a token are dispersed to multiple entities and collected during a transaction, rather than transmitting the whole token multiple times. This mitigates the risk that the token can be stolen by an intermediary and increases security of the transaction compared to conventional systems and methods.
Access device 204 may be any suitable device that provides access to a remote system. Access device 204 may be in any suitable form. Some non-limiting examples of access device 204 may include POS or point of sale devices (e.g., POS terminals), cellular phones, PDAs, personal computers (PCs), tablet PCs, hand-held specialized readers, set-top boxes, electronic cash registers (ECRs), automated teller machines (ATMs), virtual cash registers (VCRs), kiosks, security systems, access systems, and the like. Access device 204 may use any suitable contact or contactless mode of operation to send or receive data from, or associated with a user device (e.g., payment device) associated with user 202. In some embodiments, access device 204 may be a client computer associated with resource provider computer 206.
Access device 204 may also be used for communicating with other systems. For example, access device 204 may communicate with resource provider computer 206, transport computer 208, a processing network 210, authorization computer 212, or any other suitable system. Access device 204 may generally be located in any suitable location, such as at the location of the resource providing entity associated with resource provider computer 206. In some embodiments, access device 204 may receive data from a user device for a remote transaction (e.g., e-commerce transaction) and may forward the received data to an appropriate entity.
Access device 204 may enable interaction with user 202, such as receive identification data (e.g., biometric data) from user 202. Access device 204 may comprise a data capture device 250, a display 251, and an identification algorithm module 252. Similar components of access device 204 may be described in more detail in
Resource provider computer 206 may be a device that is associated with a resource providing entity. The resource providing entity may engage in transactions, sell goods or services, or provide access to goods or services to user 202. Resource provider computer 206 may accept multiple forms of payment and may be associated with multiple tools to conduct different types of transactions. For example, resource provider computer 206 may be associated with access device 204 and communicate information to and from access device 204. In some cases, resource provider computer 206 may host a website associated with the resource providing entity through which the user may conduct an enrollment process or make a transaction. In some embodiments, resource provider computer 206 may store a validation identity token precursor 215 or a validation identity token 220.
Transport computer 208 may be a device that may transmit information between entities. Transport computer 208 may be associated with resource provider computer 206, and may manage authorization requests on behalf of resource provider computer 206. Transport computer 208 may also handle token request messages on behalf of the resource provider computer 208. For example, in some embodiments, transport computer 208 may receive and forward token request messages in the same manner as authorization request messages. In some cases, transport computer 208 may be an acquirer computer associated with an acquirer. In some embodiments, transport computer 208 may store a plurality of validation keys, including a validation key 225.
Processing network 210 may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. For example, processing network 210 may comprise a server coupled to a network interface (e.g., by an external communication interface), and databases of information. In some cases, processing network 210 may be a transaction processing network (e.g., payment processing network). Processing network 210 may use any suitable wired or wireless network, including the Internet. In some embodiments, processing network 210 may store a plurality of validation keys, including a validation key 235.
Authorization computer 212 may be a device associated with an authorizing entity. Authorization computer 212 may authorize an entity to conduct a transaction or to receive access to goods or services on behalf of the authorizing entity. Authorization computer 212 may receive and process an authorization request message, as well as generate and transmit an authorization response message. In some cases, authorization computer 212 may be an issuer computer. In some embodiments, authorization computer 212 may store a plurality of validation keys, including a validation key 245.
In some cases, at a later time (e.g., at the end of the day), a clearing and settlement process can occur between transport computer 208, processing network 210, and authorization computer 212.
Communications network 260 may be any suitable network. Suitable communications networks may be any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like.
Messages between the computers, networks, and devices described herein may be transmitted using a secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), ISO (e.g., ISO 8583) and/or the like.
Processor 301 may include hardware for processing functions of access device 300. Processor 301 may include hardware within access device 300 that carries out instructions embodies as code in computer readable medium 310 (e.g., a non-transitory computer-readable medium). An exemplary processor may be a central processing unit (CPU). As used herein, a processor can include a single-core processor, a plurality of single-core processors, a multi-core processor, a plurality of multi-core processors, or any other suitable combination of hardware configured to perform arithmetical, logical, and/or input/output operations of a computing device.
Display 302 may be a screen that can show information to a user. In some cases, display 302 may be any suitable screen that enables touch functionality. In some embodiments, display 302 of access device 300 may display a user interface that may allow the user to select and interact with objects presented on display 302. The objects may include, but may not be limited to, menus, text fields, icons, and keys/inputs on a virtual keyboard. In some embodiments, display 302 may show an output from a data capture device from data capture device 330 (e.g., images from camera 231). Display 320 may be capable of displaying colors. In some embodiments, display 320 may enable a user to manually provide an electronic signature to access device 300 by directly touching display 320 with their finger or suitable touch screen stylus pen.
Input elements 303 may allow a user to input information into the device. Exemplary input elements 303 include hardware and software buttons, audio detection devices (e.g., microphone), biometric sensors, touch screens, and the like. In some cases, one or more of input elements 303 may be utilized to navigate through various screens presented by display 302 of access device 300. In some cases, a user may activate one or more of input elements 303 to pass identification data (e.g., PAN, driver's license number, etc.) to access device 300.
Network interface 304 may be any suitable combination of hardware and software that enables data to be transferred to and from access device 300. Network interface 304 may enable access device 300 to communicate data to and from another device (e.g., resource provider computer, transport computer, processing network, authorization computer, etc.). Some examples of network interface 304 may include a modem, a physical network interface (such as an Ethernet card or other Network Interface Card (NIC)), a virtual network interface, a communications port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, or the like. The wireless protocols enabled by network interface 304 may include Wi-Fi™.
Data transferred via network interface 304 may be in the form of signals which may be electrical, electromagnetic, optical, or any other signal capable of being received by the external communications interface (collectively referred to as “electronic signals” or “electronic messages”). These electronic messages that may comprise data or instructions may be provided between network interface 304 and other devices via a communications path or channel. As noted above, any suitable communication path or channel may be used such as, for instance, a wire or cable, fiber optics, a telephone line, a cellular link, a radio frequency (RF) link, a WAN or LAN network, the Internet, or any other suitable medium.
Data capture devices 330 may include any devices that can capture data. In some embodiments, the data may be identification data of a user. Data capture device 330 may comprise camera 331, microphone 332, and biometric sensors 333.
Camera 331 may be any suitable device capable of capturing image data. In some embodiments, camera 331 may capture images in certain time intervals and append them to generate a motion video. In some embodiments, camera 331 may have facial recognition technologies, such that it can differentiate the foreground (e.g., face of user) from the background of an image. In some cases, camera 331 may then subtract any unnecessary background data from the image. Camera 331 may be embedded in access device 300 or be an external attachment to access device 300.
Microphone 332 may be any suitable device that can convert sound to an electrical signal. Microphone 332 may be utilized to capture one or more voice segments from a user. For example, microphone 332 may allow the user to transmit his or her voice to access device 300. In some embodiments, the user may utilize voice commands detected by microphone 332 to provide instructions to access device 300.
Biometric sensors 333 may be any suitable devices that can capture biometric information. In some embodiments, biometric sensors 333 may capture biometric information from a user in the form of a fingerprint reader, an iris scanner, a face scanner, or other suitable form. Biometric information captured by biometric sensors 333 may uniquely identify a user. In some embodiments, biometric sensors 333 may include or work in conjunction with other data capture devices in data capture devices 330, such as camera 331 an microphone 332.
Computer readable medium 310 may comprise a number of software modules. For example, computer readable medium 310 may include a data capture device data processing module 321, an identification algorithm module 322, and a transaction processing module 326. In some embodiments, identification algorithm module 322 may include a validation identity token precursor processing submodule 323, a validation key processing submodule 324, and a validation identity token processing submodule 325.
Other modules and submodules may also reside on computer readable medium 310. Examples of additional modules may include an authorization module for processing and routing authorization request and response messages, a clearing and settlement module for processing and routing clearing messages and performing settlement between parties, and data extraction (e.g., for retrieving data from external data sources such as databases) modules, storage modules, and message modification modules. Each module in computer readable medium 310 may be combined with any of the additional modules as appropriate. Each module in computer readable medium 310 may comprise one or submodules, where each submodule may comprise one or more functions implemented by code, executable by processor 301.
Data capture device data processing module 321 may enable, with processor 301, processing of data captured by one or more devices of data capture devices 330. In some embodiments, the captured data may be identification data associated with a user conducting a transaction. Data capture device data processing module 321 may receive, with processor 301, identification data captured by one or more devices of data capture devices 330. The captured data may be in any suitable form (e.g., numerical characters, alphanumeric characters, arrays, lists, matrices, etc.). Data capture device processing module 321 may receive, with processor 301, the captured identification data in real-time (e.g., receive each frame of a video of user's face in real-time) or after a certain time period (e.g., receive all frames of a video of user's face after video capture is terminated).
Additionally, data capture device data processing module 321 may comprise computer code for determining a data capture device from which identification data is captured (e.g., camera 331, microphone 332, biometric sensors 333) and the type of identification data captured (e.g., facial images, iris scans, voice segments, fingerprint information, user identifiers, etc.). In some embodiments, data capture device may include computer code for detecting data capture devices that are activated and collecting identification data. Data capture device processing module 321 may, with processor 301, transmit at least the captured identification data and an indication of the type of the captured identification data to identification algorithm module 322.
Identification algorithm module 322 may enable, in conjunction with processor 301, processing of data for validating a user. Identification algorithm module 322 may receive, with processor 301, identification data from data capture device data processing module 321. Identification algorithm module 322 may comprise code for determining whether the user is conducting an enrollment process or a transaction and for sending any identification data to appropriate submodules within identification algorithm module 322.
Validation identity token precursor processing submodule 323 may enable, with processor 301, generation and processing of a validation identity token precursor. During enrollment, validation identity token precursor processing submodule 323 may generate, with processor 301, a validation identity token precursor that is unique to the user. This validation identity token precursor may also be known as the enrolled validation identity token precursor. Validation identity precursor processing submodule 323 may comprise computer code for storing the validation identity token precursor generated during enrollment in enrollment database 340 in a data record associated with the user. Validation identity precursor processing submodule 323 may also comprise computer code for sending the enrolled validation identity token precursor to validation identity token processing submodule 325.
Validation identity token precursor processing submodule 323 may comprise computer code for determining an algorithm to utilize for generating a validation identity token precursor, based on the type of identification data received from data capture device data processing module 321. For example, if the received identification data comprises facial images, iris scans, or fingerprint information, validation identity token precursor processing submodule 323 may generate, with processor 301, a trigonometric identity value based on the physical points in the facial images, iris scans, or fingerprint information.
Validation identity token precursor processing submodule 323 may further comprise computer code for generating a validation identity token precursor during a transaction conducted by the user. Validation identity token precursor processing submodule 323 may apply, with processor 301, the same algorithm utilized during enrollment to generate the validation identity token precursor. Validation identity precursor processing submodule 323 may comprise computer code for sending the validation identity token precursor generated during the transaction to validation identity token processing submodule 325.
Validation key processing submodule 324 may enable, with processor 301, generation and processing of validation keys. During enrollment, validation key processing submodule 324 may generate, with processor 301, validation keys based on identification data of the user. Validation key processing submodule 324 may also comprise computer code for transmitting the generated validation keys to appropriate entities (e.g., remote server computers) during the enrollment process. For example, validation key processing submodule 324 may comprise computer code for determining to which entities to send validation keys and for determining a distribution of the generated validation keys (e.g., number of validation keys for each remote server computer, etc.). In some embodiments, the determination may be made during the enrollment process (e.g., randomized). In some embodiments, the distribution of validation keys may be predefined.
Validation key processing submodule 324 may comprise computer code for determining an algorithm to utilize for generating validation keys, based on the type of identification data received from data capture device data processing module 321. For example, if the received identification data comprises facial images, iris scans, or fingerprint information, validation key processing submodule 324 may generate, with processor 301, validation keys, where each validation key may be generated based on a certain portion of the facial images, iris scans, or fingerprint information. In some implementations, each validation key may correspond to a value representing a physical point (e.g., distance from nose) on the facial images, iris scans, or fingerprint information.
Validation identity token processing submodule 325 may enable, with processor 301, generation and processing of a validation identity token. Validation identity token processing submodule 325 may comprise code for generating a validation identity token, also known as the enrolled validation identity token, during the enrollment process, based on combining validation keys and in some cases, the enrollment validation identity token precursor. Validation identity token processing submodule 325 may comprise computer code for storing the enrolled validation identity token in enrollment database 340 in a data record associated with the user.
Validation identity token processing submodule 325 may also comprise code for generating a validation identity token during a transaction conducted by the user, based on validation keys and in some cases, the validation identity token precursor generated during the transaction. Validation identity token processing submodule 325 may utilize, with processor 301, the same algorithm for generating the validation identity token during enrollment and the validation identity token during the transaction. The algorithm may comprise any suitable combination of operations (e.g., summation, subtraction, multiplication by coefficients, etc.) that utilize at least the validation keys retrieved during the transaction.
Transaction processing module 326 may enable, with processor 301, any processing of data related to a transaction. Transaction processing module 326 may generate, with processor 301, a request message including identification data of the user received by data capture device data processing module 321 and may send, with processor 301, the request message to other entities (e.g., resource provider computer, transport computer, processing network, authorization computer). In some embodiments, transaction processing module 326 may comprise computer code for including an identifier in the request message or for sending the identifier with the request message, where the identifier indicates that the transaction is to be conducted with a validation identity token.
Transaction processing module 326 may also comprise code for processing a response message. Transaction processing module 326 may, with processor 301, retrieve validation keys included in the response message by other entities and may, with processor 301, send them to validation identity token processing submodule 325 for generating a validation identity token for the transaction. Transaction processing module 326 may comprise computer code for determining whether the user can be authenticated based on comparing the generated validation identity token and the previously enrolled validation identity token of the user. Transaction processing module 326 may enable, with processor 301, storage of any data related to the transaction in transaction database 350 in a data record associated with the user.
Access device 300 may also comprise several databases, including enrollment database 340 and transaction database 350. Each database may be a conventional, fault tolerant, relational, scalable, secure database such as those commercially available from Oracle™ or Sybase™. In some embodiments, any of the databases may be combined into a single database, or may be separated into multiple databases. Access device 300 may have other databases that are not shown in
Enrollment database 340 may store any data associated with enrollment. In some embodiments, enrollment database 340 may store enrollment data associated with a plurality of users. Information associated with each user may be stored in a data record associated with the user. Enrollment data may include any information provided by a user during an enrollment process. For example, the information may include identification data of the user, such as an account identifier (e.g., PAN, email address, etc.), biometric data (e.g., facial images, iris scans, voice prints, fingerprint information, etc.), and any other information that may be utilized to identify the user (e.g., name, etc.). Additionally, in some cases, the information may include an enrolled validation identity token precursor and an enrolled validation identity token associated with the user.
Transaction database 350 may store any data related to transactions. In some embodiments, transaction database 350 may store transaction data associated with a plurality of users. Information associated with each user may be stored in a data record associated with the user. In some cases, the data stored in transaction database 350 may include a timestamp, a response message, an authorization decision, an indicator indicating whether the user was authenticated with a valid validation identity token, and any other data related to a transaction.
In some embodiments, access device 300 may not include some components shown in
Processor 401 may include hardware for processing functions of server computer 400. Processor 401 may include hardware within server computer 400 that carries out instructions embodies as code in computer readable medium 410 (e.g., a non-transitory computer-readable medium). An exemplary processor may be a central processing unit (CPU). As used herein, a processor can include a single-core processor, a plurality of single-core processors, a multi-core processor, a plurality of multi-core processors, or any other suitable combination of hardware configured to perform arithmetical, logical, and/or input/output operations of a computing device.
Network interface 402 may be any suitable combination of hardware and software that enables data to be transferred to and from server computer 400. Network interface 402 may enable server computer 400 to communicate data to and from another device (e.g., access device, resource provider computer, transport computer, processing network, authorization computer, etc.). Some examples of network interface 402 may include a modem, a physical network interface (such as an Ethernet card or other Network Interface Card (NIC)), a virtual network interface, a communications port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, or the like. The wireless protocols enabled by network interface 402 may include Wi-Fi™.
Data transferred via network interface 402 may be in the form of signals which may be electrical, electromagnetic, optical, or any other signal capable of being received by the external communications interface (collectively referred to as “electronic signals” or “electronic messages”). These electronic messages that may comprise data or instructions may be provided between network interface 402 and other devices via a communications path or channel. As noted above, any suitable communication path or channel may be used such as, for instance, a wire or cable, fiber optics, a telephone line, a cellular link, a radio frequency (RF) link, a WAN or LAN network, the Internet, or any other suitable medium.
Computer readable medium 410 may comprise a number of software modules. For example, computer readable medium 410 may include a validation key retrieval module 421, a user information retrieval module 422, and a transaction processing module 423.
Other modules and submodules may also reside on computer readable medium 410. Examples of additional modules may include an authorization module for processing and routing authorization request and response messages, a clearing and settlement module for processing and routing clearing messages and performing settlement between parties, and data extraction (e.g., for retrieving data from external data sources such as databases) modules, storage modules, and message modification modules. Each module in computer readable medium 410 may be combined with any of the additional modules as appropriate. Each module in computer readable medium 410 may comprise one or submodules, where each submodule may comprise one or more functions implemented by code, executable by processor 401.
Validation key retrieval module 421 may enable, in conjunction with processor 401, retrieval of one or more validation keys for a transaction. Validation key retrieval module 421 may comprise computer code for receiving user identification data (e.g., email address, driver's license number, validation identity token precursor, etc.) from transaction processing module 423 and for retrieving the validation keys from validations keys database 440 based on the identification data. Validation key retrieval module 421 may send, with processor 401, the retrieved validation keys to transaction processing module 234.
User information retrieval module 422 may enable, with processor 401, retrieval of data related to a user conducting a transaction. User information retrieval module 422 may comprise computer code for receiving user identification data (e.g., email address, driver's license number, validation identity token precursor, etc.) from transaction processing module 423. User information retrieval module 422 may also comprise computer code for retrieving user information that may be utilized for processing the transaction from user information database 450, based on the received identification data. In some embodiments, the transaction may be a financial transaction and the retrieved user information may be account information (e.g., PAN).
Transaction processing module 423 may enable, with processor 401, any processing of data related to a transaction. For example, transaction processing module 423 may comprise code for processing a received request message. Transaction processing module 423 may comprise code for determining that, based on an identifier included in or sent with the request message, the transaction will involve a validation identity token. In some embodiments, no identifier may be received and transaction processing module 423 may determine, with processor 401, that the transaction will involve a validation identity token based on receiving a validation identity token precursor in the request message. Transaction processing module 423 may send, with processor 401, an instruction to validation key retrieval module 421 to retrieve any relevant validation keys. Transaction processing module 423 may comprise computer code for receiving the retrieved validation keys and for updating the request message to include the retrieved validation keys. Transaction processing module 423 may transmit, with processor 401, the request message to another server computer.
Server computer 400 may also comprise several databases, including validation keys database 440 and user information database 450. Each database may be a conventional, fault tolerant, relational, scalable, secure database such as those commercially available from Oracle™ or Sybase™. In some embodiments, any of the databases may be combined into a single database, or may be separated into multiple databases. Server computer 400 may have other databases that are not shown in
Validation keys database 440 may store any data related to validation keys. In some embodiments, validation keys database 440 may store enrollment data associated with a plurality of users. Information associated with each user may be stored in a data record associated with the user. Validation keys database 440 may store validation keys of the user in association with identification data associated with the user received during enrollment.
User information database 450 may store any data related to a user. In some embodiments, user information database 450 may store user information associated with a plurality of users. Information associated with each user may be stored in a data record associated with the user. In some cases, user information database 450 may store identification data of the user, such as account information (e.g., PAN), a validation identity token precursor, or any other information that may help to identity a user. In some cases, user information database 450 may store transaction data, such as data related to past transactions, associated with the user.
In some embodiments, server computer 400 may include some components not shown in
Referring back to
One embodiment of the invention is described with respect to
In one embodiment, user 202 may conduct the enrollment process with access device 204 associated with resource provider computer 206. Initially, user 202 may provide enrollment data to access device 204. In some embodiments, the enrollment data may include identification data, such as any combination of biometric data (e.g., facial image, iris scan, voice prints, fingerprint scans, etc.) and account identifiers (e.g., PAN, driver's license number, etc.) associated with user 202.
User 202 may provide their enrollment data in any suitable manner. In some cases, user 202 may physically be at the location of access device 204 and may directly provide identification data into access device 204. For example, user 202 many interact with data capture device 250 to enter biometric data (e.g., camera of access device 204 takes picture of user 202) and other input elements to enter account identifiers and other account information (e.g., user enters PAN with buttons of access device 204). In other cases, user 202 may provide enrollment data by sending identification data captured by their user device over a communications network to access device 204 or resource provider computer 208 associated with access device 204. For example, user 202 may access an application or website associated with resource provider computer 206, enter their identification data into the application or website (e.g., user takes picture of their face with the camera of their user device and types in account identifier with the keyboard of their user device), and confirm transmission of the identification data to resource provider computer 206. Resource provider computer 206 may forward the identification data to access device 204.
Access device 204 may then process the enrollment data. In some embodiments, access device 204 may generate multiple pieces of information during the enrollment process (e.g., process 501 in
In some embodiments, access device 204 may generate a validation identity token precursor based on identification data included in the enrollment data. This validation identity token precursor may also be known as the enrolled validation identity token precursor. The enrolled validation identity token precursor may be any information that may be based on or derived from identification data included in the enrollment data and may be utilized to uniquely identity user 202. In one exemplary case, the identification data may comprise an image of the face of user 202 and the enrolled validity identity token precursor may be a trigonometric identity calculated using a plurality of physical points on the image of the face of user 202. The trigonometric identity may be unique to user 202. An exemplary method for calculating the trigonometric identity is described.
First, information related to multiple points from the image of the face of user 202 may be gathered. In some cases, the points may be positioned such that they create an n-sided polygon spanning the outer edge of the head, eyes, nose, mouth, and chin of the face. Each point may be associated with a set of coordinates (e.g., x, y coordinates). While an embodiment utilizing a two-dimensional coordinate system is described for simplicity, a three-dimensional coordinate system may be utilized. In such cases, the camera of access device 204 may be able to generate a three-dimensional representation of user's face (e.g., digital 3D model, topographic map, etc.).
Next, a trigonometric identity may be calculated based on the gathered points. Numerical values may be calculated associated with the points gathered. In one exemplary case, a distance from each point to another part of the face may be calculated. For example, the distance may from a point to the tip of nose, top of the forehead, bottom of the chin, or any other suitable position that can be detected from the image. It is understood that the distance may be calculated using geometric principles, such as calculating the hypotenuse length of a right triangle in which two point positions are known.
These numerical values may then be utilized as parameters for a combination of operations that may be predefined by access device 204. In some embodiments, the operations may comprise a summation based on the distance values. For example, the distance values may be totaled to generate a value. In another example, ratios of certain distance values (e.g., ratio between distances to tip of nose and distances to top of forehead, etc.) may be calculated and summed together. It is understood that the embodiments described above are specific examples and are not limiting. Any suitable combination of operations (e.g., addition, subtraction, multiplication, division, exponentiation, averaging, etc.) may be utilized.
Accordingly, the resulting value may be generated based on unique features of the user (e.g., facial structure) and may serve as the enrolled validation identity token precursor associated with the user. In some embodiments, the enrolled validation identity token precursor may be stored by access device 204 in any suitable storage, such as a database (e.g., enrollment database).
In some embodiments, access device 204 may generate a plurality of validation keys associated with user 202 using identification data included in the enrollment data. In some embodiments, each validation key may be generated based on a certain portion of the identification data. In one example, access device 204 may generate three validation keys (e.g., first, second, third keys, etc.), validation key 225, validation key 235, and validation key 245, where each validation key may be generated based on a different section of the image of the face of user 202. For example, a first validation key may be generated based on one or more points located in a first section of the image. The first validation key may be a numerical value associated with any of the one or more points, such as a distance between two of the one or more points, a distance between one of the points to another location on the face (e.g., tip of the nose), or a ratio between two distance values generated based on the points.
In some embodiments, access device 204 may send the validation keys to a plurality of remote server computers. Each server computer may receive one or more validation keys that may be utilized to form at least part of a validation identity token. In the example depicted in
In some embodiments, each of the remote server computers may store the received validation key in association with other identification data of user 202. For example, access device 204 may send the validation key in association with an account identifier (e.g., PAN, email address, etc.) provided by user 202 during enrollment. This may enable certain remote server computers, such as processing network 210, to associate the received validation key with information that may already be stored related to user 202 (e.g., payment account information). In some embodiments, access device 204 may also send the enrolled validation identity token precursor in association with the validation key. Each of the remote server computers may utilize such information associated with the validation key to retrieve an appropriate validation key associated with user 202 at a later time (e.g., during a future transaction.
Access device 204 may generate a validation identity token. This validation identity token may also be known as the enrolled validation identity token. In some embodiments, the enrolled validation identity token may be generated using the enrolled validation identity token precursor and the validation keys (e.g., process 502 in
At any time after completion of the enrollment process, user 202 may conduct a transaction. In the embodiment described, the transaction may be performed by user 202 without utilizing a user device (e.g., cardless).
At step 1, user 202 initiates a transaction by providing identification data to access device 204 during a transaction. In some embodiments, user 202 may provide identification data by interacting with data capture device 250 of access device 204. In one embodiment, data capture device 250 may be a camera, which may capture one or more images of the face of user 202.
At step 2, access device 204 may process the identification data. In some embodiments, access device 204 may generate certain information based on the identification data and store the information at resource provider computer 206. In some implementations, access device 204 may generate a validation identity token precursor 215 based on the identification data provided by user 202 (e.g., process 503 in
In some embodiments, access device 204 may generate a request message comprising identification data of user 202. For example, the request message may comprise validation identity token precursor 215. The validation identity token precursor 215 may indicate to other entities receiving the request message that user 202 is conducting the transaction.
In some embodiments, remote entities (e.g., transport computer 208, processing network 210, and authorization computer 212) may determine that the transaction is to involve a validation identity token based on recognizing that a validation identity token precursor was received in the request message. In other embodiments, an identifier may be included in or sent with the request message such that the remote entities may recognize that the transaction will utilize a validation identity token. This may instruct the remote entities to retrieve appropriate validation keys for the transaction.
At step 3, the request message comprising identification data of user 202 may be sent to transport computer 208. In some embodiments, access device 204 may send the request message to transport computer 208 via resource provider computer 206. Transport computer 208 may receive the request message including validation identity token precursor 215. In some embodiments, transport computer 208 may have validation key 225 associated with user 202 stored in association with the enrolled validation identity token precursor. Transport computer 208 may retrieve validation key 225 based on matching validation identity token precursor 215 and the enrolled validation identity token precursor of user 202. Transport computer 208 may then include validation key 225 in the request message.
It is understood that in some cases, validation key 225 may be stored in association with other information related to validation identity token precursor 215 that is not the enrolled validation identity token precursor. For example, validation key 225 may be stored in association with a hash value of the enrolled validation identity token precursor. In this case, transport computer 208 may generate a hash of validation identity token precursor 215 upon receiving the request message and retrieve validation key 225 based on matching the hash of the enrolled validation identity token precursor and the hash of validation identity token precursor 215. In other embodiments, the other information may be any other identification data (e.g., email address, driver's license number, etc.) that may be stored by transport computer 208 during the enrollment process and which may be provided by user 202 during the transaction. Transport computer 208 may then retrieve validation key 225 based on the other information and include validation key 225 in the request message.
At step 4, the request message comprising identification data of user 202 may be sent to processing network 210. Processing network 210 may receive the request message including validation identity token precursor 215. In some embodiments, processing network 210 may have validation key 235 associated with user 202 stored in association with the enrolled validation identity token precursor. Processing network 210 may retrieve validation key 235 based on matching validation identity token precursor 215 and the enrolled validation identity token of user 202. Processing network may include validation key 235 in the request message.
It is understood that in some cases, validation key 235 may be stored in association with other information related to validation identity token precursor 215 that is not the enrolled validation identity token precursor. For example, validation key 235 may be stored in association with a hash value of the enrolled validation identity token precursor. In this case, processing network 210 may generate a hash of validation identity token precursor 215 upon receiving the request message and retrieve validation key 235 based on matching the hash of the enrolled validation identity token precursor and the hash of validation identity token precursor 215. In other embodiments, the other information may be any other identification data (e.g., email address, driver's license number, etc.) that may be stored by processing network 210 during the enrollment process and which may be provided by user 202 during the transaction. Processing network 210 may then retrieve validation key 235 based on the other information and include validation key 235 in the request message.
Additionally, in some embodiments, processing network 210 may retrieve further information related to user 202 and include the information in the request message. For example, processing network 210 may retrieve account information associated with user 202 based on identification data in the request message. In some embodiments, processing network 210 may have the account information stored in association with the enrolled validation identity token precursor. In some cases, the account information may include a PAN associated with a payment account of user 202. Processing network 210 may include the account information in the request message, which may help authorization computer 212 identify the account of user 202 to utilize for the transaction.
At step 5, the request message comprising identification data of user 202 may be sent to authorization computer 212. Authorization computer 212 may receive the request message including validation identity token precursor 215. In some embodiments, authorization computer 212 may have validation key 245 associated with user 202 stored in association with the enrolled validation identity token precursor. Authorization computer 212 may retrieve validation key 245 based on matching validation identity token precursor 215 and the enrolled validation identity token of user 202.
It is understood that in some cases, validation key 245 may be stored in association with other information related to validation identity token precursor 215 that is not the enrolled validation identity token precursor. For example, validation key 245 may be stored in association with a hash value of the enrolled validation identity token precursor. In this case, authorization computer 212 may generate a hash of validation identity token precursor 215 upon receiving the request message and retrieve validation key 245 based on matching the hash of the enrolled validation identity token precursor and the hash of validation identity token precursor 215. In other embodiments, the other information may be any other identification data (e.g., email address, driver's license number, etc.) that may be stored by authorization computer 212 during the enrollment process and which may be provided by user 202 during the transaction. Authorization computer 212 may then retrieve validation key 245 based on the other information.
Additionally, in some embodiments, authorization computer 212 may retrieve further information related to user 202. For example, based on the account information (e.g., PAN) included in the request message by processing network 210, authorization computer 212 may be able to identify the account of user 202 to utilized for the transaction. Accordingly, authorization computer 212 may conduct an authorization process to determine whether the transaction may be authorized. For example, authorization computer 212 may conduct fraud analyses based on historical information related to the account of user 202 and information surrounding the transaction. In some embodiments, the fraud analyses may include checks on any abnormalities of characteristics associated with the transaction (e.g., location, transaction amount, resource provider type, etc.). Authorization computer 212 may determine whether the transaction may be authorized.
At step 6, authorization computer 212 may generate a response message and send the response message to processing network 210. In some embodiments, the response message may comprise information including at least validation key 225 and validation key 235 included in the request message, validation key 245 retrieved by authorization computer 212, and an authorization decision based on the authorization process conducted by authorization computer 212. In some cases, the response message may further comprise any fraud information related to the transaction collected in step 5. In some embodiments, the response message may also include validation identity token precursor 215. Authorization computer 212 may send the response message to processing network 210. The response message may be sent over any suitable communication network, such as communications network 260.
At step 7, processing network 210 may send the response message to transport computer 208. The response message may be sent over any suitable communication network, such as communications network 260.
At step 8, transport computer 208 may send the response message to resource provider computer 206. The response message may be sent over any suitable communication network, such as communications network.
At step 9, resource provider computer 206 may forward the response message to access device 204, which may determine whether user 202 may be authenticated. In some embodiments, access device 204 may generate a validation identity token 220, which can indicate whether the transaction is valid. In some implementations, access device 204 may generate validation identity token 220 using information provided in the response message. For example, this information may include validation key 225, validation key 235, validation key 245, and validation identity token precursor 215 (e.g., process 504 in
Validation identity token 220 may be generated by access device 204 using the algorithm utilized to generate the enrolled validation identity token during the enrollment process (see above). Thus, it is expected that validation identity token 220 is the same or similar to the enrolled validation identity token if user 202 conducts the transaction. In some cases, resource provider computer 206 may store validation identity token 220 received from access device 204 for the authentication process.
Access device 204 may conduct an authentication process to determine whether user 202 may be authenticated. In some embodiments, the authentication process may comprise comparing validation identity token 220 generated during the transaction with the enrolled validation identity token previously provided by user 202 (e.g., process 505 in
At step 10, upon comparing validation identity token 220 and the enrolled validation identity token, access device 204 may authenticate user 202 and present a notification of completion of the transaction to user 202. For example, access device 204 may choose to complete the transaction upon determining that the difference between validation identity token 220 and the enrolled validation identity token is within a threshold. In some cases, access device 204 may show a notification of completion of the transaction on display 251 to indicate to user 202 that the transaction has been successfully completed. In some embodiments, a transaction amount associated with the transaction may be debited from the account of user 202 and user 202 may receive goods or services related to the transaction.
In some cases, at a later time (e.g., at the end of the day), a clearing and settlement process can occur between transport computer 208, processing network 210, and authorization computer 212.
While an embodiment in which the identification data included in the request message sent to remote server computers (e.g., transport computer 208, processing network 210, and authorization computer 212) comprises validation identity token precursor 215 is described above, embodiments are not so limited. For example, the identification data included in the request message may not include validation identity token precursor 215 and instead may include other information that can help identity user 202. Thus, user 202 may provide other identification data (e.g., driver's license number, PAN, a phone number, an email address, etc.) during the transaction that may previously have been stored by the remote server computers during the enrollment process. When the remote computers receive the request message, they may match this other information to their previously stored data related to user 202, and retrieve appropriate information (e.g., validation keys, account information, etc.) to be utilized for the transaction.
In cases in which validation identity token precursor 215 is not included in the request message sent during the transaction, validation identity token 220 may be generated in different ways. In some cases, even though validation identity token precursor 215 may be not sent to other remote server computers in the request message, it may still be generated and stored (e.g., by resource provider computer 206) at the time of the transaction and utilized to form at least a part of validation identity token 220. In this case, validation identity token 220 may be generated utilizing validation identity token precursor 215, which may be stored at resource provider computer 206 but not sent in the request message, and the validation keys 225, 235, and 245 in a similar manner to that described above. To authenticate validation identity token 220, it may be compared with an enrolled validation identity token, which may be generated using an enrolled validation identity token precursor and validation keys 225, 235, and 245 during the enrollment process. If the difference between the generated validation identity token 220 and enrolled validation identity token is within a threshold, user 202 may be authenticated for the transaction.
In other cases, validation identity token precursor 215 may not be generated during the transaction. In such cases, validation identity token 220 may be generated utilizing the validation keys 225, 235, and 245. To authenticate validation identity token 220, it may be compared with an enrolled validation identity token, which may be generated using the validation keys 225, 235, and 245 during the enrollment process. If the difference between the generated validation identity token 220 and enrolled validation identity token is within a threshold, user 202 may be authenticated for the transaction.
While embodiments in which an enrollment process is conducted by user 202 with access device 204 or resource provider computer 206 associated with access device 204 are described above, embodiments are not so limited. For example, the embodiments described above may still be performed when user 202 conducts the enrollment process with another entity (e.g., remote server computer), such as processing network 210.
One embodiment that is simplified to enable an efficient transaction, in which the enrollment process may be conducted with processing network 210, is described below with respect to
The enrollment process that may be conducted by processing network 210 is described. User 202 may provide processing network 210 with enrollment data, including identification data, over a communications network. For example, user 202 may access a website or application hosted by processing network 210 on their user device to conduct the enrollment process. In some cases, user 202 may provide biometric information, such as by taking a picture of their face with their user device and sending the picture to processing network 210. Additionally, user 202 may enter any other enrollment data (e.g., PAN, email address, etc.) that may be utilized to identify user 202 or conduct a transaction into their user device and send the other enrollment data over the communications network.
Processing network 210 may then process the enrollment data including identification data. First, processing network 210 may generate validation keys 225, 235, and 245 based on identification data of the user (e.g., process 601 in
Processing network 210 and the resource providing entity associated with access device 204 may have a previous agreement on how to generate a validation identity token using validation keys. In some cases, the agreement may indicate that the validation keys may be joined in such a way that the combination may generate the picture of the face of user 202 provided by user 202 during enrollment. It is then expected that the image associated with validation identity token 220, which may be generated by access device 204 during a future transaction, may match up to the face of user 202.
At a later time, user 202 may conduct a transaction using access device 204. User 202 may provide identification data (e.g., driver's license number, PAN, etc.) that may enable other entities to identify that user 202 is conducting the transaction. In this embodiment, user 202 may not need access device 204 to take an image of their face during the transaction. Access device 204 may include the identification data in the request message sent to the remote server computers. As described in the flow above, validation keys 225, 235, and 245 may be retrieved by remote server computers based on the associated identification data and returned to access device 204 in a response message.
Access device 204 may then generate validation identity token 220 by combining the validation keys 225, 235, and 245 in the method agreed upon with processing network 210 during enrollment (e.g., process 602 in
Access device 204 may then display the generated validation identity token 220 as an image for authentication of user 202 (e.g., process 603 in
In some embodiments, to forgo the step of the cashier performing the validity check of validation identity token 220, access device 204 may conduct the validity check. For example, user 202 may allow access device 204 to take an image of their face during the transaction, which access device 204 may compare to the image generated based on validation identity token 220. In some embodiments, the comparison may comprise a simple subtraction of the foreground (e.g., face of user 202) of the two images. In other embodiments, the comparison may utilize facial recognition technology, such as comparing the shape of the face and distance ratios of parts on the face (e.g., eyes, nose, mouth, chin, etc.) in both images to determine whether user 202 is likely the individual shown in the image generated based on validation identity token 220.
While the embodiments described above describe validation identity token 220 being generated near the end of the processing of the transaction, embodiments are not so limited. For example, validation identity token 220 may be generated at any suitable earlier stage of transaction processing (e.g., at authorization computer 212, processing network 210, and transport computer 208). The generated validation identity token 220 may be sent to resource provider computer 206 and access device 204, which may determine whether the transaction is valid based on validation identity token 220. Additionally, in some cases, multiple entities may generate validation identity token 220.
For example, in some cases, authorization computer 212 can construct validation identity token 220 after receiving the request message. This may be possible because it has the validation identity token precursor 215, as well as the validation keys 225, 235, 245. The authorization computer 212 may link the validation identity token precursor 215 to an account number (if the account number was not transmitted in the request message). Positive verification of the constructed validation identity token 220, based on the enrolled validation identity token 220 provided to authorization computer 212 during enrollment, may prove to the authorizing entity operating the authorization computer 212 that the user conducting the transaction is in fact authentic. Authorization computer 212 may then authorize the transaction based upon the account number linked to the validation identity token 220. In other embodiments, if the account number is present in the request message, then the constructed validation identity token 220 may serve as purely an authentication mechanism. In some cases, the response message generated by authorization computer 212 may include a check on whether or not the proper validation identity token was constructed.
Another embodiment of the transaction is described with respect to
While use of one exemplary color representation is described in embodiments described herein, it is understood that any suitable color representation may be utilized. For example, the color representation may utilize any appropriate number of bits (e.g., 8-bit, 6-bit, 24-bit, 36-bit, etc.) in any suitable color space (e.g., red-green-blue (RGB), cyan-magenta-yellow-key (CMYK), hue-saturation-value (HSV), etc.). Additionally, the color representations may be expressed using any suitable numerical representations (e.g., decimal, binary, hexadecimal, etc.).
In some embodiments, access device 204 may generate multiple pieces of information based on identification data provided by user 202 during the enrollment process. For example, access device 204 may generate an enrolled chromatic identity token precursor and chromatic keys (e.g., process 701 of
However, an additional step may be performed, such that resulting values may be further mapped to a numerical value representing a color. For example, generating the enrolled chromatic identity token precursor may comprise calculating a validation identity token precursor as described above and then mapping the resulting value to a certain 24-bit color representation in the RGB color space. Similarly, the chromatic keys may be mapped to a certain 24-bit color representation in the RGB color space. The enrolled chromatic identity token precursor and chromatic keys may be mapped to any suitable color, as long as the enrolled chromatic identity token generated using enrolled chromatic identity token precursor and chromatic keys may result in a baseline authentication value (see below).
Access device 204 may generate a chromatic identity token during the enrollment process. This may also be known as the enrolled chromatic identity token. The enrolled chromatic identity token may be generated using the enrolled chromatic identity token precursor and chromatic keys (e.g., process 702 in
Any combination of suitable operations may be utilized to combine the enrolled chromatic identity token precursor and chromatic keys, such that the enrolled chromatic identity token results in the baseline authentication value. In one example, the enrolled chromatic identity token precursor and the three chromatic keys may be mapped to hexadecimal values such that the hexadecimal values sum to a hexadecimal value #00FF00 representing green (e.g., each chromatic key is #002200, and enrolled chromatic identity token precursor is #009900). In another example, the enrolled chromatic identity token precursor and the three chromatic keys may be mapped to values that can be weighted by certain coefficients and summed to get hexadecimal value #00FF00 representing green (e.g., first chromatic key is #001100 with coefficient 2, second chromatic key is #001100 with coefficient 3, third chromatic key is #001100 with coefficient 4, and enrolled chromatic identity token precursor is #006600). In yet another example, the sum of the chromatic keys may be subtracted from the enrolled chromatic identity token precursor to get hexadecimal value #00FF00 representing green (e.g., each chromatic key is #550055, and enrolled chromatic identity token precursor is #FFFFFF). It is understood that the combinations of operations described above show specific examples, and hence additional and more complicated operations may be utilized to generate the enrolled chromatic identity token precursor.
User 202 may provide identification data to access device 204 when conducting the transaction. In some implementations, access device 204 may generate the chromatic identity token precursor based on the identification data provided by user 202 (e.g., process 703 in
After receiving a response message for the transaction, access device 204 may generate the chromatic identity token. In some embodiments, the chromatic identity token may be generated utilizing the chromatic keys generated during enrollment and the chromatic identity token precursor (e.g., process 704 in
The generated chromatic identity token may be displayed and visually show the validity of the transaction (e.g., process 705 in
The chromatic identity token may indicate that the transaction is valid if the generated chromatic identity token is the same or within a threshold of the baseline authentication value (e.g., #00FF00 representing green) corresponding to the enrolled chromatic identity token. On the other hand, if the chromatic identity token deviates from the enrolled chromatic identity token by any amount, the generated chromatic identity token may not match the color associated with the baseline authentication value. In this case, the chromatic identity token may correspond to a different color than that associated with the baseline authentication value. For example, a slight deviation may result in the chromatic identity token corresponding to a different shade of green (e.g., #00AD00), a greater deviation may result in the chromatic identity token corresponding to a shade of orange (e.g., #FF9900), and an even greater deviation may result in the chromatic identity token corresponding to a shade of red (e.g., #FF0000).
In some embodiments, the deviation of the chromatic identity token from the enrolled chromatic identity token may be caused by several factors. Some of these factors are described with respect to
One factor may be that the chromatic identity token precursor deviates from the enrolled chromatic identity token precursor. As shown by 802, this may result in an inaccurate parameter utilized to generate the chromatic identity token. In some cases, the deviation of the chromatic identity token precursor may be small. This may indicate that user 202 is likely conducting the transaction and the deviation may be accounted for by a slight change in appearance of user 202 (e.g., different hairstyle, facial hair, makeup, etc.). In some cases, the deviation of the chromatic identity token precursor may be large. This may show that user 202 is not conducting the transaction and indicate that a potential fraudster may be conducting the transaction.
Another factor may be that a chromatic key deviates from the chromatic key originally stored in a remote server computer. As shown by 804, this may also result in an inaccurate parameter utilized to generate the chromatic identity token. In some cases, the deviation may be accounted for by flags or alerts issued by the remote server computer.
In one example, authorization computer 212 may conduct fraud analyses on the transaction and upon detecting potential fraud, may issue flags or alerts. In some embodiments, authorization computer 212 may send the flags or alerts within the response message to access device 204, which may account for them by changing the value (e.g., subtracting some value) of the relevant chromatic key before utilizing it as a parameter to generate the chromatic identity token. In some embodiments, authorization computer 212 may account for the flags or alerts by changing the value of the chromatic key included in the response message before sending it to access device 204. Certain types of flags or alerts may affect the value of the chromatic key more than others. For example, a flag that indicates that the transaction is being conducted in a region neighboring a local area typically associated with user 202 may result in a smaller deviation compared to an alert that indicates that the transaction amount is significantly greater than a typical transaction by user 202.
Another factor may be that a chromatic key was not appropriately received from a remote server computer. As shown by 806, this may also result in an inaccurate parameter utilized to generate the chromatic identity token. In some embodiments, a missing chromatic key may indicate that the request message for the transaction was not properly handled by a transaction entity. For example, if the chromatic key associated with transport computer 208 is missing, this may indicate that the request message did not travel through transport computer 208 or that transport computer 208 could not properly retrieve the chromatic key or process the request message.
Any of the factors described above may affect the resulting chromatic identity token. Thus, it may be up to the resource providing entity associated with access device 204 to determine for what values of the chromatic identity token the transaction may be approved. In some embodiments, if the chromatic identity token is displayed as a color and it is still not clear whether the transaction can be approved, addition validity checks may be performed, as shown in 808. For example, the resource providing entity may want to check the specific causes for the deviation of the chromatic identity token from the enrolled chromatic identity token. The reasons may include any combination of the factors described above. If the resource providing entity finds that the determined reasons do not likely indicate fraud, such as a slight deviation in the chromatic identity token precursor or a non-urgent alert issued by authorization computer 212, then the transaction may be approved. If the resource providing entity finds that the determined causes indicate high risk and potential fraudulent activity, such as a significantly different chromatic identity token precursor or an urgent alert issued by an authorization computer, then the transaction may be denied.
Embodiments of the invention may provide a number of advantages. Embodiments of the invention enable elements utilized to generate the validation identity token to not be stored by any one entity. For example, a validation identity token precursor may be provided by a user's presence at a POS terminal, while validation keys may be dispersed amongst several remote server computers (e.g., transport computer, processing network, and authorization computer). Since no single server computer may have possession of all elements to generate a complete validation identity token, the risk of the whole token being intercepted by an intermediary is mitigated.
Additionally, the resulting validation identity token can indicate the authenticity of the source and path associated with the validation identity token. For example, the validation identity token may deviate from the enrolled validation identity token if the source, the identity of the user conducting the transaction, is inaccurate. This is because the validation identity token may be generated based on identification data (e.g., biometric data) of the user. Additionally, the validation identity token may deviate significantly from the enrolled validation identity token if any part of the path, including entities (e.g., remote server computers) handling processing for the transaction, is dysfunctional for any reason. This is because the validation identity token may be generated based on validation keys, which may be distributed amongst the entities. The validation identity token may provide a way to effectively determine the validity of the transaction and provide additional insight into specific reasons as to why the transaction may not be valid.
The use of a chromatic identity token, a type of validation identity token, may also provide advantages. The chromatic identity token can visually indicate the authenticity of the source and path associated with the chromatic identity token. This may enable an efficient and intuitive way to recognize the validity of the transaction. Additionally, a resource provider may not have to follow predefined rules regarding what value of the chromatic identity token a corresponding transaction should be approved or denied.
Instead, an individual associated with the resource provider (e.g., cashier) may decide on a case-by-case basis whether additional validity checks should be performed for the transaction before approving or denying the transaction. For example, the cashier may see the color associated with the chromatic identity token, decide to conduct additional validity checks, and determine that the deviation of the chromatic identity token from a valid color (e.g., green) may be due to insignificant reasons (e.g., non-urgent flag issued by a remote server computer). This may enable fraudulent transactions to be more effectively distinguished from non-fraudulent transactions, which can forgo the use of processing power and resources for reprocessing transactions that are unnecessarily declined.
Embodiments of this invention further provide an efficient method of carrying out a transaction. For example, in some embodiments, a transaction may be conducted without use of a payment device. This is convenient as a user does not have to spend time handling their payment device during the transaction (e.g., taking card out of wallet, swiping card at access device, etc.). However, it is understood that embodiments of the invention can still be utilized for transaction utilizing payment devices.
Accordingly, embodiments of the invention provide an efficient and secure method of conducting a transaction. The use of the validation identity token allows for quick and easy detection of the state of the transaction without compromising security by mitigating risk. Further, the validation identity token enables authenticity of the source and path of the transaction to be monitored, which can provide insight as to specific reasons for which a transaction may be considered at risk.
Mitigating risk by separating components of a token amongst multiple entities can be applied outside of financial transaction contexts as well. For example, a general data transaction may similarly comprise certain data elements divided amongst multiple entities, wherein all the elements are necessary to view the data sent in the transaction. An exemplary situation is described in
Resource 920 may be in various forms. In one exemplary case, resource 920 may be an electronic resource (e.g., electronic document). In another exemplary case, resource 920 may be a physical building. In yet another exemplary case, resource 920 may be a service.
The remote server computers may be associated with any entities that have interest in authenticating user 902. For example, resource 920 may be associated with multiple owners (e.g., one or more editors and a publisher of an electronic document) that may want to take part in authenticating user 902 for the transaction. Accordingly, each remote server computer may be associated an owner entity.
Prior to the transaction, user 901 may enroll with the resource providing entity. In some embodiments, the enrollment process may be conducted immediately before the transaction. In other embodiments, the enrollment process may be conducted a longer time period (e.g., several months) prior to the transaction. During the enrollment process, user 901 may provide identification data to access device 902. For example, the identification data may be an iris scan of the eye of user 901 and any additional information (e.g., name, email address, etc.) that may be utilized to identify user 901.
Access device 902 may generate several pieces of information. In some embodiments, access device 902 may generate and store a validation identity token precursor based on identification data of user 901. This may also be known as the enrolled validation identity token precursor. Access device 902 may also generate validation keys based on the identification data and may distribute the validation keys to the remote server computers, such as first computer 903, second computer 904, authorization computer 905, and any additional computers that may exist between second computer 904 and authorization computer 905. In some cases, access device 902 may send certain identification data of user 901 received during enrollment, so that the remote server computers may store the validation key in association with the identification data.
Any distribution of validation keys may be utilized. In some embodiments, a single remote computer may receive multiple validation keys and certain remote computers may not receive any validation keys. However, the validation keys may be distributed such that no single remote computer may store all of the validation keys. Access device 902 may utilize the distributed validation keys and enrolled validation identity token precursor to generate a validation identity token indicating validity of a transaction.
User 901 may conduct the transaction. In some embodiments, user 901 may provide identification data to access device 902. For example, user 901 may allow access device 902 to collect an iris scan of their eye. In some cases, user 901 may also provide additional identification data (e.g., name, email address, etc.) that may help the resource provider and remote server computers identify user 901. Access device 902 may generate and store a validation identity token precursor based on the iris scan performed during the transaction. Access device 902 may generate a request message that may travel through the remote server computers.
During the transaction, the remote server computers may retrieve their respective validation keys. For example, first computer 903 may retrieve a validation key associated with user 901 stored during enrollment, second computer 904 may retrieve a validation key associated with user 901 stored during enrollment, and authorization computer 905 may retrieve a validation key associated with user 901 stored during enrollment. Any of the additional computers residing between second computer 904 and authorization computer 905 may also retrieve a validation key associated with user 901 stored during enrollment. The validation keys may be sent back to access device 902 in a response message generated by authorization computer 905, which may authorize the transaction.
Access device 902 may generate a validation identity token using the validation keys in the response message and stored validation identity token precursor. If the generated validation identity token matches or is within a threshold of the validation identity token generated during enrollment, the transaction may be approved and user 901 may receive access to resource 920.
As shown, embodiments of the invention may be applied to any general data transaction. The risk of the validation identity token being stolen by an intermediary can be mitigated, since portions of the validation identity token are distributed to several remote server computers. It is understood that any of the various embodiments described herein related to financial transactions may be applied to a general data transaction.
A computer system may be utilized to implement any of the entities or components described above. Subsystems of the computer system may be interconnected via a system bus. Additional subsystems may include a printer, a keyboard, a fixed disk (or other memory comprising computer readable media), a monitor, which is coupled to a display adapter, and others. Peripherals and input/output (I/O) devices, which couple to an I/O controller (which can be a processor or other suitable controller), can be connected to the computer system by any number of means known in the art, such as by a serial port. For example, the serial port or external interface can be used to connect the computer apparatus to a wide area network such as the Internet, a mouse input device, or a scanner. The interconnection via system bus allows the central processor to communicate with each subsystem and to control the execution of instructions from system memory or the fixed disk, as well as the exchange of information between subsystems. The system memory and/or the fixed disk may embody a computer readable medium. In some embodiments, the monitor may be a touch sensitive display screen.
A computer system can include a plurality of the same components or subsystems, e.g., connected together by external interface or by an internal interface. In some embodiments, computer systems, subsystem, or apparatuses can communicate over a network. In such instances, one computer can be considered a client and another computer a server, where each can be part of a same computer system. A client and a server can each include multiple systems, subsystems, or components.
It should be understood that any of the embodiments of the present invention can be implemented in the form of control logic using hardware (e.g. an application specific integrated circuit or field programmable gate array) and/or using computer software with a generally programmable processor in a modular or integrated manner. As used herein, a processor includes a single-core processor, multi-core processor on a same integrated chip, or multiple processing units on a single circuit board or networked. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement embodiments of the present invention using hardware and a combination of hardware and software.
Any of the software components or functions described in this application may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C, C++, C#, Objective-C, Swift, or scripting language such as Perl or Python using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions or commands on a computer readable medium for storage and/or transmission, suitable media include random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like. The computer readable medium may be any combination of such storage or transmission devices.
Such programs may also be encoded and transmitted using carrier signals adapted for transmission via wired, optical, and/or wireless networks conforming to a variety of protocols, including the Internet. As such, a computer readable medium according to an embodiment of the present invention may be created using a data signal encoded with such programs. Computer readable media encoded with the program code may be packaged with a compatible device or provided separately from other devices (e.g., via Internet download). Any such computer readable medium may reside on or within a single computer product (e.g. a hard drive, a CD, or an entire computer system), and may be present on or within different computer products within a system or network. A computer system may include a monitor, printer, or other suitable display for providing any of the results mentioned herein to a user.
The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.
One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention.
A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary.
All patents, patent applications, publications, and descriptions mentioned above are herein incorporated by reference in their entirety for all purposes. None is admitted to be prior art.
This application is a divisional application of U.S. non-provisional application Ser. No. 15/013,825, filed Feb. 2, 2016 which claims the benefit of priority to U.S. Provisional Application No. 62/111,520, filed Feb. 3, 2015, which are hereby incorporated by reference in their entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 784152 | Goodacre | Mar 1905 | A |
| 5613012 | Hoffman et al. | Mar 1997 | A |
| 5781438 | Lee et al. | Jul 1998 | A |
| 5883810 | Franklin et al. | Mar 1999 | A |
| 5953710 | Fleming | Sep 1999 | A |
| 5956699 | Wong et al. | Sep 1999 | A |
| 6000832 | Franklin et al. | Dec 1999 | A |
| 6014635 | Harris et al. | Jan 2000 | A |
| 6044360 | Picciallo | Mar 2000 | A |
| 6118874 | Okamoto et al. | Sep 2000 | A |
| 6163771 | Walker et al. | Dec 2000 | A |
| 6227447 | Campisano | May 2001 | B1 |
| 6236981 | Hill | May 2001 | B1 |
| 6267292 | Walker et al. | Jul 2001 | B1 |
| 6327578 | Linehan | Dec 2001 | B1 |
| 6341724 | Campisano | Jan 2002 | B2 |
| 6385596 | Wiser et al. | May 2002 | B1 |
| 6422462 | Cohen | Jul 2002 | B1 |
| 6425523 | Shem-Ur et al. | Jul 2002 | B1 |
| 6592044 | Wong et al. | Jul 2003 | B1 |
| 6636833 | Flitcroft et al. | Oct 2003 | B1 |
| 6748367 | Lee | Jun 2004 | B1 |
| 6805287 | Bishop et al. | Oct 2004 | B2 |
| 6879965 | Fung et al. | Apr 2005 | B2 |
| 6891953 | DeMello et al. | May 2005 | B1 |
| 6901387 | Wells et al. | May 2005 | B2 |
| 6931382 | Laage et al. | Aug 2005 | B2 |
| 6938019 | Uzo | Aug 2005 | B1 |
| 6941285 | Sarcanin | Sep 2005 | B2 |
| 6980670 | Hoffman et al. | Dec 2005 | B1 |
| 6990470 | Hogan et al. | Jan 2006 | B2 |
| 6991157 | Bishop et al. | Jan 2006 | B2 |
| 7051929 | Li | May 2006 | B2 |
| 7069249 | Stolfo et al. | Jun 2006 | B2 |
| 7103576 | Mann, III et al. | Sep 2006 | B2 |
| 7113930 | Eccles et al. | Sep 2006 | B2 |
| 7136835 | Flitcroft et al. | Nov 2006 | B1 |
| 7177835 | Walker et al. | Feb 2007 | B1 |
| 7177848 | Hogan et al. | Feb 2007 | B2 |
| 7194437 | Britto et al. | Mar 2007 | B1 |
| 7264154 | Harris | Sep 2007 | B2 |
| 7287692 | Patel et al. | Oct 2007 | B1 |
| 7292999 | Hobson et al. | Nov 2007 | B2 |
| 7350230 | Forrest | Mar 2008 | B2 |
| 7353382 | Labrou et al. | Apr 2008 | B2 |
| 7379919 | Hogan et al. | May 2008 | B2 |
| RE40444 | Linehan | Jul 2008 | E |
| 7415443 | Hobson et al. | Aug 2008 | B2 |
| 7444676 | Asghari-Kamrani et al. | Oct 2008 | B1 |
| 7469151 | Khan et al. | Dec 2008 | B2 |
| 7548889 | Bhambri et al. | Jun 2009 | B2 |
| 7567934 | Flitcroft et al. | Jul 2009 | B2 |
| 7567936 | Peckover et al. | Jul 2009 | B1 |
| 7571139 | Giordano et al. | Aug 2009 | B1 |
| 7571142 | Flitcroft et al. | Aug 2009 | B1 |
| 7580898 | Brown et al. | Aug 2009 | B2 |
| 7584153 | Brown et al. | Sep 2009 | B2 |
| 7593896 | Flitcroft et al. | Sep 2009 | B1 |
| 7606560 | Labrou et al. | Oct 2009 | B2 |
| 7627531 | Breck et al. | Dec 2009 | B2 |
| 7627895 | Gifford et al. | Dec 2009 | B2 |
| 7650314 | Saunders | Jan 2010 | B1 |
| 7685037 | Reiners et al. | Mar 2010 | B2 |
| 7702578 | Fung et al. | Apr 2010 | B2 |
| 7707120 | Dominguez et al. | Apr 2010 | B2 |
| 7712655 | Wong | May 2010 | B2 |
| 7734527 | Uzo | Jun 2010 | B2 |
| 7753265 | Harris | Jul 2010 | B2 |
| 7770789 | Oder, II et al. | Aug 2010 | B2 |
| 7784685 | Hopkins, III | Aug 2010 | B1 |
| 7793851 | Mullen | Sep 2010 | B2 |
| 7801826 | Labrou et al. | Sep 2010 | B2 |
| 7805376 | Smith | Sep 2010 | B2 |
| 7805378 | Berardi et al. | Sep 2010 | B2 |
| 7828220 | Mullen | Nov 2010 | B2 |
| 7835960 | Breck et al. | Nov 2010 | B2 |
| 7841523 | Oder, II et al. | Nov 2010 | B2 |
| 7841539 | Hewton | Nov 2010 | B2 |
| 7844550 | Walker et al. | Nov 2010 | B2 |
| 7849020 | Johnson | Dec 2010 | B2 |
| 7853529 | Walker et al. | Dec 2010 | B1 |
| 7853995 | Chow et al. | Dec 2010 | B2 |
| 7865414 | Fung et al. | Jan 2011 | B2 |
| 7873579 | Hobson et al. | Jan 2011 | B2 |
| 7873580 | Hobson et al. | Jan 2011 | B2 |
| 7890393 | Talbert et al. | Feb 2011 | B2 |
| 7891563 | Oder, II et al. | Feb 2011 | B2 |
| 7896238 | Fein et al. | Mar 2011 | B2 |
| 7922082 | Muscato | Apr 2011 | B2 |
| 7931195 | Mullen | Apr 2011 | B2 |
| 7938318 | Fein et al. | May 2011 | B2 |
| 7954705 | Mullen | Jun 2011 | B2 |
| 7959076 | Hopkins, III | Jun 2011 | B1 |
| 7996288 | Stolfo | Aug 2011 | B1 |
| 8025223 | Saunders et al. | Sep 2011 | B2 |
| 8046256 | Chien et al. | Oct 2011 | B2 |
| 8060448 | Jones | Nov 2011 | B2 |
| 8060449 | Zhu | Nov 2011 | B1 |
| 8074877 | Mullen et al. | Dec 2011 | B2 |
| 8074879 | Harris | Dec 2011 | B2 |
| 8082210 | Hansen et al. | Dec 2011 | B2 |
| 8095113 | Kean et al. | Jan 2012 | B2 |
| 8104679 | Brown | Jan 2012 | B2 |
| RE43157 | Bishop et al. | Feb 2012 | E |
| 8109436 | Hopkins, III | Feb 2012 | B1 |
| 8121942 | Carlson et al. | Feb 2012 | B2 |
| 8121956 | Carlson et al. | Feb 2012 | B2 |
| 8126449 | Beenau et al. | Feb 2012 | B2 |
| 8171525 | Pelly et al. | May 2012 | B1 |
| 8196813 | Vadhri | Jun 2012 | B2 |
| 8205791 | Randazza et al. | Jun 2012 | B2 |
| 8224702 | Mengerink et al. | Jul 2012 | B2 |
| 8225385 | Chow et al. | Jul 2012 | B2 |
| 8265993 | Chien et al. | Sep 2012 | B2 |
| 8280777 | Mengerink et al. | Oct 2012 | B2 |
| 8328095 | Oder, II et al. | Dec 2012 | B2 |
| 8376225 | Hopkins, III | Feb 2013 | B1 |
| 8380177 | Laracey | Feb 2013 | B2 |
| 8387873 | Saunders et al. | Mar 2013 | B2 |
| 8401539 | Beenau et al. | Mar 2013 | B2 |
| 8401898 | Chien et al. | Mar 2013 | B2 |
| 8402555 | Grecia | Mar 2013 | B2 |
| 8403211 | Brooks et al. | Mar 2013 | B2 |
| 8412623 | Moon et al. | Apr 2013 | B2 |
| 8412837 | Emigh et al. | Apr 2013 | B1 |
| 8417642 | Oren | Apr 2013 | B2 |
| 8447699 | Batada et al. | May 2013 | B2 |
| 8453223 | Svigals et al. | May 2013 | B2 |
| 8453925 | Fisher et al. | Jun 2013 | B2 |
| 8458487 | Palgon et al. | Jun 2013 | B1 |
| 8484134 | Hobson et al. | Jul 2013 | B2 |
| 8485437 | Mullen et al. | Jul 2013 | B2 |
| 8494959 | Hathaway et al. | Jul 2013 | B2 |
| 8498908 | Mengerink et al. | Jul 2013 | B2 |
| 8504478 | Saunders et al. | Aug 2013 | B2 |
| 8510816 | Quach et al. | Aug 2013 | B2 |
| 8533860 | Grecia | Sep 2013 | B1 |
| 8538845 | Liberty | Sep 2013 | B2 |
| 8555079 | Shablygin et al. | Oct 2013 | B2 |
| 8566168 | Bierbaum et al. | Oct 2013 | B1 |
| 8567670 | Stanfield et al. | Oct 2013 | B2 |
| 8571939 | Lindsey et al. | Oct 2013 | B2 |
| 8577336 | Mechaley, Jr. | Nov 2013 | B2 |
| 8577803 | Chatterjee et al. | Nov 2013 | B2 |
| 8578176 | Mattsson | Nov 2013 | B2 |
| 8583494 | Fisher | Nov 2013 | B2 |
| 8584251 | McGuire et al. | Nov 2013 | B2 |
| 8589237 | Fisher | Nov 2013 | B2 |
| 8589271 | Evans | Nov 2013 | B2 |
| 8589291 | Carlson et al. | Nov 2013 | B2 |
| 8595098 | Starai et al. | Nov 2013 | B2 |
| 8595812 | Bomar et al. | Nov 2013 | B2 |
| 8595850 | Spies et al. | Nov 2013 | B2 |
| 8606638 | Dragt | Dec 2013 | B2 |
| 8606700 | Carlson et al. | Dec 2013 | B2 |
| 8606720 | Baker et al. | Dec 2013 | B1 |
| 8615468 | Varadarajan | Dec 2013 | B2 |
| 8620754 | Fisher | Dec 2013 | B2 |
| 8635157 | Smith et al. | Jan 2014 | B2 |
| 8646059 | Von Behren et al. | Feb 2014 | B1 |
| 8651374 | Brabson et al. | Feb 2014 | B2 |
| 8656180 | Shablygin et al. | Feb 2014 | B2 |
| 8695071 | Nandakumar | Apr 2014 | B2 |
| 8751391 | Freund | Jun 2014 | B2 |
| 8887308 | Grecia | Nov 2014 | B2 |
| 20010029485 | Brody et al. | Oct 2001 | A1 |
| 20010034720 | Armes | Oct 2001 | A1 |
| 20010054003 | Chien et al. | Dec 2001 | A1 |
| 20020007320 | Hogan et al. | Jan 2002 | A1 |
| 20020016749 | Borecki et al. | Feb 2002 | A1 |
| 20020029193 | Ranjan et al. | Mar 2002 | A1 |
| 20020035548 | Hogan et al. | Mar 2002 | A1 |
| 20020073045 | Rubin et al. | Jun 2002 | A1 |
| 20020116341 | Hogan et al. | Aug 2002 | A1 |
| 20020133467 | Hobson et al. | Sep 2002 | A1 |
| 20020147913 | Lun Yip | Oct 2002 | A1 |
| 20030028481 | Flitcroft et al. | Feb 2003 | A1 |
| 20030130955 | Hawthorne | Jul 2003 | A1 |
| 20030191709 | Elston et al. | Oct 2003 | A1 |
| 20030191945 | Keech | Oct 2003 | A1 |
| 20040010462 | Moon et al. | Jan 2004 | A1 |
| 20040050928 | Bishop et al. | Mar 2004 | A1 |
| 20040059682 | Hasumi et al. | Mar 2004 | A1 |
| 20040093281 | Silverstein et al. | May 2004 | A1 |
| 20040117638 | Monroe | Jun 2004 | A1 |
| 20040139008 | Mascavage, III | Jul 2004 | A1 |
| 20040143532 | Lee | Jul 2004 | A1 |
| 20040158532 | Breck et al. | Aug 2004 | A1 |
| 20040210449 | Breck et al. | Oct 2004 | A1 |
| 20040210498 | Freund | Oct 2004 | A1 |
| 20040232225 | Bishop et al. | Nov 2004 | A1 |
| 20040260646 | Berardi et al. | Dec 2004 | A1 |
| 20050037735 | Coutts | Feb 2005 | A1 |
| 20050080730 | Sorrentino | Apr 2005 | A1 |
| 20050108178 | York | May 2005 | A1 |
| 20050199709 | Linlor | Sep 2005 | A1 |
| 20050246293 | Ong | Nov 2005 | A1 |
| 20050269401 | Spitzer et al. | Dec 2005 | A1 |
| 20050269402 | Spitzer et al. | Dec 2005 | A1 |
| 20060235795 | Johnson et al. | Oct 2006 | A1 |
| 20060237528 | Bishop et al. | Oct 2006 | A1 |
| 20060256961 | Brainard et al. | Nov 2006 | A1 |
| 20060278704 | Saunders et al. | Dec 2006 | A1 |
| 20060291001 | Sung | Dec 2006 | A1 |
| 20070101126 | Choi et al. | May 2007 | A1 |
| 20070107044 | Yuen et al. | May 2007 | A1 |
| 20070129955 | Dalmia et al. | Jun 2007 | A1 |
| 20070136193 | Starr | Jun 2007 | A1 |
| 20070136211 | Brown et al. | Jun 2007 | A1 |
| 20070170247 | Friedman | Jul 2007 | A1 |
| 20070179885 | Bird et al. | Aug 2007 | A1 |
| 20070208671 | Brown et al. | Sep 2007 | A1 |
| 20070245414 | Chan et al. | Oct 2007 | A1 |
| 20070288377 | Shaked | Dec 2007 | A1 |
| 20070291995 | Rivera | Dec 2007 | A1 |
| 20080015988 | Brown et al. | Jan 2008 | A1 |
| 20080029607 | Mullen | Feb 2008 | A1 |
| 20080035738 | Mullen | Feb 2008 | A1 |
| 20080052226 | Agarwal et al. | Feb 2008 | A1 |
| 20080054068 | Mullen | Mar 2008 | A1 |
| 20080054079 | Mullen | Mar 2008 | A1 |
| 20080054081 | Mullen | Mar 2008 | A1 |
| 20080065554 | Hogan et al. | Mar 2008 | A1 |
| 20080065555 | Mullen | Mar 2008 | A1 |
| 20080065901 | Takaku et al. | Mar 2008 | A1 |
| 20080201264 | Brown et al. | Aug 2008 | A1 |
| 20080201265 | Hewton | Aug 2008 | A1 |
| 20080228646 | Myers et al. | Sep 2008 | A1 |
| 20080243702 | Hart et al. | Oct 2008 | A1 |
| 20080245855 | Fein et al. | Oct 2008 | A1 |
| 20080245861 | Fein et al. | Oct 2008 | A1 |
| 20080283591 | Oder, II et al. | Nov 2008 | A1 |
| 20080289020 | Cameron et al. | Nov 2008 | A1 |
| 20080302869 | Mullen | Dec 2008 | A1 |
| 20080302876 | Mullen | Dec 2008 | A1 |
| 20080313264 | Pestoni | Dec 2008 | A1 |
| 20090006262 | Brown et al. | Jan 2009 | A1 |
| 20090010488 | Matsuoka et al. | Jan 2009 | A1 |
| 20090034725 | Davies, Sr. | Feb 2009 | A1 |
| 20090037333 | Flitcroft et al. | Feb 2009 | A1 |
| 20090037386 | Theobald | Feb 2009 | A1 |
| 20090037388 | Cooper et al. | Feb 2009 | A1 |
| 20090043702 | Bennett | Feb 2009 | A1 |
| 20090048971 | Hathaway et al. | Feb 2009 | A1 |
| 20090106112 | Dalmia et al. | Apr 2009 | A1 |
| 20090106160 | Skowronek | Apr 2009 | A1 |
| 20090134217 | Flitcroft et al. | May 2009 | A1 |
| 20090157555 | Biffle et al. | Jun 2009 | A1 |
| 20090159673 | Mullen et al. | Jun 2009 | A1 |
| 20090159700 | Mullen et al. | Jun 2009 | A1 |
| 20090159707 | Mullen et al. | Jun 2009 | A1 |
| 20090173782 | Muscato | Jul 2009 | A1 |
| 20090200371 | Kean et al. | Aug 2009 | A1 |
| 20090248583 | Chhabra | Oct 2009 | A1 |
| 20090276347 | Kargman | Nov 2009 | A1 |
| 20090294527 | Brabson et al. | Dec 2009 | A1 |
| 20090307139 | Mardikar et al. | Dec 2009 | A1 |
| 20090308921 | Mullen | Dec 2009 | A1 |
| 20090327131 | Beenau et al. | Dec 2009 | A1 |
| 20100008535 | Abulafia et al. | Jan 2010 | A1 |
| 20100088237 | Wankmueller | Apr 2010 | A1 |
| 20100094755 | Kloster | Apr 2010 | A1 |
| 20100106644 | Annan et al. | Apr 2010 | A1 |
| 20100120408 | Beenau et al. | May 2010 | A1 |
| 20100133334 | Vadhri | Jun 2010 | A1 |
| 20100138347 | Chen | Jun 2010 | A1 |
| 20100145860 | Pelegero | Jun 2010 | A1 |
| 20100161433 | White | Jun 2010 | A1 |
| 20100174914 | Shafir | Jul 2010 | A1 |
| 20100185545 | Royyuru et al. | Jul 2010 | A1 |
| 20100211505 | Saunders et al. | Aug 2010 | A1 |
| 20100223186 | Hogan et al. | Sep 2010 | A1 |
| 20100228668 | Hogan et al. | Sep 2010 | A1 |
| 20100235284 | Moore | Sep 2010 | A1 |
| 20100258620 | Torreyson et al. | Oct 2010 | A1 |
| 20100291904 | Musfeldt et al. | Nov 2010 | A1 |
| 20100306076 | Taveau et al. | Dec 2010 | A1 |
| 20100325041 | Berardi et al. | Dec 2010 | A1 |
| 20110010292 | Giordano et al. | Jan 2011 | A1 |
| 20110016047 | Wu et al. | Jan 2011 | A1 |
| 20110016320 | Bergsten et al. | Jan 2011 | A1 |
| 20110040640 | Erikson | Feb 2011 | A1 |
| 20110083018 | Kesanupalli et al. | Apr 2011 | A1 |
| 20110087596 | Dorsey | Apr 2011 | A1 |
| 20110093397 | Carlson et al. | Apr 2011 | A1 |
| 20110123071 | Shah | May 2011 | A1 |
| 20110125597 | Oder, II et al. | May 2011 | A1 |
| 20110153362 | Valin | Jun 2011 | A1 |
| 20110153437 | Archer et al. | Jun 2011 | A1 |
| 20110154466 | Harper et al. | Jun 2011 | A1 |
| 20110161233 | Tieken | Jun 2011 | A1 |
| 20110191244 | Dai | Aug 2011 | A1 |
| 20110238511 | Park et al. | Sep 2011 | A1 |
| 20110238573 | Varadarajan | Sep 2011 | A1 |
| 20110246317 | Coppinger | Oct 2011 | A1 |
| 20110272471 | Mullen | Nov 2011 | A1 |
| 20110272478 | Mullen | Nov 2011 | A1 |
| 20110276380 | Mullen et al. | Nov 2011 | A1 |
| 20110276381 | Mullen et al. | Nov 2011 | A1 |
| 20110276424 | Mullen | Nov 2011 | A1 |
| 20110276425 | Mullen | Nov 2011 | A1 |
| 20110295745 | White et al. | Dec 2011 | A1 |
| 20110302081 | Saunders et al. | Dec 2011 | A1 |
| 20120023567 | Hammad | Jan 2012 | A1 |
| 20120028609 | Hruska | Feb 2012 | A1 |
| 20120035998 | Chien et al. | Feb 2012 | A1 |
| 20120041881 | Basu et al. | Feb 2012 | A1 |
| 20120047237 | Arvidsson et al. | Feb 2012 | A1 |
| 20120066078 | Kingston et al. | Mar 2012 | A1 |
| 20120072350 | Goldthwaite et al. | Mar 2012 | A1 |
| 20120078735 | Bauer et al. | Mar 2012 | A1 |
| 20120078798 | Downing et al. | Mar 2012 | A1 |
| 20120078799 | Jackson et al. | Mar 2012 | A1 |
| 20120095852 | Bauer et al. | Apr 2012 | A1 |
| 20120095865 | Doherty et al. | Apr 2012 | A1 |
| 20120116902 | Cardina et al. | May 2012 | A1 |
| 20120116976 | Hammad et al. | May 2012 | A1 |
| 20120123882 | Carlson et al. | May 2012 | A1 |
| 20120123940 | Killian et al. | May 2012 | A1 |
| 20120129514 | Beenau et al. | May 2012 | A1 |
| 20120143767 | Abadir | Jun 2012 | A1 |
| 20120143772 | Abadir | Jun 2012 | A1 |
| 20120158580 | Eram et al. | Jun 2012 | A1 |
| 20120158593 | Garfinkle et al. | Jun 2012 | A1 |
| 20120173431 | Ritchie et al. | Jul 2012 | A1 |
| 20120185386 | Salama et al. | Jul 2012 | A1 |
| 20120197807 | Schlesser et al. | Aug 2012 | A1 |
| 20120203664 | Torossian et al. | Aug 2012 | A1 |
| 20120203666 | Torossian et al. | Aug 2012 | A1 |
| 20120215688 | Musser et al. | Aug 2012 | A1 |
| 20120215696 | Salonen | Aug 2012 | A1 |
| 20120231844 | Coppinger | Sep 2012 | A1 |
| 20120233004 | Bercaw | Sep 2012 | A1 |
| 20120246070 | Vadhri | Sep 2012 | A1 |
| 20120246071 | Jain et al. | Sep 2012 | A1 |
| 20120265631 | Cronic et al. | Oct 2012 | A1 |
| 20120271770 | Harris et al. | Oct 2012 | A1 |
| 20120297446 | Webb et al. | Nov 2012 | A1 |
| 20120300932 | Cambridge et al. | Nov 2012 | A1 |
| 20120303503 | Cambridge et al. | Nov 2012 | A1 |
| 20120303961 | Kean et al. | Nov 2012 | A1 |
| 20120304273 | Bailey et al. | Nov 2012 | A1 |
| 20120310725 | Chien et al. | Dec 2012 | A1 |
| 20120310831 | Harris et al. | Dec 2012 | A1 |
| 20120316992 | Oborne | Dec 2012 | A1 |
| 20120317035 | Royyuru et al. | Dec 2012 | A1 |
| 20120317036 | Bower et al. | Dec 2012 | A1 |
| 20130017784 | Fisher | Jan 2013 | A1 |
| 20130019098 | Gupta et al. | Jan 2013 | A1 |
| 20130054337 | Brendell et al. | Feb 2013 | A1 |
| 20130054466 | Muscato | Feb 2013 | A1 |
| 20130054474 | Yeager | Feb 2013 | A1 |
| 20130081122 | Svigals et al. | Mar 2013 | A1 |
| 20130091028 | Oder | Apr 2013 | A1 |
| 20130110658 | Lyman et al. | May 2013 | A1 |
| 20130111599 | Gargiulo | May 2013 | A1 |
| 20130117185 | Collison et al. | May 2013 | A1 |
| 20130124290 | Fisher | May 2013 | A1 |
| 20130124291 | Fisher | May 2013 | A1 |
| 20130124364 | Mittal | May 2013 | A1 |
| 20130138525 | Bercaw | May 2013 | A1 |
| 20130144888 | Faith et al. | Jun 2013 | A1 |
| 20130145148 | Shablygin et al. | Jun 2013 | A1 |
| 20130145172 | Shablygin et al. | Jun 2013 | A1 |
| 20130159178 | Colon et al. | Jun 2013 | A1 |
| 20130166402 | Parento et al. | Jun 2013 | A1 |
| 20130166456 | Zhang et al. | Jun 2013 | A1 |
| 20130173736 | Krzeminski et al. | Jul 2013 | A1 |
| 20130185202 | Goldthwaite et al. | Jul 2013 | A1 |
| 20130191286 | Cronic et al. | Jul 2013 | A1 |
| 20130191289 | Cronic et al. | Jul 2013 | A1 |
| 20130198071 | Jurss | Aug 2013 | A1 |
| 20130200146 | Moghadam | Aug 2013 | A1 |
| 20130204787 | Dubois | Aug 2013 | A1 |
| 20130204793 | Kerridge et al. | Aug 2013 | A1 |
| 20130212007 | Mattsson et al. | Aug 2013 | A1 |
| 20130212017 | Bangia | Aug 2013 | A1 |
| 20130212019 | Mattsson et al. | Aug 2013 | A1 |
| 20130212024 | Mattsson et al. | Aug 2013 | A1 |
| 20130212666 | Mattsson et al. | Aug 2013 | A1 |
| 20130218698 | Moon et al. | Aug 2013 | A1 |
| 20130226813 | Voltz | Aug 2013 | A1 |
| 20130246202 | Tobin | Sep 2013 | A1 |
| 20130246203 | Laracey | Sep 2013 | A1 |
| 20130246258 | Dessert | Sep 2013 | A1 |
| 20130246259 | Dessert | Sep 2013 | A1 |
| 20130246267 | Tobin | Sep 2013 | A1 |
| 20130254028 | Salci | Sep 2013 | A1 |
| 20130254052 | Royyuru et al. | Sep 2013 | A1 |
| 20130254102 | Royyuru | Sep 2013 | A1 |
| 20130254117 | von Mueller et al. | Sep 2013 | A1 |
| 20130262296 | Thomas et al. | Oct 2013 | A1 |
| 20130262302 | Lettow et al. | Oct 2013 | A1 |
| 20130262315 | Hruska | Oct 2013 | A1 |
| 20130262316 | Hruska | Oct 2013 | A1 |
| 20130262317 | Collinge et al. | Oct 2013 | A1 |
| 20130275300 | Killian et al. | Oct 2013 | A1 |
| 20130275307 | Khan | Oct 2013 | A1 |
| 20130275308 | Paraskeva et al. | Oct 2013 | A1 |
| 20130282502 | Jooste | Oct 2013 | A1 |
| 20130282575 | Mullen et al. | Oct 2013 | A1 |
| 20130282588 | Hruska | Oct 2013 | A1 |
| 20130297504 | Nwokolo et al. | Nov 2013 | A1 |
| 20130297508 | Belamant | Nov 2013 | A1 |
| 20130304649 | Cronic et al. | Nov 2013 | A1 |
| 20130308778 | Fosmark et al. | Nov 2013 | A1 |
| 20130311382 | Fosmark et al. | Nov 2013 | A1 |
| 20130317982 | Mengerink et al. | Nov 2013 | A1 |
| 20130332344 | Weber | Dec 2013 | A1 |
| 20130339253 | Sincai | Dec 2013 | A1 |
| 20130346314 | Mogollon et al. | Dec 2013 | A1 |
| 20140007213 | Sanin et al. | Jan 2014 | A1 |
| 20140013106 | Redpath | Jan 2014 | A1 |
| 20140013114 | Redpath | Jan 2014 | A1 |
| 20140025581 | Calman | Jan 2014 | A1 |
| 20140025585 | Calman | Jan 2014 | A1 |
| 20140025958 | Calman | Jan 2014 | A1 |
| 20140032417 | Mattsson | Jan 2014 | A1 |
| 20140032418 | Weber | Jan 2014 | A1 |
| 20140040137 | Carlson et al. | Feb 2014 | A1 |
| 20140040139 | Brudnicki et al. | Feb 2014 | A1 |
| 20140040144 | Plomske et al. | Feb 2014 | A1 |
| 20140040145 | Ozvat et al. | Feb 2014 | A1 |
| 20140040148 | Ozvat et al. | Feb 2014 | A1 |
| 20140040628 | Fort et al. | Feb 2014 | A1 |
| 20140041018 | Bomar et al. | Feb 2014 | A1 |
| 20140046853 | Spies et al. | Feb 2014 | A1 |
| 20140052532 | Tsai et al. | Feb 2014 | A1 |
| 20140052620 | Rogers et al. | Feb 2014 | A1 |
| 20140052637 | Jooste | Feb 2014 | A1 |
| 20140067679 | O'Reilly | Mar 2014 | A1 |
| 20140100973 | Brown | Apr 2014 | A1 |
| 20140101453 | Senthurpandi | Apr 2014 | A1 |
| 20140136419 | Kiyohara | May 2014 | A1 |
| 20140222596 | Prakash | Aug 2014 | A1 |
| 20140294175 | Boloker et al. | Oct 2014 | A1 |
| 20140365373 | Pelegero | Dec 2014 | A1 |
| 20150032625 | Dill et al. | Jan 2015 | A1 |
| 20150032626 | Dill et al. | Jan 2015 | A1 |
| 20150032627 | Dill et al. | Jan 2015 | A1 |
| 20150046338 | Laxminarayanan et al. | Feb 2015 | A1 |
| 20160005029 | Ivey | Jan 2016 | A1 |
| 20160224983 | Cash | Aug 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 2156397 | Feb 2010 | EP |
| 0135304 | May 2001 | WO |
| 0135304 | May 2002 | WO |
| 2004042536 | May 2004 | WO |
| 2006113834 | Oct 2006 | WO |
| 2009032523 | Mar 2009 | WO |
| 2010078522 | Jul 2010 | WO |
| 2012068078 | May 2012 | WO |
| 2012098556 | Jul 2012 | WO |
| 2012142370 | Oct 2012 | WO |
| 2012167941 | Dec 2012 | WO |
| 2013048538 | Apr 2013 | WO |
| 2013056104 | Apr 2013 | WO |
| 2013119914 | Aug 2013 | WO |
| 2013179271 | Dec 2013 | WO |
| 2016126729 | Aug 2016 | WO |
| Entry |
|---|
| U.S. Appl. No. 15/013,825 , Advisory Action, dated Mar. 19, 2021, 5 pages. |
| U.S. Appl. No. 15/013,825 , Final Office Action, dated Jan. 7, 2021, 15 pages. |
| U.S. Appl. No. 15/013,825 , Final Office Action, dated Mar. 21, 2019, 20 pages. |
| U.S. Appl. No. 15/013,825 , Non-Final Office Action, dated Jul. 24, 2018, 19 pages. |
| U.S. Appl. No. 15/013,825 , Non-Final Office Action, dated May 6, 2020, 22 pages. |
| U.S. Appl. No. 15/013,825 , Notice of Allowance, dated Aug. 18, 2021, 9 pages. |
| U.S. Appl. No. 15/013,825 , “Restriction Requirement”, dated May 7, 2018, 6 pages. |
| Application No. PCT/US2016/016208 , International Search Report and Written Opinion, dated May 27, 2016, 12 pages. |
| “Petition for Inter Partes Review of U.S. Pat. No. 8,533,860 Challenging Claims 1-30 Under 35 U.S.C. § 312 and 37 C.F.R. § 42.104”, USPTO Patent Trial and Appeal Board, IPR 2016-00600, Feb. 17, 2016, 65 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220020031 A1 | Jan 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62111520 | Feb 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15013825 | Feb 2016 | US |
| Child | 17489463 | US |
