DIN CWA 14050-3-2001 Extensions for Financial Services (XFS) interface specification - Release 3 0 - Part 3 Printers Device Class Interface (English version CWA 14050-3 2000)《金融服务辅.pdf

1、April 2001Extensions for Financial Services (XFS)interface specification Release 3.0 Part 3: Printers Device Class InterfaceCWA 14050-3Englische Fassung CWA 14050-3:2000ICS 35.200; 35.240.40Erweiterungen fr die Schnittstellenspezifikation fr Finanzdienst-leistungen (XFS) Version 3.0 Teil 3: Schnitts

2、telle fr die Gerteklasse “Drucker“Nationales VorwortDieses CEN Workshop Agreement CWA 14050-3, 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 sich v

3、onEuropischen 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 dieZustimm

4、ung 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 Widersprch

5、e zu Normen und Rechtsvorschriften geprft.Fortsetzung 73 Seiten CWA Beuth Verlag GmbH, 2001 .Jede Art der Vervielfltigung, auch auszugsweise, Ref. Nr. DIN CWA 14050-3:2001-04nur mit Genehmigung des Beuth Verlages gestattet. RW DIN CWA Preisgr. 10Alleinverkauf der Normen durch Beuth Verlag GmbH, 1077

6、2 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 14050-3AGREEMENTNovember 2000ICS 35.200; 35.240.40Extensions for Financial Services (XFS)

7、 interface specification -Release 3.0 - Print 3: Printers Device Class Interface 2000 CEN All rights of exploitation in any form and by any means reserved world-wide forCEN National MembersRef. No CWA 14050-3:2000 EThis CEN Workshop Agreement can in no way be held as being an official standardas dev

8、eloped by CEN National Members.Page 2CWA 14050-3:2000Table of ContentsForeword41. Introduction .61.1 Background to Release 3.0. 61.2 XFS Service-Specific Programming. 62. Banking Printers83. Banking Printer Types 94. Forms Model105. References.116. Command Overview127. Info Commands .137.1 WFS_INF_P

9、TR_STATUS 137.2 WFS_INF_PTR_CAPABILITIES . 167.3 WFS_INF_PTR_FORM_LIST . 197.4 WFS_INF_PTR_MEDIA_LIST. 207.5 WFS_INF_PTR_QUERY_FORM 207.6 WFS_INF_PTR_QUERY_MEDIA 227.7 WFS_INF_PTR_QUERY_FIELD. 248. Execute Commands268.1 WFS_CMD_PTR_CONTROL_MEDIA 268.2 WFS_CMD_PTR_PRINT_FORM 288.3 WFS_CMD_PTR_READ_FO

10、RM. 318.4 WFS_CMD_PTR_RAW_DATA. 338.5 WFS_CMD_PTR_MEDIA_EXTENTS . 348.6 WFS_CMD_PTR_RESET_COUNT. 358.7 WFS_CMD_PTR_READ_IMAGE 368.8 WFS_CMD_PTR_RESET . 388.9 WFS_CMD_PTR_RETRACT_MEDIA. 398.10 WFS_CMD_PTR_DISPENSE_PAPER . 409. Events 429.1 WFS_EXEE_PTR_NOMEDIA . 429.2 WFS_EXEE_PTR_MEDIAINSERTED 429.3

11、 WFS_EXEE_PTR_FIELDERROR. 429.4 WFS_EXEE_PTR_FIELDWARNING 439.5 WFS_USRE_PTR_RETRACTBINTHRESHOLD 43Page 3CWA 14050-3:20009.6 WFS_SRVE_PTR_MEDIATAKEN 439.7 WFS_USRE_PTR_PAPERTHRESHOLD. 439.8 WFS_USRE_PTR_TONERTHRESHOLD. 449.9 WFS_SRVE_PTR_MEDIAINSERTED 449.10 WFS_USRE_PTR_LAMPTHRESHOLD . 449.11 WFS_U

12、SRE_PTR_INKTHRESHOLD . 459.12 WFS_SRVE_PTR_MEDIADETECTED. 4510. Form, Sub-Form, Field, Frame, Table and Media Definitions.4610.1 Definition Syntax 4610.2 Form and Media Measurements. 4610.3 Form Definition . 4810.4 SubForm Definition . 5010.5 Field Definition 5110.6 Frame Definition 5610.7 Media Def

13、inition 6210.8 XFS form/media definition files in multi-vendor environments 6411. C-Header File 65Page 4CWA 14050-3:2000ForewordThis CWA is revision 3.0 of the XFS interface specification.The move from an XFS 2.0 specification (CWA 13449) to a 3.0 specification has been prompted by a series offactor

14、s.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 been pressure, through implementation experience and the advance of the Microsofttechnology, to ext

15、end 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

16、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 of the protection of technical investment for existingapplications and the design to safeguard futur

17、e 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 available from the CEN/ISSS Secretariat.This CWA was formally approved by the XFS Workshop meeting on 200

