AS ISO IEC 19784.2:2010 pdf download – Information technology—Biometric application programming interface Part 2: Biometric archive function provider interface
1Scope
This part of ISO/IEC 19784 specifies the interface to an archive biometric function provider.
NOTE The interface 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 abstractionlayer presenting a database interface.)
This part of lSO/IEC 19784 enables any third party to create biometric archive function providers, which maybe plugged into any biometric service provider supporting this interface.
lt is not in the scope of this part of lSO/EC 19784 to define security and privacy requirements for storage andmanagement of BiRs.
2Conformance
A conformant BAFP is required to support all functions and parameters specified in this part of ISOIEC 19784.No subsets of conformant BAFP functions are defined.
NOTE BSPs may require any of those functions and parameters.
3Terms and definitions
For the purposes of this document, the following terms and definitions apply.
NOTE Function names and data element names are not included here, but are defined within the body of this part ofISO/IEC 19784.
3.1
biometric archive function providerBAFP
BioAPl component, attached to a BSP via its interface , for storage, management and interchange of BIRs
3.2
biometric archive function provider interfaceBAFPI
BAFP-to-BSP interface which supports the functions to manage the BAFP itself, its databases or BIRs
4lnterface architecture
ISOIEC 19784-1:2006 specifies the interface at the top of the BioAPl Framework,which a biometricapplication uses to interact with BSPs, and through that to biometric units either directly or through BFPs (seeFigure 1 and Figure 2 of ISO/IEC 19784-1:2006).
The BAFPI contains the following types of 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 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 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 respective 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_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;
⎯ BioAFPI_DbGetNextBIR;
⎯ BioAFPI_DbQueryBIR;
⎯ BioAFPI_DbDeleteBIR.
5 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 BioAPI_ 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).
BAFPUuid (input) — The UUID 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 the format of the BioAFPI_BAFPPropertySchema. When a BAFP claims to be conformant to this part of ISO/IEC 1 9784, it has to use a PropertySchema as defined within this part of ISO/IEC 19784.AS ISO IEC 19784.2 pdf download.
