ANSI INCITS 358 AMD 1-2007 Information Technology C BioAPI Specification C Amendment 1 Support for Biometric Fusion.pdf

1、American National StandardDeveloped byfor Information Technology BioAPI Specification Amendment 1: Support forBiometric FusionANSI INCITS 358-2002/AM1-2007ANSIINCITS358-2002/AM1-2007ANSIINCITS 358-2002/AM1-2007Supplement toANSI INCITS 358-2002American National Standardfor Information Technology BioA

2、PI Specification Amendment 1: Support forBiometric FusionSecretariatInformation Technology Industry CouncilApproved August 17, 2007 American National Standards Institute, Inc.Approval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other

3、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 reached by directly andmaterially affected interests. Substantial agreement means much more thana simple majority, but no

4、t necessarily unanimity. Consensus requires that allviews and objections 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 stand

5、ards or not, from manufacturing, marketing, purchasing, or usingproducts, 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 pe

6、rson shall have the right or authority to issue aninterpretation of an 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

7、: 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 reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on al

8、l standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2007 by Information Technology Industry Council (ITI)All rights reserved.No part of this public

9、ation 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 United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may berequ

10、ired 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 identifywhich, if any, patents may apply to this standard. As of the date of publication of this standardand following call

11、s 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-veloper or publisher in respect to any standard it processes. No representation is made or impliedthat licenses are not requi

12、red to avoid infringement in the use of this standard.iForeword (This foreword is not part of American National Standard ANSI INCITS 358-2002/AM1-2007.)INCITS (The InterNational Committee for Information Technology Standards) is theANSI-recognized Standards Development Organization for information t

13、echnologywithin the United States of America. Members of INCITS are drawn from Govern-ment, Corporations, Academia and other organizations with a material interest in thework of INCITS and its Technical Committees. INCITS does not restrict membershipand attracts participants in its technical work fr

14、om 13 different countries, and oper-ates under the rules of the American National Standards Institute.In the field of Biometrics, INCITS has established the Technical Committee M1. Stan-dards developed by this Technical Committee have reached consensus throughoutthe development process and have been

15、 thoroughly reviewed through several PublicReview processes. In addition, the INCITS Executive Board and the ANSI Board ofStandards Review have approved this American National Standard for Publication asan ANSI INCITS Standard.Requests for interpretation, suggestions for improvement or addenda, or d

16、efect re-ports are welcome. They should be sent to 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 ne

17、cessarily imply that all committee mem-bers voted for its approval. At the time it approved this standard, INCITS had thefollowing members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAIM Global Dan MullenCharles Biss (Alt.)Apple Computer, Inc. Da

18、vid MichaelElectronic Industries Alliance Edward Mikoski, Jr.David Thompson (Alt.)EMC Corporation Gary RobinsonFarance, Inc Frank FaranceTimothy Schoechle (Alt.)GS1 US Frank SharkeyJames Chronowski (Alt.)Mary Wilson (Alt.)Hewlett-Packard Company. Karen HigginbottomSteve Mills (Alt.)Scott Jameson (Al

19、t.)IBM Corporation . Ronald F. SillettiPeter Schirling (Alt.)IEEE . Judith GormanTerry DeCourcelle (Alt.)Bill Ash (Alt.)Jodi Haasz (Alt.)Bob Labelle (Alt.)Intel. Philip WennblomDave Thewlis (Alt.)Jesse Walker (Alt.)Grace Wei (Alt.)Lexmark International . Don WrightDwight Lewis (Alt.)Paul Menard (Alt

20、.)Microsoft Corporation . Jim HughesDon Stanwyck (Alt.)Isabelle Valet-Harper (Alt.)iiOrganization Represented Name of RepresentativeNational Institute of Standards b) three new BIR data types (BioAPI_DATA_TYPE_SCORE, BioAPI_DATA_TYPE_DECISION, and BioAPI_DATA_TYPE_BIOGRAPHIC); and c) one new BIR pur

21、pose (BioAPI_PURPOSE_DECIDE). The new data type BioAPI_DATA_TYPE_BIOGRAPHIC is intended to designate non-biometric data that potentially affects a biometric operation (to which that data is passed as input), and is not intended to enable BioAPI to manage biographic information in general. This amend

