INTEGRATED MOBILE TRUSTED SERVICE MANAGER

• US 20130151400A1
• Filed: 12/13/2012
• Published: 06/13/2013
• Est. Priority Date: 12/13/2011
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Wong, Erick, Makhotin, Oleg, Lopez, Eduardo
• Granted Patent: US 10,373,152 B2
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• 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/3263 characterised by activation or deactivation of payment capabilities
• CPC Class Codes: G06Q 20/3265 characterised by personalisation for use
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• 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

Abstract

Embodiments of the present invention are directed to a centralized trusted service manager system in the form of a trusted service manager interconnectivity service hub, which facilitates and provides communications between entities involved I mobile contactless payment systems. One embodiment is directed to a method for processing a message related to a mobile payment application on a secure element of a mobile communication device through an interconnectivity services hub including receiving the message from a first entity in a first protocol and determining a trusted service manager associated with the secure element from among a plurality of trusted service managers using a routing table comprising routing information. Then the method continues by determining a second protocol corresponding to the trusted service manager associated with the secure element, translating the message into the second protocol, and sending the translated message to the trusted service manager which communicates with the secure element.

Claims

1. A method for processing a message related to a mobile payment application on a secure element of a mobile communication device through an interconnectivity services hub, the method comprising:

receiving the message from a first entity in a first protocol;

determining, by a server computer, a trusted service manager associated with the secure element from among a plurality of trusted service managers using a routing table comprising routing information corresponding to predetermined secure element management relationships;

determining a second protocol corresponding to the trusted service manager associated with the secure element;

translating the message into the second protocol; and

sending the translated message to the trusted service manager, wherein the trusted service manager communicates with the secure element.

2. The method of claim 1, wherein the first protocol is also the second protocol.

3. The method of claim 1, wherein the message provides value added services for the mobile payment application on the secure element of the mobile communication device.

4. The method of claim 1, wherein the first entity is an issuer.

5. The method of claim 1, wherein the message includes a request, and wherein the request includes adding, deleting, activating, unlocking, locking, reissuing, replacing, or updating the mobile payment application on the secure element.

6. The method of claim 1, wherein the first entity is an issuer, a trusted service manager associated with the issuer, a wallet provider, or a mobile network operator.

7. The method of claim 1, wherein translating the message into the second protocol further comprises:

identifying the first entity;

determining a request by comparing the message to a first entity protocol mapping; and

mapping information in the message according to a secure element trusted service manager protocol mapping for the request.

8. The method of claim 1, wherein translating the electronic communication into the second protocol further comprises:

determining a request based on uniform commands in the message; and

generating information to be included in the translated message based on a secure element trusted service manager protocol mapping for the request.

9. The method of claim 1, wherein translating the electronic communication into the second protocol further comprises:

determining a request based on uniform commands in the message;

generating a plurality of translated messages based on a range of available trusted service manager requirements; and

selecting the correct translated message from the plurality of translated messages for the trusted service manager associated with the secure element.

10. The method of claim 1, further comprising:

receiving application personalization information from an application personalization preparation service using a master key;

sending the application personalization information to the trusted service manager in the translated message, wherein the trusted service manager uses the application personalization information to provision a new payment application on the secure element; and

sending the application personalization information to the first entity, wherein the first entity uses the application personalization information to update consumer records.

11. A server computer comprising:

a processor; and

a non-transitory computer readable medium coupled to the processor, the computer readable medium comprising code executable by the processor for implementing a method for processing a message related to a mobile payment application on a secure element of a mobile communication device through an interconnectivity services hub, the method comprising;

receiving the message from a first entity in a first protocol;

determining a trusted service manager associated with the secure element from among a plurality of trusted service managers using a routing table comprising routing information corresponding to predetermined secure element management relationships;

determining a second protocol for the trusted service manager associated with the secure element;

translating the message into the second protocol; and

sending the translated message to the trusted service manager, wherein the trusted service manager communicates with the secure element.

12. The server computer of claim 11, wherein the first protocol is also the second protocol.

13. The server computer of claim 11, wherein the electronic communication allows the first entity to provide value added services for a stored payment account on a mobile communication device.

14. The server computer of claim 11, wherein the first entity is an issuer.

15. The server computer of claim 11, wherein the electronic communication includes a request, wherein the request includes adding, deleting, activating, unlocking, locking, reissuing, replacing, or updating the mobile payment application on the secure element.

16. The server computer of claim 11, wherein the first entity is an issuer, a trusted service manager associated with an issuer, a wallet provider, or a mobile network operator.

17. The server computer of claim 11, wherein translating the electronic communication into the second protocol further comprises:

identifying the first entity;

determining a request by comparing the message to a first entity protocol mapping; and

mapping information in the message according to a second entity protocol mapping for the request.

18. The server computer of claim 11, wherein translating the electronic communication into the second protocol further comprises:

determining a request based on uniform commands in the message; and

generating information to be included in the translated message based on a second entity protocol mapping for the request.

19. The server computer of claim 11, wherein translating the electronic communication into the second protocol further comprises:

determining a request based on uniform commands in the message;

generating a plurality of translated messages based on a range of available trusted service manager requirements; and

selecting the correct translated message from the plurality of translated messages for the trusted service manager.

20. The server computer of claim 11, wherein the method further comprises:

receiving application personalization information from an application personalization preparation service using a master key;

sending the application personalization information to the trusted service manager in the translated message, wherein the trusted service manager uses the application personalization information to provision a new payment application on the secure element; and

sending the application personalization information to the first entity, wherein the first entity uses the application personalization information to update consumer records.