1 / 14

PC/SC Applications and New Developments

PC/SC Applications and New Developments. Boris Balacheff Member of PC/SC Technical Workgroup. CTST’ 2000 Miami. PC/SC Revision 1.0 Limitations. Emergence of Multi-application smartcards finds a lack of support in Revision 1.0 (I.e. Windows for Smartcards, JavaCards…):

venice
Download Presentation

PC/SC Applications and New Developments

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PC/SC Applications and New Developments Boris Balacheff Member of PC/SC Technical Workgroup CTST’ 2000 Miami

  2. PC/SC Revision 1.0 Limitations • Emergence of Multi-application smartcards finds a lack of support in Revision 1.0 (I.e. Windows for Smartcards, JavaCards…): It is not possible to manage dynamically the off-card components that are used to interact with on-card applications • Smartcard reader support is not up-to-date with current reader technology developments • No support for synchronous and contactless cards CTST’ 2000 Miami

  3. Multi-Application Cards • Currently, Service Providers are mapped to a specific card-type (using ATR) in the Resource Manager database • With multi-application cards, the card-type does not reflect the card’s functionality/applications • Need for a flexible and dynamic mechanism to update Service Provider information on the PC platform along with on-card applications changes CTST’ 2000 Miami

  4. Multi-Application Cards (cont.) • It is not enough that the PC/SC Resource Manager can only recognise a smartcard based on manufacturer-specific ATR information • To be able to dynamically assign Services Providers, information describing the card must be held on the card • Need for a card recognition mechanism that is more flexible, in order to reflect what is on the card dynamically CTST’ 2000 Miami

  5. Enhanced Smartcard Readers • Revision 1.0 only supports readers with basic APDU communication capabilities • Reader technologies with extended capabilities become widespread (pinpads, displays, multi-slot, SecurePin, biometrics…) • Need to allow interoperability between cards and PC applications that use these new reader capabilities CTST’ 2000 Miami

  6. Other Card Technologies • Contactless cards are a growing market • Synchronous cards are already used by many applications • Need to provide some support to allow the same interfaces and look-and-feel as asynchronous cards, at the PC application level CTST’ 2000 Miami

  7. Introducing PC/SC Revision 2.0 Revision 2.0 of PC/SC aims at addressing these limitations. It does this by introducing the following: • A New card recognition mechanism • A Dynamic Service Provider Assignment mechanism • A Mechanism for enhanced smartcard reader support • Support for contactless and synchronous cards CTST’ 2000 Miami

  8. PC/SC 2.0 Architecture ICCSPs in the PC/SC Revision 1.0 sense Card-Aware Application Interfaces Enhanced reader capabilities ADSP IFD SP ICCOS-SP ADSP Locator Resource Manager Abstraction of reader capabilities Slot 1 Slot 2 Pin Pad Display New component to manage dynamic access to on-card applications IFD Handler Reader Smart Card CTST’ 2000 Miami

  9. Card and Reader Card Operating System Card Applications CardInfo Structure IFD Subsystem (IFD + IFD Handler) Software Components ICCOS Service Provider (ICCOS-SP) Application Domain Service Provider (ADSP) ADSP Locator (ADSPL) IFD Service Provider (IFDSP) Revision 2.0 Approach Typical Responsibility Card Vendor Application Developer Card Issuer IFD Vendor CTST’ 2000 Miami

  10. Initial Access Data ATR CardInfo Data Structures CardInfo structure ATR History Bytes 3 1 2 ADSPL id ICCOS id Communications Parameters Initial Access Data Command Card Recognition Resource Manager Smartcard CTST’ 2000 Miami

  11. ListAppInterfaces ADSP-L ID_ADSP_AppX + reader name Find AppInterfaces I1 and I2 AppInterfaces and corresponding ADSP Guids Instantiate (from ADSPL id) ListAppInterfaces AppInterfaces Guid of ADSP IIDs of Interfaces 4 1 2 3 5 6 7 8 ID_ADSP_AppX IID_I1, IID_I2 Service Provider Assignment Application Resource Manager Smartcard CTST’ 2000 Miami

  12. These components are responsible for implementing and interfacing the Enhanced Reader Capabilities Enhanced IFDs ICC-Aware Application ADSP IFD SP ICCOS-SP ADSP Locator Resource Manager Slot 1 Slot 2 Pin Pad Display IFD Handler Reader Smart Card CTST’ 2000 Miami

  13. Contactless and Synchronous Cards ICC-Aware Application ADSP IFD SP ICCOS-SP ADSP Locator Resource Manager Slot 1 Slot 2 Pin Pad Display IFD Handler These components are responsible for implementing PC/SC support for Contactless and/or Synchronous cards Reader Smart Card CTST’ 2000 Miami

  14. Further Information • WhitePaper on PC/SC Revision 2.0 available at: http://www.pcscworkgroup.com CTST’ 2000 Miami

More Related