DIN CWA 14050-13-2001 Extensions for Financial Services (XFS) interface specification - Release 3 0 - Part 13 Alarm device class interface (English Version CWA 14050-13 2000)《金融服务辅.pdf

《DIN CWA 14050-13-2001 Extensions for Financial Services (XFS) interface specification - Release 3 0 - Part 13 Alarm device class interface (English Version CWA 14050-13 2000)《金融服务辅.pdf》由会员分享，可在线阅读，更多相关《DIN CWA 14050-13-2001 Extensions for Financial Services (XFS) interface specification - Release 3 0 - Part 13 Alarm device class interface (English Version CWA 14050-13 2000)《金融服务辅.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

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

2、stelle fr die Gerteklasse “Alarmeinrichtungen“Nationales VorwortDieses CEN Workshop Agreement CWA 14050-13, 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 untersc

3、heiden 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 ledigli

4、ch 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 eventuelle Fehler od

5、er Widersprche zu Normen und Rechtsvorschriften geprft.Fortsetzung 14 Seiten CWA Beuth Verlag GmbH, 2001 .Jede Art der Vervielfltigung, auch auszugsweise, Ref. Nr. DIN CWA 14050-13:2001-04nur mit Genehmigung des Beuth Verlages gestattet. RW DIN CWA Preisgr. 01Alleinverkauf der Normen durch Beuth Ver

6、lag 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 COMIT EUROPE

7、N DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG WORKSHOPCWA 14050-13AGREEMENTNovember 2000ICS 35.200; 35.240.40Extensions for Financial Services (XFS) interface specification -Release 3.0 - Part 13: Alarm Device Class Interface 2000 CEN All rights of exploitation in any form and by any means reser

8、ved world-wide forCEN National MembersRef. No CWA 14050-13: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-13:2000Table of ContentsForeword .

9、 31. Introduction . 51.1 Background to Release 3.0. 51.2 XFS Service-Specific Programming. 52. Alarms 73. References. 84. Info Commands. 94.1 WFS_INF_ALM_STATUS . 94.2 WFS_INF_ALM_CAPABILITIES. 105. Execute Commands 115.1 WFS_CMD_ALM_SET_ALARM . 115.2 WFS_CMD_ALM_RESET_ALARM 115.3 WFS_CMD_ALM_RESET.

10、 116. Events 126.1 WFS_SRVE_ALM_DEVICE_SET . 126.2 WFS_SRVE_ALM_DEVICE_RESET 127. C - Header file 13B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 3CWA 14050-13:2000ForewordThis CWA is revision 3.0 of the XFS interface specification.The move from an XFS 2.0 specification (

11、CWA 13449) 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 the XFS Manager toinclude new devices, such as the Card Embossing Unit.Similarly, there has also been pressure, through imp

12、lementation 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 is now over 2years old.

13、Increasing market acceptance and the need to meet this demand is driving the Workshop towards this release.The clear direction of the CEN/ISSS XFS Workshop, therefore, is the delivery of a new Release 3.0 specification basedon a C API. It will be delivered with the promise of the protection of techn

14、ical investment for existing applications andthe 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 available from the CEN/ISSS Sec

15、retariat.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, superseding this revision 3.

16、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 - Programmers ReferencePart 4: Ident

17、ification 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 8: Depository Device Clas

18、s 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: Camera Device Class Int

19、erface - 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) - Service Provider Inte

