ANSI INCITS ISO IEC 19784-2 CORR 1-2011 Information technology - Biometric application programming interface - Part 2 Biometric archive function provider interface Technical Cor 1.pdf

1、 INCITS/ISO/IEC 19784-2:2007/Cor1: 2011 2013 ISO/IEC 19784-2:2007/Cor1:2011 Information technology Biometric application programming interface Part 2: Biometric archive function provider interface Technical Cor 1 INCITS/ISO/IEC 19784-2:2007/Cor1:2011 2013 PDF disclaimer This PDF file may contain emb

2、edded 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, parties accept therein the responsibility of

3、 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 relative to the file; the PDF-creation parameters

4、 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. Adopted by INCITS (InterNational Committee for Inf

5、ormation Technology Standards) as an American National Standard. Date of ANSI Approval: 6/26/2013 Published by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2013 by Information Technology Industry Council (ITI). All rights reserved. These materials ar

6、e 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 this publication may be reproduced in any fo

7、rm, 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 ii ITIC 2013 All rights reserved INTERNATIONAL STANDARD IS

8、O/IEC 19784-2:2007TECHNICAL CORRIGENDUM 1 Published 2011-05-15 INTERNATIONAL ORGANIZATION FOR STANDARDIZATION ORGANISATION INTERNATIONALE DE NORMALISATIONINTERNATIONAL ELECTROTECHNICAL COMMISSION COMMISSION LECTROTECHNIQUE INTERNATIONALEInformation technology Biometric application programming interf

9、ace Part 2: Biometric archive function provider interface TECHNICAL CORRIGENDUM 1 Technologies de linformation Interface de programmation dapplications biomtriques Partie 2: Interface du fournisseur de fonction darchives biomtriques RECTIFICATIF TECHNIQUE 1 Technical Corrigendum 1 to ISO/IEC 19784-2

10、:2007 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 37, Biometrics. Page 6, 5.2.1 Replace the Description section with the following: Description This function initializes a BFP. Initialization includes registering the BSP event handler for the spec

11、ified BFP and enabling all events. The BSP can choose to provide an event handler function to receive notification of events. Many BSPs can independently and concurrently load the same BFP, and each BSP can establish its own event handler. They will all receive notification of an event. The same or

12、different event handlers can be used if a BSP loads multiple BFPs. ICS 35.040 Ref. No. ISO/IEC 19784-2:2007/Cor.1:2011(E) ISO/IEC 2011 All rights reserved Published in Switzerland ISO/IEC 19784-2:2007/Cor.1:2011(E) 2 ISO/IEC 2011 All rights reservedA BSP may establish as many event handlers as it wi

13、shes, for a given BFP, by calling BioAFPI_BAFPLoad one or more times for that BFP. An event handler is identified by the address of the notification. When an event occurs in a BFP, the BFP may send an event notification to the BSP by calling the BSPs event handler. If a BSP has set up multiple event

14、 handlers, they shall be called one at a time (in any order chosen by the BFP) rather than concurrently. Event notifications may occur at any time, either during a BioSPI call (related or unrelated to the event) or while there is no BioSPI call in execution. BSP writers should ensure that all callba

15、cks are properly and safely handled by the BSP, no matter when the BSP receives them. NOTE This usually requires the use of thread synchronization techniques and discipline in the actions performed by the BSP code placed in event handlers. There is a “use count” on the establishment of event handler

16、s; they have to be de-established (by BioAFPI_BAFPUnload) as many times as they were established. When a BFP is loaded (BioAFPI_BAFPLoad), it shall raise an “insert” event immediately for each present BioAPI Unit. This will indicate to the BSP that it can go ahead and do a BioAFPI_UnitAttach. If the

17、 hardware component for a specific functionality is not present, the “insert” event cannot be raised until the hardware component has been plugged in. The function BioAFPI_UnitAttach can be invoked multiple times for each call to BioAFPI_BAFPLoad. A callback is used to notify the BSP of events of ty

18、pe BioAPI_EVENT. The BAFP shall retain this information for later use. NOTE See Annex A for additional information on loading BFPs. Page 24 Insert the following annex after 5.2.19: Annex A (informative) Selecting and loading BFPs and BioAPI_Units A.1 Obtaining information about BFPs and BioAPI_Units

19、 The component registry contains information about the BioAPI framework, BSPs and BFPs (see 6.3 of ISO/IEC 19784-1:2006). BFP information is stored in a structure called BioAPI_BFP_SCHEMA (see 7.3 of ISO/IEC 19784-1:2006). The BioAPI_BFP_SCHEMA contains data elements BFPPropertyID and BFPProperty. T

