# US 2019/0318341 A1 · Integrated mobile trusted service manager > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0318341 A1 - Document ID: US20190318341A1 - Status: Published application - Kind: A1 - Application number: 16/453,574 - Filed: 2019-06-26 - Published: 2019-10-17 - Earliest claimed: 2011-12-13 - Assignees: Visa International Service Association - Applicants: Visa International Service Association - Inventors: Oleg Makhotin; Eduardo Lopez; Erick Wong - Web page: https://patentgrep.com/patent/US20190318341A1 ## CPC - G06Q 20/326: {Payment applications installed on the mobile devices} - G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] - G06Q 20/3226: {Use of secure elements separate from M-devices} - G06Q 20/3227: {using secure elements embedded in M-devices} - G06Q 20/3229: {Use of the SIM of a M-device as secure element} - G06Q 20/3263: {characterised by activation or deactivation of payment capabilities} - G06Q 20/3265: {characterised by personalisation for use} - G06Q 20/327: {Short range or proximity payments by means of M-devices} - G06Q 20/3278: {RFID or NFC payments by means of M-devices} - G06Q 20/36: using electronic wallets or electronic money safes - H04L 69/18: Multiprotocol handlers, e.g. single devices capable of handling multiple protocols - H04W 4/50: Service provisioning or reconfiguring - H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication - H04W 12/08: Access security - H04W 12/35: {Protecting application or service provisioning, e.g. securing SIM application provisioning} - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## 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 ### Claim at position 1 -20. (canceled) ### Claim 21 A method for processing messages related to mobile payment applications associated with secure elements of mobile communication devices through an interconnectivity services hub, the method comprising: receiving, by a server computer storing a routing table including addresses for routing messages, and protocol adapting information for translating messages into a plurality of protocols for communications with different trusted service managers, 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 associated with 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; 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 to the first trusted service manager computer using the routing table; 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 associated with 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; 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. ### Claim 22 (depends on 21) The method of claim 21, wherein the first message provides value added services for the first mobile payment application associated with the first secure element of the first mobile communication device. ### Claim 23 (depends on 21) The method of claim 21, wherein the first entity computer is an issuer. ### Claim 24 (depends on 21) The method of claim 21, 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 associated with the first secure element. ### Claim 25 (depends on 21) The method of claim 21, wherein the first entity computer is an issuer, a trusted service manager associated with an issuer, a wallet provider, or a mobile network operator. ### Claim 26 (depends on 21) The method of claim 21, wherein translating the first message into the first translated message in 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. ### Claim 27 (depends on 21) The method of claim 21, 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. ### Claim 28 (depends on 21) The method of claim 21, 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 associated with a third secure element of a third mobile communication device, wherein the third trusted service manager computer communicates with secure elements using the 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. ### Claim 29 (depends on 21) The method of claim 21, further comprising: receiving application personalization information from an application personalization preparation service using a master key; sending the application personalization information to the first trusted service manager computer in the first translated message, wherein the first trusted service manager computer uses the application personalization information to provision a new payment application associated with the first secure element; and sending the application personalization information to the first entity computer, wherein the first entity computer uses the application personalization information to update consumer records. ### Claim 30 (depends on 21) The method of claim 21, 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. ### Claim 31 A server computer storing a routing table including addresses for routing messages, and protocol adapting information for translating messages into a plurality of protocols for communications with different trusted service managers, the 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 associated with secure elements of mobile communication devices through an interconnectivity services hub, the method comprising: 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 associated with 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; 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 to the first trusted service manager computer using the routing table; 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 associated with 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; 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. ### Claim 32 (depends on 31) The server computer of claim 31, wherein the first message allows the first entity computer to provide value added services for a stored payment account associated with the first mobile communication device. ### Claim 33 (depends on 31) The server computer of claim 31, wherein the first entity computer is an issuer. ### Claim 34 (depends on 31) The server computer of claim 31, 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 associated with the first secure element. ### Claim 35 (depends on 31) The server computer of claim 31, wherein the first entity computer is an issuer, a trusted service manager associated with an issuer, a wallet provider, or a mobile network operator. ### Claim 36 (depends on 31) The server computer of claim 31, 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. ### Claim 37 (depends on 31) The server computer of claim 31, 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. ### Claim 38 (depends on 31) The server computer of claim 31, 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 associated with a third secure element of a third mobile communication device, wherein the third trusted service manager computer communicates with secure elements using the 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. ### Claim 39 (depends on 31) The server computer of claim 31, 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 first trusted service manager computer in the first translated message, wherein the first trusted service manager computer uses the application personalization information to provision a new payment application associated with the first secure element; and sending the application personalization information to the first entity computer, wherein the first entity computer uses the application personalization information to update consumer records. ### Claim 40 (depends on 31) The server computer of claim 31, wherein the method further comprises: decoding the first message using a first stored key for messages from the first entity computer; and encoding the first translated message using a second stored key for messages for the first trusted service manager computer.