20、rface (SPI) - Migration from Version 2.0 (seeCWA 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 ReferenceB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2

21、007-03 Page 4CWA 14050-13:2000Part 18: Identification Card Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers ReferencePart 19: Cash Dispenser Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Progra

22、mmers ReferencePart 20: PIN Keypad Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (this CWA)- Programmers ReferencePart 21: Depository Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (this CWA) -Programmers ReferencePart 22: Text

23、 Terminal Unit Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers ReferencePart 23: Sensors and Indicators Unit Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version3.0 (this CWA) - Programmers ReferencePart 24: Camera

24、Device Class Interface - Migration from Version 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

25、a complementarydocument, called Release Notes. The Release Notes contain clarifications and explanations on the CWA specifications,which are not requiring functional changes. The current version of the Release Notes is available online fromhttp:/www.cenorm.be/isss/Workshop/XFS.The information in thi

26、s document represents the Workshops current 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/ISSS makesno warranty, express or implied, with respect to this document.Revision History:3.00 18 Octob

27、er, 2000 Initial releaseB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 5CWA 14050-13:20001. 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 AP

28、I. 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 deliberations of the creation ofan industry standard. This move towards opening the participation beyond the BSVCs original membership has be

29、envery 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 both serviceproviders and application developers. This has been achieved to date by sub groups working electronically and quart

30、erlymeetings.The move from an XFS 2.0 specification to a 3.0 specification has been prompted by a series of factors. Initially, therehas been a technical imperative to extend the scope of the existing specification of the XFS Manager to include newdevices, such as the Card Embossing Unit.Similarly,

31、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 is also clear that our customers and the market are asking for an update to a spec

32、ification, which is now over 2years old. Increasing market acceptance and the need to meet this demand is driving the Workshop towards this release.The clear direction of the XFS Workshop, therefore, is the delivery of a new Release 3.0 specification based on a C API.It will be delivered with the pr

33、omise of the protection of technical investment for existing applications and the design tosafeguard future developments.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 command

34、s 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 API for basic or administration functions.When a service-specific command is common among two or more classes of service providers, the synt

35、ax of thecommand is as similar as possible across all services, since a major objective of the Extensions for Financial Services isto standardize function codes and structures for the broadest variety of services. For example, using the WFSExecutefunction, the commands to read data from various serv

36、ices are as similar as possible to each other in their syntax anddata structures.In general, the specific command set for a service class is defined as a superset of the specific capabilities likely to beprovided by the developers of the services of that class; thus any particular device will normal

37、ly support only a subset ofthe defined command set.There are three cases in which a service provider may receive a service-specific command that it does not support:B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 6CWA 14050-13:2000The requested capability is defined for the

38、 class of service providers by the XFS specification, the particular vendorimplementation of that service does not support it, and the unsupported capability is not considered to befundamental to the service. In this case, the service provider returns a successful completion, but does no operation.A

39、n example would be a request from an application to turn on a control indicator on a passbook printer; the serviceprovider recognizes the command, but since the passbook printer it is managing does not include that indicator, theservice provider does no operation and returns a successful completion

40、to the application.The requested capability is defined for the class of service providers by the XFS specification, the particular vendorimplementation of that service does not support it, and the unsupported capability is considered to be fundamentalto the service. In this case, a WFS_ERR_UNSUPP_CO

41、MMAND error is returned to the calling application. Anexample would be a request from an application to a cash dispenser to dispense coins; the service providerrecognizes the command but, since the cash dispenser it is managing dispenses only notes, returns this error.The requested capability is not

42、 defined for the class of service providers by the XFS specification. In this case, aWFS_ERR_INVALID_COMMAND error is returned to the calling application.This design allows implementation of applications that can be used with a range of services that provide differingsubsets of the functionalities t

43、hat 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 modify theirbehavior accordingly, or they may use functions and then deal with WFS_ERR_UNSUPP_COMMAND error returns tom

44、ake decisions as to how to use the service.B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 7CWA 14050-13:20002. AlarmsThis specification describes the functionality of the services provided by Alarms (ALM) under XFS, by defining theservice-specific commands that can be issu

45、ed, using the WFSGetInfo, WFSAsyncGetInfo, WFSExecute andWFSAsyncExecute functions. This section describes the functionality of an Alarm (ALM) service that applies to bothattended and unattended (self-service) devices.The Alarm device class is provided as a separate service due to the need to set or reset an Alarm when one or morelogical services associated with an attended CDM or unattended (self-service) device are locked. Because logicalservices can be locke