18、0-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, superseding this revision 3.0.The CWA is published as a multi-part document, consisting of:Part 1: App

19、lication Programming Interface (API) - Service Provider Interface (SPI); Programmers ReferencePart 2: Service Classes Definition; Programmers ReferencePart 3: Printer Device Class Interface - Programmers ReferencePart 4: Identification Card Device Class Interface - Programmers ReferencePart 5: Cash

20、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 - Programmers ReferencePart 9: Text Terminal Unit Device Class

21、 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 - Programmers ReferencePart 13: Alarm Device Class Interface - Prog

22、rammers 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) - Migration from Version 2.0(see CWA 13449) to Version 3.0 (th

23、is 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 Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0(this CWA) - Programmers

24、ReferencePage 5CWA 14050-3: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 Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers Re

25、ferencePart 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 - Migration from Version 2.0 (see CWA 13449) to Version 3.0(this CWA) - Programmers ReferencePart 23: Sens

26、ors 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 Version 2.0 (see CWA 13449) to Version 3.0 (this CWA)- Programmers ReferencePart 25: Identification Card

27、 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 Notes. The Release Notes contain clarifications and explanations on theCWA specifications, which are not

28、 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 views on the issues discussed as of the date ofpublication. It is furnished for informational purpos

29、es only and is subject to change without notice. CEN/ISSSmakes no warranty, express or implied, with respect to this document.Revision History:1.0 May 24, 1993 Initial release of API and SPI specification1.11 February 3, 1995 Separation of specification into separate documents forAPI/SPI and service

30、 class definitions2.00 November 11, 1996 Update release encompassing the self-service environment3.00 October 18, 2000 Update release encompassing:- multi-page support- 24 bit color support- paper source support- passbook available print line detection- additions for build in scanners- additions for

31、 devices with more than one retract bin- support of passbook dispensing and parking- addition of a reset functionFor a detailed description see CWA 14050-17PTR Migration from Version 2.00 to Version 3.00, Revision1.00, October 18, 2000.Page 6CWA 14050-3:20001. Introduction1.1 Background to Release 3

32、.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 both banks and vendors to take part in the

33、 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 are to promote a clear and unambiguous spe

34、cification 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. Initially,there has been a technical impe

35、rative 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 extend the functionality and capabilities of th

36、e 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 the Workshop towardsthis release.The clear d

37、irection 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 developments.1.2 XFS Service-Specific ProgrammingTh

38、e service classes are defined by their service-specific commands and the associated data structures, error codes,messages, etc. These commands are used to request functions that are specific to one or more classes of serviceproviders, but not all of them, and therefore are not included in the common

39、 API for basic or administrationfunctions.When a service-specific 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

40、and structures for the broadest variety of services. For example, using theWFSExecute function, the commands to read data from various services are as similar as possible to each other intheir syntax and data structures.In general, the specific command set for a service class is defined as the union

41、 of the sets of specific capabilitieslikely to be provided by the developers of the services of that class; thus any particular device will normally supportonly 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

42、that it does not support:The 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 unsupported capability is not considered tobe fundamental to the service. In this case, the servi

43、ce provider returns a successful completion, but does nooperation. An example would be a request from an application to turn on a control indicator on a passbookprinter; the service provider recognizes the command, but since the passbook printer it is managing does notinclude that indicator, the ser

44、vice provider does no operation and returns a successful completion to theapplication.The 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 unsupported capability is considered

45、 to befundamental to the service. In this case, a WFS_ERR_UNSUPP_COMMAND error is returned to the callingPage 7CWA 14050-3:2000application. An example would be a request from an application to a cash dispenser to dispense coins; theservice provider recognizes the command but, since the cash dispense

46、r it is managing dispenses only notes,returns this error.The requested capability is not defined for the class of service providers by the XFS specification. In this case,a WFS_ERR_INVALID_COMMAND error is returned to the calling application.This design allows implementation of applications that can

47、 be used with a range of services that provide differingsubsets of the functionalities that are defined for their service class. Applications may use the WFSGetInfo andWFSAsyncGetInfo commands to inquire about the capabilities of the service they are about to use, and modifytheir behavior accordingl

48、y, or they may use functions and then deal with WFS_ERR_UNSUPP_COMMAND errorreturns to make decisions as to how to use the service.Page 8CWA 14050-3:20002. Banking PrintersThis specification describes the functionality of the services provided by banking printers under XFS, focusing onthree areas:ap

49、plication programming for printingprint document definitionintegration with the Windows architectureThese descriptions include definitions of the service-specific commands that can be issued, using theWFSAsyncExecute, WFSExecute, WFSGetInfo and WFSAsyncGetInfo functions.The requirements for printing in banking applications are significantly different from those of the conventional PCenvironment, and the XFS support delivers the foundation for financial application printing, including:Controlled access to shared printersThe banking p