IP Library Granted Patent US 8,447,699
Granted Patent B2
US 8,447,699 · App. 12/717,620 · Granted May 21, 2013

Global secure service provider directory

Inventors: Asif Batada (Atlanta, GA); Moshe Levy (Sunnyvale, CA)
Assignee: QUALCOMM Incorporated
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,447,699
App. No.
12/717,620
Granted
May 21, 2013
Kind
B2
Abstract

Systems and methods enable members of a secure transaction network to readily identify the appropriate trusted service manager (TSM) to support a particular transaction. A global directory of TSM providers is provided that a secure service provider can use for determining which TSM provider is the authorized manager of a security domain for the particular transaction. In aspect the directory of TSM providers may be stored within a mobile device secure element. In another aspect, the directory of TSM providers may be stored in a central TSM repository. In a further aspect, the directory of TSM providers may be distributed among a number of secondary TSM repositories. The appropriate TSM may be identified based upon a secure element identifier and an application identifier provided by a secure element as part of the transaction. Communication of the identifiers from mobile devices may be via cellular or near field communication links.

Claims (114)

1. A method for identifying a trusted service manager (TSM) provider, comprising:

determining by a processor a secure element identifier corresponding to a secure element of a computing device;

determining by the processor an application identifier corresponding to a security domain within the secure element;

providing by a mobile computing device, the secure element identifier and the application identifier to a first repository of TSM providers; and

receiving, by a server, from the first repository, an identifier of the TSM provider that corresponds to the security domain;

identifying by the server, a TSM provider using the received identifier; and

sending, by the server, a request for a credit card link to the identified TSM provider, the credit card link request including the secure element and a credit card number.

2. The method of claim 1 , further comprising:

providing the secure element identifier to a second repository of TSM providers; and

receiving, from the second repository, an identifier of the first repository.

3. The method of claim 1 , wherein determining a secure element identifier corresponding to a secure element comprises:

sending a query to the secure element via a system bus connecting a central processor of the computing device; and

receiving the identifier from the secure element via the system bus.

4. The method of claim 1 , wherein determining a secure element identifier corresponding to a secure element comprises:

sending a query to the secure element via a near field communication (NFC) communication link; and

receiving the identifier from the secure element via the NFC communication link.

5. The method of claim 3 , wherein determining an application identifier corresponding to a security domain within the secure element comprises:

sending a query to the secure element via the system bus; and

receiving the identifier from the secure element via the system bus.

6. The method of claim 4 , wherein determining an application identifier corresponding to a security domain within the secure element comprises:

sending a query to the secure element via the NFC communication link; and

receiving the identifier from the secure element via the NFC communication link.

7. The method of claim 1 , wherein providing the secure element identifier and the application identifier to a first repository of TSM providers comprises:

sending, from the mobile device, a query to the first repository of TSM providers;

wherein the query includes the secure element identifier and the application identifier.

8. The method of claim 7 , further comprising:

sending, from the mobile device to a server corresponding to a secure service provider, the identifier of the TSM provider that corresponds to the security domain.

9. The method of claim 1 , wherein providing the secure element identifier and the application identifier to a first repository of TSM providers comprises:

sending, from a server corresponding to a secure service provider, a query to the first repository of TSM providers;

wherein the query includes the secure element identifier and the application identifier.

10. A computing device, comprising:

means for determining a secure element identifier corresponding to a secure element of a computing device;

means for determining an application identifier corresponding to a security domain within the secure element;

means for providing the secure element identifier and the application identifier to a first repository of TSM providers;

means for receiving, from the first repository, an identifier of the TSM provider that corresponds to the security domain;

means for identifying a TSM provider using the received identifier; and

means for sending a request for a credit card link to the identified TSM provider, the credit card link request including the secure element and a credit card number.

11. The computing device of claim 10 , further comprising:

means for providing the secure element identifier to a second repository of TSM providers; and

means for receiving, from the second repository, an identifier of the first repository.

12. The computing device of claim 10 , wherein means for determining a secure element identifier corresponding to a secure element comprises:

means for sending a query to the secure element via a system bus connecting a central processor of the computing device; and

means for receiving the identifier from the secure element via the system bus.

13. The computing device of claim 10 , wherein means for determining a secure element identifier corresponding to a secure element comprises:

means for sending a query to the secure element via a near field communication (NFC) communication link; and

means for receiving the identifier from the secure element via the NFC communication link.

14. The computing device of claim 12 , wherein means for determining an application identifier corresponding to a security domain within the secure element comprises:

means for sending a query to the secure element via the system bus; and

means for receiving the identifier from the secure element via the system bus.

15. The computing device of claim 13 , wherein means for determining an application identifier corresponding to a security domain within the secure element comprises:

means for sending a query to the secure element via the NFC communication link; and

means for receiving the identifier from the secure element via the NFC communication link.

16. The computing device of claim 10 , wherein means for providing the secure element identifier and the application identifier to a first repository of TSM providers comprises:

means for sending, from the computing device, a query to the first repository of TSM providers;

wherein the query includes the secure element identifier and the application identifier.

17. The computing device of claim 16 , further comprising:

means for sending, from the computing device to a server corresponding to a secure service provider, the identifier of the TSM provider that corresponds to the security domain.

18. A financial transaction system, comprising:

a computing device;

means for determining a secure element identifier corresponding to a secure element of the computing device;

means for determining an application identifier corresponding to a security domain within the secure element;

means for providing the secure element identifier and the application identifier to a first repository of TSM providers;

means for receiving, from the first repository, an identifier of the TSM provider that corresponds to the security domain;

