ANSI INCITS ISO IEC 29141-2009 Information technology - Biometrics - Tenprint capture using biometric application programming interface (BioAPI).pdf

《ANSI INCITS ISO IEC 29141-2009 Information technology - Biometrics - Tenprint capture using biometric application programming interface (BioAPI).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS ISO IEC 29141-2009 Information technology - Biometrics - Tenprint capture using biometric application programming interface (BioAPI).pdf（32页珍藏版）》请在麦多课文档分享上搜索。

1、 INCITS/ISO/IEC 29141:2009 2010 ISO/IEC 29141:2009 Information technology Biometrics Tenprint capture using biometric application programming interface (BioAPI) Reaffirmed as INCITS/ISO/IEC 29141:2009 R2015INCITS/ISO/IEC 29141:2009 2010 PDF disclaimer This PDF file may contain embedded typefaces. In

2、 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 not infringing Ado

3、bes 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 were optimized for

4、 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 Information Technology

5、 Standards) as an American National Standard. Date of ANSI Approval: 9/28/2010 Published by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2010 by Information Technology Industry Council (ITI). All rights reserved. These materials are subject to copyri

6、ght 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 form, including an el

7、ectronic 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 2010 All rights reserved ISO/IEC 29141:2009(E) ISO/IEC 2009 All right

8、s reserved iiiContents Page Foreword .v Introductionvi 1 Scope1 2 Conformance .1 3 Normative references1 4 Terms and definitions .1 5 Abbreviated terms .3 6 Requirements.3 7 BioAPI function calls.4 7.1 BioAPI_ControlUnit().4 7.1.1 Usage4 7.1.2 Function definition 4 7.1.3 Parameters .4 7.2 BioAPI_Cap

9、ture().5 7.2.1 Usage5 7.2.2 Function definition 5 7.2.3 Parameters .5 7.2.4 Additional error return codes.6 7.3 BioAPI_QueryUnits().6 7.3.1 Usage6 7.3.2 Function definition 6 7.3.3 Parameters .6 7.3.4 BioAPI_UNIT_SCHEMA.7 8 Capture control blocks (CCB) 9 9 Record types and fields9 9.1 Control and re

10、quired fields.9 9.2 Image height and width.11 9.3 Image data11 9.4 Amputated or bandaged fingers 11 9.4.1 Type-4 records.11 9.4.2 Type-14 records.11 9.5 Capture resolution.12 9.6 Image compression.12 9.7 Selecting images to be captured .12 9.8 Calculation of finger segment position.13 9.9 Segmentati

11、on quality .13 9.10 Image quality13 9.10.1 General .13 9.10.2 Setting quality thresholds 13 9.11 Bits per pixel 14 9.12 Date printed14 9.13 Image capture equipment.14 10 Returned BIR14 10.1 BIR header14 10.2 BDB format.15 11 Error codes 15 ISO/IEC 29141:2009(E) iv ISO/IEC 2009 All rights reserved11.

12、1 Unable to parse15 11.2 Roll capture not supported.15 11.3 Slap capture not supported 15 11.4 Segment position calculation not supported .15 11.5 Quality algorithm not supported15 11.6 Compression algorithm not supported .15 11.7 Segment position calculation algorithm not supported16 11.8 Image res

13、olution not supported.16 11.9 Type-4 records not supported16 11.10 Type-14 records not supported16 11.11 Finger position not supported16 12 Example capture orders16 Annex A (informative) Example capture control blocks (CCB) for acquisition of images 18 A.1 Three slaps (FANC TOT) .18 A.1.1 Type-1 rec

14、ord .18 A.1.2 Type-2 record (IDC 0) 18 A.1.3 Type-14 record (IDC 1) 18 A.1.4 Type-14 record (IDC 2) 19 A.1.5 Type-14 record (IDC 3) 19 A.2 Ten plain impressions (no TOT).20 A.2.1 Type-1 record .20 A.2.2 Type-2 record (IDC 0) 20 A.2.3 Type-4 record (IDC 1) 20 A.2.4 Type-4 record (IDC 2) 20 A.2.5 Type

15、-4 record (IDC 3) 21 A.2.6 Type-4 record (IDC 4) 21 A.2.7 Type-4 record (IDC 5) 21 A.2.8 Type-4 record (IDC 6) 22 A.2.9 Type-4 record (IDC 7) 22 A.2.10 Type-4 record (IDC 8) 22 A.2.11 Type-4 record (IDC 9) 23 A.2.12 Type-4 record (IDC 10) 23 Annex B (informative) BioAPI calling sequence example.24 I

