Payment object reading devices are devices that read information from payment objects, such as credit cards. Payment object reading devices typically include circuitry that reads, stores, or conveys sensitive information such as a customer's credit card number or personal identification number (“PIN”). If such circuitry of the payment object reader is left unprotected, a malicious party could potentially retrieve a customer's sensitive information by accessing the circuitry of the payment object reader that reads, stores, or conveys the sensitive information.
A secure enclosure refers to an enclosure or housing that includes tamper detection circuitry integrated into the enclosure or housing itself. Circuitry that is within the secure enclosure is protected or secured, while circuitry that is outside of the secure enclosure is generally unprotected and unsecured. A processor can be within a secure enclosure to protect or secure the processor. Tamper detection circuitry can interface with such a secured processor to help the secured processor identify an attempt by a malicious party to tamper with the secure enclosure.
An output device such as a speaker or a display can be controlled by a processor to output audio or to display visual media, respectively.
There is a need in the art for sharing of output devices between a secured processor and an unsecured processor, for example in a payment object reading device.
A point of sale (POS) device includes an output device such as a speaker, a display screen, or a network interface. The POS device also includes a secure enclosure housing a secure processor and tamper detection circuitry for detecting attempts to tamper with the secure enclosure. Use of the output device is shared between the secure processor and a main processor via a switch that is controlled by the secure processor. The secure processor can switch control of the output device from the main processor to itself and can output an output dataset via the output device in a number of scenarios. These scenarios include the secure processor detecting an attempt to tamper with the secure enclosure, the secure processor recognizing that the main processor is behaving suspiciously, or the secure processor wanting to output sensitive information. The output dataset may include visual data, audio data, or network data.
The terms “main processor 110” and “secure processor 120” as used herein should be understood to each include a set of one or more of any type of processor(s), controller(s), microcontroller(s), application specific integrated circuit(s) (ASIC), or combinations thereof. The “main processor 110” and “secure processor 120” may include any circuit board component illustrated or discussed with respect to the “processor(s)/controller(s) 710” or any of the rest of the circuit board components 700 illustrated or discussed with respect to
The main processor 110 and/or secure processor 120 may run a one or more operating systems such as Google® Android®, Apple® iOS®, Microsoft® Windows®, Google® Chrome OS®, Apple® MacOS®, Microsoft® Windows Phone OS®, a distribution of Linux®, or some combination thereof. The main processor 110 and/or secure processor 120 may include instructions for one or more applications, such as financial applications, point of sale (POS) applications, transit pass applications, or ticketing applications that may send data acquired from transaction object reader circuitry 770 as illustrated and discussed with respect to
The output device 170 of
The switch 130 allows either the secure processor 150 or the main processor 110 electrically couple to and thereby control output device circuitry 150 that electrically couples to, controls, and/or drives the output device 170. The switch 130 may be or include at least a transistor, such as a field effect transistor (FET).
The state of the switch 130 is controlled by the secure processor 150 via a control input/pin, such as a gate pin of a transistor. The switch 130 is located inside the secure enclosure 180 to prevent a main processor 110 that is misbehaving, malfunctioning, or compromised by a malicious party from inappropriately taking control of the output device circuitry 150. Alternate embodiments could have the switch 130 located outside of the secure enclosure 180 and/or controlled by the main processor 110, but this would likely be less secure in the event of a misbehaving main processor 110.
The switch 130 of
Instruction signals 140 coming from either processor through the switch 130 and to the output device circuitry 150 may be digital signals using control/communication protocols and/or standards such as Inter-Integrated Circuit (I2C), Universal Asynchronous Receiver/Transmitter (UART), Universal Synchronous/Asynchronous Receiver/Transmitter (USART), Serial Peripheral Interfaces (SPI), Universal Serial Bus (U6B), or some combination thereof. Output signals 160 between the output device circuitry 150 and the output device 170 may include analog signals and may be scrambled, encrypted, filtered, use a proprietary or non-standard format, be otherwise difficult to interpret, or some combination thereof. Scrambling may involve sending different portions of information in an unusual order, for example. Generally, output signals 160 are more difficult to interpret than the instruction signals 140 and therefore it is safer for them to be conveyed outside of the secure enclosure 180 than for the instruction signals 140 to be conveyed outside of the secure enclosure 180. The output device circuitry 150 of
The output device circuitry 150 may include hardware and/or software elements that restrict and/or prevent information from flowing “backwards” through the switch 130 from the from the output device 170 and to the secure processor 120, in case a malicious party attempts to access or alter the secure processor 150 in this manner. The hardware and/or software elements that restrict and/or prevent information from flowing “backwards” through the switch 130 may include diodes, such as isolation diodes.
The switch 130 of
The output device circuitry 150 of
The architecture illustrated in
The architecture illustrated in
The architecture illustrated in
An output-sharing circuit can be made with any combination of features/elements illustrated in and/or discussed with respect to
Step 205 includes transmitting a first output instruction from the main processor 110 to the output device through a switch 130 while the switch 130 is in a first state. This first output instruction may be, for example, an instruction from a transaction application running on the main processor 110 to output a transaction user interface to be used by the main processor to conduct a transaction, such as between a buyer and a merchant.
Such a transaction may involve receiving transaction information at the secure processor 120 from a transaction object such as a credit card via transaction object reader circuitry 770. The transaction may optionally include processing the transaction information at the secure processor 120 by encrypting it, password-protecting it, stripping out certain information, reformatting it, or converting it from one format to another, or some combination thereof, before sending the transaction information from the secure processor 120 to the main processor 110, after processing if applicable. Once the main processor 110 receives the processed transaction information from the secure processor 120, the main processor 110 then sends the processed transaction information from the main processor 110 to a transaction server such as a credit card server or bank server via a wired or wireless network interface, where the transaction server ensures that an appropriate transaction amount is transferred from a buyer account to a merchant account. The transaction user interface may incorporate a number of user interfaces that, for example, can assist the buyer or merchant in identifying/tabulating/totaling purchased items and amounts, instruct the buyer or merchant as to when to swipe or insert or tap or remove a transaction card or other transaction object, or ask the buyer about memberships associated with the merchant, charity donations to give along with the transaction, tip percentages/amounts associated with the transaction, whether the buyer wants a paper/plastic bag and if so what kind, and the like.
Step 210 includes outputting a first output via the output device while the switch 130 is in the first state in which the main processor 110 is electrically coupled through the switch 130 to the output device 170 as discussed with respect to
Step 210 may alternately be followed by step 205, step 215, or step 225.
Step 215 includes detecting, at a secure processor 120 and via tamper detection circuitry electrically coupled to the secure processor 120, an attempt to tamper with a secure enclosure.
The tamper detection circuitry can include a variety of different types of sensors and sensing methods. The tamper detection circuitry can use a “tamper mesh,” in which two long conductive tamper trace lines run in parallel and in a zig-zagging or boustrophedonic pattern that covers at least a majority of at least one surface of the secure enclosure 180. The two tamper trace lines are at different voltages, and the tamper detection circuitry includes voltage sensors that detect any changes in voltage along either or both lines. A malicious party attempting to drill into the secure enclosure 180 would likely break at least one of these conductive trace lines, connect the two lines together via the conductive metal of the drill itself, short two portions of the same line together via the conductive metal of the drill itself, or some combination thereof—all of which can be detectable as a voltage fluctuation/change over a predefined voltage change threshold as measured via the voltage sensors. The tamper detection circuitry can include inductive sensors that detect nearby objects that are metal or have conductive properties in response to an inductive sensor measurement exceeding a predefined threshold. The tamper detection circuitry can include capacitive sensors that detect touches to surface(s) of the secure enclosure 180 in response to a capacitive sensor measurement exceeding a predefined threshold, where the surface(s) of the secure enclosure 180 should remain internal and should not be touched. The detection of step 210 may include any of these sensors or any combination thereof.
Step 220 includes toggling the switch 130 from the first state to a second state via the secure processor 120 in response to detecting the attempt to tamper with the secure enclosure. In the second state, the secure processor 120 is electrically coupled through the switch 130 to the output device 170 as discussed with respect to
Step 225 includes detecting, at a secure processor 120, that the main processor 110 is likely to be compromised. This detection may be based on receipt of a warning by the secure processor 120 from security software and/or hardware. For example, such a warning may include an indication of unexpected or unsanctioned network activity from a firewall, an indication of virus detection from an antivirus program, an indication of adware detection from an anti-adware program, an indication of spyware detection from an anti-spyware program, an indication of malware detection from an anti-malware program, or some combination thereof. This detection may additionally or alternatively be based on detection of unusual behavior at the main processor 110, such as if the main processor 110 attempts to output a “spoof” of a user interface normally output through or in conjunction with the secure processor 120. Such as “spoof” user interface might, for example, attempt to simulate an “enter PIN” or “enter signature” user interface that would normally send the resulting PIN or signature from the user to the secure processor 120, but where the “spoof” version would instead collect the PIN or signature from the user at the main processor 110. A malicious party taking over the main processor 110 could then steal sensitive information, such as a PIN or signature, from a user. Therefore, detection of such as “spoof” interface by searching for similarities to legitimate security interfaces would be one way to detect that the main processor 110 is likely to be compromised at step 225.
Step 230 includes toggling the switch 130 from the first state to a second state via the secure processor 120 in response to detecting that the main processor 110 is likely to be compromised.
Step 235 includes transmitting a second output instruction from the secure processor 120 to the output device 170 through the switch 130 while the switch 130 is in the second state. Step 235 here could be preceded by step 220 and/or 230 and can occur in response to either or both of those. The second output instruction here could a warning user interface indicating that the POS device is likely tampered with or compromised based on the detections of step 215 and/or 225.
Step 240 includes outputting a second output via the output device while the switch 130 is in the second state. Various format conversions, such as digital to analog, may occur between step 235 and 240, as discussed with respect to the instruction signals 140, output device circuitry 150, and output signals 160 of
Step 250 includes transmitting a first output instruction from the main processor 110 to the output device through a switch 130 while the switch 130 is in a first state. This is similar to step 205 of
Step 255 includes outputting a first output via the output device while the switch 130 is in the first state. This is similar to step 210 of
Step 260 includes receiving and accessing sensitive information at the secure processor 120, wherein the main processor 110 lacks access to the sensitive information.
The sensitive information can include different types of data and can come from a different sources/components. The sensitive information may include payment object information, such as a credit or debit card number, expiration date, or security code, or some combination thereof received from transaction object reader circuitry 770. The sensitive information may include personal user financial information, such as a bank account balance, a debt amount, an interest rate, an unpaid bill, a paid bill, or some combination thereof received from a wired and/or wireless network interface. The sensitive information may include a PIN code, signature, or user interface selection from a keypad, keyboard, mouse, touchscreen, or touch-sensitive surface of the POS device, or a touch-sensitive or a memory within the secure enclosure 180.
The sensitive information may be scrambled, encrypted, password-protected, or otherwise difficult to read. The term “access” as used with respect to step 260 thus may refer to read access, indicating that the main processor 110 cannot read and/or decrypt and/or unscramble the sensitive information even though it might be capable of retrieving an encrypted, scrambled, or password-protected copy of the sensitive information. On the other hand, the term “access” as used with respect to step 260 may simply refer to the ability (or lack thereof) of the main processor 110 to retrieve any copy of the sensitive information, encrypted/scrambled/protected or not.
Step 265 includes toggling the switch 130 from the first state to a second state via the secure processor 120 in response to receiving the sensitive information.
Step 270 includes transmitting a second output instruction from the secure processor 120 to the output device through the switch 130 while the switch 130 is in the second state.
Step 275 includes outputting a second output via the output device while the switch 130 is in the second state, wherein the second output includes the sensitive information. Various format conversions, such as digital to analog, may occur between step 270 and 275, as discussed with respect to the instruction signals 140, output device circuitry 150, and output signals 160 of
The main processor 110 of
The secure processor 120 of
The main processor 110 of
The secure processor 120 of
The H-Bridge 320 may be driven with power from the secure processor 120, the main processor 110, a battery within or outside of the secure enclosure 180, some other power source, or some combination thereof. The speaker output 330 may be driven with power from the secure processor 120, the main processor 110, a battery within or outside of the secure enclosure 180, some other power source, or some combination thereof. The headset output 340 may be driven with power from the secure processor 120, the main processor 110, a battery within or outside of the secure enclosure 180, some other power source, or some combination thereof.
An output-sharing circuit can be made with any combination of features/elements illustrated in and/or discussed with respect to
The payment object reader device 400 of
The touch-sensitive surface circuitry 492 may be a touch-sensitive layer that detects touches of a touchscreen whose display screen portion is the display screen 466. Having the touch-sensitive surface circuitry 492 in the secure enclosure 180 and connected to both the secure processor 120 and the main processor 110 allows sensitive user inputs, such as a personal identification number (PIN) code or a password or a personal telephone number, to be routed to the secure processor 120, while non-sensitive user inputs can be routed to the main processor 110.
The secure processor 120 is electrically coupled to a separate battery 474, the touch-sensitive surface circuitry 492, tamper detection circuitry 476 of the secure enclosure 180 itself, one or more magstripe read head(s) 480 for reading magnetic stripe transaction cards, and various transaction object reader circuitry 770. The transaction object reader circuitry 770 of
The transaction object reader circuitry 770 of
The audio output 464 may be a speaker output 330, a headset output 340, any other type of audio circuitry discussed with respect to the output device circuitry 750 of
The charge and/or communication connector 452 may be a port, a plug, or a wireless transceiver, or some combination thereof, and can be used to connect the payment object reader device 400 to a power source. The portable computing device can provide power to the payment object reader device 400. The charge and/or communication port 452 can be, for example, a Universal Serial Bus (USB) port, an Apple® Lightning® port, or a TRS or TRRS audio/microphone jack port. Power coming into the payment object reader device 400 via the charge and/or communication port 452 can power the main processor 110, the secure processor 120, audio output 464, display screen 466, the transaction object reader circuitry 770 of
In particular, switch 130A of
Like
The H-bridge 320A of
Resistors R1 and R2 positioned as in
The H-bridge 320A of
Resistors R1 and R2 positioned as in
The payment object reader device 400 of
The connections between the payment object reader device 400 and the host device 490 of
It should be understood that the payment object reader devices 400 of
A payment object reader device 400 can be made with any combination of features/elements illustrated in and/or discussed with respect to
The H-bridge 320 of
The H-bridge 320 of
When all of the switches are in their “off” state—that is, when they are all open and not conducting—the secure processor 120 does not drive output (e.g., audio) to the load 550. This state occurs when the first control input 540 and second control input 545 are in an “off” state.
When the first control input 540 is in an “on” state, the switches 515A and 520A are in an “on” state—that is, a closed state—and therefore conduct. Power is driven through the load 550 and through closed switches 515A and 520A.
When the second control input 545 is in an “on” state, the switches 510A and 525A are in an “on” state—that is, a closed state—and therefore conduct. Power is driven through the load 550 and through closed switches 510A and 525A.
The H-bridge 320 of
The four switches 510A, 515A, 520A, and 525A of
In
The H-bridge 320 otherwise functions similarly to the one in
The H-bridge 320 can be made with any combination of features/elements illustrated in and/or discussed with respect to
The H-bridge 320 of
The secure processor 120 is illustrated as connecting to the control inputs of
As in
The control inputs of
The H-bridge 320 illustrated in any of
In some cases, the H-bridge 320 may be replaced with or supplemented by a switch or transistor set up similarly to the switch illustrated in
The H-bridge 320 can be made with any combination of features/elements illustrated in and/or discussed with respect to
The circuit board components 700 of
The circuit board components 700 of
The circuit board components 700 of
The circuit board components 700 of
The circuit board components 700 of
The circuit board components 700 of
Transaction object reader circuitry 770 may include, for example, a magnetic read head or other type of magnetic stripe reader that is capable of reading information from a magnetic stripe of a transaction card. Transaction object reader circuitry 770 can also include an integrated circuit (IC) chip reader and/or smartcard chip reader for reading an IC chip and/or smartcard chip embedded in a transaction card. Such an IC chip/smartcard chip can follow the Europay-Mastercard-Visa (EMV) payment chip standard. The IC chip/smartcard chip reader can be contact-based, in that it can include one or more conductive prongs that contact a conductive metal contact pad of the IC chip/smartcard chip. The IC chip/smartcard chip can instead be contactless and use a contactless antenna. The contactless antenna can also double as a receiver for near-field-communication (NFC) signals, radio-frequency identification (RFID) signals, Bluetooth® wireless signals, wireless local area network (WLAN) signals, 802.xx Wi-Fi signals, or some combination thereof, which can be sent from a transaction card or from a another type of transaction object as discussed above. In some cases, a transaction object may only send these wireless signals in response to receipt of a magnetic field or other wireless signals from the transaction object reader circuitry 770. For example, if the transaction object is a passive NFC/RFID tag or functions based on similar technology, it generates energy from the magnetic field or other wireless signals from the transaction object reader circuitry 770 via induction coil(s) that is then used to transmit the wireless signals that are ultimately read by the transaction object reader circuitry 770.
The information read from the transaction object by the transaction object reader circuitry 770, regardless of the type of the transaction object, may include at least credit card information, debit card information, automated teller machine (ATM) information, gift card account information, transit account information, identification card information, game token card information, ticket information, bank account information, credit union account information, online gaming account information, HSA/FSA account information, health insurance account information, healthcare information, or some combination thereof. Certain terms discussed herein should be understood to refer to transaction objects, including but not limited to “payment object,” “transaction object,” “financial object,” “payment card,” “transaction card,” or “financial card.”
Peripheral circuitry 780 may include any type circuitry permitting connection and use of computer support devices to add additional functionality to the circuit board 100. For example, peripheral circuitry 780 may support connection of a modem or a router. The components shown in
While various flow diagrams have been described above, it should be understood that these show a particular order of operations performed by certain embodiments of the invention, and that such order is exemplary. Alternative embodiments can perform the operations in a different order, combine certain operations, or overlap certain operations illustrated in or described with respect to each flow diagram.
The foregoing detailed description of the technology has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology, its practical application, and to enable others skilled in the art to utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claim.
This application claims the benefit of U.S. Provisional Application No. 62/578,657, filed Oct. 30, 2017, entitled, “Sharing Output Device Between Unsecured Processor and Secured Processor”, which is hereby incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
3128349 | Nash | Apr 1964 | A |
4758714 | Carlson | Jul 1988 | A |
4776003 | Harris | Oct 1988 | A |
4860336 | D'Avello | Aug 1989 | A |
5221838 | Gutman | Jun 1993 | A |
5351296 | Sullivan | Sep 1994 | A |
5388155 | Smith | Feb 1995 | A |
5408513 | Busch, Jr. | Apr 1995 | A |
5714741 | Pieterse | Feb 1998 | A |
5729591 | Bailey | Mar 1998 | A |
5740232 | Pailles | Apr 1998 | A |
5752046 | Oprescu | May 1998 | A |
5838773 | Eisner | Nov 1998 | A |
5850599 | Seiderman | Dec 1998 | A |
5867795 | Novis | Feb 1999 | A |
5940510 | Curry | Aug 1999 | A |
6010067 | Elbaum | Jan 2000 | A |
6065679 | Levie | May 2000 | A |
6098881 | DeLand, Jr. | Aug 2000 | A |
6144336 | Preston | Nov 2000 | A |
6234389 | Valliani | May 2001 | B1 |
6278779 | Bryant | Aug 2001 | B1 |
6481623 | Grant | Nov 2002 | B1 |
6600823 | Hayosh | Jul 2003 | B1 |
6886742 | Stoutenburg | May 2005 | B2 |
6990683 | Itabashi | Jan 2006 | B2 |
7003316 | Elias | Feb 2006 | B1 |
7066382 | Kaplan | Jun 2006 | B2 |
7083090 | Zuili | Aug 2006 | B2 |
7124937 | Myers | Oct 2006 | B2 |
7163148 | Durbin | Jan 2007 | B2 |
7210627 | Morley, Jr. | May 2007 | B2 |
7343496 | Hsiang et al. | Mar 2008 | B1 |
7363054 | Elias et al. | Apr 2008 | B2 |
7424732 | Matsumoto | Sep 2008 | B2 |
7433452 | Taylor | Oct 2008 | B2 |
7506956 | Usui | Mar 2009 | B2 |
7591425 | Zuili et al. | Sep 2009 | B1 |
7673799 | Hart | Mar 2010 | B2 |
7810729 | Morley, Jr. | Oct 2010 | B2 |
7896248 | Morley, Jr. | Mar 2011 | B2 |
8086531 | Litster | Dec 2011 | B2 |
8126734 | Dicks | Feb 2012 | B2 |
8265553 | Cheon | Sep 2012 | B2 |
8355003 | Pope | Jan 2013 | B2 |
8397988 | Zuili | Mar 2013 | B1 |
8553055 | Martell | Oct 2013 | B1 |
8702007 | Yisraelian | Apr 2014 | B2 |
9020853 | Hoffman | Apr 2015 | B2 |
9092766 | Bedier | Jul 2015 | B1 |
9223376 | Derbyshire | Dec 2015 | B2 |
9344281 | Kobres | May 2016 | B2 |
9355277 | Kobres | May 2016 | B2 |
9396368 | Lamba et al. | Jul 2016 | B1 |
9489703 | Kauniskangas | Nov 2016 | B2 |
9529758 | Szeto | Dec 2016 | B1 |
9590747 | Thoukydides | Mar 2017 | B2 |
9607181 | Matsumoto | Mar 2017 | B2 |
9659441 | Kelly et al. | May 2017 | B2 |
9679286 | Colnot et al. | Jun 2017 | B2 |
9824350 | Dorsey et al. | Nov 2017 | B2 |
10140604 | Douthat et al. | Nov 2018 | B1 |
10182328 | Maibach | Jan 2019 | B1 |
10733589 | Douthat et al. | Aug 2020 | B2 |
20020091633 | Proctor | Jul 2002 | A1 |
20020153414 | Stoutenburg | Oct 2002 | A1 |
20030135418 | Shekhar | Jul 2003 | A1 |
20030154414 | von Mueller | Aug 2003 | A1 |
20030183691 | Lahteenmaki | Oct 2003 | A1 |
20030200108 | Malnoe | Oct 2003 | A1 |
20040012875 | Wood | Jan 2004 | A1 |
20040041911 | Odagiri | Mar 2004 | A1 |
20040059682 | Hasumi | Mar 2004 | A1 |
20040088449 | Sakaki | May 2004 | A1 |
20040167820 | Melick | Aug 2004 | A1 |
20040204082 | Abeyta | Oct 2004 | A1 |
20040251908 | Knopf | Dec 2004 | A1 |
20050097015 | Wilkes | May 2005 | A1 |
20050109841 | Ryan | May 2005 | A1 |
20050179956 | Silverbrooks | Aug 2005 | A1 |
20050236480 | Vrotsos | Oct 2005 | A1 |
20060032905 | Bear | Feb 2006 | A1 |
20060049255 | von Mueller | Mar 2006 | A1 |
20060049256 | von Mueller | Mar 2006 | A1 |
20060056401 | Bohm | Mar 2006 | A1 |
20060223580 | Antonio | Oct 2006 | A1 |
20070067833 | Colnot | Mar 2007 | A1 |
20070168300 | Quesselaire | Jul 2007 | A1 |
20070194104 | Fukuda | Aug 2007 | A1 |
20070198436 | Weiss | Aug 2007 | A1 |
20080091617 | Hazel | Apr 2008 | A1 |
20080104631 | Krock | May 2008 | A1 |
20080148394 | Poidomani | Jun 2008 | A1 |
20080238687 | Ozer | Oct 2008 | A1 |
20090070583 | von Mueller et al. | Mar 2009 | A1 |
20090112768 | Hammad | Apr 2009 | A1 |
20090164326 | Bishop | Jun 2009 | A1 |
20090271270 | Regmi et al. | Oct 2009 | A1 |
20090317161 | Vo et al. | Dec 2009 | A1 |
20100057620 | Li | Mar 2010 | A1 |
20100220136 | Sheahan et al. | Sep 2010 | A1 |
20100243732 | Wallner | Sep 2010 | A1 |
20110019234 | Nakamura | Jan 2011 | A1 |
20110078034 | Hayhow | Mar 2011 | A1 |
20110080422 | Lee et al. | Apr 2011 | A1 |
20110321173 | Weston | Dec 2011 | A1 |
20120039469 | Mueller et al. | Feb 2012 | A1 |
20120060041 | Hashimoto | Mar 2012 | A1 |
20120203620 | Dobyns | Aug 2012 | A1 |
20130013515 | Walters | Jan 2013 | A1 |
20130079037 | Dobyns | Mar 2013 | A1 |
20130094668 | Poulsen et al. | Apr 2013 | A1 |
20130103190 | Carapelli | Apr 2013 | A1 |
20130262708 | McLeod | Oct 2013 | A1 |
20140021254 | Marshall | Jan 2014 | A1 |
20140108241 | Tunnell | Apr 2014 | A1 |
20140127995 | Hendricksen | May 2014 | A1 |
20140191913 | Ge | Jul 2014 | A1 |
20140206339 | Lindoff | Jul 2014 | A1 |
20140249942 | Hicks | Sep 2014 | A1 |
20140295777 | Wang | Oct 2014 | A1 |
20140368339 | Thaker et al. | Dec 2014 | A1 |
20150199882 | Fernando | Jul 2015 | A1 |
20150227485 | Maung | Aug 2015 | A1 |
20150254621 | Matsumoto | Sep 2015 | A1 |
20150269805 | Korala | Sep 2015 | A1 |
20150302708 | Hattori | Oct 2015 | A1 |
20160014623 | Tanner et al. | Jan 2016 | A1 |
20160117662 | Bedier | Apr 2016 | A1 |
20160125376 | Beatty | May 2016 | A1 |
20160154967 | Lee et al. | Jun 2016 | A1 |
20160174038 | Menardais et al. | Jun 2016 | A1 |
20160211843 | Wang | Jul 2016 | A1 |
20160275478 | Li et al. | Sep 2016 | A1 |
20160307010 | Ge | Oct 2016 | A1 |
20160307171 | Haga | Oct 2016 | A1 |
20160335132 | Ash et al. | Nov 2016 | A1 |
20170004485 | Lee et al. | Jan 2017 | A1 |
20170017943 | Bilhan | Jan 2017 | A1 |
20170076269 | Saeed et al. | Mar 2017 | A1 |
20170160819 | Yi et al. | Jun 2017 | A1 |
20170220822 | Kobres | Aug 2017 | A1 |
20170255927 | Dorsey | Sep 2017 | A1 |
20170300893 | Sasaki et al. | Oct 2017 | A1 |
20170309137 | Shah et al. | Oct 2017 | A1 |
20170337403 | Ohno | Nov 2017 | A1 |
20180026373 | Schwent | Jan 2018 | A1 |
20180314661 | Douthat | Nov 2018 | A1 |
20180316815 | Douthat | Nov 2018 | A1 |
20200334657 | Douthat et al. | Oct 2020 | A1 |
20210216988 | Binder et al. | Jul 2021 | A1 |
Number | Date | Country |
---|---|---|
2324402 | Jun 2002 | AU |
20320080 | Apr 2004 | DE |
201 22 899 | Sep 2009 | DE |
0 895 203 | Feb 1999 | EP |
1205895 | May 2002 | EP |
1 874 014 | Jan 2008 | EP |
2 965 167 | Jan 2016 | EP |
2 812 744 | Feb 2002 | FR |
2 812 745 | Feb 2002 | FR |
2 834 156 | Jun 2003 | FR |
H09231285 | Sep 1997 | JP |
2000-030146 | Jan 2000 | JP |
2000-071580 | Mar 2000 | JP |
2000-276539 | Oct 2000 | JP |
2001-222595 | Aug 2001 | JP |
2002-074507 | Mar 2002 | JP |
2002-123771 | Apr 2002 | JP |
2002-137506 | May 2002 | JP |
2002-279320 | Sep 2002 | JP |
2002-352166 | Dec 2002 | JP |
2002-358285 | Dec 2002 | JP |
2003-108777 | Apr 2003 | JP |
2003-281453 | Oct 2003 | JP |
2003-308438 | Oct 2003 | JP |
2003-316558 | Nov 2003 | JP |
2004-054651 | Feb 2004 | JP |
2004-062733 | Feb 2004 | JP |
2004-078553 | Mar 2004 | JP |
2004-078662 | Mar 2004 | JP |
2004-157604 | Jun 2004 | JP |
2004-199405 | Jul 2004 | JP |
2004-351899 | Dec 2004 | JP |
2006-195589 | Jul 2006 | JP |
4248820 | Apr 2009 | JP |
2010-218196 | Sep 2010 | JP |
2013-511787 | Apr 2013 | JP |
2013-086448 | May 2013 | JP |
2015-170356 | Sep 2015 | JP |
2016-514442 | May 2016 | JP |
2017-056698 | Mar 2017 | JP |
10-1999-0066397 | Aug 1999 | KR |
10-1999-0068618 | Sep 1999 | KR |
200225019 | Mar 2001 | KR |
10-2003-0005936 | Jan 2003 | KR |
10-2003-0005984 | Jan 2003 | KR |
10-2003-0012910 | Feb 2003 | KR |
200333809 | Nov 2003 | KR |
10-2004-0016548 | Feb 2004 | KR |
100447431 | Aug 2004 | KR |
200405877 | Jan 2006 | KR |
100649151 | Nov 2006 | KR |
10-2007-0107990 | Nov 2007 | KR |
100842484 | Jun 2008 | KR |
2284578 | Sep 2006 | RU |
1998012674 | Mar 1998 | WO |
2000011624 | Mar 2000 | WO |
2000025277 | May 2000 | WO |
2001086599 | Nov 2001 | WO |
2002033669 | Apr 2002 | WO |
2002043020 | May 2002 | WO |
2002082388 | Oct 2002 | WO |
2002084548 | Oct 2002 | WO |
2003044710 | May 2003 | WO |
2003079259 | Sep 2003 | WO |
2004023366 | Mar 2004 | WO |
2006131708 | Dec 2006 | WO |
2017053699 | Mar 2017 | WO |
2018200730 | Nov 2018 | WO |
2018200732 | Nov 2018 | WO |
Entry |
---|
Final office Action dated Mar. 11, 2019, for U.S. Appl. No. 15/582,174, of Douthat, C., et al., filed Apr. 28, 2017. |
Non-Final Office Action dated Jul. 28, 2017, for U.S. Appl. No. 15/597,035, of Douthat, C., et al., filed May 16, 2017. |
Final Office Action dated Jan. 12, 2018, for U.S. Appl. No. 15/597,035, of Douthat, C., et al., filed May 16, 2017. |
Non-Final Office Action dated Apr. 16, 2018, for U.S. Appl. No. 15/620,642, of Maibach, M.H., et al., filed Jun. 12, 2017. |
International Search Report and Written Opinion for International Application No. PCT/US2018/029451, dated Sep. 17, 2018. |
Non-Final Office Action dated Jul. 25, 2019, for U.S. Appl. No. 15/599,826, of Dorsey, J., et al., filed May 19, 2017. |
Non-Final Office Action dated Oct. 1, 2019, for U.S. Appl. No. 15/582,166, of Douthat, C., et al., filed Apr. 28, 2017. |
“Connection of Terminal Equipment to the Telephone Network,” FCC 47 CFR Part 68, Retrieved from the URL: http://www.tscm.com/FCC47CFRpart68.pdf, on Sep. 24, 2019 Oct. 1, 1999 Edition. |
“Embedded FINancial transactional IC card READer,” Retrieved from the URL: https://cordis.europa.eu/project/rcn/58338/factsheet/en. |
Geethapriya Venkataramani and Srividya Gopalan., “Mobile phone based RFID architecture for secure electronic payments using RFID credit cards,” 2007 IEEE, (ARES'07). |
“Guideline for the Useof Advanced Authentication Technology,” FIPS 190, Sep. 28, 1994. |
“Identification cards—Recording technique—Part 4—Location of read-only magnetic tracks—Track 1 and 2,” ISO/IEC 7811-4:1995, International Organization for Standardization, Aug. 1995. |
Jerome Svigals., “The Long Life and Imminent Death of the Mag-stripe Card,” IEEE Spectrum, vol. 49, Issue 61, Jun. 2012. |
“Magensa's Decryption Services and MagTek's MagneSafe™ Bluetooth Readers Selected by eProcessing Network to Implement Secure Customer Card Data with Mobile Devices,” Retrieved from the URL: https://www.magnensa.net/aboutus/articles/eProcessing - rev1.pdf Apr. 14, 2008. |
Martha E. Haykin et al., “Smart Card Technology: New Methods for Computer Access Control,” NIST Special Publication 500-157, Sep. 1988. |
“MSP430x1xx Family User's Guide,” (including 2016 correction sheet at 2), Texas Instruments Inc., 2006. |
Spegele, Joseph Brain., “A Framework for Evaluating Application of Smart Cards and Related Technology Within the Department of Defense,” Naval Postgraduate School, Jan. 1995. |
Stephen A. Sherman et al., “Secure Network Access Using Multiple Applications of AT&T's Smart Card,” AT&T Technical Journal, Sep./Oct. 1994. |
Notice of Allowance dated Jul. 18, 2018, for U.S. Appl. No. 15/597,035, of Douthat, C., et al., filed May 16, 2017. |
Notice of Allowance dated Sep. 6, 2018, for U.S. Appl. No. 15/620,642, of Maibach, M.H., et al., filed Jun. 12, 2017. |
Non-Final Office Action dated Sep. 7, 2018, for U.S. Appl. No. 15/582,174, of Douthat, C., et al., filed Apr. 28, 2017. |
International Search Report and Written Opinion for International Application No. PCT/US2018/029449, dated Jul. 31, 2018. |
Notice of Allowance dated Oct. 24, 2019, for U.S. Appl. No. 15/582,174, of Douthat, C., et al., filed Apr. 28, 2017. |
Non-Final Office Action dated Jan. 27, 2020, for U.S. Appl. No. 15/836,713, of Douthat, C., et al., filed Dec. 8, 2017. |
Non-Final Office Action dated Jun. 15, 2020, for U.S. Appl. No. 15/836,753, of Binder, J. et al., filed Dec. 8, 2017. |
Notice of Allowance dated Mar. 25, 2020, for U.S. Appl. No. 15/582,166, of Douthat, C., et al., filed Apr. 28, 2017. |
European Office Action for European Patent Application No. 18742856.0 dated Feb. 18, 2020. |
Intention to Grant European Patent Application No. 18724079.1 dated May 20, 2020. |
Office Action for European Patent Application No. 20177533.5 dated May 25, 2021. |
English language translation of Decision to Grant for Japanese Patent Application No. 2019-554368 dated Jun. 25, 2021. |
English language translation of Decision to Grant received in Japanese Patent Application No. 2019-554332 dated Jul. 2, 2021. |
Final Office Action dated Oct. 5, 2020, for U.S. Appl. No. 15/836,753, of Binder, J. C., et al., filed Dec. 8, 2017. |
Advisory Action dated Nov. 4, 2020, for U.S. Appl. No. 15/836,753, of Binder, J. C., et al., filed Dec. 8, 2017. |
Notice of Allowance dated Dec. 10, 2020, for U.S. Appl. No. 15/836,753, of Binder, J. C., et al., filed Dec. 8, 2017. |
Notice of Allowance dated Jan. 12, 2021, for U.S. Appl. No. 15/836,753, of Binder, J. C., et al., filed Dec. 8, 2017. |
Non-Final Office Action dated May 12, 2021, for U.S. Appl. No. 16/923,671, of Douthat, C., et al., filed Jul. 8, 2020. |
Office Action for European Patent Application No. 18724079.1 dated Sep. 29, 2020. |
Examiner Requisition for Canadian Patent Application No. 3059245, dated Nov. 12, 2020. |
English language translation of Notice of Reason for Refusal for Japanese Patent Application No. 2019-554368 dated Nov. 20, 2020. |
Examiner Requisition for Canadian Patent Application No. 3059051, dated Jan. 4, 2021. |
English language translation of Office Action received in Japanese Patent Application No. 2019-554332 dated Jan. 5, 2021. |
Examiner Requisition for Canadian Patent Application No. 3059051, dated Oct. 20, 2021. |
Summons to oral proceedings for European Patent Application No. 20177533.5 dated Oct. 25, 2021. |
Final Office Action dated Nov. 10, 2021, for U.S. Appl. No. 16/923,671, of Douthat, C., et al., filed Jul. 8, 2020. |
Number | Date | Country | |
---|---|---|---|
62578657 | Oct 2017 | US |