means for identifying a TSM provider using the received identifier; and

means for sending a request for a credit card link to the identified TSM provider, the credit card link request including the secure element and a credit card number.

19. The financial transaction system of claim 18 , further comprising:

means for providing the secure element identifier to a second repository of TSM providers; and

means for receiving, from the second repository, an identifier of the first repository.

20. The financial transaction system of claim 18 , wherein means for determining a secure element identifier corresponding to a secure element comprises:

means for sending a query to the secure element via a system bus connecting a central processor of the computing device; and

means for receiving the identifier from the secure element via the system bus.

21. The financial transaction system of claim 18 , wherein means for determining a secure element identifier corresponding to a secure element comprises:

means for sending a query to the secure element via a near field communication (NFC) communication link; and

means for receiving the identifier from the secure element via the NFC communication link.

22. The financial transaction system of claim 20 , wherein means for determining an application identifier corresponding to a security domain within the secure element comprises:

means for sending a query to the secure element via the system bus; and

means for receiving the identifier from the secure element via the system bus.

23. The financial transaction system of claim 21 , wherein means for determining an application identifier corresponding to a security domain within the secure element comprises:

means for sending a query to the secure element via the NFC communication link; and

means for receiving the identifier from the secure element via the NFC communication link.

24. The financial transaction system of claim 18 , wherein means for providing the secure element identifier and the application identifier to a first repository of TSM providers comprises:

means for sending, from the computing device, a query to the first repository of TSM providers;

wherein the query includes the secure element identifier and the application identifier.

25. The financial transaction system of claim 24 , further comprising:

means for sending, from the computing device to a server corresponding to a secure service provider, the identifier of the TSM provider that corresponds to the security domain.

26. The financial transaction system of claim 18 , wherein means for providing the secure element identifier and the application identifier to a first repository of TSM providers comprises:

means for sending, from a server corresponding to a secure service provider, a query to the first repository of TSM providers;

means for wherein the query includes the secure element identifier and the application identifier.

27. A tangible non-transitory processor-readable storage medium having stored thereon processor-executable instructions which when executed by a processor of a computing device cause the processor of a computing device to perform operations, comprising:

determining a secure element identifier corresponding to a secure element of the computing device;

determining an application identifier corresponding to a security domain within the secure element;

providing the secure element identifier and the application identifier to a first repository of TSM providers;

receiving, from the first repository, an identifier of the TSM provider that corresponds to the security domain;

identifying a TSM provider using the received identifier; and

sending the request for a credit card link to the identified TSM provider, the credit card link request including the secure element and a credit card number.

28. The tangible non-transitory processor-readable storage medium of claim 27 , further comprising:

providing the secure element identifier to a second repository of TSM providers; and

receiving, from the second repository, an identifier of the first repository.

29. The tangible non-transitory processor-readable storage medium of claim 27 , wherein determining a secure element identifier corresponding to a secure element comprises:

sending a query to the secure element via a system bus connecting to the processor; and

receiving the identifier from the secure element via the system bus.

30. The tangible non-transitory processor-readable storage medium of claim 27 , wherein determining a secure element identifier corresponding to a secure element comprises:

sending a query to the secure element via a near field communication (NFC) communication link; and

receiving the identifier from the secure element via the NFC communication link.

31. The tangible non-transitory processor-readable storage medium of claim 29 , wherein determining an application identifier corresponding to a security domain within the secure element comprises:

sending a query to the secure element via the system bus; and

receiving the identifier from the secure element via the system bus.

32. The tangible non-transitory processor-readable storage medium of claim 30 , wherein determining an application identifier corresponding to a security domain within the secure element comprises:

sending a query to the secure element via the NFC communication link; and receiving the identifier from the secure element via the NFC communication link.

33. The tangible non-transitory processor-readable storage medium of claim 27 , wherein providing the secure element identifier and the application identifier to a first repository of TSM providers comprises:

sending, from the processor, a query to the first repository of TSM providers;

wherein the query includes the secure element identifier and the application identifier.

34. The tangible non-transitory processor-readable storage medium of claim 33 , further comprising:

sending, from the processor to a server corresponding to a secure service provider, the identifier of the TSM provider that corresponds to the security domain.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 24, 2012
From: FIRETHORN MOBILE, INC.
To: QUALCOMM INCORPORATED
Reel/Frame 029184/0436 →
CHANGE OF NAME Recorded Apr 26, 2011
From: OUTLIER, INC.
To: FIRETHORN MOBILE, INC.
Reel/Frame 026182/0877 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 30, 2010
From: FIRETHORN HOLDINGS, LLC
To: OUTLIER, INC.
Reel/Frame 025431/0784 →
CORRECTIVE ASSIGNMENT TO CORRECT THE APPLICANT MISTAKENLY ASSIGNED THE APPLICATION TO PARENT INSTEAD OF THE SUBSIDIARY. PREVIOUSLY RECORDED ON REEL 024030 FRAME 0446. ASSIGNOR(S) HEREBY CONFIRMS THE APPLICANT MISTAKENLY ASSIGNED THE APPLICATION TO PARENT INSTEAD OF THE SUBSIDIARY.. Recorded Oct 19, 2010
From: BATADA, ASIF; LEVY, MOSHE
To: FIRETHORN HOLDINGS, LLC
Reel/Frame 025158/0189 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 4, 2010
From: BATADA, ASIF; LEVY, MOSHE
To: QUALCOMM INCORPORATED
Reel/Frame 024030/0446 →
Continuity (2)
Provisional Application 61251231 · Oct 13, 2009
Related Publication 20110087610A1 · Apr 14, 2011