Systems, methods, and computer program products for managing service installation

• US 9,286,049 B2
• Filed: 03/24/2014
• Issued: 03/15/2016
• Est. Priority Date: 03/26/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Gargiulo, Michael J., Hay, Florent
• Primary Examiner(s): Lee, Marina
• Application Number:
  US14/223,207
• Publication Number:
  US 20140298322A1
• Time in Patent Office: 722 Days
• Field of Search: 717/175
• US Class Current: 1/1
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: H04W 12/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning

Abstract

Systems, methods, and computer program products are provided for managing installation of services on a secure element having a secure element profile. A request to install a service on the secure element is received. There is a determination of a preferred version of the service corresponding to the secure element profile of the secure element. There is also a determination of an existing version of the service loaded on the secure element. Using a rules engine, there is a determination of whether to install on the secure element either the existing version of the service or the preferred version of the service. A command is transmitted to either (a) install the existing version of the service or (b) delete the existing version of the service and load and install the preferred version of the service, based on the determination using the rules engine.

Claims

1. A system to manage installation of services on secure elements having secure element profiles, comprising:

at least one memory including a rules engine; and

a processor coupled to the at least one memory, the processor being operable to;

receive a request to install a service on a secure element comprising a secure element profile, the request comprising a service identifier identifying the service;

access a rules engine providing a correspondence between the service identifier, a secure element profile, and an indication of a preferred version of the service;

determine, using the rules engine, the preferred version of the service corresponding to the secure element profile of the secure element;

determine an existing version of the service already loaded but not installed in the secure element;

determine, if the preferred version of the service is the same as the existing version of the service, to install the existing version of the service on the secure element and, if the preferred version of the service is not the same as the existing version of the service, to install the preferred version of the service on the secure element; and

transmit a command to the secure element, the command comprising instructions either to (a) install the existing version of the service on the secure element or (b) load and install the preferred version of the service on the secure element, in accordance with the determination regarding whether or not the preferred version of the service is the same as the existing version of the service.

2. The system according to claim 1,

wherein the request to install a service is received from a service provider associated with the service;

and

wherein the processor is further operable to transmit a response indicating the installed version of the service to the associated service provider.

3. The system according to claim 2, wherein the service provider generates one or more scripts to personalize the service and to install credentials for service based on the response.

4. The system according to claim 1, wherein the rules engine includes a list of preferred versions of a service corresponding to specific secure element profiles.

5. The system according to claim 4, wherein the rules engine is configurable dynamically in real-time or pseudo-real-time.

6. The system according to claim 1, wherein the command includes instructions to remove the existing version of the service from the secure element if the preferred version is different from the existing version.

7. The system according to claim 1, wherein the secure element profile comprises information about the corresponding secure element including model information, processing and memory capabilities, and applications loaded on the secure element.

8. The system according to claim 1, wherein the processor is further operable to report an error if the service to be installed is not eligible to be installed on the secure element.

9. The system according to claim 8, wherein the determination of eligibility is based on the rules engine.

10. The system according to claim 1, wherein the service includes one or more applets.

11. A method for managing installation of services on a secure element having a secure element profile, the method comprising:

receiving a request to install a service on the secure element;

determining a preferred version of the service corresponding to the secure element profile of the secure element;

determining an existing version of the service already loaded on the secure element but not installed;

determining, using a rules engine, whether to install on the secure element either the existing version of the service or the preferred version of the service; and

transmitting a command to delete the existing version of the service and load and install the preferred version of the service, based on the determination using the rules engine.

12. The method according to claim 11, wherein the request to install a service is received from a service provider associated with the service, and wherein the processor is further operable to transmit a response indicating the installed version of the service to the associated service provider.

13. The method according to claim 12, wherein the service provider generates one or more scripts for personalizing the service and installing credentials for service based on the response.

14. The method according to claim 11, wherein the rules engine includes a list of preferred versions of a service corresponding to specific secure element profiles.

15. The method according to claim 14, wherein the rules engine is configurable dynamically in real-time or pseudo-real-time.

16. The method according to claim 11, wherein the rules engine includes instructions to remove the existing version of the service from the secure element.

17. The method according to claim 11, wherein a secure element profile comprises information about a corresponding secure element including model information, processing and memory capabilities, and applications loaded on the secure element.

18. The method according to claim 11, further comprising reporting an error if the service to be installed is not eligible to be installed on the secure element.

19. The method according to claim 18, wherein the determination of eligibility is based on the rules engine.

20. The method according to claim 11, wherein the service includes one or more applets.

21. A non-transitory computer-readable medium having stored thereon sequences of instructions for causing one or more processors to:

receive a request to install a service on a secure element;

determine a preferred version of the service corresponding to a secure element profile of the secure element;

determine an existing version of the service already loaded on the secure element but not installed;

determine, using a rules engine, whether to install on the secure element either the existing version of the service or the preferred version of the service; and

transmit a command to install the existing version of the service based on the determination using the rules engine.

22. The computer-readable medium according to claim 21, wherein the request to install a service is received from a service provider associated with the service, and wherein the processor is further operable to transmit a response indicating the installed version of the service to the associated service provider.