IDENTIFICATION OF A SMART CARD ON A PLUG AND PLAY SYSTEM

• US 20090328179A1
• Filed: 06/27/2008
• Published: 12/31/2009
• Est. Priority Date: 06/27/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Francomacaro, Salvatore, Kasselman, Pieter Retief, Herskedal, Eirik, Su, Xiaohong
• Granted Patent: US 8,607,321 B2
• Time in Patent Office: Days
• US Class Current: 726/9
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers

Abstract

Techniques for identifying a smart card in a plug and play system. The technique requires identifying a unique code identifier and loading a smart card minidriver according to the unique code identifier.

Claims

1. A method comprising:

inserting a smart card into a plug and play system;

identifying an application linking the application to the smart card, wherein the identifying comprises;

issuing a get data command, wherein the get data command comprises a unique identifier comprising a version number, a vendor number, and a global unique identifier (GUID); and

loading a corresponding smart card minidriver according to an identification of the smart card.

2. The method according to claim 1, wherein the GUID uniquely identifies the smart card and the application combination used to detect and load the corresponding smart card minidriver.

3. The method according to claim 1, further comprising identifying the application linking the application to the smart card by reading an elementary file of an answer to reset (EF.ATR), if the smart card does not answer to the get data command.

4. The method according to claim 3, wherein the EF.ATR comprises being used for a contactless smart card.

5. The method according to claim 3, further comprising identifying the application linking the application to the smart card using a historical byte of the answer to reset (ATR), wherein the historical byte is extracted by parsing the ATR.

6. A system comprising:

a processor;

a memory coupled to the processor;

one or more smart card readers coupled to the processor and configured to establish a connection with one or more smart cards;

a smart card service manager configured to identify one or more smart card applications corresponding to the one or more smart cards, wherein the one or more smart cards are identified utilizing a series of commands.

7. The system according to claim 6, wherein the smart application comprises a cryptographic service provider.

8. The system according to claim 6, further comprising a corresponding smart card minidriver.

9. The system according to claim 8, wherein the corresponding smart card minidriver comprises being loaded in response to a get data command.

10. The system according to claim 9, wherein the response to the get data command comprises a 16-byte global unique identifier (GUID).

11. The system according to claim 6, wherein the corresponding smart card minidriver comprises being loaded in response to an EF.ATR command.

12. The system according to claim 11, wherein the response to the EF.ATR command comprises a 16-byte GUID.

13. The system according to claim 12, wherein the smart card comprises a contactless smart card.

14. The system according to claim 8, wherein the corresponding smart card minidriver comprises being loaded in response to a historical byte of an answer to reset (ATR).

15. One or more computer-readable storage media containing instructions that are executable by a computing device to perform actions comprising:

inserting a smart card into a system;

identifying an application linking the application to the smart card, wherein the identifying comprises;

issuing a get data command;

issuing an elementary file of an answer to reset (EF.ATR) command if the smart card does not respond to the get data command;

loading a smart card minidriver according to an identification of a combination of the application and the smart card.

16. The one or more computer-readable storage media according to claim 15, wherein the get data command comprises a unique identifier to implement the smart card.

17. The one or more computer-readable storage media according to claim 15, wherein a response to the EF.ATR command comprises a 16-byte GUID.

18. The one or more computer-readable storage media according to claim 17, wherein the EF.ATR comprises being used for a contactless smart card.

19. The one or more computer-readable storage media according to claim 15, wherein the smart application comprises being a cryptographic service provider.

20. The one or more computer-readable storage media according to claim 15, further comprising identifying the application linking the application to the smart card using a historical byte of the answer to reset (ATR), wherein the historical byte is extracted by parsing the ATR.