Secure device based NFC transactions

• US 9,836,744 B2
• Filed: 10/12/2012
• Issued: 12/05/2017
• Est. Priority Date: 11/14/2007
• Status: Active Grant

• Current Assignee: Blaze Mobile, Inc. (iWin, Inc.)
• Original Assignee: Michelle Fisher
• Inventors: Fisher, Michelle
• Primary Examiner(s): Ludwig, Peter L
• Application Number:
  US13/650,257
• Publication Number:
  US 20130041769A1
• Time in Patent Office: 1,880 Days
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3226 Use of secure elements separate from M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/3229 Use of the SIM of a M-device as secure element
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/3552 Downloading or loading of personalisation data
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 30/0238 at point-of-sale [POS]
• CPC Class Codes: H04B 5/72 for local intradevice communication
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04W 12/062 Pre-authentication
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 12/082 : using revocation of authorisation
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

A method for transmitting data between a mobile communication device and a server. The method includes running a mobile application on the mobile communication device. The mobile application is hosted on the mobile communication device through the server as a Software as a Service (SaaS). The method further includes transmitting data associated with the mobile application between the mobile communication device and the server, in which transmission of the data between the mobile communication device and the server is monitored through the server.

Claims

1. A method for conducting a Near Field Communication (NFC) contactless transaction, the method comprising:

maintaining a secure element application and an identification code in a secure element memory;

initiating triggering of a secure element processor which executes the secure element application in response to an NFC inductive trigger between an NFC terminal and the secure element during the NFC contactless transaction;

in response to the NFC inductive trigger between the NFC terminal and the secure element, transmitting the identification code to the NFC terminal via an NFC transceiver using the secure element application and further transmitting the identification code to a remote server by the NFC terminal;

in response to receiving the identification at the remote server, processing, by the remote server, the NFC contactless transaction using a payment method corresponding to the identification code,

wherein the secure element is permanently embedded within a body of a mobile device comprising a mobile device memory, a mobile device display, a mobile device processor configured to execute a non-browser based mobile application, and a mobile device transceiver that supports voice and data interactions through a first communication channel including at least one of CDMA and GSM.

4. The method of claim 1, further wherein the secure element is disabled temporarily to prevent NFC contactless transaction.

5. The method of claim 1, further wherein the non-browser based application receives user authentication information via the mobile device display of the mobile device.

6. The method of claim 1, wherein the payment method is a default payment method.

7. The method of claim 1, wherein the payment method is a user selected payment method.

8. The method of claim 5, wherein the authentication information includes biometric data.

9. The method of claim 5, wherein the authentication information is a personal identification number (PIN).

10. The method of claim 1, further wherein data stored on the mobile device is encrypted using software tools native to the mobile operating system.

11. The method of claim 1, further comprising applying a coupon during the NFC contactless transaction.

12. The method of claim 11, wherein the coupon is automatically applied during an NFC inductive interaction between the secure element and the NFC terminal.

13. The method of claim 1, further wherein, after the NFC contactless transaction has processed, the non-browser based mobile application receives a digital artifact from the server.

18. The method of claim 1, further wherein the secure element receives a digital artifact from the NFC terminal during an inductive NFC interaction between the secure element and the NFC terminal.

24. The method of claim 1, further wherein, after the NFC transaction has processed, the non-browser based mobile application receives a digital artifact from the server.

26. The method of claim 1, further wherein the secure element receives a digital artifact from the NFC terminal during the inductive NFC interaction between the secure element and the NFC terminal.

2. A secure element for conducting a Near Field Communication (NFC) contactless transaction, the secure element comprising:

a secure element memory configured to maintain a secure element application and an identification code;

a secure element processor configured to initiate, in response to an NFC inductive trigger between an NFC terminal and the secure element, execution of the secure element application during the NFC contactless transaction;

an NFC transceiver configured to transmit the identification code from the secure element to the NFC terminal via an NFC transceiver using the secure element application in response to the NFC inductive trigger between the NFC terminal and the secure element and further in response to the NFC inductive trigger where-in the identification code is sent to a remote server by the NFC terminal;

in response to receiving the identification code at the remote server, processing, by the remote server, the NFC contactless transaction using a payment method corresponding to the identification code;

wherein the secure element is permanently embedded within a body of a mobile device comprising a mobile device memory, a mobile device display, a mobile device processor configured to execute a non-browser based mobile application, and a mobile device transceiver that supports voice and data interactions through a first communication channel including at least one of CDMA and GSM.

3. The secure element of claim 2, further wherein the secure element is disabled temporarily to prevent NFC contactless transactions.

14. The secure element of claim 2, further wherein data stored on the mobile device is encrypted using software tools native to the mobile operating system.

15. The secure element of claim 2, further comprising applying a coupon during then NFC contactless transaction.

16. The secure element of claim 15, wherein the coupon is automatically applied during the NFC inductive interaction between the secure element and the NFC terminal.

17. The method of claim 16, wherein the digital artifact comprises an advertisement, receipt, ticket, coupon, and/or content.

19. The secure element of claim 2, wherein the payment method is a default payment method.

20. The secure element of claim 2, wherein the payment method is a user selected payment method.

21. The secure element of claim 2, further wherein the non-browser based application receives user authentication information via the mobile device display of the mobile device.

22. The secure element of claim 21, wherein the authentication includes biometric data.

23. The secure element of claim 21, wherein the authentication is a personal identification number (PIN).

25. The method of claim 16, wherein the digital artifact comprises an advertisement, receipt, ticket, coupon, and content.