1、April 2001Extensions for Financial Services (XFS)interface specification Release 3.0 Part 8: Depository Device Class InterfaceCWA 14050-8Englische Fassung CWA 14050-8:2000ICS 35.200; 35.240.40Erweiterungen fr die Schnittstellenspezifikation fr Finanzdienst-leistungen (XFS) Version 3.0 Teil 8: Schnit
2、tstelle fr die Gerteklasse “Depositgerte“Nationales VorwortDieses CEN Workshop Agreement CWA 14050-8, das vom CEN/ISSS XFS Workshop erarbeitet wurde,wird ausschlielich in englischer Sprache zur Verfgung gestellt.CEN Workshop Agreements werden im Rahmen eines Konsortiums entwickelt. Sie unterscheiden
3、 sich vonEuropischen Normen dadurch, dass sie grundstzlich kein ffentliches Einspruchsverfahren durchlaufenund dass auch keine nationale Meinungsbildung stattfindet. Im Gegensatz zu Europischen Normen, dieden Konsens aller interessierten Kreise darstellen, haben CEN Workshop Agreements lediglich die
4、Zustimmung 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-Zentralsekretariat, noch die CEN-Mitglieder haben den Inhaltauf eventuelle Fehler oder Wid
5、ersprche zu Normen und Rechtsvorschriften geprft.Fortsetzung 23 Seiten CWA Beuth Verlag GmbH, 2001 .Jede Art der Vervielfltigung, auch auszugsweise, Ref. Nr. DIN CWA 14050-8:2001-04nur mit Genehmigung des Beuth Verlages gestattet. RW DIN CWA Preisgr. 04Alleinverkauf der Normen durch Beuth Verlag Gmb
6、H, 10772 BerlinB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Leerseite B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Rue de Stassart, 36 B-1050 BruxellesTel : +32 2 550 08 11 Fax : +32 2 550 08 19EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NO
7、RMALISATION EUROPISCHES KOMITEE FR NORMUNG WORKSHOPCWA 14050-8AGREEMENTNovember 2000ICS 35.200; 35.240.40Extensions for Financial Services (XFS) interface specification -Release 3.0 - Part 8: Depository Device Class Interface 2000 CEN All rights of exploitation in any form and by any means reserved
8、world-wide forCEN National MembersRef. No CWA 14050-8:2000 EThis CEN Workshop Agreement can in no way be held as being an official standardas developed by CEN National Members.B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 2CWA 14050-8:2000Table of ContentsForeword 31. Int
9、roduction 51.1 BACKGROUND TO RELEASE 3.0.51.2 XFS SERVICE-SPECIFIC PROGRAMMING52. Depository Unit 73. References84. Info Commands94.1 WFS_INF_DEP_STATUS 94.2 WFS_INF_DEP_CAPABILITIES115. Execute Commands.135.1 WFS_CMD_DEP_ENTRY 135.2 WFS_CMD_DEP_DISPENSE 145.3 WFS_CMD_DEP_RETRACT .145.4 WFS_CMD_DEP_
10、RESET_COUNT .155.5 WFS_CMD_DEP_RESET 166. Events .176.1 WFS_SRVE_DEP_ENVTAKEN .176.2 WFS_EXEE_DEP_ENVDEPOSITED.176.3 WFS_EXEE_DEP_DEPOSITERROR 176.4 WFS_USRE_DEP_DEPTHRESHOLD.176.5 WFS_USRE_DEP_TONERTHRESHOLD .176.6 WFS_USRE_DEP_ENVTHRESHOLD.186.7 WFS_SRVE_DEP_CONTINSERTED 186.8 WFS_SRVE_DEP_CONTREM
11、OVED 186.9 WFS_SRVE_DEP_ENVINSERTED .186.10 WFS_SRVE_DEP_MEDIADETECTED187. C-Header file .20B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 3CWA 14050-8:2000ForewordThis CWA is revision 3.0 of the XFS interface specification.The move from an XFS 2.0 specification (CWA 13449
12、) 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 XFSManager to include new devices, such as the Card Embossing Unit.Similarly, there has also been pressure, through implementatio
13、n 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, which isnow over 2 years old. Increasing
14、 market acceptance and the need to meet this demand is driving the Workshoptowards this release.The clear direction of the CEN/ISSS XFS Workshop, therefore, is the delivery of a new Release 3.0specification based on a C API. It will be delivered with the promise of the protection of technical invest
15、ment forexisting applications and the design to safeguard future developments.The CEN/ISSS XFS Workshop gathers suppliers as well as banks and other financial service companies. A listof companies participating in this Workshop and in support of this CWA is available from the CEN/ISSSSecretariat.Thi
16、s CWA was formally approved by the XFS Workshop meeting on 2000-10-18. The specification iscontinuously reviewed and commented in the CEN/ISSS Workshop on XFS. It is therefore expected that anupdate of the specification will be published in due time as a CWA, superseding this revision 3.0.The CWA is
17、 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 - Programmers ReferencePart 4: Identification Ca
18、rd 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 8: Depository Device Class Interface
19、- 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: Camera Device Class Interface - Pro
20、grammers 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) - Service Provider Interface (SPI)
21、- Migration from Version2.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 (thisCWA) - Programmers ReferenceB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page
22、4CWA 14050-8:2000Part 18: Identification Card Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version3.0 (this CWA) - Programmers ReferencePart 19: Cash Dispenser Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0(this CWA) - Programmers Referen
23、cePart 20: PIN Keypad Device Class 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 Uni
24、t Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version3.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
25、Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - 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 acomplementar
26、y document, called Release Notes. The Release Notes contain clarifications and explanations onthe CWA 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 re
27、presents the Workshops current views on the issues discussed as of the dateof publication. It is furnished for informational purposes only and is subject to change without notice.CEN/ISSS makes no warranty, express or implied, with respect to this document.Revision History:1.0 May 24, 1993 Initial r
28、elease of API and SPI specification1.11 February 3, 1995 Separation of specification into separate documents forAPI/SPI and service class definitions2.00 November 11, 1996 Update release encompassing the self-service environment3.00 October 18, 2000Addition of Reset command which replaces theCLEAR_T
29、RANSPORT command.Addition of Threshold Event to ENTRY and RETRACTcommands and new status values for container andenvelope supply status.UNICODE supportAddition of the eventsWFS_SRVE_DEP_ENVINSERTED andWFS_SRVE_DEP_MEDIADETECTED.Created a References chapter.For a detailed description see CWA 14050-21
30、Depository Migration from Version 2.00 to Version 3.00Programmers Reference Revision 1.00, October 18, 2000B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 5CWA 14050-8:20001. Introduction1.1 Background to Release 3.0The CEN XFS Workshop is a continuation of the Banking Solu
31、tion Vendors Council workshop and maintains atechnical commitment to the Win 32 API. However, the XFS Workshop has extended the franchise of multivendor software by encouraging the participation of both banks and vendors to take part in the deliberations ofthe creation of an industry standard. This
32、move towards opening the participation beyond the BSVCs originalmembership has been very succesful with a current membership level of more than 20 companies.The fundamental aims of the XFS Workshop are to promote a clear and unambiguous specification for bothservice providers and application develop
33、ers. This has been achieved to date by sub groups workingelectronically and quarterly meetings.The move from an XFS 2.0 specification to a 3.0 specification has been prompted by a series of factors. Initially,there has been a technical imperative to extend the scope of the existing specification of
34、the XFS Manager toinclude new devices, such as the Card Embossing Unit.Similarly, there has also 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
35、is also clear that our customers and the market are asking for an update to a specification, which isnow over 2 years old. Increasing market acceptance and the need to meet this demand is driving the Workshoptowards this release.The clear direction of the XFS Workshop, therefore, is the delivery of
36、a new Release 3.0 specification based ona C API. It will be delivered with the promise of the protection of technical investment for existing applicationsand the design to safeguard future developments.1.2 XFS Service-Specific ProgrammingThe service classes are defined by their service-specific comm
37、ands and the associated data structures, errorcodes, messages, etc. These commands are used to request functions that are specific to one or more classes ofservice providers, but not all of them, and therefore are not included in the common API for basic oradministration functions.When a service-spe
38、cific command is common among two or more classes of service providers, the syntax of thecommand is as similar as possible across all services, since a major objective of the Extensions for FinancialServices is to standardize command codes and structures for the broadest variety of services. For exa
39、mple, usingthe WFSExecute function, the commands to read data from various services are as similar as possible to eachother in their syntax and data structures.In general, the specific command set for a service class is defined as the union of the sets of specific capabilitieslikely to be provided b
40、y the developers of the services of that class; thus any particular device will normallysupport only a subset of the command set defined for the class.There are three cases in which a service provider may receive a service-specific command that it does notsupport:The requested capability is defined
41、for the class of service providers by the XFS specification, the particularvendor implementation of that service does not support it, and the unsupported capability is not consideredto be fundamental to the service. In this case, the service provider returns a successful completion, but doesno opera
42、tion. An example would be a request from an application to turn on a control indicator on apassbook printer; the service provider recognizes the command, but since the passbook printer it ismanaging does not include that indicator, the service provider does no operation and returns a successfulcompl
43、etion to the application.B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 6CWA 14050-8:2000The requested capability is defined for the class of service providers by the XFS specification, the particularvendor implementation of that service does not support it, and the unsupp
44、orted capability is considered to befundamental to the service. In this case, a WFS_ERR_UNSUPP_COMMAND error is returned to thecalling application. An example would be a request from an application to a cash dispenser to dispensecoins; the service provider recognizes the command but, since the cash
45、dispenser it is managing dispensesonly notes, returns this error.The requested capability is not defined for the class of service providers by the XFS specification. In thiscase, a WFS_ERR_INVALID_COMMAND error is returned to the calling application.This design allows implementation of applications
46、that can be used with a range of services that providediffering subsets of the functionalities that are defined for their service class. Applications may use theWFSGetInfo and WFSAsyncGetInfo commands to inquire about the capabilities of the service they are aboutto use, and modify their behavior accordingly, or they may
