METHODS AND APPARATUS TO PROVISION PAYMENT SERVICES

• US 20130041830A1
• Filed: 08/08/2012
• Published: 02/14/2013
• Est. Priority Date: 08/09/2011
• Status: Abandoned Application

• Current Assignee: Blackberry Limited
• Original Assignee: Neil Patrick Adams, Vincenzo Kazimierz Marcovecchio
• Inventors: Singh, Ravi, Adams, Neil Patrick, Marcovecchio, Vincenzo Kazimierz
• Application Number:
  US13/569,904
• Publication Number:
  US 20130041830A1
• Time in Patent Office: Days
• US Class Current: 705/65
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• 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/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/3825 Use of electronic signatures
• CPC Class Codes: G06Q 20/3827 Use of message hashing

Abstract

Methods and apparatus to provision payment services are disclosed. An example method includes receiving an indication of a service to be provisioned to a mobile device, generating a token indicative of the service, wherein the token includes a cryptographically signed portion that was cryptographically signed by a secure element of the mobile device, sending the token to an entity for verification, and provisioning the service when the token is verified.

Claims

1. A method comprising:

receiving an indication of a service to be provisioned to a mobile device;

generating a token indicative of the service, wherein the token includes a cryptographically signed portion that was cryptographically signed by a secure element of the mobile device;

sending the token to an entity for verification; and

provisioning the service when the token is verified.

2. The method of claim 1, wherein the service includes a payment service.

3. The method of claim 1, wherein the token includes information used to construct the cryptographically signed portion.

4. The method of claim 1, wherein the token includes an identification of the service to be provisioned to the mobile device.

5. The method of claim 1, wherein the token includes a mobile device identifier.

6. The method of claim 1, wherein the token includes a timestamp.

7. The method of claim 1, wherein generating the token comprises constructing the cryptographically signed portion using a unique key assigned to the mobile device.

8. The method of claim 7, wherein the unique key is assigned to the mobile device by a trusted service manager.

9. The method of claim 8, wherein the verification is performed by the trusted service manager.

10. The method of claim 1, wherein sending the token comprises sending the token from the mobile device directly to a provider of the service.

11. The method of claim 1, wherein sending the token comprises sending the token from the mobile device to a provider of the service via a personal computer.

12. The method of claim 1, wherein receiving the indication comprises obtaining a scan of an image.

13. The method of claim 12, wherein the image is obtained from a scan of a display screen.

14. The method of claim 12, wherein the image is obtained from a scan of printed media.

15. The method of claim 12, wherein the image comprises a two-dimensional barcode.

16. The method of claim 1, wherein receiving the indication utilizes near field communication.

17. A method comprising:

obtaining a token indicative of a service to be provisioned to a mobile device, the token including a cryptographically signed portion that was cryptographically signed by a secure element of the mobile device;

obtaining a secure element key corresponding to the secure element of the mobile device;

processing at least a portion of the token using the secure element key to verify validity of the token; and

transmitting an indication that the service is to be provisioned to the mobile device.

18. The method of claim 17, further comprising assigning the secure element key to the mobile device and providing the secure element key to the secure element prior to obtaining the token.

19. The method of claim 17, further comprising instructing the mobile device to execute one or more commands to provision the service to the mobile device.

20. The method of claim 17, further comprising receiving a request to validate a token from a provider of the service.

21. The method of claim 17, wherein the service includes a payment service.

22. The method of claim 17, wherein processing the at least a portion of the token comprises processing non-encrypted information in the token in combination with the secure element key to obtain a cryptographic signature.

23. The method of claim 22, wherein processing the at least a portion of the token comprises comparing the cryptographic signature to the cryptographically signed portion of the token.

24. The method of claim 17, wherein transmitting the indication comprises transmitting the indication to a provider of the service.

25. A device, comprising:

a processor;

a secure element; and

a memory coupled to the processor and storing instructions which, when executed by the processor, cause the processor to;

generate a token indicative of a service to be provisioned to a mobile device, wherein the token includes a cryptographically signed portion that was cryptographically signed by the secure element;

send the token to an entity for verification; and

provision the service when the token is verified.

26. The device of claim 25, wherein the secure element is to store a secure element key and to construct the cryptographically signed portion using the secure element key.

27. The device of claim 25, wherein the secure element is to receive the secure element key from a trusted service manager prior to the processor generating the token.

28. The device of claim 25, further comprising a virtual wallet to store a plug-in corresponding to the service.

29. The device of claim 25, wherein the secure element is to construct the cryptographically signed portion using an identification of the service to be provisioned to the mobile device.

30. The device of claim 25, wherein the secure element is to construct the cryptographically signed portion using a mobile device identifier.

31. The device of claim 25, wherein the secure element is to construct the cryptographically signed portion using a timestamp.

32. The device of claim 25, wherein the token further includes an identification of the service to be provisioned to the mobile device, a mobile device identifier, and a timestamp.