20、he BFPPropertyID is a UUID identifying the type of data structure of the BFPProperty data. Each BFP that is compliant with ISO/IEC 19784-1 and this part of ISO/IEC 19784 must provide a standardized BFPPropertyID and a related BFPPropertySchema. ISO/IEC 19784-2:2007/Cor.1:2011(E) ISO/IEC 2011 All rig

21、hts reserved 3The information given in the BFPPropertySchema is stored at BFP installation time (see 6.4 of ISO/IEC 19784-1:2006) in the component registry. An application can obtain this information by calling BioAPI_EnumBFPs and BioAPI_QueryBFPs (see 8.1.10 and 8.1.11 of ISO/IEC 19784-1:2006). A B

22、SP can obtain this information by using the BioSPI_BFP_ENUMERATION_HANDLER (see 9.2.2 of ISO/IEC 19784-1:2006). An application can retrieve information about all BioAPI_Units supported by a particular BSP by calling the function BioAPI_QueryUnits (see 8.1.9 of ISO/IEC 19784-1:2006). This function al

23、so works if no attach session is established yet. A BSP can browse the component registry for all installed BFPs by using the callback mechanism of BioSPI_BFP_ENUMERATION_HANDLER. The BSP analyses the BFPPropertySchemas and decides which BFPs it can support. NOTE The criteria for that decision are o

24、ut of the scope of this part of ISO/IEC 19784. During the call BioSPI_QueryUnits, the BSP may load the supported BFPs. A loaded BFP automatically detects the supported BioAPI_Units and reports the BioAPI_UNIT_SCHEMAs in the return of the BioAFPI_QueryUnits call to the BSP, which reports them to the

25、application. The BSP may create a list of all BFPUuids and the UnitIDs of the supported devices for each BFP. Additional information can be found in the parameter UnitManagerUuid of the BioAPI_UNIT_SCHEMA. A.2 Loading BFPs A.2.1 Loading BFPs when attaching to an unspecified BioAPI_Unit This sub-clau

26、se describes how a BFP is loaded if the application does not choose a specific BioAPI_Unit in a call of BioAPI_BSPAttach. (If the application selects a specific BioAPI_Unit, see A.2.2). In this case the application calls the function BioAPI_BSPAttach with the value BioAPI_DONT_CARE in the particular

27、 element of the parameter UnitList. The BSP then performs the operation described in A.1 using the callback mechanism of BioSPI_BFP_ENUMERATION_HANDLER and followed by a call of BioAFPI_QueryUnits. As a result, the BSP has a list of all units supported and their supporting BFPs. The BSP chooses one

28、of the BioAPI_Units and then loads the appropriate BAFP and completes the operation with a BioAFPI_BAFPLoad function call followed by a BioAFPI_BAFPAttach function call. NOTE The criteria used to choose one of the supported BioAPI_Units are not defined in this part of ISO/IEC 19784. A.2.2 Loading BF

29、Ps when attaching to a specific BioAPI_Unit After issuing a BioAPI_BSPLoad, the framework will load the BSP (if supported) and issue a BioSPI_BSPLoad. On return, the application calls the function BioAPI_QueryUnits to determine the units supported by that BSP, and then calls BioAPI_BSPAttach giving

30、the specific Unit it wishes to use. More precisely, the application retrieves the UnitSchemaArray from the BioAPI_QueryUnits and can browse this for the BioAPI_Unit information. The application selects the UnitId it wants to attach to and calls the function BioAPI_BSPAttach. The BSP may decide to lo

31、ad an appropriate BFP at this time depending on either the list being built as described at the end of A.1 or by analysing the parameter UnitManagerUuid of the BioAPI_UNIT_SCHEMA. On return, the application calls the function BioAPI_QueryUnits to determine the units supported by that BSP, and then c

32、alls BioAPI_BSPAttach giving the specific Unit it wishes to use. More precisely, the ISO/IEC 19784-2:2007/Cor.1:2011(E) 4 ISO/IEC 2011 All rights reservedapplication retrieves the UnitSchemaArray from the BioAPI_QueryUnits and can browse this for the BioAPI_Unit information. The application selects

33、the UnitId it wants to attach to and calls the function BioAPI_BSPAttach.” If the BSP can support at least one BAFP supporting the requested Unit, it proceeds as specified in A.1. If it cannot, it will give an error return. If there are multiple choices of BAFP for the selected Unit, the BSP makes a choice (the criteria for doing this are not standardised).