22、ment also specifies a simple “score“ BDB format and a simple “decision“ BDB format. ANSI INCITS 358-2002/AM1-2007 2 Editorial conventions Throughout this document, the following conventions are used to indicate changes to the text: a) an insertion is indicated as in the following example: inserted t

23、ext; b) a simple (not extensive) replacement is indicated as in the following example: replacement text; c) a deletion is indicated as in the following example: deleted text. ANSI INCITS 358-2002/AM1-2007 3 Changes to the text 1) In 1.6, modify the text under the heading “1. Using Primitive function

24、s“ as follows: _ There are four primitive functions in the API which, when used in sequence on client and server, can accomplish the same result as the high-level abstractions: Capture Capture is always executed on the client machine; attempting to execute Capture on a machine without a biometric de

25、vice will return “function not supported”. One or more samples are acquired (either for Enrollment, Verification or Identification). The Capture function is allowed to perform as much processing on the sample(s) as it sees fit, and may, in fact, for verification or identification, complete the const

26、ruction of the BIR. If processing is incomplete, Capture returns an “intermediate” BIR; indicating that the Process (or ProcessUsingAuxBIRs) function needs to be called. If processing is complete, Capture returns a “processed” BIR; indicating that the Process (or ProcessUsingAuxBIRs) function does n

27、ot need to be called. The application specifies the purpose for which the samples are intended, giving the BSP the opportunity to do special processing. This purpose is recorded in the header of the constructed BIR. Process and ProcessUsingAuxBIRs The “processing algorithms” must be available on the

28、 server, but may also be available on the client. The Process and ProcessUsingAuxBIRs functions are intended to provide the processing of samples necessary for the purpose of verification or identification (not enrollment). Each of them always takes an “intermediate” BIR as input, and may complete t

29、he processing of the biometric data into “final” form suitable for its intended purpose. On the client, if it completes the processing, it returns a “processed” BIR; otherwise it returns an “intermediate” BIR; indicating that Process (or ProcessUsingAuxBIRs) needs to be called on the Server. On the

30、server, it will always complete processing, and always return a “processed” BIR. The application can always choose to defer processing to the server machine, but may try to save bandwidth (and server horsepower) by calling Process (or ProcessUsingAuxBIRs) on the client. “Processed” BIRs are always s

31、maller than “intermediate” BIRs; by how much is technology dependent, and also dependent on how much processing has already been done by Capture. Match Performs the actual comparison between the “processed” BIR and one template (VerifyMatch and VerifyMatchUsingAuxBIRs), or between the “processed” BI

32、R and a set of templates (IdentifyMatch). The support for VerifyMatchUsingAuxBIRs and IdentifyMatch is optional, but the supported Match functions are always available on the server, and may be available on the client. CreateTemplate CreateTemplate is provided to perform the processing of samples fo

33、r the construction of an enrollment template. CreateTemplate always takes an “intermediate” BIR as input, and constructs a template (i.e., a “processed” BIR with the recorded purpose of either “enroll_verify” and/or “enroll_identify”). Optionally, CreateTemplate can take an old template and create a

34、 new template, which is the adaptation of the old template using the new biometric samples in the “intermediate” BIR. The BSP may optionally allow the application to provide a “payload” to wrap inside the new template. (See section 1.8). _ ANSI INCITS 358-2002/AM1-2007 4 2) In 2.1.2, modify the firs

35、t paragraph as follows: _ A container for biometric data, or non-biometric data that may affect a biometric operation. A BIR may contain raw sample data, partially processed (intermediate) data, or completely processed data, score data (resulting from a matching or fusion operation), decision data (

36、resulting from a matching or fusion operation), or biographic data which can be provided as input to a biometric operation to modify its behavior. A BIR may be used to enroll a user (thus being stored persistently), or may be used to verify or identify a user (thus being used transiently). It may al

