AS ISO/IEC 19784.2—2010 pdf – Information technology—Biometric application programming interface Part 2: Biometric archive function provider interface

AS ISO/IEC 19784.2—2010 pdf – Information technology—Biometric application programming interface Part 2: Biometric archive function provider interface.
1 Scope This part of ISO/IEC 1 9784 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 abstraction layer presenting a database interface.) This part of ISO/IEC 1 9784 enables any 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 1 9784 to define security and privacy requirements for storage and management of BIRs. 2 Conformance A conformant 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 definitions apply. NOTE Function names and data element names are not included here, but are defined within the body of this part of ISO/IEC 1 9784. 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 biometric 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 1 9784-1 :2006 specifies the interface at the top of the BioAPI Framework, which a biometric application uses to interact with BSPs, and through that to biometric units either directly or through BFPs (see Figure 1 and Figure 2 of ISO/IEC 1 9784-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.
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). This event handler is passed to the BAFP during BioAFPI_BFPLoad. This is the single event handler that 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 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.
Description This function returns an array of BioAPI Unit schemas (see 7.55 of ISO/IEC 1 9784-1 :2006), which are managed by the given BAFP and are currently in the inserted state. NOTE When the BSP calls the function BioAFPI_QueryUnits of a BFP, the BFP allocates memory for the data to be returned to the BSP. In some implementation architectures, the BSP will simply pass to the framework the data and the addresses exactly as returned by the BFP because the framework will interpret the addresses in the same way as the BFP and will be able to access the data that the BFP has placed at those addresses. In other implementation architectures, the BSP will need to move all the data returned by the BFP to newly allocated memory blocks accessible to the framework, and will call BioAFPI_Free after copying each memory block but before returning from the BioSPI_QueryUnits call. In the former case, when the framework calls BioSPI_Free, the BSP will make a corresponding call to BioAFPI_Free. In the latter case, the calls to BioSPI_Free will be handled internally by the BSP. However, such differences in the behavior of the BSP are not visible to the Framework. The memory block containing the array shall be freed by the BSP via a call to BioAFPI_Free when it is no longer needed by the BSP. The memory block pointed to by the UnitProperty member within each element of the array shall also be freed by the BSP via a call to BioAFPI_Free when it is no longer needed by the BSP. This function shall only be called after BioAFPI_Load has been called for the specified BFP, and shall not be called after BioAFPI_Unload has been called for the BFP. There is no requirement that a unit ID, returned by this function for a given BioAPI unit, be made available with the same unit ID value by the BSP to the framework.