16、SO/IEC 29141:2009(E) ISO/IEC 2009 All rights reserved vForeword 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 th

17、e development 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-go

18、vernmental, 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 tas

19、k of the joint 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

20、vote. Attention 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 29141 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information tech

21、nology, Subcommittee SC 37, Biometrics. ISO/IEC 29141:2009(E) vi ISO/IEC 2009 All rights reservedIntroduction This International Standard specifies how a BioAPI application can interact with a BioAPI framework to support a tenprint capture (capture of the fingerprints of all ten fingers). It specifi

22、es and supports the deployment of large-scale identity management and credentialing systems (which often require a tenprint capture as part of the identity vetting and background-checking process). This International Standard provides additional standardization of fields (that are left undefined in

23、BioAPI), in order to standardize the support for a tenprint capture, but is in all other respects a profiling of BioAPI to support the tenprint capture. This International Standard defines a biometric data block format for carrying the data obtained from a tenprint capture. It specifies all the para

24、meters, function calls, and other information needed by an application for the use of BioAPI in support of tenprint capture. It also specifies the conformance requirements on a biometric service provider that supports tenprint capture using this International Standard. INTERNATIONAL STANDARD ISO/IEC

25、 29141:2009(E) ISO/IEC 2009 All rights reserved 1Information technology Biometrics Tenprint capture using biometric application programming interface (BioAPI) 1 Scope This International Standard specifies requirements for the use of ISO/IEC 19784-1, as amended by ISO/IEC 19784-1/Amd. 1 (BioAPI) for

26、the purpose of performing a tenprint capture operation. It specifies a BDB format that is used to interact with a BioAPI framework (and hence with BSPs) to support an application wishing to perform a tenprint capture. It specifies a capture control block and a capture output block that conforming BS

27、Ps are required to support if they conform to this International Standard. 2 Conformance Biometric Service Providers (BSPs) that claim conformance to this International Standard shall satisfy requirements specified in Clauses 6 through 10. 3 Normative references The following referenced documents ar

28、e indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ANSI/NIST-ITL 1-2007, Data Format for the Interchange of Fingerprint, Facial, 7.1.3 Pa

29、rameters 7.1.3.1 BSPHandle (input) The handle of the attached BSP. 7.1.3.2 UnitID (input) ID of the BioAPI Unit. 7.1.3.3 ControlCode (input) Indicates the purpose of this function to differentiate it from other BioAPI_ControlUnit() calls. The value of “1” shall be used to indicate that a CCB is bein

30、g set. 7.1.3.4 InputData (input) Pointer to a BioAPI_Data structure. This structure shall contain the address and length of the CCB. ISO/IEC 29141:2009(E) ISO/IEC 2009 All rights reserved 57.1.3.5 OutputData (output) No output is needed. The buffer address will be NULL and the length set to “0” with

31、in the BioAPI_DATA structure. Usage of the OutputData parameter to return diagnostic data about the CCB may be desirable. 7.1.3.6 Additional error return codes Error codes should be used to indicate errors detected in the CCB passed in the InputData parameter. See Clause 11. 7.2 BioAPI_Capture() 7.2

32、.1 Usage This function shall trigger a BSP to perform fingerprint image captures and to create a new CCB. The fingers captured and the processing done on the fingers shall be controlled by inclusion of empty fields in the current CCB, which was specified in the BioAPI_ControlUnit() call. 7.2.2 Funct

33、ion definition BioAPI_RETURN BioAPI BioAPI_Capture (BioAPI_HANDLE BSPHandle, BioAPI_BIR_PURPOSE Purpose, BioAPI_BIR_SUBTYPE Subtype, BioAPI_BIR_BIOMETRIC_DATA_FORMAT *OutputFormat, BioAPI_BIR_HANDLE *CapturedBIR, Int32_t Timeout, BioAPI_BIR_HANDLE *AuditData); 7.2.3 Parameters 7.2.3.1 BSPHandle (inp

34、ut) The handle of the attached BSP. 7.2.3.2 Purpose (input) A value indicating the purpose of the biometric data capture. For the purposes of tenprint capture, any purpose value may be used. 7.2.3.3 Subtype (input/optional) Specifies which subtype to capture. This parameter does not have the flexibi

35、lity to describe the range of possible finger image sets that might be captured. A value of BioAPI_NO_SUBTYPE_AVAILABLE (0x00) shall be used to indicate that the BSP is to select the subtypes using the current CCB. No other value may be used. ISO/IEC 29141:2009(E) 6 ISO/IEC 2009 All rights reserved7

