The present disclosure generally relates to transactions performed by means of mobile telecommunication devices of cell phone type. The present disclosure more specifically applies to such devices, further equipped with a near field communication circuit (NFC).
Cell phones are more and more often equipped with a near-field communication interface which enables them to combine electromagnetic transponder functions with mobile telephony functions. In particular, this adds functions of emulation of an electromagnetic transponder, of contactless or contactless card reader type to the mobile telecommunication device, for example a personal digital assistant, a cell phone, a smartphone, etc. This considerably enhances the features of the mobile device, which can then be used, for example, as an electronic purse, as an access or transport ticket validation device, etc.
To emulate the operation of a contactless chip card, the mobile telecommunication device is equipped with a contactless front-end integrated circuit (CLF), also called NFC router. This router is equipped with a radio frequency (RF) transceiver front head associated with a low-range antenna to communicate like an electromagnetic transponder. The router uses the capacities of the processor(s) of the mobile device for data processing and storage operations. For access control, electronic purse, payment, and other applications, a secure element enabling to authenticate the user is used. This secure element is either integrated to the mobile telecommunication device (dedicated integrated circuit, circuit welded to the printed circuit board) or contained in a microcircuit supported by a subscriber identification module (SIM), or any other removable card, for example, in the standard format of a memory card.
An NFC router may also be present in a mobile device of USB key type, in a bank teller terminal, in an adhesive device (sticker), etc.
An emulation of a contactless card in a mobile telecommunication device is capable of generating weak points in terms of transaction security.
It would be desirable to be able to detect such weak points.
It would further be desirable to avoid such weak points to secure transactions.
Embodiments overcome all or part of the disadvantages of mobile telecommunication devices associated with a near-field transmission module.
Another embodiment improves the security against a hacking attempt on a security module of subscriber identification module type, contained in a telecommunication device associated with a near-field transmission module.
Another embodiment provides a method for detecting an attempt at diversion of a communication pipe between a port of a security module and a port of a near-field communication router present in a telecommunication device, wherein the router filters the messages addressed to said security module.
According to an embodiment, the message comprises at least one pipe identifier and one instruction code, the router comparing the instruction code with authorized codes that it contains.
According to an embodiment, the router compares the format of the data of the message with authorized formats that it contains.
According to an embodiment, the router comprises a table containing, for each type of control signal that may be received, an authorization or denial code.
An embodiment also provides a method of secure data transmission in a telecommunication device.
An embodiment also provides a near-field communication router.
An embodiment also provides a telecommunication device equipped with a near-field communication router.
The foregoing and other objects, features, and advantages of the present disclosure will be discussed in detail in the following non-limiting description of specific embodiments in connection with the accompanying drawings.
The same elements have been designated with the same reference numerals in the different drawings. For clarity, only those elements and steps which are useful to the understanding of the present disclosure have been shown and will be described. In particular, the coding and communication protocols, be it for near-field transmissions or for telecommunications in GSM mode, have not been detailed, embodiments being compatible with usual protocols. Further, the circuits forming the mobile communication device have not been detailed either, the embodiments being here again compatible with usual programmable devices.
Device 1 comprises a central processing unit 12 (CPU/TH) formed of at least one microcontroller forming the device core. This microcontroller is referred to as a terminal host. For the telecommunication operation over a network (GSM, 3G, UMTS, etc.), the microcontroller uses identification and authentication data provided by a subscriber identification module 14 (SIM) which forms a security module of the device. Microcontroller 12 is capable of using one or several internal memories, not shown, of the telephone. Telephone 1 may also comprise a memory card reader 16 or other buses of communication with the outside to load data and/or applications into the telephone.
Mobile devices to which the described embodiments apply combine the telecommunication function with that of a near-field contactless transmission system (NFC). To achieve this, device 1 comprises a circuit 18 (CLF—ContactLess Front-End) forming a near-field communication module like an electromagnetic transponder. Module 18, also called NFC router, is associated with an antenna 182 distinct from an antenna 20 intended for the mobile telephony network. Circuit 18 may be associated with a security module (SSE) 24 distinct from SIM card 14 and directly present on the printed circuit board of the telephone, or supported by a removable microcircuit card (for example, in the format of a memory card). A security module is an electronic circuit for securely executing applications and guaranteeing the security (secret/integrity) of data manipulated by such applications.
The different elements of device 1 communicate according to various protocols. For example, circuits 12 and 18 communicate over a link 1218 of I2C or SPI type, SIM card 14 communicates with microcontroller 12 over a link 1214 according to ISO standard 7816-3, and security module 24 communicates with router 18 according to this standard over a link 2418. Router 18 communicates with the SIM card, for example, over a single-wire bus 1418 (SWP—Single Wire Protocol). Other versions of protocols and links are of course possible.
The embodiments will be described in relation with a GSM telephone. The embodiments, however, more generally applies to any telecommunication device adapted to a mobile network (for example, Wifi, Bluetooth, WiMax, etc.) and associated with a contactless transmission module (NFC router), for example, a USB key, a bank terminal, a power consumption meter, or other), an access or transport ticket validation terminal, etc.
Similarly, the near-field communication module will be referred to as a router since it generally integrates all the functions useful for the emulation of a contactless card within a same circuit, the described embodiments however applying to any NFC-type module.
Router 18 comprises physical terminals of connection to links 1218, 1418, and 2418 and manages logic gates for assigning these terminals to the different functions associated with near-field communications. Router 18 thus comprises a processor and volatile and non-volatile memories for storing, among others, a routing table for the different logic gates. Some gates are reserved for router administration functions while others can be freely assigned by the router.
In operation, router 18 makes available and manages different pipes of communication with the other circuits 12, 14, 24, etc. of the mobile device to provide these circuits access to the near-field communication functions, that is, to gates connected to radio frequency transmission circuits, called RF gates.
Each of the router terminals (TERMINALS) is assigned one or several gates (GATES). In the example of
The integration of NFC routers in mobile telecommunication devices and the sharing of the same security module (SIM card) generate weak points in terms of security.
Authentication tools may be provided to make sure that the links between the router and the different external circuits are not pirated. However, this appears to be insufficient in view of a weak point that the present inventors have identified and which will be described hereafter.
Router or NFC module 18 generally is a single integrated circuit and its external accesses are rather well protected against possible hacking attempts.
Up to now, the main concern has been to guarantee that a near-field transaction emulated by the mobile device would not enable a pirate device intercepting the near-field communication to exploit data provided by the security module.
However, there remains a risk, since router 18 also manages a pipe (ATPIPE symbolized in dotted lines in
It is assumed that, in a preparatory phase of the attack, GSM phone 1 has been hacked and a pipe ATPIPE has been diverted via router 18 between its SIM card 14 and its microcontroller 12. The routing table of router 18 thus contains the data of the “diverted” pipe. It is also assumed that a pirate application (PA) has been stored in a memory 13 (MEM) of phone 1 and that this application may provide instructions to microcontroller 12. Several embodiments of the preparatory phase will be discussed subsequently. The user of device 1, once it has been hacked by the loading of application PA and by the creation of pipe ATPIPE, is not capable, as will be seen hereafter, to notice a malfunction. He uses his telephone normally.
One of the functions of application PA is to automatically trigger a response of phone 1 after a request originating from the telecommunication network and transmitted by another mobile device 3 owned by the attacker. The pirate device for example is another GSM phone 3 which uses its own subscriber identification module to communicate over the GSM network (symbolized by a relay antenna 5). It may also be a microcomputer associated with a GSM module.
In the example of
Normally, for such a payment, the router of telephone 3 manages a communication pipe with the subscriber identification module (or another dedicated security module) of this telephone to authenticate the user and validate the payment.
In the mechanism of
The countermeasures providing encryptions and/or signatures between terminal 7 requesting the authentication and the security module are ineffective to counter this attack. Indeed, the data between terminal 7 and module 14 need no decoding. A communication pipe has actually been established between module 14 of telephone 1 and terminal 7 via telecommunication network 5, so that module 14 behaves as if it was in near field transaction with terminal 7.
The same type of piracy may occur for passage authentication or validation applications, of secure access type.
Further, this attack may also be successful even without for pirate device 3 to use its own NFC router, for example, if it uses a contactless communication mode, provided for the requested authentication to originate from a security module and to respect the formats and protocols used by the NFC protocol. Further, such an attack may be used to divert any data from device 1 in favor of a pirate system (for example, data duplicating the content of the magnetic track of a card in a bank payment application).
Further, the attack may involve the SIM card of cell phone 1 or of any other security module (for example, module 24), provided for a pipe to be managed by router 18 between this module and a circuit (generally, microcontroller 12) capable of managing communications over network 5.
This attack on near-field transactions, exploiting the telecommunication network, is due to the presence of a communication pipe, via the NFC router, between a security module and a microcontroller connected to this router.
Implementing the attack requires a preparatory phase in which an intervention of the telephone 1 which is desired to be pirated is necessary. This preparation requires an intervention depending on the security level provided by the SIM card to the management of the NFC communication pipes.
In a simplified embodiment, the microcontroller is allowed to create a pipe on any free gate. In this case, a pirate application loaded into the microcontroller is capable of creating a pipe through the NFC router to the SIM card. If, afterwards, the SIM card performs no other checking than to acknowledge that the format of the requests corresponds to the format of a radio frequency frame originating from an NFC circuit, the pirate application may attack the SIM card.
According to another embodiment, security module 14 is more advanced and checks the association between the numbers of the pipes or of its own gates and the RF gates.
In a first case, it is considered that SIM card 14 does not take into account the circuit with which the gate is created (and thus, the fact that it may be a gate intended for the microcontroller). This embodiment exploits the fact that the assignment of the pipe numbers (identifiers) is often sequential. It is first started by asking the microcontroller to suppress a pipe between the SIM card and the RF gates. Then, a pipe having the same identifier is created between the microcontroller and the SIM card.
The fact that, prior to the initialization of device 1, the SIM card checks whether it has already been in the presence of router 18 is exploited herein. If it has not, it reconfigures the pipes between its gates and the NFC router.
In a normal operation, at the first connection of card SIM1 in telephone 1, the card causes the creating, at the level of the so-called transport layer, of at least one communication pipe, identified as SYNCID1, with the CLF router. For this purpose, card SIM1 sends to the CLF router both synchronization data SYNCID1 and a number (typically, a random number RD1). Number RD1 is stored in the CLF router and is used by card 14 to check that it has already caused the creation of pipe with this router. On each initialization, the card verifies the existence of number RD1 in the router. To achieve this, the card requests from the router to create a pipe between one of its gates, identified as GATEID, and one of the RF gates, identified as RFGATEID. The router then creates a pipe and assigns it an identifier PIPEID and, at the same time, stores said identifier in the routing table and communicates it to card SIM1. Each time data are requested by the router, card SIM1 verifies that identifier PIPEID of the pipe is correct.
To implement the attack, the hacker should have cell phone 1 and card SIM1 in his possession for a period of time. This is relatively easy, for example, by asking the owner of the cell phone to lend it to supposedly make a call, or by fraudulently using a phone during a maintenance operation, for example, in a mobile telephony shop.
With card SIM1 and the telephone provided with router 1, the pirate starts by introducing card SIM1 into a pirate device (PIRATE READER), for example, another cell phone having a microcontroller capable of executing a piracy program complying with the described functions, or a computer provided with a card reader and simulating a router. Since card SIM1 has never met the NFC router of the pirate device or emulated by said device, it generates a new synchronization identifier SYNCID2. It sends back gate identifiers RFGATEID and GATEID to create the corresponding pipes. The pirate router then assigns, to at least one pair of gates, a pipe FPIPEID which corresponds to a gateway between the router and an external gate of the microcontroller instead of associating gate GATEID to an RF gate. Identifier FPIPEID and identifiers SYNCID2 and RD2 are then loaded into a falsified card SIM2. Card SIM2 then contains a routing table associating gates RFGATEID and GATEID with pipe FPIPEID.
Then, card SIM2 is introduced into telephone 1. Identifiers SYNCID2 and RD2 are then transferred to CLF router 18 to create pipe FPIPEID between gates designated as GATEID and RFGATEID. This amounts to modifying the routing table of the router so that when the pipe between gates GATEID and RFGATEID is called, the assigned pipe is pipe FPIPEID instead of PIPEID.
The assignment of pipe FPIPEID may take various forms according to the way in which the pipes are assigned to the gates in the router. For example, a phase of observation of the gate assignment is gone through by placing card SIM2 in the router to observe the pipe assignment method, before introducing card SIM2 into the pirate reader.
The “real” card SIM1 is then placed back into telephone 1. Since the CLF router knows identifiers RD2 and SYNCID2, the card considers that it “knows” the router and does not recreate pipes therewith. When card SIM1 requests a communication towards gate RFGATEID, the router uses the assigned pipe FPIPEID.
The GSM terminal has effectively been hacked, that is, a pipe FPIPE (or ATPIPE,
There are various possibilities, depending on device 1. For example, the routing table may be read from. If this is not possible, it is possible, when card SIM1 is in the pirate reader, to emulate an operation of the CLF circuit, in order to obtain the full configuration stored in this card. A pirate card SIM2 or a card emulator may also be used to extract the data from the routing table in valid phone 1.
It can thus be seen that it is possible to parameterize the diverting of a communication pipe between a security module and an NFC router to establish a pipe between this module and the telephone microcontroller, external to the NFC router.
So that the user of telephone 1 does not notice the piracy, even when he uses his contactless mode, the pirate application must comprise the function of redirecting pipe FPIPE towards the RF circuits of the router when a data request towards the SIM is transmitted by router 18.
As in
According to the embodiment of
More generally, a filtering table is provided for each security module connected to the router, for example, the microcontroller, another security element, etc.
Usually, an instruction INST transiting through router CLF comprises the pipe over which the message is to be transmitted the type of message, an actual instruction code and, possibly, data. This message is intercepted by the filter comprised within the CLF router before allowing its transmission to the SIM card.
According to an embodiment, all messages going from the microcontroller to the SIM card (or any other security module) are blocked by the router based on a specific instruction code (for example, the code known as HTP) or on the combination of the table and of the parameter format of this instruction. Messages are thus limited to those between the actual telephone central processing unit and the SIM card, which respect the expected instruction format. Now, to implement the above-described attack, messages meaning nothing for the application have to be sent. Such messages are thus blocked and do not reach the SIM card.
In the example of
In the example of
The implementation of the described embodiments requires a modification of the internal operation of the CLF router to provide a specific filtering table therein. This implementation is within the abilities of those skilled in the art based on the functional indications given hereabove and by using tools which are usual per se.
Various embodiments have been described. Various alterations and modifications will occur to those skilled in the art. In particular, the embodiments have been described in relation with an example of a security module formed of a SIM card. They however more generally apply to any security module capable of communicating with the NFC router.
Such alterations, modifications, and improvements are intended to be within the spirit and scope of the invention. Accordingly, the foregoing description is by way of example only and is not intended as limiting. The invention is limited only as defined in the following claims and the equivalents thereto.
Number | Date | Country | Kind |
---|---|---|---|
1060819 | Dec 2010 | FR | national |
This application is a continuation of Ser. No. 16/698,519, filed on Nov. 27, 2019 which is a continuation of U.S. Ser. No. 15/585,107, filed May 2, 2017, which is a continuation of U.S. Ser. No. 13/996,458, filed Aug. 29, 2013, which is a U.S. National Stage patent application based on International patent application No. PCT/FR2011/053023, filed Dec. 16, 2011, which claims the priority benefit of French patent application number 10/60819, filed Dec. 20, 2010, which applications are hereby incorporated by reference to the maximum extent allowable by law.
Number | Name | Date | Kind |
---|---|---|---|
6070243 | See et al. | May 2000 | A |
6092191 | Shimbo et al. | Jul 2000 | A |
6674769 | Viswanath | Jan 2004 | B1 |
6856818 | Ford | Feb 2005 | B1 |
7587044 | Kocher et al. | Sep 2009 | B2 |
7974536 | Yu et al. | Jul 2011 | B2 |
9311477 | Marinet et al. | Apr 2016 | B2 |
10278077 | Huque et al. | Apr 2019 | B2 |
10511626 | Huque | Dec 2019 | B2 |
10585738 | Marinet et al. | Mar 2020 | B2 |
10716007 | Huque et al. | Jul 2020 | B2 |
10931712 | Huque | Feb 2021 | B2 |
10999737 | Huque et al. | May 2021 | B2 |
11651064 | Peeters et al. | May 2023 | B2 |
11743721 | Huque et al. | Aug 2023 | B2 |
20040065735 | Christoffers et al. | Apr 2004 | A1 |
20040177158 | Bauch et al. | Sep 2004 | A1 |
20040232220 | Beenau et al. | Nov 2004 | A1 |
20050013310 | Banker et al. | Jan 2005 | A1 |
20050251652 | Nallusamy | Nov 2005 | A1 |
20060031933 | Costa et al. | Feb 2006 | A1 |
20060213972 | Kelley et al. | Sep 2006 | A1 |
20070006314 | Costa et al. | Jan 2007 | A1 |
20070118558 | Kahandaliyanage | May 2007 | A1 |
20070186097 | Arditti et al. | Aug 2007 | A1 |
20070263596 | Charrat | Nov 2007 | A1 |
20070282951 | Selimis et al. | Dec 2007 | A1 |
20080085001 | Charrat et al. | Apr 2008 | A1 |
20080219444 | Benteo et al. | Sep 2008 | A1 |
20080296978 | Finkenzeller et al. | Dec 2008 | A1 |
20090106824 | Morel et al. | Apr 2009 | A1 |
20090206984 | Charrat et al. | Aug 2009 | A1 |
20100043069 | Vidya | Feb 2010 | A1 |
20100084465 | Jolivet | Apr 2010 | A1 |
20100090805 | Libotte | Apr 2010 | A1 |
20100137025 | Tal et al. | Jun 2010 | A1 |
20100161403 | Fisher et al. | Jun 2010 | A1 |
20100178867 | Charrat | Jul 2010 | A1 |
20100178868 | Charrat | Jul 2010 | A1 |
20100210300 | Rizzo et al. | Aug 2010 | A1 |
20100227553 | Charrat | Sep 2010 | A1 |
20100245054 | Kim | Sep 2010 | A1 |
20100259216 | Capomaggio | Oct 2010 | A1 |
20100274677 | Florek et al. | Oct 2010 | A1 |
20100325300 | Vasters et al. | Dec 2010 | A1 |
20110065398 | Liu et al. | Mar 2011 | A1 |
20110226853 | Soh et al. | Sep 2011 | A1 |
20110237190 | Jolivet | Sep 2011 | A1 |
20110269423 | Schell et al. | Nov 2011 | A1 |
20110320825 | Greiner | Dec 2011 | A1 |
20120052801 | Kulkarni | Mar 2012 | A1 |
20120190299 | Takatsuka et al. | Jul 2012 | A1 |
20120190332 | Charles | Jul 2012 | A1 |
20130057640 | Callahan | Mar 2013 | A1 |
20130059563 | Huque et al. | Mar 2013 | A1 |
20130059566 | Huque et al. | Mar 2013 | A1 |
20130059567 | Huque et al. | Mar 2013 | A1 |
20130059568 | Huque et al. | Mar 2013 | A1 |
20130217325 | Ingels | Aug 2013 | A1 |
20130225125 | Hugue et al. | Aug 2013 | A1 |
20130337770 | Huque et al. | Dec 2013 | A1 |
20140041036 | Huque et al. | Feb 2014 | A1 |
20140201815 | Van Nieuwenhuyze et al. | Jul 2014 | A1 |
20140289833 | Briceno et al. | Sep 2014 | A1 |
20170237774 | Huque et al. | Aug 2017 | A1 |
20200099717 | Huque et al. | Mar 2020 | A1 |
20210258784 | Huque et al. | Aug 2021 | A1 |
20220244961 | Peeters et al. | Aug 2022 | A1 |
Number | Date | Country |
---|---|---|
1596018 | Mar 2005 | CN |
1717705 | Jan 2006 | CN |
1933351 | Mar 2007 | CN |
101079013 | Nov 2007 | CN |
101159008 | Apr 2008 | CN |
101202621 | Jun 2008 | CN |
101261675 | Sep 2008 | CN |
101491052 | Jul 2009 | CN |
101536008 | Sep 2009 | CN |
101192922 | May 2010 | CN |
101241541 | Aug 2010 | CN |
101299698 | May 2012 | CN |
1 909 431 | Apr 2008 | EP |
1 928 099 | Jun 2008 | EP |
2 034 705 | Mar 2009 | EP |
2 219 353 | Aug 2010 | EP |
1 763 199 | Jan 2017 | EP |
2770316 | Jun 2000 | FR |
2903549 | Jan 2008 | FR |
2921786 | Apr 2009 | FR |
2007068993 | Jun 2007 | WO |
2007093580 | Aug 2007 | WO |
2009115997 | Sep 2009 | WO |
2009147094 | Dec 2009 | WO |
Entry |
---|
ETSI, “Intelligent Transport Systems (ITS); Access layer specification for Intelligent Transport Systems using LTE Vehicle to everything communication in the 5,9 GHz frequency band,” Technical Specification 103 613, V1.1.1, Nov. 2018, 18 pages. |
ETSI, “Smart Cards; Test specification for the Host Controller Interface (HCI); Part 2: UICC features,” V7.2.0, Technical Specification 102 695-2, Oct. 2010, 62 pages. |
ETSI, “Smart Cards; UICC-CLF interface; Physical and data link layer characteristics (Release 7),” Technical Specification 102 613, V7.5.0, Apr. 2009, 56 pages. |
ETSI, “Smart Cards; UICC-CLF interface; Physical and data link layer characteristics (Release 7),” Technical Specification 102 613, V7.7.0, Oct. 2009, 58 pages. |
ETSI, “Smart Cards; UICC-Contactless Front-end (CLF) Interface; Host Controller Interface (HCI),” V10.2.0, Technical Specification 102 622, Mar. 2011, 56 pages. |
ETSI, “Smart Cards; UICC-Contactless Front-end (CLF) Interface; Host Controller Interface (HCI),” V7.4.0, Technical Specification 102 622, Apr. 2009, 53 pages. |
ETSI, “Smart Cards; UICC-Contactless Front-end (CLF) Interface; Host Controller Interface (HCI),” V7.5.0, Technical Specification 102 622, Jun. 2009, 53 pages. |
ETSI, “Smart Cards; UICC-Contactless Front-end (CLF) Interface; Part 1: Physical and data link layer characteristics (Release 7),” Technical Specification 102 613, V7.3.0, Sep. 2008, 57 pages. |
Francis et al., “Potential Misuse of NFC Enabled Mobile Phones with Embedded Security Elements as Contactless Attack Platforms,” International Conference for Internet Technology and Secured Transactions, London, United Kingdom, Nov. 9-12, 2009, 8 pages. |
Haselsteiner et al., “Security in Near Field Communication (NFC),” Workshop on RFID Security, 2006, 11 pages. |
ISO/IEC 14443-3, “Identification Cards—Contactless integrated circuit cards—Proximity cards—Part 3: Initialization and anticollision,” International Standard, Third Edition, Corrected Version, Sep. 1, 2016, 70 pages. |
ISO/IEC 15693-1, “Identification cards—Contactless integrated circuit(s) cards—Viinity Integrated Circuit(s) Card Part 1: Physical characteristics,” International Standard, Final Committee Draft, 2000, 79 pages. |
ISO/IEC 18092, “Information Technology—Telecommunications and information exchange between systems—Near Field Communication—Interface and Protocol (NFCIP-1),” International Standard, Second Edition, Mar. 15, 2013, 52 pages. |
ISO/IEC 21481, “Information technology—Telecommunications and information exchange between systems—Near Field Communication Interface and Protocol-2 (NFCIP-2),” International Standard, Second Edtion, Jul. 1, 2012. |
ISO/IEC, “Identification cards—Integrated circuit cards—Part 3: Cards with contacts—Electrical interface and transmission protocols,” International Standard 7816-3, 3rd ed., Nov. 1, 2006, 58 pages. |
ISO/IEC, “Identification cards—Integrated circuit cards—Part 4: Organization, security and commands for interchange,” International Standard 7816-4, 2nd ed., Jan. 15, 2005, 90 pages. |
Madlmayr et al., “Management of Multiple Cards in NFC-Devices,” Proceedings of the 8th IFIP WG 8.8/11/2 International Conference on Smart Card Research and Advanced Applications, London, United Kingdom, Sep. 8-11, 2008, pp. 149-161. (14 pages). |
Madlmayr et al., “NFC Devices: Security and Privacy,” Third International Conference on Availability, Reliability and Security, Barcelona, Spain, Mar. 4-7, 2008, pp. 642-647. |
Mulliner, “Attacking NFC Mobile Phones,” EUSecWest Conference, London, United Kingdom, May 2008, 71 pages. |
Mulliner, “Vulnerability Analysis and Attacks on NFC-enabled Mobile Phones,” International Conference on Availability, Reliability and Security, 2009, 6 pages. |
Pasquet et al., “‘Payment with mobile NFC phones’: How to analyze the security problems,” 2008 International Symposium on Collaborative Technologies and Systems, Irvine, California, USA, May 19-23, 2008, 8 pages. |
Rieback et al., “Keep on Blockin' in the Free World: Personal Access Control for Low-Cost RFID Tags,” in Christianson et al. (eds.), Security Protocols 2005, Springer-Verlag, Berlin, Germany, 2007, pp. 51-59. (10 pages). |
Smart Card Alliance, “Security of Proximity Mobile Payments,” CPMC-09001, May 2009, 40 pages. |
Van Damme et al., “Practical Experiences with NFC Security on mobile Phones,” Workshop on RFID Security, 2009, 37 pages. |
Number | Date | Country | |
---|---|---|---|
20210136108 A1 | May 2021 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16698519 | Nov 2019 | US |
Child | 17146063 | US | |
Parent | 15585107 | May 2017 | US |
Child | 16698519 | US | |
Parent | 13996458 | US | |
Child | 15585107 | US |