37、so be stored and used later to provide feedback to subsequent biometric operations. _ 3) In 2.1.7, modify the text as follows: _ Mask bits that may be ORd together to indicate the type of opaque data in the BIR. (raw OR intermediate OR processed OR score OR decision OR biographic) OR encrypted OR si

38、gned. typedef uint8 BioAPI_BIR_DATA_TYPE; #define BioAPI_BIR_DATA_TYPE_RAW (0x01) #define BioAPI_BIR_DATA_TYPE_INTERMEDIATE (0x02) #define BioAPI_BIR_DATA_TYPE_PROCESSED (0x04) #define BioAPI_BIR_DATA_TYPE_SCORE (0x08) #define BioAPI_BIR_DATA_TYPE_DECISION (0x09) #define BioAPI_BIR_DATA_TYPE_BIOGRAP

39、HIC (0x0A) #define BioAPI_BIR_DATA_TYPE_ENCRYPTED (0x10) #define BioAPI_BIR_DATA_TYPE_SIGNED (0x20) NOTE: In the values BioAPI_BIR_DATA_TYPE_DECISION and BioAPI_BIR_DATA_TYPE_BIOGRAPHIC, two bit positions are set to 1. NOTE: All integer values in the BIR header are little-endian. _ ANSI INCITS 358-2

40、002/AM1-2007 5 4) In 2.1.10, modify the text as follows: _ A value which defines the purpose(s) or use(s) for which the BIR is intended (when used as an input) or suitable (when used as an output or within the BIR header). typedef uint8 BioAPI_BIR_PURPOSE; #define BioAPI_PURPOSE_VERIFY (1) #define B

41、ioAPI_PURPOSE_IDENTIFY (2) #define BioAPI_PURPOSE_ENROLL (3) #define BioAPI_PURPOSE_ENROLL_FOR_VERIFICATION_ONLY (4) #define BioAPI_PURPOSE_ENROLL_FOR_IDENTIFICATION_ONLY (5) #define BioAPI_PURPOSE_AUDIT (6) #define BioAPI_PURPOSE_DECIDE (7) NOTE: All integer values in the BIR header are little-endi

42、an. NOTE: The Purpose value is utilized in two ways. First, it is used as an input parameter to allow the application to indicate to the BSP the purpose that the resulting data is intended for, thus allowing the BSP to perform the appropriate capturing and/or processing to create the proper BIR for

43、this purpose. The second use is within the BIR header to indicate to the application (or to the BSP during subsequent operations) what purposes the BIR is suitable for. For example, some BSPs use different BIR formats depending on whether the data is to be used for verification or identification, th

44、e latter generally including additional information to enhance speed or accuracy. Similarly, many BSPs use different data formats depending on whether the data is to be used as a sample for immediate verification or as a reference template for future matching (i.e., enrollment. Restrictions on the u

45、se of BIR data of a particular purpose include: a) All purposes are valid in the BIR header. b) Purposes of Verify and Identify are only valid as input to the Capture function. c) Purposes of Enroll, Enroll_for_Verification_Only, and Enroll_for_Identification_Only are only valid as input to the Capt

46、ure, Enroll, and Import functions. d) The Audit purpose is not valid as input to any function, but is only used in the BIR header. e) The Process, ProcessUsingAuxBIRs, and Create_Template, Decide, and Fuse functions do not have Purpose as an input parameter, but read the Purpose field from the BIR h

47、eader of the input Captured_BIR. f) The Process and ProcessUsingAuxBIRs functions may accept as input any intermediate BIR with a Purpose including Verify or Identify, and will output only BIRs with a Purpose of Verify and/or Identify. g) The Create_Template function may accept as input any intermed

48、iate BIR with a Purpose including Enroll, Enroll_for_Verification_Only, and/or Enroll_for_Identification, and will output only BIRs with a Purpose including that of the input BIR. h) If a BIR is suitable for enrollment for either subsequent verification or identification, then the Enroll Purpose is to be used in the returned BIR header. i) All score BIRs and decision BIRs must have the Decide purpose. Biographic BIRs may have any purpose. No other types of BIRs may have the Decide purpose. _ ANSI INCITS 358-2002/AM1-2007 6 5) In 2.2.1.1, modify the text as follows: _