The present invention relates, in general, to payments made with mobile devices, and, in particular, to payment processing without the need for user selection of a payment authentication modality.
It is common practice for consumers to conduct electronic transactions with merchants for goods or services received. Electronic payments are typically made with a token that identifies a source of funding. For example, a credit card containing a magnetic strip is a token. The payment tokens usually contain static information, such as an account number, identifying a source of payment. When a credit card is swiped, the card number is transmitted to a centralized payment-processing system. A physical token such as a credit card cannot be easily modified and, in the event that it is lost or stolen, the consumer must report the lost card and wait for a replacement to be mailed. As a result, systems that allow a consumer to pay for a transaction at the point of sale (POS), using a mobile device to display a token (usually in the form of a barcode or QR code), are becoming widely accepted. In fact, due the ease the ease of generating and replacing these tokens, mobile tokens for a wide variety of transaction types (payment tokens, ticket tokens, promotional offer tokens, etc.) are being developed. However, just as a consumer may take a few minutes to locate the appropriate credit card in his wallet, he may struggle to locate the appropriate application on his mobile device to display the token. Launching the application, once found, is another step the consumer must typically take before the token is displayed.
Accordingly, there is a need for a mobile transaction system that improves the ease and efficiency of the consumer's experience in completing a payment transaction.
In various embodiments, the present invention provides a “no-touch” mobile checkout experience that frees consumers from the need to manually locate and activate a mobile payment application in order to complete a transaction. The consumer simply brings his mobile device within close range of an interface console, which in various embodiments prompts the device to launch an application that causes display of a payment token without user action. If the consumer's device is not NFC-capable, the interface console can read a displayed token optically in the usual fashion.
Accordingly, in one aspect, the invention pertains to a method of processing a transaction between a consumer and a merchant. In representative embodiments, the method includes receiving, from a remote token-generating server, a token by a device of the consumer and storing the token in a memory of the device; positioning, by the consumer, a display of the device within view of an optical scanner of a merchant checkout system capable of NFC communications; if the device is NFC enabled and within NFC range of the checkout system, establishing, without action by the consumer, an NFC communication channel between the device and the checkout system, communicating, by the checkout system, over the communication channel a request to display the stored token, in response to the request, displaying, by the device, the stored token, optically reading and electronically decoding, by the checkout system, the token upon presentation thereof by the device, and completing, by the checkout system, the transaction based at least in part on the decoded token information; and if the device is incapable of NFC communications, in response to an action by the consumer, displaying, by the device, the stored token, optically reading and electronically decoding, by the checkout system, the token upon presentation thereof by the device, and completing, by the checkout system, the transaction based at least in part on the decoded token information.
The request may specify a type of stored token to display. In various embodiments, the checkout system receives a decryption key from the token-generation server. The device may receive and store a plurality of tokens. The device may be NFC-enabled and may poll its environment, by regularly transmitting an NFC signal, for NFC circuitry within NFC range.
In another aspect, the invention relates to a checkout system. In various embodiments, the checkout system includes NFC circuitry for establishing a communication channel with an NFC-enabled device within an NFC range and communicating over the communication channel a request to display a token; an optical scanner for reading an optically displayed token within a field of view of the scanner; reading circuitry, responsive to the optical scanner, for electronically decoding the token; and a processor for completing the transaction based at least in part on the decoded token. The NFC circuitry may be contained in an NFC tag and/or may be configured to be powered by an external NFC signal.
In another aspect, the invention relates to a wireless device. In various embodiments the wireless device includes a processor; a memory; a display; telecommunication circuitry for establishing, via the public telephone network, a channel for secure data exchange with a remote token-generating server; NFC circuitry for establishing NFC communications with an NFC-capable merchant checkout system; and a control application, executable by the processor and configured for causing storage, in the memory, of a token received from the token-generating server by the telecommunication circuitry, causing display of an action button on the display, causing the NFC circuitry to monitor for availability of NFC, where NFC availability is detected by the NFC circuitry, autonomously establishing an NFC communication channel, detecting an external request received via the NFC channel to display the stored token, and in response, causing the stored token to appear on the display without user action, and where NFC availability is not detected by the NFC circuitry, causing the stored token to appear on the display only upon user selection of the displayed button.
In various embodiments, the control application is configured for receiving a plurality of tokens and causing storage thereof in the memory. Additionally, the control application may be configured to detect a request to display a particular type of token from the plurality of tokens and to responsively cause a token of the requested type to appear on the display.
As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. Moreover, articles “a” and “an” as used in the subject specification and annexed drawings should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. In addition, the terms like “consumer equipment,” “mobile station,” “mobile,” “communication device,” “access terminal,” “terminal,” “handset,” and similar terminology, refer to a wireless device (e.g., cellular phone, smart phone, computer, PDA, set-top box, Internet Protocol Television (IPTV), electronic gaming device, printer, and so forth) utilized by a consumer of a wireless communication service to receive or convey data, control, voice, video, sound, gaming, or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably in the subject specification and related drawings. The terms “component,” “system,” “platform,” “module,” and the like refer broadly to a computer-related entity or an entity related to an operational machine with one or more specific functionalities. Such entities can be hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. Also, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal).
In the drawings, like reference characters generally refer to the same parts throughout the different views. Also, the drawings are not necessarily to scale, with an emphasis instead generally being placed upon illustrating the principles of the invention. In the following description, various embodiments of the present invention are described with reference to the following drawings, in which:
Refer first to
Each checkout system 108 may be associated with a merchant who offers goods or services for sale to, among others, the consumer possessing the mobile device 102 and who wishes to offer a no-touch checkout experience to the consumer. The checkout system 108 may be a POS system (e.g., an electronic cash register, a ticketing kiosk, etc.) that connects to a device interface console 112. The device interface console 112 is responsible for establishing an NFC channel with an NFC-enabled device 102 within NFC range (e.g., within approximately 20 cm) to request the display of a token, reading and decoding a token, and making the decoded information available to the checkout system 108. In addition, the console 112 may be mobile or physically associated with the checkout system 108. The checkout system 108 may be responsible for completing the transaction based on information provided therein and/or for decrypting any encrypted token information. Alternatively, the checkout system 108 may transmit the token information to the transaction processor 110 to request authorization for the transaction. The transaction processor 110 may be responsible for authorizing the transaction, and, in some cases, for decrypting the token. In one embodiment, the transaction processor 110 is a payment processor responsible for or actually performing the transaction based on financial information included in, or linked to, the token. For example, a so-called “direct” payment processor represents the financial-processing backend provider to credit-card issuers and payment services such as PAYPAL. An “indirect” payment processor is an independent entity processing transactions for multiple payment services and maintains its own records and data. The distribution of responsibility for various aspects of transaction processing among the checkout system 108 and other entities represents a design choice.
The mobile device 102 acts as a gateway for transmitting the consumer's data to the network 104. The mobile device 102 can support multiple communication channels for exchanging multimedia and other data with the token-generating server 106, the console 112, and other devices using a Wi-Fi LAN (e.g., IEEE 802.11 standard) for Internet access, a short-range Bluetooth wireless connection for point-to-point access, and/or an NFC channel (e.g., IEEE 802.2 standard) for close-proximity access. Referring to
The memory 210 includes an operating system (OS) 212, such as GOOGLE ANDROID, NOKIA SYMBIAN, BLACKBERRY RIM or MICROSOFT WINDOWS MOBILE, and a code process 214 that implements the device-side functions as further described below. Additional transactional information may be embedded in the code process 214 for transmission through the network 104 for later processing on a back-end server (e.g., the token-generating server 106). As used herein, the term “mobile device” refers to a “smart phone” or tablet with advanced computing ability that, generally, facilitates bi-directional communication and data transfer using a mobile telecommunication network, and is capable of executing locally stored applications and/or payment transactions. Mobile devices include, for example, IPHONES (available from Apple Inc., Cupertino, Calif.), BLACKBERRY devices (available from Research in Motion, Waterloo, Ontario, Canada), or any smart phones equipped with the ANDROID platform (available from Google Inc., Mountain View, Calif.), tablets, such as the IPAD and KINDLE FIRE, and personal digital assistants (PDAs). The memory 210 may include computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) and random access memory (RAM). A basic input/output system (BIOS), containing the basic routines that help to transfer information between elements, such as during start-up, is typically stored in ROM. RAM typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit.
In operation, with reference to
The token contains data that identifies the consumer and/or the token, and may contain actual financial account information, coupon information, and/or ticketing information or may instead contain information (such as an email address, telephone number, or random unique data) that can be mapped to the consumer's account by the transaction processor 110. In one embodiment, before being sent, the token is encrypted using, for example, a private key. The encrypted token is then transmitted to the mobile device 102. The token-generation process may take place at any time after a consumer registers an account and the token may be delivered to the mobile device 102 at any time a network connection can be established. Accordingly, generation of the token and delivery of the token may occur as two separate steps and may not happen at the same time. In one embodiment, the mobile device 102 stores a stack of tokens that may be rotated periodically or upon a triggering event, such as display. Additionally, the app may receive and store multiple tokens for various types of transactions and in response to a request for a specific type of token retrieve the appropriate token from storage in device 102.
The checkout system 108 may be configured to offer the consumer possessing mobile device 102 a no-touch checkout experience. Referring to
The checkout system 108 is physically or remotely connected to, or includes, the device interface console 112, which is capable of communicating over an NFC channel with a mobile device 102 within NFC range. For example, in response to the polling signal, the communication module 234 may send a message to the device 102 that causes it to display a token in connection with the transaction; for example, the message may “wake up” an app running in the background on the device 102. Once the token is displayed, the console 112 may read the token using any suitable modality, providing a no-touch checkout experience for the consumer. Thus, the term “display” broadly connotes presentation, e.g., as an optically readable pattern on the display 202 of the device 102 or as data communicated by NFC. The console 112 contains an optical scanner 238 and an NFC communication chip 240, enabling it to read data optically or via NFC, and may contain further communication capabilities if interaction over other communication modalities is desired.
The scanner 238 may be any form of optical scanner capable of reading and decoding an optically displayed token, such as a barcode or QR code. In various embodiments, the scanner 238 is configured to continuously, or periodically, scan its environment to detect an optical token within its field of view. Alternatively, or in addition, the checkout system 108 may signal the scanner 238, via the console interface 224, that a barcode is expected when a mobile device has been detected within NFC range. The NFC communication chip 240 contains NFC circuitry, an NFC antenna (e.g., a loop-inductor-antenna), and a memory for storing data. The NFC chip 240 is capable of operating the console 112 to communicate wirelessly, for example, at 13.56 MHz with other NFC devices within NFC range to transmit and receive data. A message communicated by the NFC chip 240 may contain a request to open, or a URL for, the client app downloaded on mobile device 102; when read, the message triggers the app to open and display a token. Additionally, in some embodiments, that message also contains a request for a specific type of token (e.g., a payment token). In various embodiments, this message is modifiable and/or customizable to the merchant's type of business or checkout needs. The NFC communication chip 240 may draw power from the console 112 or checkout system 108 and be capable of operating in both passive and active modes; in various embodiments, the operating mode may be selected manually by an operator of the checkout system 108. When operating in active mode the NFC communication chip 240 may poll its environment to detect other NFC devices within range and establish an NFC communication channel with the detected device. Alternatively, the chip 240 may be an NFC tag (i.e., ISO 14443 or FeLiCa compliant) that functions without any battery or power source of its own. Instead, when the consumer brings his NFC-enabled mobile device 102 within NFC range of the tag by “tapping” his device to the console 112, the NFC tag 240 becomes powered by the mobile device's signal and, for example, may modulate the polling signal to send data to the mobile device. In this embodiment, it is possible to convert any optical scanner 238 to operate in accordance herewith merely by affixing such a tag (e.g., in the form of a sticker) to the scanner.
With reference to
If the mobile device 102 is NFC-enabled, the consumer may choose to execute the client app and present a token simply by tapping her device 102 to the console 112. Once an NFC-enabled device 102 is detected by the checkout system 108, a high-frequency magnetic field is created between the loosely coupled coils of the NFC antennas in the mobile device 102 and the console 112 (step 310). Once this field is established, a connection is formed and information can be passed between the device 102 and the console 112 (step 312). Where both the console 112 and mobile device 102 are operating in active NFC modes, a handshake may take place in which the roles are assigned, or the devices may take turns operating as interrogator and target in the half-duplex standard of NFC communication. The system 108 may query, via the NFC chip 240, the device 102 to determine whether the device is capable of displaying a token in visual form (step 314), and if so, signaling a request to execute the client app that will display a token without any action from the consumer (step 316). The optical scanner 238, operating responsively or independently of the NFC chip 240, detects the token displayed by the device 102 (step 304). For example, the checkout system 108 may receive notification from the console 112 that an NFC device has been detected in range, and that the device possesses adequate graphical capability to display a token; the system 108, in turn, signals the optical scanner 238 that token presentation is imminent. In response, the scanner 238 may “wake up” to detect the token immediately upon its presentation. The optical scanner 238 reads and decodes the token information (step 306) and transmits the data through the console interface 224 to the checkout system 108. If, however, the system 108 determines that the device 102 cannot display the token visually, the console 112, via the NFC chip 240, may request the token information from the device 102 as an NFC signal (step 318). The console 112 then electronically decodes the token upon receipt thereof (step 320) and transmits the data through the console interface 224 to the checkout system 108. In one embodiment, a secure NFC communication channel may be first established and all token information sent in encrypted form.
The transaction module 232 then determines how to process the transaction based on the information received from the console 112 (step 308). For example, the transaction module 232 may decide whether to accept the consumer's payment based on the decoded token information, saving the transactional information in the storage device 268 for later transmission through the network 104 for processing on a back-end server (e.g., the transaction processor 110). Alternatively, the transaction module 232 may send the token to the transaction processor 110 for verification of the validity and/or the consumer's ability to pay before processing the transaction. Additionally, the transaction module 232 may store one or more decryption keys obtained from the token-generating server 106 and use one of these to decrypt the token prior to evaluating the information contained therein. The transaction module 232 may authorize a transaction based on any successfully decrypted token, or may instead additionally evaluate the decrypted token information.
Given the widespread adoption among consumers of wireless devices (e.g., smartphones or tablets) with advanced graphical displays, the merchant may deem it unnecessary to have a checkout system 108 capable of receiving a token via NFC. In such cases, the NFC chip 240 in console 112 may be a simple NFC tag that functions without any battery or power source of its own. As described above, when the consumer brings his NFC-enabled mobile device 102 within NFC range of the tag by “tapping” his device to the console 112, the NFC tag 240 becomes powered by the mobile device's signal. Alternatively, the checkout system 108 may have a conventional NFC chip 240 set to operate in a passive mode.
If the mobile device 102 is NFC-enabled, the consumer may choose to execute the client app and display a token simply by tapping her device 102 to the console 112. When the consumer brings his NFC-enabled mobile device 102 within NFC range of the NFC tag 240 by tapping his device to the console 112, the tag 240 becomes powered by the mobile device's signal (step 360). NFC information can be passed between the device 102 and the console 112 (step 362). The mobile device 102, operating in an active NFC mode, acts as the interrogator; the tag may respond simply by modulating the reading signal, or may draw power from the signal to operate in an active mode that facilitates data exchange. The mobile device 102 may send, for example, an interrogation message to the NFC tag 240 to find out what type of communication it uses, such as Type A/B or FeLiCa. When the NFC tag 240 responds, the interrogating mobile device 102 sends its first commands in the appropriate fashion. The commands may be transmitted, for example, using phase jitter modulation (PJM) to modify the surrounding field and send out a signal, or using any suitable modality known to those in the art. The NFC tag 240 receives the instruction and checks if it is valid. If it is a valid request, the tag 240 responds with a message that, when read by the device 102, triggers the app to open and ultimately display a visual token without any action from the consumer (step 364). The optical scanner 238 detects the token that is now on display within its field of view. The optical scanner 238 reads and decodes the token information (step 356) and transmits the data through the console interface 224 to the checkout system 108. As previously described, the transaction module 232 then determines whether to authorize the transaction immediately or undertake further processing (step 358).
While several inventive embodiments have been described and illustrated herein, those of ordinary skill in the art will readily envision a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein, and each of such variations and/or modifications is deemed to be within the scope of the inventive embodiments described herein. For example, each of the processors described herein may be a general-purpose computer, but alternatively may be a CSIC (consumer-specific integrated circuit), ASIC (application-specific integrated circuit), a logic circuit, a digital signal processor, a programmable logic device, such as an FPGA (field-programmable gate array), PLD (programmable logic device), PLA (programmable logic array), RFID processor, smart chip, or any other device or arrangement of devices that is capable of implementing the steps of the processes of the invention.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof These various implementations can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
The various modules and apps described herein can include machine instructions for a programmable processor, and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms “machine-readable medium” “computer-readable medium” refers to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor.
The terms and expressions employed herein are used as terms and expressions of description and not of limitation, and there is no intention, in the use of such terms and expressions, of excluding any equivalents of the features shown and described or portions thereof. In addition, having described certain embodiments of the invention, it will be apparent to those of ordinary skill in the art that other embodiments incorporating the concepts disclosed herein may be used without departing from the spirit and scope of the invention. Accordingly, the described embodiments are to be considered in all respects as only illustrative and not restrictive.
This application is a continuation of and claims priority to U.S. patent application Ser. No. 13/939,434, filed on Jul. 11, 2013, the disclosure of which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
D38205 | Alexander | Aug 1906 | S |
D104560 | Chamberlain | May 1937 | S |
D127030 | Bettcher | May 1941 | S |
D154818 | Strauss | Aug 1949 | S |
D164158 | Clay | Aug 1951 | S |
D169369 | Forrester | Apr 1953 | S |
D173647 | Elle et al. | Dec 1954 | S |
D180734 | Hirose | Aug 1957 | S |
D180887 | Weinstein | Aug 1957 | S |
D181019 | Parcher | Sep 1957 | S |
D181589 | Kellock et al. | Dec 1957 | S |
D184351 | Grosso | Feb 1959 | S |
D199598 | Lanigan | Nov 1964 | S |
D210281 | Specht | Feb 1968 | S |
D213446 | Sabella | Mar 1969 | S |
D215035 | Steinbach | Aug 1969 | S |
3748765 | Bass et al. | Jul 1973 | A |
D240460 | Simonelli | Jul 1976 | S |
D240609 | Schwartz | Jul 1976 | S |
D245934 | Donaldson | Sep 1977 | S |
D249527 | Stralka | Sep 1978 | S |
D252932 | Felder | Sep 1979 | S |
D254602 | Gess | Apr 1980 | S |
D255455 | Gensike et al. | Jun 1980 | S |
D260096 | Overman et al. | Aug 1981 | S |
D268029 | Fisher | Feb 1983 | S |
D268590 | Miller et al. | Apr 1983 | S |
D270644 | Kinney | Sep 1983 | S |
D276618 | Hanke | Dec 1984 | S |
D280103 | Bonnefoy | Aug 1985 | S |
D290708 | Rea | Jul 1987 | S |
D295413 | Nakamura et al. | Apr 1988 | S |
D310359 | Inukai | Sep 1990 | S |
D316707 | Allegeier | May 1991 | S |
D323894 | Rosati et al. | Feb 1992 | S |
D325729 | Forsythe et al. | Apr 1992 | S |
D327878 | Fukutake et al. | Jul 1992 | S |
5140141 | Inagaki et al. | Aug 1992 | A |
5198650 | Wike, Jr. | Mar 1993 | A |
D334896 | Shimizu et al. | Apr 1993 | S |
D344745 | Miyazawa | Mar 1994 | S |
D348260 | Allgeier | Jun 1994 | S |
5343529 | Goldfine et al. | Aug 1994 | A |
5396417 | Burks et al. | Mar 1995 | A |
D359059 | Omi | Jun 1995 | S |
D359483 | Saunders et al. | Jun 1995 | S |
D373354 | Maslow | Sep 1996 | S |
D373576 | Liggett | Sep 1996 | S |
D378587 | Kanno et al. | Mar 1997 | S |
D378916 | Kanno et al. | Apr 1997 | S |
5619574 | Johnson et al. | Apr 1997 | A |
D381590 | Thoeni et al. | Jul 1997 | S |
D381651 | Banik et al. | Jul 1997 | S |
5665955 | Collins, Jr. et al. | Sep 1997 | A |
D386489 | Goldman et al. | Nov 1997 | S |
D387337 | Sween et al. | Dec 1997 | S |
D388075 | Bayer et al. | Dec 1997 | S |
5710886 | Christensen et al. | Jan 1998 | A |
5719382 | White | Feb 1998 | A |
5756981 | Roustaei et al. | May 1998 | A |
5784463 | Chen et al. | Jul 1998 | A |
5797002 | Patterson, Jr. et al. | Aug 1998 | A |
5819226 | Gopinathan et al. | Oct 1998 | A |
D400553 | Kung | Nov 1998 | S |
5834751 | Jager et al. | Nov 1998 | A |
5885214 | Monroe et al. | Mar 1999 | A |
D408806 | Schmidt et al. | Apr 1999 | S |
5892900 | Ginter et al. | Apr 1999 | A |
5992747 | Katoh et al. | Nov 1999 | A |
D420657 | Keen et al. | Feb 2000 | S |
6078908 | Schmitz | Jun 2000 | A |
D430588 | Goldberg et al. | Sep 2000 | S |
6178409 | Weber et al. | Jan 2001 | B1 |
6216953 | Kumagai et al. | Apr 2001 | B1 |
6233064 | Griffin | May 2001 | B1 |
D445417 | Lee et al. | Jul 2001 | S |
D447137 | Hultzman | Aug 2001 | S |
D454879 | Lin et al. | Mar 2002 | S |
6357661 | Schonenberg et al. | Mar 2002 | B1 |
D464969 | Byun et al. | Oct 2002 | S |
D480397 | Forsythe et al. | Oct 2003 | S |
D483371 | Johnston | Dec 2003 | S |
D486827 | Detallante | Feb 2004 | S |
6760843 | Carter | Jul 2004 | B1 |
D493794 | Berentzen et al. | Aug 2004 | S |
D495335 | Masamitsu et al. | Aug 2004 | S |
6799271 | Kugai | Sep 2004 | B2 |
6834270 | Pagani et al. | Dec 2004 | B1 |
6836485 | Bendak et al. | Dec 2004 | B1 |
D504429 | Muto | Apr 2005 | S |
D509508 | Ko et al. | Sep 2005 | S |
D512065 | Ko et al. | Nov 2005 | S |
D512698 | Augenbraun et al. | Dec 2005 | S |
D515574 | Colburn | Feb 2006 | S |
D520638 | Zeindler | May 2006 | S |
7048188 | Kumagai et al. | May 2006 | B2 |
7081979 | Cotter et al. | Jul 2006 | B2 |
7093757 | Boucher et al. | Aug 2006 | B2 |
D528444 | Horie et al. | Sep 2006 | S |
D542291 | Kang et al. | May 2007 | S |
7280981 | Huang et al. | Oct 2007 | B2 |
7287009 | Liebermann | Oct 2007 | B1 |
7287692 | Patel et al. | Oct 2007 | B1 |
D556068 | Fugman et al. | Nov 2007 | S |
D558811 | Higgins et al. | Jan 2008 | S |
D562834 | Bashan et al. | Feb 2008 | S |
7328189 | Ling | Feb 2008 | B2 |
7330826 | Porat et al. | Feb 2008 | B1 |
RE40444 | Linehan | Jul 2008 | E |
7400932 | Ackley et al. | Jul 2008 | B2 |
D574738 | Khurana | Aug 2008 | S |
D574829 | Shirai et al. | Aug 2008 | S |
D578535 | Schmitz | Oct 2008 | S |
7437757 | Holdsworth | Oct 2008 | B2 |
7442167 | Dunki-Jacobs et al. | Oct 2008 | B2 |
7454356 | Fields et al. | Nov 2008 | B2 |
7496527 | Silverstein et al. | Feb 2009 | B2 |
7533044 | Scott | May 2009 | B2 |
7555460 | Barkan | Jun 2009 | B1 |
D596969 | Igelmund | Jul 2009 | S |
D597865 | Bernard et al. | Aug 2009 | S |
D598305 | Li et al. | Aug 2009 | S |
7596530 | Glasberg | Sep 2009 | B1 |
D602913 | Han et al. | Oct 2009 | S |
7606560 | Labrou et al. | Oct 2009 | B2 |
7627967 | Torvik | Dec 2009 | B1 |
7690614 | Mudd et al. | Apr 2010 | B1 |
D615887 | Alexander et al. | May 2010 | S |
7730321 | Gasparini et al. | Jun 2010 | B2 |
7734527 | Uzo | Jun 2010 | B2 |
7753265 | Harris | Jul 2010 | B2 |
7822666 | Bursch | Oct 2010 | B1 |
D628611 | Lewis | Dec 2010 | S |
7870077 | Woo et al. | Jan 2011 | B2 |
7917444 | Bursch | Mar 2011 | B1 |
7941369 | Juras et al. | May 2011 | B2 |
7946502 | Faith et al. | May 2011 | B2 |
7978363 | Takayama | Jul 2011 | B2 |
D646187 | Edgar | Oct 2011 | S |
8041603 | Suk | Oct 2011 | B2 |
8052057 | Smith et al. | Nov 2011 | B2 |
D651530 | Baumgartner et al. | Jan 2012 | S |
8131642 | De Ruiter et al. | Mar 2012 | B2 |
8157175 | Kotlarsky et al. | Apr 2012 | B2 |
8186592 | Fletcher | May 2012 | B2 |
D662534 | Chang | Jun 2012 | S |
8205797 | Tredoux et al. | Jun 2012 | B2 |
8255696 | Florencio et al. | Aug 2012 | B2 |
8290876 | Powell | Oct 2012 | B1 |
8300799 | Steul | Oct 2012 | B2 |
8301494 | Wills | Oct 2012 | B2 |
D671542 | Siekmann et al. | Nov 2012 | S |
D671934 | Alman et al. | Dec 2012 | S |
8335745 | Perlman et al. | Dec 2012 | B2 |
8346670 | Hasson et al. | Jan 2013 | B2 |
8359274 | Yoder et al. | Jan 2013 | B2 |
8364544 | McAlhaney | Jan 2013 | B2 |
8366005 | Kotlarsky et al. | Feb 2013 | B2 |
8380177 | Laracey | Feb 2013 | B2 |
8381969 | Miller et al. | Feb 2013 | B1 |
8386349 | Dixon et al. | Feb 2013 | B2 |
8423466 | Lanc | Apr 2013 | B2 |
D682905 | Kendall et al. | May 2013 | S |
8442894 | Blackhurst et al. | May 2013 | B2 |
8473354 | Psota et al. | Jun 2013 | B2 |
8479992 | Kotlarsky et al. | Jul 2013 | B2 |
D689478 | Wikel et al. | Sep 2013 | S |
8534559 | Drzymala et al. | Sep 2013 | B2 |
8538821 | Nguyen et al. | Sep 2013 | B2 |
8559923 | Drzyzga et al. | Oct 2013 | B2 |
8571996 | Johnson | Oct 2013 | B2 |
8577803 | Chatterjee et al. | Nov 2013 | B2 |
8584251 | McGuire et al. | Nov 2013 | B2 |
8589237 | Fisher | Nov 2013 | B2 |
8595841 | Britton et al. | Nov 2013 | B2 |
8620754 | Fisher | Dec 2013 | B2 |
8620790 | Priebatsch | Dec 2013 | B2 |
8630620 | Cha et al. | Jan 2014 | B2 |
8630851 | Hertschuh et al. | Jan 2014 | B1 |
8635157 | Smith et al. | Jan 2014 | B2 |
8639619 | Priebatsch | Jan 2014 | B1 |
D701894 | Reznik et al. | Apr 2014 | S |
8694438 | Jernigan et al. | Apr 2014 | B1 |
D706145 | Pavlak et al. | Jun 2014 | S |
8770478 | Priebatsch | Jul 2014 | B2 |
D712756 | Rump et al. | Sep 2014 | S |
8838501 | Priebatsch | Sep 2014 | B1 |
8924260 | Priebatsch | Dec 2014 | B1 |
D721371 | Rivera et al. | Jan 2015 | S |
20010032884 | Ring et al. | Oct 2001 | A1 |
20020069155 | Nafeh et al. | Jun 2002 | A1 |
20020095303 | Asayama et al. | Jul 2002 | A1 |
20020120587 | D'Agostino | Aug 2002 | A1 |
20020131444 | Moodie et al. | Sep 2002 | A1 |
20020154342 | Haining | Oct 2002 | A1 |
20020193141 | Wu | Dec 2002 | A1 |
20030004901 | Dutta et al. | Jan 2003 | A1 |
20030059127 | Khovaylo et al. | Mar 2003 | A1 |
20030061170 | Uzo | Mar 2003 | A1 |
20030061171 | Gilbert et al. | Mar 2003 | A1 |
20030074317 | Hofi | Apr 2003 | A1 |
20030171993 | Chappuis | Sep 2003 | A1 |
20030181168 | Herrod et al. | Sep 2003 | A1 |
20030200184 | Dominguez et al. | Oct 2003 | A1 |
20040010463 | Hahn-Carlson et al. | Jan 2004 | A1 |
20040024707 | Perre et al. | Feb 2004 | A1 |
20040039651 | Grunzig et al. | Feb 2004 | A1 |
20040073688 | Sampson | Apr 2004 | A1 |
20040107170 | Labrou et al. | Jun 2004 | A1 |
20040133507 | Barbour | Jul 2004 | A1 |
20040230489 | Goldthwaite et al. | Nov 2004 | A1 |
20050091068 | Ramamoorthy et al. | Apr 2005 | A1 |
20050171900 | Onneken | Aug 2005 | A1 |
20050199727 | Schmidt et al. | Sep 2005 | A1 |
20060095369 | Hofi | May 2006 | A1 |
20060116892 | Grimes et al. | Jun 2006 | A1 |
20060131390 | Kim | Jun 2006 | A1 |
20060151609 | Schonenberg et al. | Jul 2006 | A1 |
20060165060 | Dua | Jul 2006 | A1 |
20060235796 | Johnson et al. | Oct 2006 | A1 |
20070130463 | Law et al. | Jun 2007 | A1 |
20070219905 | Gohmann et al. | Sep 2007 | A1 |
20070233615 | Tumminaro | Oct 2007 | A1 |
20070260544 | Wankmueller | Nov 2007 | A1 |
20070299736 | Perrochon et al. | Dec 2007 | A1 |
20080033880 | Fiebiger et al. | Feb 2008 | A1 |
20080210754 | Lovett | Sep 2008 | A1 |
20080212771 | Hauser | Sep 2008 | A1 |
20080262925 | Kim et al. | Oct 2008 | A1 |
20080281726 | Gupta | Nov 2008 | A1 |
20080281733 | Kubo et al. | Nov 2008 | A1 |
20080319905 | Carlson | Dec 2008 | A1 |
20090024452 | Martinez et al. | Jan 2009 | A1 |
20090198617 | Soghoian et al. | Aug 2009 | A1 |
20090281948 | Carlson | Nov 2009 | A1 |
20090300738 | Dewe et al. | Dec 2009 | A1 |
20100070364 | Dugan | Mar 2010 | A1 |
20100088236 | Karabulut et al. | Apr 2010 | A1 |
20100106569 | Grimes | Apr 2010 | A1 |
20100145861 | Law et al. | Jun 2010 | A1 |
20100218239 | Tang et al. | Aug 2010 | A1 |
20100250290 | Lefkowitz et al. | Sep 2010 | A1 |
20100257023 | Kendall et al. | Oct 2010 | A1 |
20100262546 | Sahota et al. | Oct 2010 | A1 |
20100312649 | Lurie | Dec 2010 | A1 |
20100318412 | Karypis et al. | Dec 2010 | A1 |
20100325053 | Hogg et al. | Dec 2010 | A1 |
20110054981 | Faith et al. | Mar 2011 | A1 |
20110078081 | Pirzadeh et al. | Mar 2011 | A1 |
20110087595 | Sabella | Apr 2011 | A1 |
20110112957 | Ingram et al. | May 2011 | A1 |
20110112968 | Florek et al. | May 2011 | A1 |
20110155799 | Meszaros et al. | Jun 2011 | A1 |
20110161233 | Tieken | Jun 2011 | A1 |
20110191160 | Blackhurst et al. | Aug 2011 | A1 |
20110196796 | Florek et al. | Aug 2011 | A1 |
20110238476 | Carr et al. | Sep 2011 | A1 |
20110246284 | Chaikin et al. | Oct 2011 | A1 |
20110251892 | Laracey | Oct 2011 | A1 |
20110283042 | Jeon et al. | Nov 2011 | A1 |
20120000982 | Gao et al. | Jan 2012 | A1 |
20120011019 | Wakim | Jan 2012 | A1 |
20120016799 | Killian et al. | Jan 2012 | A1 |
20120018516 | Gao et al. | Jan 2012 | A1 |
20120028609 | Hruska | Feb 2012 | A1 |
20120078789 | Harrell | Mar 2012 | A1 |
20120089461 | Greenspan | Apr 2012 | A1 |
20120095855 | Sterling | Apr 2012 | A1 |
20120116861 | Dobyns | May 2012 | A1 |
20120123847 | Wane et al. | May 2012 | A1 |
20120136780 | El-Awady et al. | May 2012 | A1 |
20120150598 | Griggs | Jun 2012 | A1 |
20120150748 | Law et al. | Jun 2012 | A1 |
20120158455 | Pathak et al. | Jun 2012 | A1 |
20120159647 | Sanin et al. | Jun 2012 | A1 |
20120162401 | Melder et al. | Jun 2012 | A1 |
20120166264 | Shum et al. | Jun 2012 | A1 |
20120169857 | Sato | Jul 2012 | A1 |
20120179558 | Fischer | Jul 2012 | A1 |
20120187184 | Challa et al. | Jul 2012 | A1 |
20120191556 | Forbes et al. | Jul 2012 | A1 |
20120197749 | Gray | Aug 2012 | A1 |
20120197801 | Jimenez | Aug 2012 | A1 |
20120203620 | Dobyns | Aug 2012 | A1 |
20120209630 | Ihm et al. | Aug 2012 | A1 |
20120226540 | Batalion et al. | Sep 2012 | A1 |
20120239577 | Wolfs et al. | Sep 2012 | A1 |
20120246015 | Bennett et al. | Sep 2012 | A1 |
20120253852 | Pourfallah et al. | Oct 2012 | A1 |
20120253903 | Tavares et al. | Oct 2012 | A1 |
20120284195 | McMillen et al. | Nov 2012 | A1 |
20120290376 | Dryer et al. | Nov 2012 | A1 |
20120290389 | Greenough et al. | Nov 2012 | A1 |
20120296828 | Bergdale et al. | Nov 2012 | A1 |
20120303425 | Katzin et al. | Nov 2012 | A1 |
20120310838 | Harris et al. | Dec 2012 | A1 |
20120316950 | LaPorte et al. | Dec 2012 | A1 |
20120317036 | Bower et al. | Dec 2012 | A1 |
20120323657 | Tiku et al. | Dec 2012 | A1 |
20120323663 | Leach | Dec 2012 | A1 |
20120330744 | Aissa | Dec 2012 | A1 |
20120330846 | Light et al. | Dec 2012 | A1 |
20130013433 | Rose et al. | Jan 2013 | A1 |
20130018715 | Zhou et al. | Jan 2013 | A1 |
20130024254 | Libenson et al. | Jan 2013 | A1 |
20130043305 | Zhou et al. | Feb 2013 | A1 |
20130046603 | Grigg et al. | Feb 2013 | A1 |
20130080231 | Fisher | Mar 2013 | A1 |
20130080239 | Okerlund | Mar 2013 | A1 |
20130103486 | Hess et al. | Apr 2013 | A1 |
20130103512 | Fisher | Apr 2013 | A1 |
20130103574 | Conrad et al. | Apr 2013 | A1 |
20130110658 | Lyman et al. | May 2013 | A1 |
20130126605 | Rooke et al. | May 2013 | A1 |
20130134213 | Pallakoff et al. | May 2013 | A1 |
20130138491 | Gao et al. | May 2013 | A1 |
20130144792 | Nilsson et al. | Jun 2013 | A1 |
20130145173 | Shablygin et al. | Jun 2013 | A1 |
20130151402 | Howard | Jun 2013 | A1 |
20130158455 | Ruschmeyer et al. | Jun 2013 | A1 |
20130159170 | Gandhi et al. | Jun 2013 | A1 |
20130173475 | Lund | Jul 2013 | A1 |
20130191195 | Carlson et al. | Jul 2013 | A1 |
20130191213 | Beck et al. | Jul 2013 | A1 |
20130197991 | Basu et al. | Aug 2013 | A1 |
20130204690 | Liebmann | Aug 2013 | A1 |
20130204894 | Faith et al. | Aug 2013 | A1 |
20130212007 | Mattsson et al. | Aug 2013 | A1 |
20130218701 | Challa et al. | Aug 2013 | A1 |
20130218721 | Borhan et al. | Aug 2013 | A1 |
20130246203 | Laracey | Sep 2013 | A1 |
20130246266 | Coleman et al. | Sep 2013 | A1 |
20130254028 | Salci | Sep 2013 | A1 |
20130254052 | Royyuru et al. | Sep 2013 | A1 |
20130256403 | MacKinnon Keith | Oct 2013 | A1 |
20130262204 | Stiles et al. | Oct 2013 | A1 |
20130268381 | Randazza et al. | Oct 2013 | A1 |
20130275308 | Paraskeva et al. | Oct 2013 | A1 |
20130276023 | Kent et al. | Oct 2013 | A1 |
20130282581 | Singh | Oct 2013 | A1 |
20130282588 | Hruska | Oct 2013 | A1 |
20130311375 | Priebatsch | Nov 2013 | A1 |
20130325621 | Sanginiti et al. | Dec 2013 | A1 |
20130332251 | Ioannidis et al. | Dec 2013 | A1 |
20130334308 | Priebatsch | Dec 2013 | A1 |
20140006289 | Puthenveetil | Jan 2014 | A1 |
20140019358 | Priebatsch | Jan 2014 | A1 |
20140039999 | Levene et al. | Feb 2014 | A1 |
20140074571 | Hope et al. | Mar 2014 | A1 |
20140074719 | Gressel et al. | Mar 2014 | A1 |
20140129450 | Priebatsch | May 2014 | A1 |
20140263608 | Rivera et al. | Sep 2014 | A1 |
20140279554 | Priebatsch et al. | Sep 2014 | A1 |
20140279556 | Priebatsch et al. | Sep 2014 | A1 |
20140351012 | Jernigan et al. | Nov 2014 | A1 |
20140351030 | Priebatsch | Nov 2014 | A1 |
20140351126 | Priebatsch | Nov 2014 | A1 |
20150019428 | Priebatsch | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
101593197 | Dec 2009 | CN |
102254264 | Nov 2011 | CN |
202221590 | May 2012 | CN |
1467300 | Oct 2004 | EP |
1710980 | Oct 2006 | EP |
2224781 | Sep 2010 | EP |
2507762 | Oct 2012 | EP |
2605202 | Jun 2013 | EP |
2003-187281 | Jul 2003 | JP |
10-2010-0097951 | Sep 2010 | KR |
194379 | Nov 2013 | SG |
0177856 | Oct 2001 | WO |
03084175 | Oct 2003 | WO |
2004053640 | Jun 2004 | WO |
2005017795 | Feb 2005 | WO |
2005086593 | Sep 2005 | WO |
2006039353 | Apr 2006 | WO |
2008069969 | Jun 2008 | WO |
2008148118 | Dec 2008 | WO |
2009012731 | Jan 2009 | WO |
2009131549 | Oct 2009 | WO |
2009151832 | Dec 2009 | WO |
2010064128 | Jun 2010 | WO |
2010133755 | Nov 2010 | WO |
2010141239 | Dec 2010 | WO |
2011028486 | Mar 2011 | WO |
2011056609 | May 2011 | WO |
2011097250 | Aug 2011 | WO |
2011140301 | Nov 2011 | WO |
2011146054 | Nov 2011 | WO |
2012064964 | May 2012 | WO |
2012065128 | May 2012 | WO |
2012078407 | Jun 2012 | WO |
2012097171 | Jul 2012 | WO |
2012119052 | Sep 2012 | WO |
2012125940 | Sep 2012 | WO |
2012151590 | Nov 2012 | WO |
2012154189 | Nov 2012 | WO |
2012158133 | Nov 2012 | WO |
2013006725 | Jan 2013 | WO |
2013012953 | Jan 2013 | WO |
2013049528 | Apr 2013 | WO |
2013051031 | Apr 2013 | WO |
2013068719 | May 2013 | WO |
2013071310 | May 2013 | WO |
2013106679 | Jul 2013 | WO |
2013115853 | Aug 2013 | WO |
2013117738 | Aug 2013 | WO |
2013119914 | Aug 2013 | WO |
2013126815 | Aug 2013 | WO |
2013126894 | Aug 2013 | WO |
2013126996 | Sep 2013 | WO |
2013127579 | Sep 2013 | WO |
2013138195 | Sep 2013 | WO |
2013140196 | Sep 2013 | WO |
2013142209 | Sep 2013 | WO |
2013144929 | Oct 2013 | WO |
2013144930 | Oct 2013 | WO |
2013149578 | Oct 2013 | WO |
2013151797 | Oct 2013 | WO |
2013152247 | Oct 2013 | WO |
2013163217 | Oct 2013 | WO |
2013170228 | Nov 2013 | WO |
Entry |
---|
Bichsel et al., “Data-Minimizing Authentication Goes Mobile”, Lecture Notes in Computer Science, vol. 7394, 2012, pp. 55-71. |
U.S. Appl. No. 13/718,466, filed Dec. 18, 2012 by Priebatsch et al.; Non-Final Office Action mailed May 20, 2013 and Notice of Allowance mailed Nov. 25, 2013. |
U.S. Appl. No. 13/899,760, filed May 22, 2013 by Priebatsch Seth; Non-Final Office Action mailed Oct. 17, 2013; Final Office Action mailed Jan. 29, 2014 and Advisory Action mailed May 19, 2014. |
U.S. Appl. No. 13/901,344, filed May 23, 2013 by Jernigan et al.; Non-Final Office Action mailed Dec. 23, 2013; Final Office Action mailed Jun. 6, 2014. |
U.S. Appl. No. 13/901,352, filed May 23, 2013 by Priebatsch Seth; Non-Final Office Action mailed Dec. 9, 2013; Final Office Action mailed Mar. 3, 2014 and Advisory Action mailed Jun. 3, 2014. |
U.S. Appl. No. 13/925,158, filed Jun. 24, 2013 by Priebatsch Seth; Non-Final Office Action mailed Dec. 6, 2013 and Final Office Action mailed Jun. 26, 2014. |
U.S. Appl. No. 13/939,434, filed Jul. 11, 2013 by Priebatsch Seth; Non-Final Office Action mailed Nov. 15, 2013 and Notice of Allowance mailed Mar. 14, 2014. |
U.S. Appl. No. 13/939,676, filed Jul. 11, 2013 by Priebatsch Seth; Notice of Allowance mailed Oct. 17, 2013. |
U.S. Appl. No. 13/960,260, filed Aug. 6, 2013 by Jernigan et al.; Notice of Allowance mailed Jan. 28, 2014. |
U.S. Appl. No. 14/097,737, filed Dec. 5, 2013 by Priebatsch Seth; Non-Final Office Action mailed May 9, 2014. |
U.S. Appl. No. 14/107,677, filed Dec. 16, 2013 by Priebatsch Seth; Non-Final Office Action mailed Mar. 4, 2014 and Non-Final Office Action mailed Jul. 9, 2014. |
U.S. Appl. No. 14/172,163, filed Feb. 4, 2014 by Priebatsch Seth; Non-Final Office Action mailed Apr. 30, 2014. |
U.S. Appl. No. 14/174,116, filed Feb. 6, 2014 by Priebatsch Seth; Non-Final Office Action mailed Apr. 25, 2014. |
U.S. Appl. No. 14/189,482, filed Feb. 25, 2014 by Priebatsch Seth; Non-Final Office Action mailed May 8, 2014. |
U.S. Appl. No. 14/190,695, filed Feb. 26, 2014 by Priebatsch Seth; Notice of Allowance mailed May 15, 2014. |
U.S. Appl. No. 14/227,514, filed Mar. 27, 2014 by Priebatsch, Seth; Non-Final Office Action mailed Jul. 31, 2014. |
U.S. Appl. No. 13/797,287, filed Mar. 12, 2013 by Jernigan, Charles Carter Carter et al. |
U.S. Appl. No. 13/864,754, filed Apr. 17, 2013 by Priebatsch, Seth. |
U.S. Appl. No. 14/103,101, filed Dec. 11, 2013 by Priebatsch, Seth. |
U.S. Appl. No. 29/449,235, filed Mar. 14, 2013 by Steve S. Rivera et al. |
U.S. Appl. No. 14/307,066, filed Jun. 17, 2014 by Priebatsch, Seth et al. |
U.S. Appl. No. 14/460,628, filed Aug. 15, 2014 by Priebatsch, Seth. |
Number | Date | Country | |
---|---|---|---|
20150014413 A1 | Jan 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13939434 | Jul 2013 | US |
Child | 14283771 | US |