Integrated mobile trusted service manager

• US 10,373,152 B2
• Filed: 12/13/2012
• Issued: 08/06/2019
• 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: Makhotin, Oleg, Lopez, Eduardo, Wong, Erick
• Primary Examiner(s): Kim, Steven S
• Application Number:
  US13/713,938
• Publication Number:
  US 20130151400A1
• Time in Patent Office: 2,427 Days
• 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 messages related to mobile payment applications on secure elements of mobile communication devices through an interconnectivity services hub, the method comprising:

storing, by a server computer, a routing table including addresses for routing messages;

storing, by the server computer, protocol adapting information for translating messages into a plurality of protocols for communications with different trusted service managers;

receiving, by the server computer, application personalization information from an application personalization preparation service, the application personalization information generated using a master key;

receiving, by the server computer, a first message for a first trusted service manager computer from a first entity computer, the first message being in a first protocol, the first message related to a first mobile payment application on a first secure element of a first mobile communication device, wherein the first trusted service manager computer communicates with secure elements using a second protocol;

determining, by the server computer, that the first message received from the first entity computer is in the first protocol;

determining, by the server computer using the first message, that the first trusted service manager computer is a recipient of the first message;

determining, by the server computer, that the second protocol is associated with the first trusted service manager computer;

determining, by the server computer using the routing table, an address of the first trusted service manager computer;

translating, by the server computer using the protocol adapting information, the first message into a first translated message in the second protocol used by the first trusted service manager computer;

sending, by the server computer, the first translated message and the application personalization information to the first trusted service manager computer using the routing table and the address of the first trusted service manager computer, wherein the first trusted service manager computer uses the application personalization information to provision a new payment application on the first secure element;

receiving, by the server computer, a second message for a second trusted service manager computer from the first entity computer, the second message being in the first protocol, the second message related to a second mobile payment application on a second secure element of a second mobile communication device, wherein the second trusted service manager computer communicates with secure elements using a third protocol;

determining, by the server computer, that the second message received from the first entity computer is in the first protocol;

determining, by the server computer using the second message, that the second trusted service manager computer is a recipient of the second message;

determining, by the server computer, that the third protocol is associated with the second trusted service manager computer;

determining, by the server computer using the routing table, an address of the second trusted service manager computer;

translating, by the server computer using the protocol adapting information, the second message into a second translated message in the third protocol used by the second trusted service manager computer; and

sending, by the server computer, the second translated message to the second trusted service manager computer using the routing table and the address of the second trusted service manager computer.

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

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

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

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

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

identifying the first entity computer;

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

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

7. The method of claim 1, further comprising:

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

generating information based on a first secure element trusted service manager protocol mapping for the request, wherein the first translated message includes the generated information.

8. The method of claim 1, further comprising:

receiving, by the server computer, a third message for a third trusted service manager computer from a second entity computer, the third message being in a fourth protocol, the third message related to a third mobile payment application on a third secure element of a third mobile communication device, wherein the third trusted service manager computer communicates with secure elements using a fourth protocol;

determining a request based on commands in the third message;

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

selecting a third translated message from the plurality of translated messages, the third translated message being translated to the fourth protocol for the third trusted service manager computer associated with the third secure element.

9. The method of claim 1, wherein the routing table comprises identifiers, addresses, protocol indicators, and relationship information for each of the first entity computer, the first trusted service manager computer, and the second trusted service manager computer.

10. The method of claim 1, further comprising:

decoding, by the server computer, the first message using a first stored key for messages from the first entity computer; and

encoding, by the server computer, the first translated message using a second stored key for messages for the first trusted service manager computer.

11. The method of claim 1, further comprising requesting, by the server computer, the first entity computer to include additional information in the first message, wherein the translating of the first message into the second protocol is based on the additional information included in the first message.

12. The method of claim 1, wherein the application personalization information includes a unique derived key that is generated using a mobile payment application identifier that is unique to the first mobile payment application.

13. A server computer comprising:

a processor; and

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

storing a routing table including addresses for routing messages;

storing protocol adapting information for translating messages into a plurality of protocols for communications with different trusted service managers;

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

receiving a first message for a first trusted service manager computer from a first entity computer, the first message being in a first protocol, the first message related to a first mobile payment application on a first secure element of a first mobile communication device, wherein the first trusted service manager computer communicates using a second protocol;

determining that the first message received from the first entity computer is in the first protocol;

determining, using the first message, that the first trusted service manager computer is a recipient of the first message;

determining that the second protocol is associated with the first trusted service manager computer;

determining, using the routing table, an address of the first trusted service manager computer;

translating, using the protocol adapting information, the first message into a first translated message in the second protocol used by the first trusted service manager computer;

sending the first translated message and the application personalization information to the first trusted service manager computer using the routing table and the address of the first trusted service manager computer, wherein the first trusted service manager computer uses the application personalization information to provision a new payment application on the first secure element;

receiving a second message for a second trusted service manager computer from the first entity computer, the second message being in the first protocol, the second message related to a second mobile payment application on a second secure element of a second mobile communication device, wherein the second trusted service manager computer communicates using a third protocol;

determining, by the server computer, that the second message received from the first entity computer is in the first protocol;

determining, by the server computer using the second message, that the second trusted service manager computer is a recipient of the second message;

determining, by the server computer, that the third protocol is associated with the second trusted service manager computer;

determining, by the server computer using the routing table, an address of the second trusted service manager computer;

translating, using the protocol adapting information, the second message into a second translated message in the third protocol used by the second trusted service manager computer; and

sending the second translated message to the second trusted service manager computer using the routing table and the address of the second trusted service manager computer.

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

15. The server computer of claim 13, wherein the first entity computer is an issuer.

16. The server computer of claim 13, wherein the first message includes a request, wherein the request includes adding, deleting, activating, unlocking, locking, reissuing, replacing, or updating the first mobile payment application on the first secure element.

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

18. The server computer of claim 13, wherein translating the first message into the second protocol further comprises:

identifying the first entity computer;

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

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

19. The server computer of claim 13, wherein the method further comprises:

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

generating information based on a second entity protocol mapping for the request, wherein the first translated message includes the generated information.

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

receiving a third message for a third trusted service manager computer from a second entity computer, the third message being in a fourth protocol, the third message related to a third mobile payment application on a third secure element of a third mobile communication device, wherein the third trusted service manager computer communicates with secure elements using a fourth protocol;

determining a request based on commands in the third message;

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

selecting a third translated message from the plurality of translated messages, the third translated message being translated to the fourth protocol for the third trusted service manager computer associated with the third secure element.

21. The server computer of claim 13, wherein the routing table comprises identifiers, addresses, protocol indicators, and relationship information for each of the first entity computer, the first trusted service manager computer, and the second trusted service manager computer.