36、.2.3.4 OutputFormat (input/optional) Specifies which BDB (biometric data block) format to use for the returned CapturedBIR. The CBEFF Format Owner and CBEFF Format Type shall be set to 0x001B and 0x8013 respectively to designate that the BDB in the CBEFF BIR is a COB. 7.2.3.5 CapturedBIR (output) A

37、handle to a BIR whose BDB is a COB containing the captured data. See Clause 10 for a specification of this BIR. 7.2.3.6 Timeout (input) Specifies the timeout value (in milliseconds) for the entire capture operation requested by the application. If this timeout is reached, the function returns an err

38、or, and no results. This value can be any positive number. Avalue of -1 means the BSPs default timeout value will be used. 7.2.3.7 AuditData (output/optional) A handle value of BioAPI_UNSUPPORTED_BIR_HANDLE shall be used to indicate that AuditData is not available. 7.2.4 Additional error return code

39、s BioAPI includes codes such as BioAPIERR_UNABLE_TO_CAPTURE to indicate that the BSP could not collect the data that it is meant to. Additional error codes specific to tenprint capture are specified in Clause 11. 7.3 BioAPI_QueryUnits() 7.3.1 Usage Applications will use this function to determine if

40、 the device attached to the BSP conforms to this International Standard and if so, to discover what specific capabilities are supported by the attached tenprint capture device (unit). 7.3.2 Function definition BioAPI_RETURN BioAPI BioAPI_QueryUnits (const BioAPI_UUID *BSPUuid, BioAPI_UNIT_SCHEMA *Un

41、itSchemaArray, uint32_t *NumberOfElements); 7.3.3 Parameters 7.3.3.1 BSPUuid (input) The unique identifier for the (tenprint) BSP to which the unit (tenprint scanning device) is attached and for which the unit information is to be returned. ISO/IEC 29141:2009(E) ISO/IEC 2009 All rights reserved 77.3

42、.3.2 UnitSchemaArray (output) A pointer to the address of the array of elements of type BioAPI_UNIT_SCHEMA containing the unit schema information. Specific elements of interest are defined in 6.3.4, below. 7.3.3.3 NumberOfElements (output) A pointer to the number of elements in the array. 7.3.4 BioA

43、PI_UNIT_SCHEMA This schema is defined in Clause 7.55 of the base standard (BioAPI specification). There are three elements of this structure that are of particular interest for the purpose of tenprint capture (the UnitProperties, UnitPropertyID, and UnitProperty elements), though other elements of t

44、he schema may also be of general use (e.g., vendor information, firmware version, etc.). If more than one type of BioAPI Unit is attached to the BSP, more than one Unit schema may be returned. Tenprint scanner devices shall set UnitCategory to BioAPI_CATEGORY_SENSOR (0x00000008). 7.3.4.1 UnitPropert

45、ies UUID indicating a set of properties of the BioAPI Unit. The indicated set can either be specified by each vendor or follow a related standard. The UUID “ba38567f-66be-468c-9ada-0b1eeb0cc7fb” shall indicate that the unit supports the profile/standard for “Tenprint Capture Using BioAPI”. 7.3.4.2 U

46、nitPropertyID UUID of the format of the following Unit property structure. The UUID “10568e83-c7f8-418d-9913-4e80f01aecfb” shall be used for the format ID for Tenprint Scanner Properties. 7.3.4.3 UnitProperty UnitProperty is of type BioAPI_DATA, which is defined in 7.19 of the BioAPI specification (

47、ISO/IEC 19784-1). It includes the address and length of a memory buffer containing the Unit. The format and content of the Unit property can either be specified by the vendor or be specified in a related standard. For tenprint scanners conforming to this International Standard, the Unit property str

48、ucture shall be defined as shown in Table 1. Use sequential, bit-oriented fields. Values for all fields shall be present. Big-endian (network) byte ordering shall be used. ISO/IEC 29141:2009(E) 8 ISO/IEC 2009 All rights reservedTable 1 - UnitProperty structure Field Name Type Size Values Notes Rolls

49、 Boolean 1B 0x00, 0x01 01 indicates device can capture rolled fingerprints Slaps Boolean 1B 0x00, 0x01 01 indicates device can capture slap prints Segment position calculation Boolean 1B 0x00, 0x01 01 indicates device can calculate bounding boxes Number of quality algorithms supported Integer 1B 0-255 Number of quality algorithm identifiers contained in the next field Quality algorithms supported Integer (array) Var. Ea