IP Library Granted Patent US 11,601,273
Granted Patent B2
US 11,601,273 · App. 17/176,001 · Granted Mar 7, 2023

Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements

Inventor: Michael J. Gargiulo (Corinth, TX)
Assignee: GOOGLE LLC
H04L9/321G06F8/61H04L9/00H04L67/10H04L67/34H04W4/50H04W4/60H04W4/80H04W8/18H04W12/086H04W12/35H04W12/40H04L2209/80
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 11,601,273
App. No.
17/176,001
Granted
Mar 7, 2023
Kind
B2
Abstract

System, methods, and computer program products are provided for interfacing between one of a plurality of service provider (SP) trusted service managers (TSM) and one of a plurality of secure elements (SE). A first request to renew a service is received from an SP system over a communications network. The first request includes a service qualifier associated with the service. A secure element corresponding to the service qualifier is determined. A second request to delete data associated with the service qualifier from the secure element is transmitted to the secure element. A third request to install an application on the secure element is transmitted to the secure element. A fourth request to activate the application on the secure element is transmitted to the secure element.

Claims (45)

1. A computer-implemented method to interface with secure elements, comprising:

receiving, by a central trusted service manager computing system, a request to delete one or more services stored on a secure element, the request including a service qualifier identifying a particular instance of the one or more services to be deleted from the secure element;

determining, by the central trusted service manager computing system, one or more commands executable by the secure element to delete the particular instance of the one or more services; and

transmitting, by the central trusted service manager computing system to a central security domain of the secure element, a request to execute the one or more commands to delete from the secure element data associated with the service qualifier identifying the particular instance of the one or more services.

2. The computer-implemented method of claim 1 , wherein the one or more commands are configured for execution by the secure element to:

identify data corresponding to each of the one or more services, the identified data comprising one or more unique numbers each identifying a different payment account, and

delete, via the central security domain, the one or more unique numbers each identifying the different payment account from the secure element.

3. The computer-implemented method of claim 1 , further comprising:

determining, by the central trusted service manager computing system, that the secure element corresponds to the request to delete the one or more services stored on the secure element.

4. The computer-implemented method of claim 1 , further comprising:

determining, by the central trusted service manager computing system, which commands are executable by the secure element to delete the data associated with the one or more services from the secure element.

5. The computer-implemented method of claim 1 , wherein the secure element comprises one or more instances of an application associated with each of the one or more services on the secure element.

6. The computer-implemented method of claim 5 , wherein each instance of the application is associated with a different service provider computing system.

7. The computer-implemented method of claim 1 , wherein the one or more commands are configured for execution by the secure element to:

lock an application associated with the data.

8. A system to interface with secure elements, comprising:

one or more computing devices comprising at least one memory and a processor communicatively coupled to the at least one memory, wherein the processor executes application code instructions that are stored in the at least one memory to cause the one or more computing devices to:

receive, by a central trusted service manager computing system, a request to delete one or more services stored on a secure element, the request including a service qualifier identifying a particular instance of the one or more services to be deleted from the secure element;

determine, by the central trusted service manager computing system, one or more commands executable by the secure element to delete the particular instance of the one or more services; and

transmit, by the central trusted service manager computing system to a central security domain of the secure element, a request to execute the one or more commands to delete from the secure element data associated with the service qualifier identifying the particular instance of the one or more services.

9. The system of claim 8 , wherein the one or more commands are configured for execution by the secure element to:

identify data corresponding to each of the one or more services, the identified data comprising one or more unique numbers each identifying a different payment account, and

delete, via the central security domain, the one or more unique numbers each identifying the different payment account from the secure element.

10. The system of claim 8 , wherein the operations further comprise:

determining, by the central trusted service manager computing system, that the secure element corresponds to the request to delete the one or more services stored on the secure element.

11. The system of claim 8 , wherein the operations further comprise:

determining, by the central trusted service manager computing system, which commands are executable by the secure element to delete the data associated with the one or more services from the secure element.

12. The system of claim 8 , wherein the secure element comprises one or more instances of an application associated with each of the one or more services on the secure element.

13. The system of claim 12 , wherein each instance of the application is associated with a different service provider computing system.

14. The system of claim 8 , wherein the one or more commands are configured for execution by the secure element to:

lock an application associated with the data.

15. One or more non-transitory computer readable media that collectively store instructions that when executed by one or more processors cause the one or more processors to perform operations, the operations comprising:

receiving, by a central trusted service manager computing system, a request to delete one or more services stored on a secure element, the request including a service qualifier identifying a particular instance of the one or more services to be deleted from the secure element;

determining, by the central trusted service manager computing system, one or more commands executable by the secure element to delete the particular instance of the one or more services; and

transmitting, by the central trusted service manager computing system to a central security domain of the secure element, a request to execute the one or more commands to delete from the secure element data associated with the service qualifier identifying the particular instance of the one or more services.

16. The one or more non-transitory computer readable media of claim 15 , wherein the one or more commands are configured for execution by the secure element to:

identify data corresponding to each of the one or more services, the identified data comprising one or more unique numbers each identifying a different payment account, and

delete, via the central security domain, the one or more unique numbers each identifying the different payment account from the secure element.

17. The one or more non-transitory computer readable media of claim 15 , further comprising:

determining, by the central trusted service manager computing system, that the secure element corresponds to the request to delete the one or more services stored on the secure element.

18. The one or more non-transitory computer readable media of claim 15 , wherein the operations further comprise:

determining, by the central trusted service manager computing system, which commands are executable by the secure element to delete the data associated with the one or more services from the secure element.

19. The one or more non-transitory computer readable media of claim 15 , wherein the secure element comprises one or more instances of an application associated with each of the one or more services on the secure element.

20. The one or more non-transitory computer readable media of claim 15 , wherein the one or more commands are configured for execution by the secure element to:

lock an application associated with the data.

Assignments (3)
ENTITY CONVERSION Recorded Feb 16, 2021
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 056530/0406 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 16, 2021
From: JVL VENTURES, LLC
To: GOOGLE INC.
Reel/Frame 055265/0027 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 16, 2021
From: GARGIULO, MICHAEL J.
To: JVL VENTURES, LLC
Reel/Frame 055304/0649 →
Continuity (5)
Continuation 16054264 · Aug 3, 2018
Continuation 15280104 · Sep 29, 2016
Division 14029463 · Sep 17, 2013
Provisional Application 61702653 · Sep 18, 2012
Related Publication 20210167961A1 · Jun 3, 2021