1、April 2001Extensions for Financial Services (XFS)interface specification Release 3.0 Part 11: Vendor Dependent Mode Class InterfaceCWA 14050-11Englische Fassung CWA 14050-11:2000ICS 35.200; 35.240.40Erweiterungen fr die Schnittstellenspezifikation fr Finanzdienst-leistungen (XFS) Version 3.0 Teil 11
2、: Schnittstelle fr die Klasse “herstellerabhngiger Modus“Nationales VorwortDieses CEN Workshop Agreement CWA 14050-11, 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.
3、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 aller interessierten Kreise darstellen, haben CEN Workshop Agreeme
4、nts 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-Zentralsekretariat, noch die CEN-Mitglieder haben den Inhaltauf eventuell
5、e Fehler oder Widersprche zu Normen und Rechtsvorschriften geprft.Fortsetzung 21 Seiten CWA Beuth Verlag GmbH, 2001 .Jede Art der Vervielfltigung, auch auszugsweise, Ref. Nr. DIN CWA 14050-11:2001-04nur mit Genehmigung des Beuth Verlages gestattet. RW DIN CWA Preisgr. 04Alleinverkauf der Normen durc
6、h Beuth Verlag GmbH, 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 C
7、OMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG WORKSHOPCWA 14050-11AGREEMENTNovember 2000ICS 35.200; 35.240.40Extensions for Financial Services (XFS) interface specification -Release 3.0 - Part 11: Vendor Dependent Mode Class Interface 2000 CEN All rights of exploitation in any form an
8、d by any means reserved world-wide forCEN National MembersRef. No CWA 14050-11: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-11:2000Table o
9、f ContentsForeword. 31. Introduction 51.1 Background to Release 3.051.2 XFS Service-Specific Programming52. Vendor Dependent Mode . 73. References 144. Info Commands 154.1 WFS_INF_VDM_STATUS154.2 WFS_INF_VDM_CAPABILITIES .165. Execute Commands. 175.1 WFS_CMD_VDM_ENTER_MODE_REQ.175.2 WFS_CMD_VDM_ENTE
10、R_MODE_ACK.175.3 WFS_CMD_VDM_EXIT_MODE_REQ.175.4 WFS_CMD_VDM_EXIT_MODE_ACK.186. Events . 196.1 WFS_SRVE_VDM_ENTER_MODE_REQ .196.2 WFS_SRVE_VDM_EXIT_MODE_REQ .196.3 WFS_SYSE_VDM_MODEENTERED 196.4 WFS_SYSE_VDM_MODEEXITED 197. C-Header file . 20B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Sta
11、nd 2007-03 Page 3CWA 14050-11: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 aseries of factors.Initially, there has been a technical imperative to extend the scope of the existing
12、 specification of theXFS Manager to include new devices, such as the Card Embossing Unit.Similarly, there has also been pressure, through implementation experience and the advance of theMicrosoft technology, to extend the functionality and capabilities of the existing devices covered by thespecifica
13、tion.Finally, it is also clear that our customers and the market are asking for an update to a specification,which is now over 2 years old. Increasing market acceptance and the need to meet this demand isdriving the Workshop towards this release.The clear direction of the CEN/ISSS XFS Workshop, ther
14、efore, 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 technicalinvestment for existing applications and the design to safeguard future developments.The CEN/ISSS XFS Workshop gathers suppliers as well as banks and other f
15、inancial servicecompanies. A list of companies participating in this Workshop and in support of this CWA is availablefrom the CEN/ISSS Secretariat.This CWA was formally approved by the XFS Workshop meeting on 2000-10-18. The specification iscontinuously reviewed and commented in the CEN/ISSS Worksho
16、p on XFS. It is therefore expectedthat an update of the specification will be published in due time as a CWA, superseding this revision3.0.The CWA is published as a multi-part document, consisting of:Part 1: Application Programming Interface (API) - Service Provider Interface (SPI); ProgrammersRefer
17、encePart 2: Service Classes Definition; Programmers ReferencePart 3: Printer Device Class Interface - Programmers ReferencePart 4: Identification Card Device Class Interface - Programmers ReferencePart 5: Cash Dispenser Device Class Interface - Programmers ReferencePart 6: PIN Keypad Device Class In
18、terface - Programmers ReferencePart 7: Check Reader/Scanner Device Class Interface - Programmers ReferencePart 8: Depository Device Class Interface - Programmers ReferencePart 9: Text Terminal Unit Device Class Interface - Programmers ReferencePart 10: Sensors and Indicators Unit Device Class Interf
19、ace - Programmers ReferencePart 11: Vendor Dependent Mode Device Class Interface - Programmers ReferencePart 12: Camera Device Class Interface - Programmers ReferencePart 13: Alarm Device Class Interface - Programmers ReferencePart 14: Card Embossing Unit Class Interface - Programmers ReferencePart
20、15: Cash In Module Device Class Interface- Programmers ReferencePart 16: Application Programming Interface (API) - Service Provider Interface (SPI) - Migration fromVersion 2.0 (see CWA 13449) to Version 3.0 (this CWA) - Programmers ReferenceB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stan
21、d 2007-03 Page 4CWA 14050-11:2000Part 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) toVersion 3.0 (this CWA) - Programmer
22、s ReferencePart 19: Cash Dispenser Device Class Interface - Migration from Version 2.0 (see CWA 13449) toVersion 3.0 (this CWA) - Programmers ReferencePart 20: PIN Keypad Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version3.0 (this CWA) - Programmers ReferencePart 21: Depo
23、sitory Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version3.0 (this CWA) - Programmers ReferencePart 22: Text Terminal Unit Device Class Interface - Migration from Version 2.0 (see CWA 13449) toVersion 3.0 (this CWA) - Programmers ReferencePart 23: Sensors and Indicators U
24、nit Device Class Interface - Migration from Version 2.0 (see CWA13449) to Version 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 Device Class Interf
25、ace - 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 andexplanations on the CWA specifications, which are not requiring functiona
26、l changes. The currentversion of the Release Notes is available online from http:/www.cenorm.be/isss/Workshop/XFS.The information in this document represents the Workshops current views on the issues discussed as ofthe date of publication. It is furnished for informational purposes only and is subje
27、ct to change withoutnotice. CEN/ISSS makes no warranty, express or implied, with respect to this document.Revision History:2.00 November 11, 1996 Initial release3.00 October 18, 2000 Updated for XFS version 3.00B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 5CWA 14050-11:2
28、0001. Introduction1.1 Background to Release 3.0The CEN XFS Workshop is a continuation of the Banking Solution Vendors Council workshop andmaintains a technical commitment to the Win 32 API. However, the XFS Workshop has extended thefranchise of multi vendor software by encouraging the participation
29、of both banks and vendors to takepart in the deliberations of the creation of an industry standard. This move towards opening theparticipation beyond the BSVCs original membership has been very succesful with a currentmembership level of more than 20 companies.The fundamental aims of the XFS Worksho
30、p are to promote a clear and unambiguous specification forboth service providers and application developers. This has been achieved to date by sub groupsworking electronically and quarterly meetings.The move from an XFS 2.0 specification to a 3.0 specification has been prompted by a series of factor
31、s.Initially, there has been a technical imperative to extend the scope of the existing specification of theXFS Manager to include new devices, such as the Card Embossing Unit.Similarly, there has also been pressure, through implementation experience and the advance of theMicrosoft technology, to ext
32、end the functionality and capabilities of the existing devices covered by thespecification.Finally, it is also clear that our customers and the market are asking for an update to a specification,which is now over 2 years old. Increasing market acceptance and the need to meet this demand isdriving th
33、e Workshop towards this release.The clear direction of the 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 forexisting applications and the design to safeguard future developm
34、ents.1.2 XFS Service-Specific ProgrammingThe 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 ormore classes of service providers, but not all of them, a
35、nd therefore are not included in the commonAPI for basic or administration functions.When a service-specific command is common among two or more classes of service providers, thesyntax of the command is as similar as possible across all services, since a major objective of theExtensions for Financia
36、l Services is to standardize command codes and structures for the broadestvariety of services. For example, using the WFSExecute function, the commands to read data fromvarious services are as similar as possible to each other in their syntax and data structures.In general, the specific command set
37、for a service class is defined as the union of the specificcapabilities likely to be provided by the developers of the services of that class; thus any particulardevice will normally support only a subset of the defined command set.B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03
38、 Page 6CWA 14050-11:2000There are three cases in which a service provider may receive a service-specific command that it doesnot support:The requested capability is defined for the class of service providers by the XFS specification, theparticular vendor implementation of that service does not suppo
39、rt it, and the unsupported capabilityis not considered to be fundamental to the service. In this case, the service provider returns asuccessful completion, but does no operation. An example would be a request from an applicationto turn on a control indicator on a passbook printer; the service provid
40、er recognizes the command,but since the passbook printer it is managing does not include that indicator, the service providerdoes no operation and returns a successful completion to the application.The requested capability is defined for the class of service providers by the XFS specification, thepa
41、rticular vendor implementation of that service does not support it, and the unsupported capabilityis considered to be fundamental to the service. In this case, a WFS_UNSUPP_COMMAND error isreturned to the calling application. An example would be a request from an application to a cashdispenser to di
42、spense coins; the service provider recognizes the command but, since the cashdispenser 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
43、 to the calling application.This design allows implementation of applications 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
44、capabilities of the service theyare about to use, and modify their behavior accordingly, or they may use functions and then deal withWFS_ERR_UNSUPP_COMMAND error returns to make decisions as to how to use the service.B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 7CWA 1405
45、0-11:20002. Vendor Dependent ModeThis specification describes the functionality of the services provided by the Vendor Dependent Mode(VDM) services under XFS, by defining the service-specific commands that can be issued, using theWFSGetInfo, WFSAsyncGetInfo, WFSExecute and WFSAsyncExecute functions.In all device classes there needs to be some method of going into a vendor specific mode to allow forcapabilities which go beyond the scope of the current XFS specif
