ENHANCED LIFECYCLE MANAGEMENT OF SECURITY MODULE

• US 20130152159A1
• Filed: 12/07/2012
• Published: 06/13/2013
• Est. Priority Date: 12/07/2011
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Holtmanns, Silke, Lindholm, Rune
• Granted Patent: US 9,021,548 B2
• Time in Patent Office: Days
• US Class Current: 726/1
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 2221/2147 Locking files
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/48 using secure binding, e.g. securely binding identity modules to devices, services or applications

Abstract

A method, computer program, apparatus and a secure module are described. By example, in the method there are steps of receiving a request from a first entity for a secure module to enter an unlock lifecycle state; requesting confirmation to enter the unlock lifecycle state; and if the request is confirmed, transitioning the secure module from a current lifecycle state to the unlock lifecycle state.

Claims

1. A method comprising:

receiving a request for a secure module to enter an unlocked lifecycle state;

requesting confirmation to enter the unlocked lifecycle state;

if the request is confirmed, transitioning the secure module from a current lifecycle state to the unlocked lifecycle state; and

subsequently transitioning the secure module from the unlocked lifecycle state to a locked lifecycle state.

2. The method of claim 1, where requesting confirmation comprises requesting an entity that currently manages the secure module to confirm the request to enter the unlocked lifecycle state.

3. The method of claim 1, where transitioning to the locked lifecycle state comprises requesting a user associated with the secure module to confirm the transition to the locked lifecycle state.

4. The method of claim 3, where the user'"'"'s confirmation indicates that the user has knowledge of a contract that will apply when the locked lifecycle state is entered.

5. The method as in claim 3, where the user confirms via a user interface of a device in which the secure module is contained.

6. The method of claim 1, where transitioning the secure module from the current lifecycle state to the unlocked lifecycle state enables a forward reference to stored information related to operation in the unlocked life cycle state.

7. The method of claim 1, further comprising transitioning the secure module from the unlocked lifecycle state to the locked lifecycle state without user intervention.

8. The method of claim 1, where transitioning the secure module from the current lifecycle state to the unlocked lifecycle state occurs automatically upon expiration of a current contract.

9. The method of claim 1, where transitioning the secure module from the unlocked lifecycle state to the locked lifecycle state transfers management responsibility for the secure module to an entity that had management responsibility for the secure module when the secure module was previously in the locked lifecycle state, or to a different entity.

10. The method as in claim 1, where the method is performed at least in part by a policy control function of the secure module, and where the secure module is embodied as a UICC or is embodied as an embedded UICC.

11-12. -12. (canceled)

13. A non-transitory computer-readable medium that contains software program instructions, where execution of the software program instructions by at least one data processor results in performance of operations that comprise:

receiving a request for a secure module to enter an unlocked lifecycle state;

requesting confirmation to enter the unlocked lifecycle state;

if the request is confirmed, transitioning the secure module from a current lifecycle state to the unlocked lifecycle state; and

subsequently transitioning the secure module from the unlocked lifecycle state to a locked lifecycle state.

14. The computer readable medium of claim 13, where requesting confirmation comprises requesting an entity that currently manages the secure module to confirm the request to enter the unlocked lifecycle state.

15. The computer readable medium of claim 13, where transitioning to the locked lifecycle state comprises requesting a user associated with the secure module to confirm the transition to the locked lifecycle state, where the user'"'"'s confirmation indicates that the user has knowledge of a contract that will apply when the locked lifecycle state is entered, and where transitioning the secure module to the unlocked lifecycle state occurs automatically upon expiration of a current contract.

21. The computer readable medium of claim 13, where transitioning the secure module from the unlocked lifecycle state to the locked lifecycle state returns management responsibility for the secure module to an entity that had management responsibility for the secure module when the secure module was previously in the locked lifecycle state, or to a different entity.

16-20. -20. (canceled)

22-24. -24. (canceled)

25. An apparatus comprising a processor and a memory including computer program code, the memory and computer program code being configured, with the processor, to cause the apparatus at least to receive a request for a secure module to enter an unlocked lifecycle state;

to request confirmation to enter the unlocked lifecycle state;

if the request is confirmed, to transition the secure module from a current lifecycle state to the unlocked lifecycle state; and

to subsequently transition the secure module from the unlocked lifecycle state to a locked lifecycle state.

26. The apparatus of claim 25, where requesting confirmation comprises requesting an entity that currently manages the secure module to confirm the request to enter the unlocked lifecycle state.

27. The apparatus of claim 25, where transitioning to the locked lifecycle state comprises requesting a user associated with the secure module to confirm the transition to the locked lifecycle state.

31. The apparatus of claim 25, where transitioning the secure module from the unlocked lifecycle state to the locked lifecycle state without user intervention automatically upon expiration of a current contract.

33. The apparatus of claim 25, where transitioning the secure module from the unlocked lifecycle state to the locked lifecycle state returns management responsibility for the secure module to an entity that had management responsibility for the secure module when the secure module was previously in the locked lifecycle state, or to a different entity.

35. The apparatus of claim 25, where the secure module is embodied as a UICC or is embodied as an embedded UICC.

28-30. -30. (canceled)

32. (canceled)

34. (canceled)

36-39. -39. (canceled)