Method for removable element authentication in an embedded system

• US 8,397,289 B2
• Filed: 05/07/2008
• Issued: 03/12/2013
• Est. Priority Date: 05/07/2007
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Naniyat, Arun, Arunan, Thenmozhi
• Primary Examiner(s): Chea, Philip
• Assistant Examiner(s): DOLLY, KENDALL LYNN
• Application Number:
  US12/151,470
• Publication Number:
  US 20090241186A1
• Time in Patent Office: 1,770 Days
• Field of Search: 726 4- 7, 726 16- 19, 726/21
• US Class Current: 726/17
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 21/6272 by registering files or documents with a third party
• CPC Class Codes: G06F 21/73 by creating or determining hardware identification, e.g. serial numbers
• CPC Class Codes: G06F 2221/2129 Authenticate client device independently of the user
• CPC Class Codes: H04W 12/065 Continuous authentication

Abstract

The present invention proposes a method for protecting and monitoring removable entities in an embedded system. In accordance with the present invention, prior to insertion of a removable entity in the embedded system, a user registers details of the removable entity in the device host. The details may be entered after entering a password or a PIN. A registration identification is calculated based on an algorithm in the device host and is then stored in the host. After the removable entity is inserted, it is registered in an unalterable area (e.g. flash memory) of the device host. Information such as the category of the removable entity, a device number, etc. may be exchanged between the device host and the removable entity. The device host then computes a registration identification based on a Removable Entity Registration Algorithm. The identifications are then compared, and the device host displays the details of the removable entity to the user.

Claims

1. A method for removable element authentication in an embedded system comprising the steps of:

receiving, by a device host, a first removable entity product manufacture number, a first removable entity type category and a first secret key previously stored in the embedded system prior to insertion of a removable entity into the embedded system;

calculating, by the device host, a first registration identification by-applying the first removable entity product manufacture number, the first removable entity type category and the first secret key to a secure algorithm stored in the device host and storing the result of the calculation in the device host;

receiving, by the device host, a second removable entity product manufacture number, a second removable entity type category and a third registration identification stored in the removable entity after the removable entity is inserted into the embedded system;

calculating, by the device host, a second registration identification by-applying the second removable entity product manufacture number, the second removable entity type category and the first secret key to the secure the algorithm;

comparing the first registration identification, the second registration identification and the third registration identification with each other; and

displaying details of the removable entity to a user by the device if the first registration identification, the second registration identification and the third registration identification are identical to each other;

wherein when the embedded system is powered off, a device host user interface of the embedded system remains active and a device authentication of the removable entity is performed upon insertion of the removable entity into the embedded system regardless of a power status of the embedded system via a battery backup of the device host user interface.

2. A method as claimed in claim 1, wherein the interface between the removable entity and the device host is made operable, even during device power off, by using standby battery support.

3. A method as claimed in claim 1, wherein an authenticity of the removable entity is checked constantly by the device host.

4. A method as claimed in claim 1, wherein registering details are registered in the device host after entering a password or a Personal Identification Number(PIN).

5. A method as claimed in claim 1, wherein the device host reads the second removable entity product manufacture number, the second removable entity type category and the third registration identification through a prescribed message sent from the device host to the removable entity.

6. A method as claimed in claim 1, wherein the usage of the second registration identification by the device host is performed through a Host_TEE_Interaction message, and by this message, the device is authenticated before every secure data transaction.

14. A method as claimed in claim 1, wherein a secret key is extracted from a secure registry location of the embedded system and is also supplied with the removable entity or sent to a user via Short Message Service (SMS).

7. A device for removable entity authentication in an embedded system, comprising:

a slot for receiving said removable entity;

an input/output device for receiving/output desired data items;

a processor in communication with said slot, said input/output device and a memory, the memory contain code which when accessed by the processor causing the processor to;

receive a first removable entity product manufacture number, a first removable entity type category and a first secret key previously stored in the embedded system prior to insertion of the removable entity into the embedded system;

calculate a first registration identification by applying the first removable entity product manufacture number, the first removable entity type category and the first secret key to a secure algorithm;

receive a second removable entity product manufacture number, a second removable entity type category and a third registration identification stored in the removable entity after the removable entity is inserted into the embedded system;

calculate a second registration identification by applying the second removable entity product manufacture number, the second removable entity type category and the first secret key to the secure the algorithm;

compare the first registration identification, the second registration identification and the third registration identification with each other; and

display details of the removable entity to a user if the first registration identification, the second registration identification and the third registration identification are identical to each other;

wherein when the embedded system is powered off, a device host user interface of the embedded system remains active and a device authentication of the removable entity is performed upon insertion of the removable entity into the embedded system regardless of a power status of the embedded system via a battery backup of the device host user interface.

8. The device as claimed in claim 7, further comprising:

a standby battery, wherein an interface in said slot between the removable entity and the processor is operable, even during device power off, by using said standby battery.

9. The device as claimed in claim 7, wherein said processor further:

continually checking an authenticity of the removable entity.

10. The device as claimed in claim 7, wherein the first removable entity product manufacture number, the first removable entity type category and the first secret key are registered after entering a password or a Personal Identification Number(PIN).

11. The device as claimed in claim 7, wherein the processor reads the second removable entity product manufacture number, the second removable entity type category and the third registration identification through a prescribed message sent from the processor to the removable entity.

12. The device as claimed in claim 7, wherein the usage of the second registration identification by the processor is done through a Host_TEE_Interaction message, and by this message, the device is authenticated before every secure data transaction.

13. The device as claimed in claim 7, the processor, in response to removal of said removable entity, executing code for:

de-registering the removable entity;

de-listing the removable entity as non-secure; and

deleting the first registration identification.

15. A device as claimed in claim 7, wherein a secret key is extracted from a secure registry location of the embedded system and is also supplied with the removable entity or sent to a user via Short Message Service (SMS).