1、April 2001Extensions for Financial Services (XFS) interfacespecification Release 3.0 Part 25: Identification CardDevice Class Interface PC/SC Integration GuidelinesCWA 14050-25Englische Fassung CWA 14050-25:2000ICS 35.200; 35.240.15Erweiterungen fr die Schnittstellenspezifikation fr Finanzdienst-lei
2、stungen (XFS) Version 3.0 Teil 25: Schnittstelle fr die Gerteklasse “ID-Kartengerte“ Richtlinien fr die PC/SC-IntegrationNationales VorwortDieses CEN Workshop Agreement CWA 14050-25, das vom CEN/ISSS XFS Workshop erarbeitet wurde,wird ausschlielich in englischer Sprache zur Verfgung gestellt.CEN Wor
3、kshop Agreements werden im Rahmen eines Konsortiums entwickelt. Sie unterscheiden sich vonEuropischen Normen dadurch, dass sie grundstzlich kein ffentliches Einspruchsverfahren durchlaufenund dass auch keine nationale Meinungsbildung stattfindet. Im Gegensatz zu Europischen Normen, dieden Konsens al
4、ler interessierten Kreise darstellen, haben CEN Workshop Agreements lediglich dieZustimmung der unmittelbar beteiligten Mitglieder des Konsortiums gefunden.Fr den Inhalt sind ausschlielich die Mitglieder des Konsortiums verantwortlich (siehe ergnzendeHinweise im CWA-Vorwort). Weder das CEN-Zentralse
5、kretariat, noch die CEN-Mitglieder haben den Inhaltauf eventuelle Fehler oder Widersprche zu Normen und Rechtsvorschriften geprft.Fortsetzung 18 Seiten CWA Beuth Verlag GmbH, 2001 .Jede Art der Vervielfltigung, auch auszugsweise, Ref. Nr. DIN CWA 14050-25:2001-04nur mit Genehmigung des Beuth Verlage
6、s gestattet. RW DIN CWA Preisgr. 01Alleinverkauf der Normen durch Beuth Verlag GmbH, 10772 Berlin Leerseite Rue de Stassart, 36 B-1050 BruxellesTel : +32 2 550 08 11 Fax : +32 2 550 08 19EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG WORKSHOPCWA
7、14050-25AGREEMENTNovember 2000ICS 35.200; 35.240.15Extensions for Financial Services (XFS) interface specification -Release 3.0 - Part 25: Identification Card Device Class Interface - PC/SCIntegration Guidelines 2000 CEN All rights of exploitation in any form and by any means reserved world-wide for
8、CEN National MembersRef. No CWA 14050-25:2000 EThis CEN Workshop Agreement can in no way be held as being an official standardas developed by CEN National Members.Page 2CWA 14050-25:2000Table of ContentsForeword31. Introduction .51.1 Background to Release 3.0. 51.2 PC/SC Background 51.3 References 6
9、1.3.1 XFS specifications 61.3.2 PC/SC Workgroup specifications . 61.3.3 International standards 61.3.4 Microsoft documentation 61.4 Glossary 72. PC/SC Overview 82.1 Architecture 82.1.1 Integrated Circuit Card (ICC). 82.1.2 Interface Device (IFD) 92.1.3 Interface Device Handler 92.1.4 ICC Resource Ma
10、nager. 92.1.5 Service Provider . 92.1.6 ICC Service Provider 92.2 XFS IDC Capabilities not directly exposed by Smart Card subsystem 102.2.1 Motorized Card Readers. 102.2.2 Magnetic tracks. 112.2.3 Associated Security Module . 113. Architectural Overview .123.1 Generic Model 123.1.1 IFD Service Provi
11、der 133.1.2 ICC Service Provider 133.1.3 XFS IDC Service Provider generic implementation. 133.2 New Interfaces 133.3 Integration of card readers . 143.4 Integration of smart cards. 144. IFD Service Provider COM-based interfaces 154.1 IFD Service Provider 154.2 IXFSIFDManage 164.2.1 Properties 164.2.
12、2 Methods 164.3 IXFSIFDMotorized 164.3.1 Properties 164.3.2 Methods 174.4 IXFSIFDMagneticTracks 174.4.1 Properties 174.4.2 Methods 174.5 IXFSIFDSecurityModule 184.5.1 Properties 184.5.2 Methods 18Page 3CWA 14050-25:2000ForewordThis CWA is revision 3.0 of the XFS interface specification.The move from
13、 an XFS 2.0 specification (CWA 13449) to a 3.0 specification has been prompted by a series offactors.Initially, there has been a technical imperative to extend the scope of the existing specification of the XFS Managerto include new devices, such as the Card Embossing Unit.Similarly, there has also
14、been pressure, through implementation experience and the advance of the Microsofttechnology, to extend the functionality and capabilities of the existing devices covered by the specification.Finally, it is also clear that our customers and the market are asking for an update to a specification, whic
15、h is nowover 2 years old. Increasing market acceptance and the need to meet this demand is driving the Workshop towardsthis release.The clear direction of the CEN/ISSS XFS Workshop, therefore, is the delivery of a new Release 3.0 specificationbased on a C API. It will be delivered with the promise o
16、f the protection of technical investment for existingapplications and the design to safeguard future developments.The CEN/ISSS XFS Workshop gathers suppliers as well as banks and other financial service companies. A list ofcompanies participating in this Workshop and in support of this CWA is availa
17、ble from the CEN/ISSS Secretariat.This CWA was formally approved by the XFS Workshop meeting on 2000-10-18. The specification is continuouslyreviewed and commented in the CEN/ISSS Workshop on XFS. It is therefore expected that an update of thespecification will be published in due time as a CWA, sup
18、erseding this revision 3.0.The CWA is published as a multi-part document, consisting of:Part 1: Application Programming Interface (API) - Service Provider Interface (SPI); Programmers ReferencePart 2: Service Classes Definition; Programmers ReferencePart 3: Printer Device Class Interface - Programme
19、rs ReferencePart 4: Identification Card Device Class Interface - Programmers ReferencePart 5: Cash Dispenser Device Class Interface - Programmers ReferencePart 6: PIN Keypad Device Class Interface - Programmers ReferencePart 7: Check Reader/Scanner Device Class Interface - Programmers ReferencePart
20、8: Depository Device Class Interface - Programmers ReferencePart 9: Text Terminal Unit Device Class Interface - Programmers ReferencePart 10: Sensors and Indicators Unit Device Class Interface - Programmers ReferencePart 11: Vendor Dependent Mode Device Class Interface - Programmers ReferencePart 12
21、: Camera Device Class Interface - Programmers ReferencePart 13: Alarm Device Class Interface - Programmers ReferencePart 14: Card Embossing Unit Class Interface - Programmers ReferencePart 15: Cash In Module Device Class Interface- Programmers ReferencePart 16: Application Programming Interface (API
22、) - Service Provider Interface (SPI) - Migration from Version 2.0(see CWA 13449) to Version 3.0 (this CWA) - Programmers ReferencePart 17: Printer Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (this CWA) -Programmers ReferencePart 18: Identification Card Device C
23、lass Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0(this CWA) - Programmers ReferencePage 4CWA 14050-25:2000Part 19: Cash Dispenser Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers ReferencePart 20: PIN Keypad Device Cl
24、ass Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers ReferencePart 21: Depository Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers ReferencePart 22: Text Terminal Unit Device Class Interface - Migr
25、ation from Version 2.0 (see CWA 13449) to Version 3.0(this CWA) - Programmers ReferencePart 23: Sensors and Indicators Unit Device Class Interface - Migration from Version 2.0 (see CWA 13449) toVersion 3.0 (this CWA) - Programmers ReferencePart 24: Camera Device Class Interface - Migration from Vers
26、ion 2.0 (see CWA 13449) to Version 3.0 (this CWA)- Programmers ReferencePart 25: Identification Card Device Class Interface - PC/SC Integration GuidelinesIn addition to these Programmers Reference specifications, the reader of this CWA is also referred to acomplementary document, called Release Note
27、s. The Release Notes contain clarifications and explanations on theCWA specifications, which are not requiring functional changes. The current version of the Release Notes isavailable online from http:/www.cenorm.be/isss/Workshop/XFS.The information in this document represents the Workshops current
28、views on the issues discussed as of the date ofpublication. It is furnished for informational purposes only and is subject to change without notice. CEN/ISSSmakes no warranty, express or implied, with respect to this document.Revision History:3.00 October 18, 2000 First editionPage 5CWA 14050-25:200
29、01. Introduction1.1 Background to Release 3.0The CEN XFS Workshop is a continuation of the Banking Solution Vendors Council workshop and maintains atechnical commitment to the Win 32 API. However, the XFS Workshop has extended the franchise of multi vendorsoftware by encouraging the participation of
30、 both banks and vendors to take part in the deliberations of the creationof an industry standard. This move towards opening the participation beyond the BSVCs original membership hasbeen very succesful with a current membership level of more than 20 companies.The fundamental aims of the XFS Workshop
31、 are to promote a clear and unambiguous specification for both serviceproviders and application developers. This has been achieved to date by sub groups working electronically andquarterly meetings.The move from an XFS 2.0 specification to a 3.0 specification has been prompted by a series of factors
32、. Initially,there has been a technical imperative to extend the scope of the existing specification of the XFS Manager to includenew devices, such as the Card Embossing Unit.Similarly, there has also been pressure, through implementation experience and the advance of the Microsofttechnology, to exte
33、nd the functionality and capabilities of the existing devices covered by the specification.Finally, it is also clear that our customers and the market are asking for an update to a specification, which is nowover 2 years old. Increasing market acceptance and the need to meet this demand is driving t
34、he Workshop towardsthis release.The clear direction of the XFS Workshop, therefore, is the delivery of a new Release 3.0 specification based on a CAPI. It will be delivered with the promise of the protection of technical investment for existing applications and thedesign to safeguard future developm
35、ents.1.2 PC/SC BackgroundAs part of the XFS specification, the IDC (Identification Card) Device Class includes the following support for ICC(Integrated Circuit Card, also referred as chip) management, in respect to ISO 7816 (contacted) and ISO 10536(contactless) international standards:retrieve ATR
36、(Answer To Reset), when contacting the chip through a WFS_CMD_IDC_READ_RAW_DATAcommand;communicate with the chip, through WFS_CMD_IDC_CHIP_IO commands;handle power management, through the WFS_CMD_IDC_CHIP_POWER command.Although these mechanisms provide independence to the channel used to exchange da
37、ta with the chip, through thecard reader, it does not provide independence to a given subset of capabilities provided by software embedded onthe chip, which may offer the same level of functionality, but may be implemented in different ways for chipsmanufactured by different vendors.The smart card s
38、ubsystem provided in the Win32 environment follows the specifications published by the PC/SCWorkgroup, including the following components of interest:a resource manager providing access to readers and smart cards,several COM-based smart card service providers, each providing access to a subset of ca
39、pabilities for a chip.The PC/SC (Personal Computer / Smart Card) Workgroup was formed in May 1996 in partnership with major PCand smart card companies. The main focus of the workgroup has been to develop specifications that ensureinteroperability among smart cards, smart card readers, and computers
40、made by different manufacturers. Version 1.0of these specifications were released in December 1997.This document aims to describe the relation between XFS and PC/SC and to provide guidelines for integration ofPC/SC compliant readers in the XFS subsystem, ensuring compatibility with future extensions
41、 to the IDC DeviceClass.Page 6CWA 14050-25:20001.3 ReferencesThis document is intended to cover in detail the relation between XFS and PC/SC. However, many details aboutPC/SC and smart cards are intentionally omitted for the interest of brevity, and this document often assumesbackground knowledge on
42、 these topics. The following documents may be of interest:1.3.1 XFS specificationsA.1. XFS Application Programming Interface (API)/Service Provider Interface ( SPI), Programmers ReferenceRevision 3.0, October 18, 2000A.2. XFS Identification Card Unit Device Class Interface (IDC), Programmers Referen
43、ce Revision 3.00, October18, 20001.3.2 PC/SC Workgroup specificationsInteroperability Specification for ICCs and Personal Computer Systems, version 1.0, December 1997These specifications are available on the Web at: http:/B.1. Part 1. Introduction and Architecture OverviewB.2. Part 2. Interface Requ
44、irements for Compatible IC Cards and Interface DevicesB.3. Part 3. Requirements for PC-Connected Interface DevicesB.4. Part 4. IFD Design Considerations and Reference Design InformationB.5. Part 5. ICC Resource Manager DefinitionB.6. Part 6. ICC Service Provider Interface DefinitionB.7. Part 7. Appl
45、ication Domain/Developer Design ConsiderationsB.8. Part 8. Recommendation for Implementation of Security and Privacy ICC Devices1.3.3 International standardsC.1. ISO/IEC 7816-4 Identification Cards - Integrated Circuit(s) cards with contacts - Part 4: Interindustrycommands for interchangeC.2. ISO/IE
46、C 7816-5 Identification Cards - Integrated Circuit(s) cards with contacts - Part 5: Numbering systemand registration procedure for application identifiers1.3.4 Microsoft documentationD.1. MSDN Library, Platform SDK, Base Services, Smart CardD.2. MSDN Library, DDK Documentation, Smart Card DDKD.3. Sm
47、art Cards for Windows, on the Web at: http:/ 7CWA 14050-25:20001.4 GlossaryAPDU Application Protocol Data Unit.ATR Answer To Reset.The transmission sent by an ICC to the reader in response to a reset condition.CLSID Class Identifier.A globally unique identifier (GUID) associated with a COM class obj
48、ect. If a classobject will be used to create more than one instance of an object, the associatedserver application should register its CLSID in the system registry so that clients canlocate and load the executable code associated with the object(s).CHV Card Holder Verification.COM Component Object M
49、odel.The OLE object-oriented programming model that defines how objects interactwithin a single process or between processes. In COM, clients have access to anobject through interfaces implemented on the object. See also Interface.COM Object An object that conforms to the OLE Component Object Model (COM). A COMobject is an instance of an object definition, which specifies the objects data and oneor more implementations of interfaces on the object. Clients inte
