1、INCITS/ISO/IEC 19784-2-20072008(ISO/IEC 19784-2-2007, IDT) Information technology Biometricapplication programming interface Part 2: Biometric archive function provider interfaceINCITS/ISO/IEC 19784-2-20072008 (ISO/IEC 19784-2-2007, IDT)INCITS/ISO/IEC 19784-2-20072008 ii ITIC 2008 All rights reserve
2、d PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file
3、, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info rel
4、ative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. Adop
5、ted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard. Date of ANSI Approval: 7/1/2008 Published by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2008 by Information Technology Industry Council (
6、ITI). All rights reserved. These materials are subject to copyright claims of International Standardization Organization (ISO), International Electrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resale. No part of
7、 this publication may be reproduced in any form, including an electronic retrieval system, without the prior written permission of ITI. All requests pertaining to this standard should be submitted to ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America iiiContents P
8、age Foreword iv Introduction v 1 Scope. 1 2 Conformance. 1 3 Terms and definitions 1 4 Interface architecture 1 5 BAFPI Definition 3 5.1 BAFPI data structures 3 5.1.1 BioAFPI_EventHandler. 3 5.1.2 BioAFPI_BAFPPropertyID 3 5.1.3 BioAFPI_BAFPPropertySchema 4 5.1.4 BioAFPI_UnitPropertyID. 4 5.1.5 BioAF
9、PI_UnitPropertySchema. 5 5.2 BAFP Functions 6 5.2.1 BioAFPI_BAFPLoad 6 5.2.2 BioAFPI_BAFPUnload 7 5.2.3 BioAFPI_UnitAttach 8 5.2.4 BioAFPI_UnitDetach . 9 5.2.5 BioAFPI_QueryUnits. 10 5.2.6 BioAFPI_Free 11 5.2.7 BioAFPI_ControlUnit 12 5.2.8 BioAFPI_Cancel 13 5.2.9 BioAFPI_SetPowerMode 14 5.2.10 BioAF
10、PI_DbOpen 15 5.2.11 BioAFPI_DbClose . 16 5.2.12 BioAFPI_DbCreate 17 5.2.13 BioAFPI_DbDelete 18 5.2.14 BioAFPI_DbSetMarker 19 5.2.15 BioAFPI_DbFreeMarker 20 5.2.16 BioAFPI_DbStoreBIR 21 5.2.17 BioAFPI_DbGetBIR . 22 5.2.18 BioAFPI_DbGetNextBIR . 23 5.2.19 BioAFPI_DbDeleteBIR 24 INCITS/ISO/IEC 19784-2-
11、20072008 ITIC 2008 - All rights reservediv Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the developmen
12、t of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental,
13、in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joi
14、nt technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attent
15、ion is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 19784-2 was prepared by Technical Committee ISO/IEC JTC 1, Information technology, Subcommi
16、ttee SC 37, Biometrics. ISO/IEC 19784 consists of the following parts, under the general title Information technology Biometric application programming interface: Part 1: BioAPI specification Part 2: Biometric archive function provider interface INCITS/ISO/IEC 19784-2-20072008 ITIC 2008 - All rights
17、 reservedvIntroduction This part of ISO/IEC 19784 specifies the interface to an archive BFP. An archive BFP is responsible for the storage and management of BIRs. The archive BFP interface covers functions to attach, detach and operate related functional units by the biometric service provider, to s
18、tore BIRs, to retrieve information about stored BIRs and to retrieve formerly stored BIRs for further processing by a BSP. ISO/IEC 19784-1 provides a high-level generic biometric authentication model. This part of ISO/IEC 19784 specifies a BSP archive interface. An archive is responsible for the man
19、agement of biometric data storage. Because of the application-specific requirements of biometric data storage, an archive interface is standardized. The BioAPI Unit where the BIRs are stored is completely under control of the archive BFP. The general model for the handling of BIRs is as if they were
20、 data records in a database. INCITS/ISO/IEC 19784-2-20072008 ITIC 2008 - All rights reservedAMERICAN NATIONAL STANDARD INCITS/ISO/IEC 19784-2-20072008 ITIC 2008 - All rights reserved 11 Scope This part of ISO/IEC 19784 specifies the interface to an archive biometric function provider. NOTE The inter
21、face assumes that the archive will be handled as a database, regardless of its physical realization. (Smartcards, tokens, memory sticks, files on hard drives and any other kind of memory can be handled via an abstraction layer presenting a database interface.) This part of ISO/IEC 19784 enables any
22、third party to create biometric archive function providers, which may be plugged into any biometric service provider supporting this interface. It is not in the scope of this part of ISO/IEC 19784 to define security and privacy requirements for storage and management of BIRs. 2 Conformance A conform
23、ant BAFP is required to support all functions and parameters specified in this part of ISO/IEC 19784. No subsets of conformant BAFP functions are defined. NOTE BSPs may require any of those functions and parameters. 3 Terms and definitions For the purposes of this document, the following terms and d
24、efinitions apply. NOTE Function names and data element names are not included here, but are defined within the body of this part of ISO/IEC 19784. 3.1 biometric archive function provider BAFP BioAPI component, attached to a BSP via its interface, for storage, management and interchange of BIRs 3.2 b
25、iometric archive function provider interface BAFPI BAFP-to-BSP interface which supports the functions to manage the BAFP itself, its databases or BIRs 4 Interface architecture ISO/IEC 19784-1:2006 specifies the interface at the top of the BioAPI Framework, which a biometric application uses to inter
26、act with BSPs, and through that to biometric units either directly or through BFPs (see Figure 1 and Figure 2 of ISO/IEC 19784-1:2006). Information technology Biometric application programming interface Part 2: Biometric archive function provider interface 2 The BAFPI contains the following types of
27、 functions. General BFP management functions, which are called by the BSP to manage the BFP and its associated BioAPI Units. These functions are not directly related to SPI functions: BioAFPI_BAFPLoad; BioAFPI_BAFPUnload; BioAFPI_UnitAttach; BioAFPI_UnitDetach; BioAFPI_QueryUnits; BioAFPI_Free (the
28、relation of this function to the respective SPI call depends on the behaviour of the BSP when the BSP copies the data the BFP has allocated memory for then it can immediately send BioAFPI_Free to the BFP, otherwise the BSP will call this function when itself is requested to free the memory for these
29、 data). Unit management functions: BioAFPI_ControlUnit (this function is directly related to the SPI function); BioAFPI_Cancel (this function can be called in relation to the respective calls of the SPI or the application, but can be called for other reasons from the BSP also when there is no respec
30、tive request from the BioAPI framework or application; BioAFPI_SetPowerMode (this function is directly related to the SPI function). Database management functions. These functions are directly related to the respective functions of the SPI: BioAFPI_DbOpen; BioAFPI_DbClose; BioAFPI_DbCreate; BioAFPI_
31、DbDelete. Record management functions. These functions are directly related to the respective functions of the SPI: BioAFPI_DbSetMarker; BioAFPI_DbFreeMarker. Data management functions. These functions are directly related to the respective functions of the SPI: BioAFPI_DbStoreBIR; BioAFPI_DbGetBIR;
32、 BioAFPI_DbGetNextBIR; BioAFPI_DbQueryBIR; BioAFPI_DbDeleteBIR. INCITS/ISO/IEC 19784-2-20072008 ITIC 2008 - All rights reserved35 BAFPI Definition 5.1 BAFPI data structures 5.1.1 BioAFPI_EventHandler This defines the event handler interface to receive asynchronous notification of events of type BioA
33、PI_ EVENT from a BioAPI Unit. Example events include insertion or removal of a BioAPI Unit (e.g. insertion or withdrawal of a Smartcard storing biometric templates for off card or on card matching). This event handler is passed to the BAFP during BioAFPI_BFPLoad. This is the single event handler tha
34、t all BioAPI Units managed by this BAFP should use to notify the BSP of event types that occur in a loaded BAFP. typedef BioAPI_RETURN (BioAPI *BioAFPI_EventHandler) (const BioAPI_UUID *BAFPUuid, BioAPI_UNIT_ID UnitID, BioAPI_UNIT_SCHEMA *UnitSchema, BioAPI_ EVENT EventType); BAFPUuid (input) The UU
35、ID of the BAFP raising the event. UnitID (input) The unit ID of the BioAPI Unit (biometric archive) associated with the event. UnitSchema (input) The schema of the BioAPI Unit raising the event. EventType (input) The BioAPI_ EVENT that has occurred. 5.1.2 BioAFPI_BAFPPropertyID Defines the UUID of t
36、he format of the BioAFPI_BAFPPropertySchema. When a BAFP claims to be conformant to this part of ISO/IEC 19784, it has to use a PropertySchema as defined within this part of ISO/IEC 19784. #define (BioAFPI_BAFPPropertyID, 0x561403e5, 0x7d2d, 0x489a, 0x89, 0x41, 0xe7, 0xa9, 0x35, 0x99, 0xcf, 0x9c); I
37、NCITS/ISO/IEC 19784-2-20072008 ITIC 2008 - All rights reserved4 5.1.3 BioAFPI_BAFPPropertySchema The BioAFPI_BAFPPropertySchema contains information about the function providers capabilities, which are presented to the BioAPI component registry and in the related function calls. The function provide
38、r capabilities can differ from the capabilities of a biometric archive unit. The capabilities usuable by a BSP or BioAPI application are the intersection of the BAFP and biometric archive unit capabilities. typedef struct _bioafpi_bafp_property_schema uint32_t MaxRecordLength; uint32_t MaxRecordNumb
39、er; uint32_t MaxDatabases; uint32_t MaxResponseTime; BioAPI_POWER_MODE SupportedPowerModes; BioAFPI_BAFP_PROPERTY_SCHEMA, *BioAFPI_BAFP_PROPERTY_SCHEMA_PTR; MaxRecordLength The value defines the maximum length in bytes of a record. A record presents a BIR. A Biometric Unit shall use a value smaller
40、or equal to this value in its UnitSchema. A 0 means that no information about the maximum record length is given. MaxRecordNumber The value defines the maximum number of records. A Biometric Unit shall use a value smaller or equal to this value in its UnitSchema. A 0 means that no information about
41、the maximum number of records is given. MaxDatabases The value defines the maximum number of databases, which can be managed by the AFP at a time. A 0 means that no information about the maximum number of databases is given. MaxResponseTime The value defines the maximum time in milliseconds a caller
42、 of any BAFP function has to wait until the function returns. A Biometric Unit shall use a value smaller or equal to this value in its UnitSchema. A 0 means that no information about the maximum time until the BioAPI Unit returns is given. SupportedPowerModes The bit mask defining, which power modes
43、 can be handled by the BFP. Handling of a power mode means to pass the related function call to the BioAPI Unit, when this supports the mode and to return the error code related to the result of the reaction of the BioAPI Unit. 5.1.4 BioAFPI_UnitPropertyID Defines the UUID of the format of the BioAF
44、PI_UnitPropertySchema. When a BAFP claims to be conformant to this part of ISO/IEC 19784, it has to use a PropertySchema as defined within this part of ISO/IEC 19784. #define (BioAFPI_UnitPropertyID, 0x94cae58f, 0x6b26, 0x41fc, 0x9d, 0xdb, 0xd9, 0x8e, 0x9a, 0xd5, 0x6f, 0xa0); INCITS/ISO/IEC 19784-2-
45、20072008 ITIC 2008 - All rights reserved55.1.5 BioAFPI_UnitPropertySchema The BioAFPI_UnitPropertySchema contains the information to be presented in the related function calls. Presenting a particular biometric archive unit this schema contains information to identify the unit itself (DbUuid and DbN
46、ame) and capability information as well. typedef struct _bioafpi_unit_property_schema BioAPI_UUID DbUuid; BioAPI_STRING DbName; uint32_t MaxRecordLength; uint32_t MaxRecordNumber; uint32_t MaxDatabases; uint32_t MaxResponseTime; BioAPI_POWER_MODE SupportedPowerModes; BioAFPI_UNIT_PROPERTY_SCHEMA, *B
47、ioAFPI_UNIT_PROPERTY_SCHEMA_PTR; DbUuid The UUID of the archive unit related database. DbName The descriptional name of the database. MaxRecordLength The value defines the maximum length in bytes of a record. A record presents a BIR. A 0 means that no information about the maximum record length is g
48、iven. MaxRecordNumber The value defines the maximum number of records. A 0 means that no information about the maximum number of records is given. MaxDatabases The value defines the maximum number of databases, which can be managed by the AFP at a time. A 0 means that no information about the maximu
49、m number of databases is given. MaxResponseTime The value defines the maximum time in milliseconds a caller of any function to the BioAPI Unit has to wait until the function returns. A 0 means that no no information about the maximum time until the BioAPI Unit returns is given. SupportedPowerModes The bit mask defining, which power modes can be handled by the BFP. Handling of a p
