1、American National StandardDeveloped byfor Information Technology Conformance TestingMethodology Standard forBiometric Data InterchangeFormat Standards Part 2: Conformance TestingMethodology for ANSI INCITS 378-2004,Finger Minutiae Format forData InterchangeANSI INCITS 423.2-2008ANSIINCITS 423.2-2008
2、Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networki
3、ng permitted without license from IHS-,-,-ANSIINCITS 423.2-2008American National Standardfor Information Technology Conformance Testing Methodology Standardfor Biometric Data InterchangeFormat Standards Part 2: Conformance Testing Methodologyfor ANSI INCITS 378-2004,Finger Minutiae Format for Data I
4、nterchangeSecretariatInformation Technology Industry CouncilApproved May 21, 2008American National Standards Institute, Inc.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-Appro
5、val of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been r
6、eached by directly andmaterially affected interests. Substantial agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Sta
7、ndards is completely voluntary; theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does no
8、t develop standards andwill in no circumstances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretati
9、ons should beaddressed to the secretariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to re
10、affirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New
11、 York, NY 10036Copyright 2008 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the
12、 United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may berequired for the implementation of the standard disclose such patents to the publisher. However,neither the developers nor the publisher have undertaken a patent search in order to ide
13、ntifywhich, if any, patents may apply to this standard. As of the date of publication of this standardand following calls for the identification of patents that may be required for the implementation ofthe standard, no such claims have been made. No further patent search is conducted by the de-velop
14、er or publisher in respect to any standard it processes. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or netwo
15、rking permitted without license from IHS-,-,-iContentsPageForeword iiIntroduction .iv1 Scope . 12 Conformance 13 Normative References 14 Terms and Definitions. 25 Symbols (and Abbreviated Terms). 36 Testable Data Format Elements. 36.1 General. 36.2 General Record Header . 36.3 View Record Header 56.
16、4 Extended Data Encoding 67 Conformance Testing Methodology 87.1 Implementation Under Test 87.2 Level 1 and Level 2 Assertions. 97.3 Test Method 137.4 Test Procedure. 167.5 Test Report. 198 Test Assertions for Type A Conformance Testing 198.1 General Consideration 198.2 Test Case Names. 198.3 Test R
17、esult Purposes . 198.4 Expected Results 208.5 Test Results Codes 20Table1 Data Record Fields with the Conformance Level Constraintsand Operators (ANSI INCITS 378-2004) 9Figures1 BDIR Data File Level 1 and Level 2 Conformance Test Flow(ANSI INCITS 378-2004) 142 BDIR Data File Conformance Testing Proc
18、edure (ANSI INCITS 378-2004) 173 BDIR Data File Level 1 and 2 Conformance Testing ImplementationProcedure (ANSI INCITS 378-2004) 18Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-
19、,-iiForeword (This foreword is not part of American National Standard ANSI INCITS 423.2-2008.)This standard defines a method of testing the validity of fingerprint minutia informa-tion as encoded in accordance with ANSI INCITS 378-2004. This conformance teststandard establishes the methodologies and
20、 test assertions that are necessary to es-tablish minimal conformance as defined in ANSI INCITS 423.1.Requests for interpretation, suggestions for improvement or addenda, or defect re-ports are welcome. They should be sent to InterNational Committee for InformationTechnology Standards (INCITS), ITI,
21、 1250 Eye Street, NW, Suite 200, Washington,DC 20005.This standard was processed and approved for submittal to ANSI by INCITS. Com-mittee approval of this standard does not necessarily imply that all committee mem-bers voted for its approval. At the time it approved this standard, INCITS had thefoll
22、owing members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc. Steve ZillesScott Foshee (Alt.)AIM Global Dan MullenCharles Biss (Alt.)Apple Computer, Inc. David MichaelDistributed Managment Task Force . Tony DiCenzoElectronic Indus
23、tries Alliance . Edward Mikoski, Jr.EMC Corporation Gary RobinsonFarance, Inc. Frank FaranceTimothy Schoechle (Alt.)Google Zaheda BhoratGS1 US Ray DelnickiFrank Sharkey (Alt.)James Chronowski (Alt.)Mary Wilson (Alt.)Hewlett-Packard Company. Karen HigginbottomSteve Mills (Alt.)Scott Jameson (Alt.)IBM
24、 Corporation . Ronald F. SillettiRobert Weir (Alt.)Sandy Block (Alt.)Richard Schwerdtfeger (Alt.)IEEE . Judith GormanTerry DeCourcelle (Alt.)Bill Ash (Alt.)Jodi Haasz (Alt.)Bob Labelle (Alt.)Susan Tatiner (Alt.)Intel. Philip WennblomDave Thewlis (Alt.)Grace Wei (Alt.)Lexmark International. Don Wrigh
25、tDwight Lewis (Alt.)Paul Menard (Alt.)Microsoft Corporation . Jim HughesDave Welsh (Alt.)Isabelle Valet-Harper (Alt.)National Institute of Standards b) conditional requirements such requirements are to be observed if the conditions set out in the specification apply; c) optional requirements such re
26、quirements can be selected to suit the implementation, and are to be observed if selected. 7.1.2 Mandatory Testing Levels As described in ANSI INCITS 423.1 and for the purposes of this part of ANSI INCITS 423, the IUT shall be tested for conformity to ANSI INCITS 378-2004 using two levels of testing
27、. These Conformance Testing Levels are: Level 1: Data Format Conformance such requirements are to be observed for all fields; Level 2: Internal Consistency Checking such requirements are to be observed for several fields, detailed in Clause 7.2. 7.1.3 Optional Testing Levels Additionally, the IUT ma
28、y be optionally tested, for the purposes of this part of ANSI INCITS 423 and as described in ANSI INCITS 423.1 using an additional level of testing: Level 3: Content Checking such requirements are to be observed in a combination of computer hardware and/or software that is used in the testing labora
29、tory. Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ANSI INCITS 423.2-2008 9 7.1.4 Conformance Evaluation To evaluate the conformity of a biometric product, it is necessary to
30、 have a statement of the capabilities that have been implemented in conformance with ANSI INCITS 378-2004 so that the implementation can be tested for conformity against relevant requirements and against those requirements only. Such a statement shall be called a Format Conformity Statement for the
31、Finger Minutia-Based Interchange Format (FCS) in ANSI INCITS 378-2004, and shall be prepared by the IUT supplier prior to the beginning of the Conformance Testing. The FCS shall contain the minimum requirements of ANSI INCITS 378-2004 that were included in the IUT. Subclause 7.2 lists the minimum re
32、quirements of the Biometric Data Record of ANSI INCITS 378-2004 with conformance level constraints in the form of assertions expressed in the Assertion Definition Language (ADL) specified in ANSI INCITS 423.1. 7.2 Level 1 and Level 2 Assertions 7.2.1 Assertion Table Table 1 Data Record Fields with t
33、he Conformance Level Constraints and Operators (ANSI INCITS 378-2004) Assertion Field Operator Operands Conditional References Level 1 Format Identifier EQ 0x464D5200 (Note 1) 6.4.1 1 2 Version EQ 0x20323000 (Note 1) 6.4.2 1 3.1 Record Length GTE 26 YES 6.4.3 1 3.2 Record Length LTE 65535 YES 6.4.3
34、1 3.3 Record Length EQ Total Bytes Read 6.4.3 2 3.4 Record Length EQ Total Bytes Expected (Note 2) YES 6.4.3 2 4 CBEFF PID Owner NEQ 0 6.4.4 1 5 CBEFF PID Type NONE 6.4.4 6 Capture Equipment Compliance NONE 6.4.5 7 Capture Equipment ID NONE 6.4.6 8 Image Size X NONE 6.4.7 9 Image Size Y NONE 6.4.8 1
35、0 Resolution X NEQ 0 6.4.9 1 11 Resolution Y NEQ 0 6.4.10 1 12.1 Number of Finger Views EQ Views Read 6.4.11 2 12.2 Number of Finger Views LTE 176 (Note 3) 6.4.11, 6.5.1.2 1 Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or netwo
36、rking permitted without license from IHS-,-,-ANSI INCITS 423.2-2008 10 13 Reserved EQ 0 6.4.12 1 14 Finger Position LTE 10 6.5.1.1 1 15 View Number C Next Finger View (Note 4) YES 6.5.1.2 2 16 Impression Type EQ 0 - 3, 8, 9 6.5.1.3 1 17 Finger Quality EQ 0 100,254,255 6.5.1.4 1 18 Number of Minutiae
37、 EQ Minutiae Read 6.5.1.5, 6.5.2 2 19 Minutiae Type EQ 0, 1, 2 6.5.2.1 1 20 Minutiae Position X LT Image Size X 6.5.2.2 2 21 Minutiae Position Y LT Image Size Y 6.5.2.2 2 22 Minutiae Position C (Note 5) 2 23 Minutiae Angle LTE 179 6.5.2.3 1 24 Minutiae Quality LTE 100 6.5.2.4 1 25 Extended Data Bloc
38、k Length EQ Bytes Read 6.6.1.1 2 25.1 Extended Data Block Length EQ Bytes Expected (Note 6) YES 6.6.1.1 2 26 Type of Extended Data Area EQ 0x0001 0x0002, 0x0101 0xFFFF 6.6.1.211 27 Length of Extended Data Area GTE 4 6.6.1.3 1 27.1 Length of Extended Data Area EQ Bytes Read YES 6.6.1.3 2 28 Ridge Ext
39、raction Method LTE 2 6.6.2.1 1 29 Minutiae Index 1 C (Note 7) 6.6.2 2 30 Minutiae Index 2 C (Note 8) 6.6.2 2 30.1 Minutiae Index 2 C (Note 9) YES 6.6.2 2 31 Ridge Count EQ 0 (Note 10) YES 6.6.2.1 1 32 Core Information Type LTE 1 6.6.3.1 1 1For the purposes of this standard, text of 6.6.1.2 of ANSI I
40、NCITS 378-2004 is used. Table 3 of ANSI INCITS 378-2004 is ignored, pending amendment to ANSI INCITS 378-2004. Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ANSI INCITS 423.2-
41、2008 11 33 Core Reserved EQ 0 6.6.3.2 1 34 Number of Cores EQ Cores Read 6.6.3.2 2 35 Core Position X LT Image Size X 6.6.3.3 2 36 Core Position Y LT Image Size Y 6.6.3.3 2 37 Core Angle LTE 179 6.6.3.4 1 38 Delta Information Type EQ 0, 1 6.6.3.5 1 39 Number of Deltas EQ Deltas Read 6.6.3.6 2 40 Del
42、ta Position X LT Image Size X 6.6.3.7 2 41 Delta Position Y LT Image Size Y 6.6.3.7 2 42 Delta Angle 1 LTE 179 6.6.3.8 1 43 Delta Angle 2 LTE 179 6.6.3.8 1 44 Delta Angle 3 LTE 179 6.6.3.8 1 Note 1 (1,2) Format Identifier, Version If these tests fail, the result should be checked to see if the littl
43、e Endian equivalence of the expected value matches, and if so, the conformance test report should indicate that there may be an issue with endianness. Note 2 (3.4) Record Length EQ Total Bytes Expected The following calculation will be evaluated once the Extended Data Block Length field for the last
44、 finger view has been parsed successfully (not having reached an End-of-File marker prematurely). In the event that an End-of-File marker is reached prematurely this test will be marked as having failed, but no value of Total Bytes Expected will be produced. Copyright American National Standards Ins
45、titute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ANSI INCITS 423.2-2008 12 The initial value of SUMBYTES below will correspond to the length of the BDIR header in bytes (26 or 30). SUMBYTES = BDIR Header Length FOR I =
46、1 TO Number of Finger Views SUMBYTES = SUMBYTES + 6 + (Number of Minutiae * 6) SUMBYTES = SUMBYTES + Extended Data Block Length END Total Bytes Expected = SUMBYTES Note 3 (12.2) Number of Finger Views This test will pass if the value of Number of Finger Views is less than or equal to the sum of all
47、possible finger positions (11) permitted by the standard multiplied by the maximum number of views per finger (16). This value must therefore be less than or equal to 176. Note 4 (15) View Number As each finger view from the BDIR is read, a counter, Next Finger View, for the corresponding finger pos
48、ition (if valid) is incremented and compared to View Number. The test shall pass if Next Finger View is equal to View Number. Note 5 (22) Minutiae Position Though not explicitly defined in the standard, all minutiae within a finger view should have unique x/y coordinates to avoid potential interoperability issues. This test shall pass if the Minutiae Position is a unique pair of minutiae x/y coordinates within the finger view. Note 6 (25.1) Extended Data Block Length EQ Bytes Expected As the individual ex
