ANSI INCITS 423 2-2008 Information Technology C Conformance Testing Methodology Standard for Biometric Data Interchange Format Standards C Part 2 Conformance Te.pdf

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-2008 (R2013)ANSI INCITS 4

2、23.2-2008(R2013)ANSIINCITS 423.2-2008(R2013)American 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 InterchangeSecretari

3、atInformation Technology Industry CouncilApproved May 21, 2008American National Standards Institute, Inc.Approval 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.Consensu

4、s is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objectio

5、ns be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproduc

6、ts, processes, or procedures not conforming to the standards.The American National Standards Institute does not 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

7、 American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations 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 ti

8、me. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Insti

9、tute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New 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

10、or otherwise,without prior written permission of ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the 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 t

11、he publisher. However,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, 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 imple

12、mentation ofthe standard, no such claims have been made. No further patent search is conducted by the de-veloper 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.iContentsPageFor

13、eword 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.4 Extended Data Encoding 67 Conformance Testing Methodology 8

14、7.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 Result Purposes . 198.4 Expected Results 208.5 Test Results Co

15、des 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 Procedure (ANSI INCITS 378-2004) 173 BDIR Data File Level 1 and 2

16、 Conformance Testing ImplementationProcedure (ANSI INCITS 378-2004) 18iiForeword (This foreword is not part of American National Standard ANSI INCITS 423.2-2008 (R2013).)This standard defines a method of testing the validity of fingerprint minutia informa-tion as encoded in accordance with ANSI INCI

17、TS 378-2004. This conformance teststandard establishes the methodologies and 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 t

18、o InterNational Committee for InformationTechnology Standards (INCITS), ITI, 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

19、 for its approval. At the time it approved this standard, INCITS had thefollowing 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.

20、David MichaelDistributed Managment Task Force . Tony DiCenzoElectronic Industries 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-

21、Packard Company. Karen HigginbottomSteve Mills (Alt.)Scott Jameson (Alt.)IBM 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

22、 WennblomDave Thewlis (Alt.)Grace Wei (Alt.)Lexmark International. Don WrightDwight 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 con

23、ditions set out in the specification apply; c) optional requirements such requirements 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

24、be tested for conformity to ANSI INCITS 378-2004 using two levels of testing. 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, de

25、tailed in Clause 7.2. 7.1.3 Optional Testing Levels Additionally, the IUT may 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 combina

26、tion of computer hardware and/or software that is used in the testing laboratory. ANSI INCITS 423.2-2008 (R2013) 9 7.1.4 Conformance Evaluation To evaluate the conformity of a biometric product, it is necessary to have a statement of the capabilities that have been implemented in conformance with AN

27、SI 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 Finger Minutia-Based Interchange Format (FCS) in ANSI INCITS 378-2004, and shall be pre

28、pared 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 requirements of the Biometric Data Record of ANSI INCITS 378-2004 with conformance level

29、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 the Conformance Level Constraints and Operators (ANSI INCITS 378-2004) Assertion Field O

30、perator 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 1 3.3 Record Length EQ Total Bytes Read 6.4.3 2 3.4 Record Length EQ Total Bytes Expect

31、ed (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 10 Resolution X NEQ 0 6.4.9 1 11 Resolution Y NEQ 0 6.4.10 1 12.1 Number of Finger Views

32、 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 ANSI INCITS 423.2-2008 (R2013) 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 Qualit

33、y EQ 0 100,254,255 6.5.1.4 1 18 Number of Minutiae 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 Minuti

34、ae Quality LTE 100 6.5.2.4 1 25 Extended Data Block 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

35、Data Area EQ Bytes Read YES 6.6.1.3 2 28 Ridge Extraction 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 pu

36、rposes of this standard, text of 6.6.1.2 of ANSI INCITS 378-2004 is used. Table 3 of ANSI INCITS 378-2004 is ignored, pending amendment to ANSI INCITS 378-2004. ANSI INCITS 423.2-2008 (R2013) 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 Si

37、ze 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 Delta 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.

38、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 little Endian equivalence of the expected value matches, and if so, the conformance test report should indicate that t

39、here 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 finger view has been parsed successfully (not having reached an End-of-File marker prematurely). In the event th

40、at 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. ANSI INCITS 423.2-2008 (R2013) 12 The initial value of SUMBYTES below will correspond to the length of the BDIR header in bytes (26 or 30). SUMBYTES = BDI

41、R Header Length FOR I = 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

42、equal to the sum of all 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

43、corresponding finger position (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 a

44、void 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 extended data areas are read, the Length of Extended Data Area param

45、eter for each one will become known. The sum of these is Bytes Expected for the extended data block, in accordance with Section 6.6.1.1 of the base standard. The test shall pass if the length is zero for a record that has no extended data. Note 7 (29) Minutiae Index 1 If Minutiae Index 1 corresponds

46、 with the first ridge count in a Four-neighbor or Eight-neighbor group, or if the Ridge Extraction Method is zero (0), the test shall pass if the index is between 1 and Number of Minutiae. Otherwise, the test shall pass only if the index is the same value as Minutiae Index 1 of the first ridge count

47、 in the same Four-neighbor or Eight-neighbor group. Note 8 (30) Minutiae Index 2 If the Ridge Extraction Method is zero (0), the test shall pass if the index is between 1 and Number of Minutiae, and if the index is not equal to Minutia Index 1. If the Ridge Extraction Method is one (1) or two (2) th

48、en the test shall pass if the index is between 0 and Number of Minutiae. ANSI INCITS 423.2-2008 (R2013) 13 Note 9 (30.1) Minutiae Index 2 This test is only evaluated if Minutiae Index 2 is not zero (0) and the Ridge Extraction Method is not zero (0). Each ridge count within the same Four-neighbor or

49、 Eight-neighbor group should refer to the same center minutiae, Minutiae Index 1, and a neighboring minutiae, Minutiae Index 2, from a different quadrant or octant. Thus, this test shall pass if Minutiae Index 2 is unique within the same Four-neighbor or Eight-neighbor group. Note 10 (31) Ridge Count This test is only evaluated if Minutiae Index 2 is zero (0) and Ridge Extraction Method is not zero (0). This test s