Method of accessing applications in a secure mobile environment

• US 9,843,933 B2
• Filed: 01/08/2015
• Issued: 12/12/2017
• Est. Priority Date: 06/24/2008
• Status: Active Grant

• Current Assignee: NXP B.V. (NXP Semiconductors NV)
• Original Assignee: NXP B.V. (NXP Semiconductors NV)
• Inventors: Corda, Alexandre, Brule, Dominique, Smith, Mathew
• Primary Examiner(s): Potratz, Daniel
• Application Number:
  US14/592,451
• Publication Number:
  US 20150135278A1
• Time in Patent Office: 1,069 Days
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/341 Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
• CPC Class Codes: G06Q 20/3552 Downloading or loading of personalisation data
• CPC Class Codes: G06Q 20/3574 Multiple applications on card
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 12/08 Access security

Abstract

A method of accessing, in a mobile communication device, an application issued by a Service Provider from a trusted application, also known as a wallet. A secure element, such as a SmartMX device, comprises a service manager that manages the application and a link between the application and an application-codec issued by the Service Provider, wherein the application-codec is designed for interfacing between the service manager and the application, for processing an access request requesting access to the application received from the service manager and, triggered by the wallet, accessing the application via the service manager by means of the link between the application and the application-codec, such that the application-codec linked with the respective application performs accessing the application under control of the service manager.

Claims

1. A mobile communication device configured to communicate with a wireless communication network comprising:

an application issued by a Service Provider;

a trusted application configured to provide service requests to a secure element; and

the secure element, separate from the trusted, application, comprising;

a service manager that is configured to manage the application issued by the Service Provider, to receive service requests provided by the trusted application, and based on the service requests to provide access requests to an application-codec; and

the application-codec that is configured to

process access requests received from the service manager and in response to the received access requests to access the application issued by the Service Provider;

wherein the service manager is configured to maintain a linking record indicating the application-codec is to process access requests to the application issued by the Service Provider, and in response to receiving a particular request from the trusted application the service manager determines, based on the linking record, to provide a particular access request to the application-codec.

2. The mobile communication device of claim 1, wherein the application-codec is part of the application issued by the Service Provider.

3. The mobile communication device of claim 1, wherein the application issued by the Service Provider is stored on the secure element.

4. The mobile communication device of claim 1, wherein the application issued by the Service Provider is stored in another unit of the mobile communication device.

5. The mobile communication device of claim 1, wherein the application-codec is a Java™

smart card object.

6. The mobile communication device of claim 5, wherein the Java™

smart card object is part of the application issued by the Service Provider.

7. The mobile communication device of claim 1, wherein the service manager is further configured to receive the application-codec and store the received application-codec in the secure element.

8. The mobile communication device of claim 1, wherein the service manager is further configured to store a linking record that reflects a link between a first application and a respective application-codec in the secure element.

9. The mobile communication device of claim 1, wherein the service manager is further configured to receive a link indication from the Service Provider in lieu of an already received application-codec.

10. The mobile communication device of claim 1, wherein the service manager is configured to generate a linking record based upon a link indication that corresponds to an already received application-codec.

11. A mobile communication device configured to communicate with a wireless communication network comprising:

an application issued by a Service Provider;

a trusted application configured to provide service requests to a secure element;

a secure element separate from the trusted application, wherein the secure element has a service manager that is configured to manage the application issued by the Service Provider, to receive service requests provided by the trusted application, and based on the service requests to provide access requests to an application-codec; and

the application-codec configured to provide an interface function, between the service manager and the application issued by the Service Provider, wherein the interface function to process access requests received from the service manager in response to requests provided by the trusted application, wherein the service manager is configured to manage a link between the application issued by the Service Provider and the interface, and request access to the application issued by the Service Provider by the link between the application issued by the Service Provider and the interface, such that the interface linked with a respective application issued by the Service Provider is configured to access the respective application issued by the Service Provider.

12. The mobile communication device of claim 11, wherein the application-codec is provided by the Service Provider substantially concurrently with the application issued by the Service Provider.

13. The mobile communication device of claim 11, wherein the application issued by the Service Provider is stored on the secure element.

14. The mobile communication device of claim 11, wherein the application issued by the Service Provider is stored in another unit of the mobile communication device.

15. The mobile communication device of claim 11, wherein the application-codec is a Java™

smart card object.

16. The mobile communication device of claim 15, wherein the Java™

smart card object is part of the application issued by the Service Provider.

17. The mobile communication device of claim 11, wherein the service manager is configured to receive the application-codec and store the received application-codec in the secure element.

18. The mobile communication device of claim 11, wherein the service manager is configured to store a linking record that reflects a link between a first application and a respective application-codec in the secure element.

19. The mobile communication device of claim 11, wherein the service manager is configured to receive a link indication from the Service Provider in lieu of an already received application-codec.

20. The mobile communication device of claim 11, wherein the service manager is configured to generate a linking record based upon a link indication that corresponds to an already received application-codec.