NISTMIN XMatch
 
 on card valuation–ConceptandAPI.

1

2

3

4

5

6

7

MIN X

An valuation
basedProgramfortheImprovementofMinutiae

Interoperability

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

MIN XII

AnAssessmentofISO/I C7816Card
Based

Match
on
CardCapabilities

PatrickGrotherandWayneSalamon

NIST

August15,2007

NIST GrotherandSalamon Page1of48

 


 




NISTMIN XMatch on card valuation–ConceptandAPI.

1 Version History 

Aug15,2007:

― ModifiedTable19andTable21toshowourminimumacceptableresponseforcardandmatcherIDs.

Aug14,2007:

― Modified10.3andFigure1:MinutiasortingshouldbethefinalstepintheI378toISO
CCconversion.

― Fixedtypos

Aug3,2007:

― InH.3.4,madeinlineexplicitlinktoNIST'sencryptionkeyforsubmissionofallmaterialtoNIST.

― Deletedredundant"7F2 xx"fromTable14'sdatafield,whicherroneouslyrepeatedTable6content.

― InH.3.2,addedexplicitHTMLlinktothepassword
protectedarea
Registeredparticipantsarerequiredto

downloadandprocessasmallvalidationsetofimages.

July25,2007:ClarifiedsectionH.2.1onhowtoparticipate.

July12,2007:Scheduledeletedhere,andmovedtonewlyestablishMIN XIIhomepage:

http://fingerprint.nist.gov/minexII

July11,2007.Thefinalsetofchangesare:

― ClarificationthattheBITstructureisaread
onlyentityinMIN XII.NISTdoesnotintendtoupdatethe

BIT,norrequirecardtosupportupdatingoftheBIT.Thismeansthatthefingerpositioninformationinthe

BITwilloftenbeincorrect.

― FixdatatypeforPC
basedsimilarityscorewiththatspecifiedforcardi.e.usetwobyteunsignedInteger

similarityscoresbothon
cardandoff
card.

― Fixmatch_templates()function–templatesizesinputvaluesweremissing.

― OnlyoneBITrequired,ifthetwowouldotherwisebeidentical.

― Tag'83'isnowoptionalinBIT.

― Typos,clarifications.

June29,2007.ThisMOCtestspecificationisaheavilyrevisedversionoftheMay24draft.Ithasbeen

producedinresponsetothemanycommentsreceived,andthedecisionsmadeataNISTworkshop.Ashort

finalcommentperiodwillcloseonJuly5,2007,andafinalplanreleasedonJuly9.Pleasenotethemain

changes:

― CorrectedcardAPDUs(sec.8).

― PC/SCcardreadernamed(sec6.3).

― AdoptionofmodifiedOngoingMIN XAPI(sec.9).

― UseofINCITS378templateswithqualityvaluesasprogenitorsofISO
CCtemplates(secs.6.4and7.2).

AbandonISO
CCgenerationbecauseISO
CCdoesn'thavequalityvalues.

― Clarifiedintentofminutiaqualityvalues(sec.7.2.2)

― Refinedtextonhowpruningproceeds(sec10.4).

― Allowtemplategeneratortoreturnacenterforpruning(sec.10.4.4)

May24,2007.ThisinterimversionisavailableforcommentuntilMay31,2007.ThechangesfromMay8are

showninblue.

May8,2007.NISTispleasedtoannouncetheavailabilityofthisdraftevaluationplan.Theentirecontentofthis

documentissubjecttorevision.

NISTspecificallyrequestsreviewersofthedocumenttosubmitcommentstotheauthors.Thesemayinclude

suggestionstoadd,subtract,orchangeitscontent.

March12,2007.NISTrequestedcommentsonthefeasibilityofMOC.NISTismostappreciativeofthe

numerous,enthusiasticandhelpfulresponses.

2

3 Provisional Timeline

October1 Phase2submissionperiod Tentative

LateSeptember WorkshoptodiscussPhase1

Sept21 ReturnofPhase1resultstosuppliers

Sept11 13 BiometricsConsortium,BaltimoreMD

NIST GrotherandSalamon Page2of48

 








NISTMIN XMatch on card valuation–ConceptandAPI.

July11 Sep10 NISTwillacceptapplicationstoparticipateinPhase1.Thisphasewillinclude

acceptancetestingandexecutionofPhase1trials.

July11 stablishmentofMIN XIIwebsite,http://fingerprint.nist.gov/minexII

July9 Finaltestplan

July5 ndofcommentperiod

June28 Releaseofdrafttestplan.NISTinvitescommentsfrominterestedparties.

May31 Commentperiodcloses Past

May24 sBMOCWorkshopatNIST

May9 FirstdraftMIN XII,ISO CC+MOCTestPlan

March29 Commentperiodclosed

March12 MOCConceptdocument+RFP

NIST GrotherandSalamon Page3of48

 


 


 
 
 


























10

20

30

40

50

NISTMIN XMatch on card valuation–ConceptandAPI.

1 Table of Contents 

2 1. Overview ..................................................................................................................7

3 2. Scope ......................................................................................................................7

4 3. NormativeReferences ..................................................................................................8

5 4. Caution ....................................................................................................................9

6 4.1. RelationshipbetweenMIN XIIandotherissues................................................................9

7 4.2. RelationshipbetweenMIN XIIandOngoingMIN X ............................................................9

8 5. Abbreviations.............................................................................................................9

9 6. Aspectsofthetest .................................................................................................... 10

6.1. Match on cardvs.match off card .............................................................................. 10

11 6.2. Fundamentalconceptofthetest ............................................................................... 10

12 6.3. Genericinterfacehardwareandsoftware..................................................................... 10

13 6.4. INCITS378:2004vs.ISO/I C19794 2:2005CompactCard .................................................. 11

14 6.5. BITProcessing....................................................................................................... 11

15 6.6. Card matchercombinations ...................................................................................... 11

16 6.7. Twophasetesting.................................................................................................. 11

17 6.8. Optionsforparticipation.......................................................................................... 12

18 6.9. Three wayinteroperability....................................................................................... 12

19 6.10. Metrics ............................................................................................................... 12

6.11. Participation ........................................................................................................ 12

21 7. ProfileofMIN XIItemplates ........................................................................................ 13

22 7.1. Overview............................................................................................................. 13

23 7.2. INCITS378:2004profile ........................................................................................... 13

24 7.3. ISO/I C19794 2:2005compactcardstructure................................................................ 14

25 7.4. Non presenceofaheader ........................................................................................ 15

26 7.5. Minutiauniqueness................................................................................................. 15

27 7.6. Failuretoacquire .................................................................................................. 15

28 8. MOCinterfacespecification ......................................................................................... 15

29 8.1. Overview............................................................................................................. 15

8.2. ApproachtotheuseofISO/I C7816 ........................................................................... 15

31 8.3. stablishCommunications ........................................................................................ 15

32 8.4. Selectionofthetestapplication ................................................................................ 15

33 8.5. Storeenrollmenttemplateonthecard ........................................................................ 16

34 8.6. NISTreadoftheBIT ............................................................................................... 16

35 8.7. Verification.......................................................................................................... 18

36 8.8. Readingcardidentifier............................................................................................ 20

37 8.9. Readingmatcheridentifier....................................................................................... 20

38 9. PC basedAPIspecification........................................................................................... 21

39 9.1. Overview............................................................................................................. 21

9.2. INCITS378:2004complianttemplates .......................................................................... 21

41 9.3. Submission........................................................................................................... 21

42 9.4. Testinginterface ................................................................................................... 21

43 9.5. SoftwareandDocumentation .................................................................................... 23

44 9.6. Runtimebehavior .................................................................................................. 24

45 10. NISTconversionofI378toISO CCtemplates ..................................................................... 25

46 10.1. Background .......................................................................................................... 25

47 10.2. PresenceofBITsoncard.......................................................................................... 25

48 10.3. UseofBITs........................................................................................................... 25

49 10.4. Numberofminutiae ............................................................................................... 26

10.5. Sortorderofminutiae............................................................................................. 28

51 10.6. Ridgecount,coreanddeltaandzonalqualityinformation ................................................ 28

52 11. References .............................................................................................................. 28

53 AnnexAComparisonoftheINCITS378andISO/I C19794 2standards ............................................... 30

54 A.1 Syntacticdifferences .............................................................................................. 30

55 A.2 Semanticdifferences .............................................................................................. 30

NIST GrotherandSalamon Page4of48

 














 





 



 


 








 


5

10

15

20

25

30

35

40

45

50

NISTMIN XMatch on card valuation–ConceptandAPI.

1 A.3 Simulationprotocol................................................................................................ 31

2 A.4 Resultsafterre quantizationofangleandposition ......................................................... 32

3 A.5 Resultsafterreductioninnumberofminutiae ............................................................... 32

4 A.6 Conclusions .......................................................................................................... 33

AnnexBThree wayinteroperability ......................................................................................... 35

6 AnnexCInputfingerprintimagespecifications ............................................................................ 37

7 C.1 Format ............................................................................................................... 37

8 C.2 Resolutionanddimensions ....................................................................................... 37

9 C.3 Sensorandimpressiontypes ..................................................................................... 37

AnnexD rrorCodesandHandling ........................................................................................... 38

11 Annex PredefinedSDKConstants ........................................................................................... 39

12 .1 Pre definedvalues ................................................................................................. 39

13 AnnexFAmbiguitiesinthestandards........................................................................................ 40

14 F.1 Compactcardsorting.............................................................................................. 40

F.2 Uniqueminutia ..................................................................................................... 40

16 F.3 Nosupportforplacingreferencedataonthecard .......................................................... 40

17 AnnexGISO/I C19794 2:2005recordprofile.............................................................................. 41

18 AnnexHApplicationtoparticipateinMIN XII............................................................................. 43

19 H.1 Whoshouldparticipate............................................................................................ 43

H.2 Howtoparticipate ................................................................................................. 43

21 H.3 NISTactivity......................................................................................................... 43

22 H.4 Pointsofcontact ................................................................................................... 44

23 H.5 AccesstoMIN XIIvalidationdata .............................................................................. 44

24 H.6 AccesstoMIN XIItestdata ...................................................................................... 45

H.7 Reportingofresults ................................................................................................ 45

26 H.8 Returnofthesuppliedmaterials ................................................................................ 45

27 H.9 Agreementtoparticipate......................................................................................... 46

28 AnnexINISTmailingaddress .................................................................................................. 48

29

List of Figures 

31 Figure1–ConversionofINCITS378toISO CC ............................................................................. 26

32 Figure2 UseofINCITS378forsimulationofISO CCaccuracy......................................................... 31

33 Figure3– ffectofminutiapruningonFNMR(above)andFMR(below) .............................................. 34

34 Figure4–Nativevs.Two wayvs.Three wayInteroperability .......................................................... 35

Figure5–Fingerprintimagerasterscanorder............................................................................. 37

36

37 List of Tables 

38 Table1–FamilyofMIN Xevaluations .........................................................................................7

39 Table2–Abbreviations...........................................................................................................9

Table3–MIN XIIclassesofparticipation .................................................................................. 12

41 Table4–MIN XIIprofileofINCITS378:2004standard................................................................... 13

42 Table5–MIN XIIprofileofISO/I C19794 2:2005standard ............................................................ 14

43 Table6–ISO/I C19794 2minutiaetemplateDO ......................................................................... 14

44 Table7–CommandAPDUforselectionofMOCapplication ............................................................. 15

Table8–ResponseAPDUfromselectionofMOCapplication ........................................................... 16

46 Table9–CommandAPDUforstorageofreferencetemplate ........................................................... 16

47 Table10–ResponseAPDUfromstorageofreferencetemplate ........................................................ 16

48 Table11–CommandAPDUforretrievalofbiometricinformationtemplate......................................... 16

49 Table12–ResponseAPDUfromretrievalofbiometricinformationtemplate ....................................... 17

Table13 ISO/I C19794 2BiometricInformationTemplate ........................................................... 17

51 Table14–CommandAPDUforcomparisonofbiometrictemplates ................................................... 18

52 Table15–ResponseAPDUfromcomparisonofbiometrictemplates .................................................. 19

53 Table16–CommandAPDUforretrievalofverificationsimilarityscore .............................................. 19

54 Table17–ResponseAPDUforretrievalofverificationsimilarityscore ............................................... 19

NIST GrotherandSalamon Page5of48

 





















 
 








NISTMIN XMatch on card valuation–ConceptandAPI.

1 Table18–CommandAPDUforretrievalofCardidentifier.............................................................. 20

2 Table19–ResponseAPDUforretrievalofCardidentifier............................................................... 20

3 Table20–CommandAPDUforretrievalofMatcheridentifier.......................................................... 20

4 Table21–ResponseAPDUforretrievalofMatcheridentifier........................................................... 20

5 Table22–NFIQMappings ...................................................................................................... 21

6 Table23–MIN Xcreate_templateAPIFunction........................................................................... 21

7 Table24–MIN XAPImatch_templatesfunction .......................................................................... 22

8 Table25–MIN XAPIget_pidsfunction ..................................................................................... 23

9 Table26–MinutiaencodingsoftheISO CCandINCITS378 ............................................................. 30

10 Table27–MinutialocationquantizationofISO CCandINCITS378templates....................................... 30

11 Table28–MinutiaanglequantizationofISO CCandINCITS378templates .......................................... 30

12 Table29–SourcecodeforconversionofINCITS378toISO CC......................................................... 31

13 Table30–RelativeaccuracyofISO CCandINCITS378templates(FixedFMR)...................................... 32

14 Table31–RelativeaccuracyofISO CCandINCITS378templates(fixedt).......................................... 32

15 Table32–MIN XAPIreturncodes ........................................................................................... 38

16 Table33–MIN XAPIpredefinedvalues ..................................................................................... 39

17 Table34 ISO/I C19794 2andISO/I C7816 11fingerpositioncodes ............................................... 39

18 Table35–MIN XIIprofileofISO/I C19794 2:2005standard........................................................... 41

19 Table36–ISO/I C19794 2minutiaetemplateDO........................................................................ 41

20 Table37–Zonalqualitydata.................................................................................................. 42

21

22

23

24

25

26 Acknowledgements 

27 Theauthorsaregratefultothefollowingcontributors,andotheranonymousindividuals,withoutwhoseinput

28 thisdocumentwouldnothavebeenconcluded.

29 A

30 B...

NIST GrotherandSalamon Page6of48

 






 
 






 






 
 





NISTMIN XMatch on card valuation–ConceptandAPI.

1 1. Overview 

2 TheMIN Xprogramisintendedtoimprovetemplate
basedinteroperabilityfromthestatereportedinMIN X

3 041

andMTIT2towardthatachievablewithimage
basedimplementations.Theapproachistoconductseveral

4 trials,MIN XII,III,IVetc,eachofwhichwillembeddevelopment,evaluation,targetedfeedbackand

5 consultationactivitiesbetweenNIST,industryandotherinterestedparties.Withinscopeisanythingtodo

6 withfingerprintminutiaeasaninteroperablebiometricforidentitymanagement.Typicaloutcomeswillbe

7 measurementsofaccuracy,processingtime,templatesize,andproposalstorevisetherelevantstandards,

8 studiesofutilityofqualitymeasures,calibrationinformation,andnewmetrics.

9 Table1givesanoverviewofthevariousMIN XactivitiesatNIST,andacontextforfuturework,startingwith

10 MIN XII.

11 Table 1 – Family of MINEX evaluations 

MIN XI

(MIN X041

)

Thistestwasconductedasaninitialcomparisonofimagevs.minutia basedinteroperability.It

assessedthecorealgorithmicabilityoffingerprintmatcherZtocompareminutiaetemplates

fromsourcesXandY.Itcomparedthatcasewithfullyproprietarytemplatesonthesamesets

ofarchivaldata.ThetestadoptedtheINCITS378templateasabasestandard.

Thetestisnowclosed.http://fingeprint.nist.gov/minex04

Ongoing

MIN X3

OngoingMIN Xisacontinuingprogramofinteroperabilityassessmentintendedtomeasure

conformanceandinteroperabilityofINCITS378:2004samples.Thetestusesoneexpanded

partitionoftheMIN X04datatoformulateinteroperablegroupsofmatchersandtemplate

generators.OneclientofOngoingMIN XistheUSGovernment'sPIVprogramwhichhasitsown

setofcriteriaagainstwhichtheinteroperablegroupisformed.

Thetestresultsareavailabletootherapplicationsorprogramswhichmayelecttosettheir

owncriteriaforinteroperableperformance.

Thetestremainsopen.

MIN XII

MIN XIIwillconsiderMatch on CardcapabilitiesusingISO/I C19794 2compactcard

templates.ThesewillbeproducedfromparentINCITS378:2004records.

Inaddition,becauseNISTconsidersthecompact cardtemplatesmallenoughtoberapidlyread

fromacard,thestudymaybeusefulfororganizationsconsideringMatch off Cardapplications.

Thetestdesigniscomplete ThisdocumentisintendedtobethedefinitiveMIN XIItestplan.

 rratawillbepostedonhttp://fingerprint.nist.gov/minexII

MIN XIII

Afutureprogram,tobeannouncedinthesummer2007,willreturntotheissueofcoreminutia

interoperability.Thescopeisyettobefinalized,butitislikelytofocusondevelopmentand

exploitationoftheminutiaqualityvalue.

12 2. Scope 

13 MIN XIIisintendedtomeasurethecorealgorithmiccapabilitiesoffingerprintmatchingalgorithmsrunning

14 onstandardizedISO/I C7816smartcards.Specificallythetestwill

15 ― instantiateamechanismforMOCtesting,

16 ― measuretheaccuracyofmatch on card(MOC)implementationsusingISO/I C19794 2:2005compactcard

17 minutiaetemplates,

18 ― timethevariousoperations,

19 ― testtheviabilityofINCITS378toISO/I C19794 2compactcardtranscoding,



1

MinutiaeInteroperability xchangeTest,MIN X,NISTInteragencyReport7296,March21,2006. 2

MinutiaeTemplateInteroperabilityTesting,http://www.mtitproject.com 3

SeetheOngoingMIN XHomepageathttp://fingerprint.nist.gov/minex

NIST GrotherandSalamon Page7of48

 












 












 














NISTMIN XMatch on card valuation–ConceptandAPI.

1 ― formulatecommentstowardpossiblerevisionoftherelevantstandards,and

2 ― testconformancetotheINCITS378:2004recordformat,asprofiledherein.

3 Theprimaryoutputsofthetestwillbestatementsofperformanceusingthefollowingmetrics.

4 ― Falsenon matchandfalsematcherrorrates,

5 ― Off cardtemplategenerationtimes,

6 ― On cardmatchingtimes.

7 Insodoing,thisevaluation

8 ― requiresproductionofINCITS378:2004templates,and

9 ― usesNIST'sopen sourcetranscodertoconvertINCITS378:2004templatestoISO/I C19794 2compact

10 cardformatformatching,

11 Notinthescopeofthisevaluation,butthesubjectofaseparateactivity4

atNISTis:

12 ― securingthecommunicationschannel,includingcryptographicprotectionofthebiometrictemplates;

13 ― templateintegrityprotectionusingdigitalsignatures;

14 ― authenticationofthecardtothereader;

15 ― contactlesscommunications;

16 Thefollowingarespecificallynotwithinthecurrentscopeofthisevaluation:

17 ― TheISO/I C19794 2"record"and"cardnormal"templates,

18 ― Ridgecount,coreanddelta,andzonalqualityextensions,

19 ― Non standardextensionstoanystandardizedminutiaformat,

20 ― valuationofreaders,includingperformance,conformanceandinteroperability,

21 ― valuationofruggednessordurabilityofthecard,

22 ― On cardtemplategeneration(i.e.extractionofminutiaefromimages),

23 ― Templateupdateoradaptation,

24 ― AlthoughthetestwilluseISO/I C7816parts4and11,andconformancetothissubsetwillbea

25 requirement,thisstudydoesnotconstituteaformaltestofconformancetoanypartofISO/I C7816,and

26 ― DevicesnotconformingtoISO/I C7816,includingallsense on carddevicesthatembedproprietary

27 templateformats.

28 3. Normative References 

29 Thefollowingreferenceddocumentsareindispensablefortheapplicationofthisdocument.Fordated

30 references,onlytheeditioncitedapplies.Forundatedreferences,thelatesteditionofthereferenced

31 document(includinganyamendments)applies.

32 ― INCITS378:2004—AmericanNationalStandardforInformationTechnology—FingerMinutiaeFormatfor

33 DataInterchange

34 ― ISO/I C7816 4:2005—Identificationcards—Integratedcircuitcards—Part4:Organization,securityand

35 commandsforinterchange

36 ― ISO/I C7816 6:2005—Identificationcards—Integratedcircuitcards—Part6:Interindustrydata

37 elementsforinterchange

38 ― ISO/I C7816 11:2004—Identificationcards—Integratedcircuitcards—Part11:Personalverification

39 throughbiometricmethods



4

Seedocumentslinkedfromhere:http://csrc.nist.gov/piv program/

NIST GrotherandSalamon Page8of48

 









 
 






 
 





 




 




 

















 


NISTMIN XMatch on card valuation–ConceptandAPI.

1 ― ISO/I C19794 2:2005—Informationtechnology—Biometricdatainterchangeformats—Part2:Finger

2 minutiaedata

3 ― ISO/I C19794 2:2005/Cor.1:2007—Informationtechnology—Biometricdatainterchangeformats—Part

4 2:Fingerminutiaedata–TechnicalCorrigendum1(firstdraft,JTC001 SC37 N 2119,circulatedMay2007)

5 ― ISO/I C19785 3:2005—Commonbiometricexchangeformatsframework—Part3:Patronformat

6 specifications(FDISdraft,JTC001 SC37 N 2163,circulatedJune6,2007)

7 ― ISO/I CFCD19795 4—BiometricPerformanceTestingandReporting—Part4:Interoperability

8 PerformanceTesting.

9 4. Caution 

10 4.1. Relationship between MINEX II and other issues 

11 Neitherthisdocument,noranyfutureexecutionofMIN XorMOCevaluationsbyNIST,shouldbeconstruedas

12 anindicationthatNIST,noranyotheragencyoftheUnitedStatesgovernment,hasdecidedfororagainstthe

13 inclusionorexclusionoftheitemslistedbelowinanycurrentorfuturegovernmentspecificationorprogram.

14 ― Contactlessbiometricinterfaces,

15 ― MOCimplementations,

16 ― ISO/I C19794 2formats,and

17 ― Definitiveformatsforstandardizedtemplatestobestoredon,ortransmittedto,cards.

18 Thisdocumentisstrictlyaspecialnoticethatisbeingpublishedtoreachawideraudience.Itisnotafederal

19 procurementaction,andnoRFQorRFPisavailable.

20 Inaddition,theidentificationofanycommercialproductortradenamedoesnotimplyendorsementor

21 recommendationbytheNationalInstituteofStandardsandTechnology.

22 4.2. Relationship between MINEX II and Ongoing MINEX 

23 MIN XIIwillusesamplesdrawnfromthesamepopulationasisusedintheOngoingMIN Xprocess.MIN XII

24 willbeconductedintwophases.Forreasonsoftimeliness,PhaseIislikelytoconsideronlyasubsetofthose

25 images,andwillonlyexaminenativeorlimitedcross vendortemplateinteroperability.PhaseIIwillextend

26 theoperationtowardfullinteroperabilitytesting,includingthekindexaminedinOngoingMIN X.PhaseII

27 mayalsoemployanexpandedsetofimagesorcomparisoncounts.

28 5. Abbreviations 

29 TheabbreviationsandacronymsofTable2areusedinmanypartsofthisdocument.

30 Table 2 – Abbreviations 

APDU ApplicationProtocolDataUnitasusedinISO/I C7816 4

BIT BiometricInformationTemplateasdefinedinISO/I C7816 11

D T Detectionerrortradeoffcharacteristic–aplotofFNMRvs.FMR(sometimesasnormal

deviates,sometimesonlog scales)

FMR Falsematchrate

FNMR Falsenon matchrate

IDMS Identitymanagementsystem

INCITS InterNationalCommitteeonInformationTechnologyStandards

ISO/I C7816 Multipartstandardfor"Identificationcards Integratedcircuit(s)cardswithcontacts"

ISO/I C19794 Multipartstandardof"Biometricdatainterchangeformats"

I378 INCITS378:2004asprofiledinthisstandard

ISO CC Thecompactcardminutiaformatofclause8inISO/I C19794 2:2005

MIN X GenericnamefortheseriesofNIST'sMinutiaInteroperability xchangeTests

MOC Matchoncard

NIST GrotherandSalamon Page9of48

 


 

 


 



 








 










 








 


NISTMIN XMatch on card valuation–ConceptandAPI.

MXC Matchoffcard

NIST NationalInstituteofStandardsandTechnology

PC/SC GenericinterfacespecificationforPCtosmartcardconnectivity

SC17 Subcommittee37ofJointTechnicalCommittee1–developerofsmartcardstandards

SC37 Subcommittee37ofJointTechnicalCommittee1–developerofbiometricstandards

SDK ThetermSoftwareDevelopmentKitreferstoanylibrarysoftwaresubmittedtoNIST

1 6. Aspects of the test 

2 6.1. Match-on-card vs. match-off-card 

3 TheMIN XIItestisspecificallyaimedattestingtheefficacyofmatch on card(MOC)implementationsthat

4 compareinstancesofISO/I C19794 2:2005compactcard(ISO CC)templates.Thus,oneuseofMIN XII

5 wouldbetoconfirmthatperformanceachievedbyaMOCsubmissiontoOngoingMIN X(anoff cardprocess)

6 isactuallyachievableonatleastoneISO/I C7816card.

7 TheMIN XIIstudyisinitiatedinresponsetonear termimperativestoevaluatethetechnology.

8 Thetestislikelytorequiresomewhatcustomizedcards(i.e.notproductioncards),atleastbecauseofthe

9 requirementtobeabletoreadsimilarityscoresfromthecard.

10 6.2. Fundamental concept of the test 

11 TheMOCcapabilityshallbetestedinthreestages:

12 ― Instage1,NISTwillmeasuretheaccuracyofthematchingalgorithmexecutingonaPCclassmachine.

13 ThetestrequiressubmissionofaPentium classimplementationofthesameMOCalgorithm5

.Thisstage

14 islikelytoembedhundredsofthousandsofgenuineandimpostorcomparisonstosupporttheaccuracy

15 measurementgoalsoftheMIN Xtests.

16 ― Instage2,NISTwillrepeatasmallsubsetofthestage1templatecomparisonsonthecard.Selected

17 genuineandimpostorcomparisonswillberepeatedonthecardbysuccessivelystoringreference

18 templatesonthecardandsendingverificationtemplatestothecardforcomparison.

19 ― Instage3,NISTwillcomparesimilarityscoresretrievedfromthecardinstage1withthosegeneratedin

20 stage3.Foranygivenpairofreferenceandverificationtemplates,theymustbeidentical.

21 Thisthree stagestrategyassuresNISTthattheaccuracyoftheMOCimplementationisidenticaltothatofthe

22 PC basedversionofthealgorithm,andthatthecarditselfistrulycapableofrunningatthemeasured

23 accuracy.

24 6.3. Generic interface hardware and software 

25 NISTintendstoaccessallcardsviathirdpartyPC/SChardwareownedbyNIST.NISTwillusetheSCRSCM3356

26 reader7

,andtheM.U.S.C.L. open sourcedrivers8underLinux.

27 NISTdoesnotcurrentlyintendtouseothercardreaders,butreservestherighttodosoforanypurpose.

28 Asinprevioustests,NISTintendstorunthePC basedportionsofthetestusingsoftwarecomponents

29 implementingasimple"C"API.



5

WhileNISTunderstandsthatthePC basedmatchersubmissionmayneedtouseonlyfixed pointarithmetic,orrun

underneathanemulator,wedonotaddressmeansofassuringequivalenceofonandoffcardimplementations.

6

Specifichardwareandsoftwareproductsidentifiedinthisplanwillusedinordertoperformtheevaluationsdescribed

inthisdocument.Innocasedoesidentificationofanycommercialproduct,tradename,orvendor,imply

recommendationorendorsementbytheNationalInstituteofStandardsandTechnology,nordoesitimplythatthe

productsandequipmentidentifiedarenecessarilythebestavailableforthepurpose.

7

Thereaderisdocumentedathttp://www.scmmicro.com/security/view_product_en.php?PID=11. 8

Seedriversoftwarehomepageishttp://www.linuxnet.com/middle.html

NIST GrotherandSalamon Page10of48

 


 





 
 









 
 




















 










 

NISTMIN XMatch on card valuation–ConceptandAPI.

1 6.4. INCITS 378:2004 vs. ISO/IEC 19794-2:2005 Compact Card 

2 InMIN XII,NISTrequiressubmittedtemplategeneratorstoproduceINCITS378:2004templates,asprofiledin

3 section7.2ofthisdocument.NISTwillconvertsuchtemplatestoISO/I C19794 2:2005compactcard

4 instancesbeforepassingthemtoPC basedandcard basedmatchingalgorithms.Conversionwillbedoneon

5 the flyandwillbeparameterizedpertheBIT(s)readfromthetargetsmartcard.

6 NISTisnotrequiringproductionofISO CCtemplatesbecausethefollowingpointshold.

7 ― Three byteISO CCminutiapointsarestrict"semanticchildren"ofsix byteINCITS378:2004orISO/I C

8 19794 2:2005recordformatminutiapoints.

9 ― TheprocessofconversionofINCITS378:2004toISO CCistrivialandmostlystandardized,andthatthere

10 isnoadditionalintellectualpropertyneededtocomputeanISO CCtemplatevs.anI378template.

11 ― MinutiaqualityvaluesarerequiredentriesinINCITS378:2004minutiaerecords.

12 ― MinutiaqualityvaluesarerequiredwhenpreparingISO CCtemplatesforMOC.

13 ― ThequalityfieldofI378isconsideredanessentialmechanismforimprovingminutia based

14 interoperabilityfromthestatemeasuredinMIN XandMTIT.

15 ― ISO CCtemplatescanexistonlyasterminalobjects,i.e.theycannotbeusedinthepreparationofother

16 standardizedminutiarecords.

17 Withregardtoissuesofminutiaselectionandplacement,NISTdrawstheattentionoftemplategenerator

18 developerstotheGermannationalbodycontribution,N2135,submittedtoSC37WorkingGroup3onMay29,

19 2007.

20 6.5. BIT Processing 

21 NISTwillreadoneortwoISO/I C7816 11BITsfromeachsubmittedcardasagroup(seethecardAPDUin

22 section8.6).TheseparameterizetheconversionofI378templatestoISO CCtemplatesbeforetheyaresent

23 to

24 ― cardbasedMOCmatcherimplementations,and

25 ― PC basedMOCmatchimplementations.

26 6.6. Card-matcher combinations 

27 TheprimaryobjectiveofMIN XIIistoascertainMOCcapabilitybymeasuringfingerprintalgorithmaccuracy

28 intheintendedenvironment(i.e.thecard).NISTconsidersthatcardvendorsmayelecttoteamwithseveral

29 fingerprintalgorithmvendors,andviceversa.NISTfurtherexpectsthatafingerprintsupplier'stechnology

30 maydemonstrateimprovedaccuracywhenimplementedonamorecapablecard.

31 NISTseekstoidentifythemostcapablecomponentsandcombinationsofcomponentsandthereforethe

32 participationagreement,AnnexH,requiresidentificationofallcardandfingerprinttechnologysuppliers,

33 withresponsiblesignatoriesfromallcollaboratingorganizations.

34 6.7. Two phase testing 

35 NISTislikelytoconductthetestintwophases.Thefirstisintendedtobeasmallerandfasterevaluationof

36 submittedsoftwareandcardsthat

37 ― willuseareducednumberofimages,

38 ― oronlyasubsetofallinteroperabilityparadigms(seesection6.9),

39 ― willgivefeedbackandresultstothesuppliers,and

40 ― isnotintendedtoincludereleaseofresultstothesponsorsorthepublic.

41 ― Suppliersshouldsubmitnewsoftwareandhardwareforthesecondphase.Thesecondphasewillinclude

42 thefullsizetestandwillresultinafinalpublicreport.

NIST GrotherandSalamon Page11of48

 


 


 
 
 


 


 
 















 


 

NISTMIN XMatch on card valuation–ConceptandAPI.

1 NISTisparticularlyinterestedinfacilitatingimprovedperformancebetweenPhase1andPhase2.Itintends

2 toprovidefeedbacktosuppliersandtoallowsubmissionofimprovedsoftwareandhardware.NISTremains

3 opentocommentonwhatfeedback(metrics,data,orcalibrationinformation)wouldbemostuseful.

4 6.8. Options for participation 

5 Forphase1,participantsshallprovidethecomponentsidentifiedinoneormorerowsofTable3.All

6 componentsinarowshallbesupplied.Uptofoursubmissions(e.g.3ClassA+1ClassB)arepermittedto

7 allow

8 ― cardsupplierstoteamwithseveralsuppliersoffingerprinttemplategenerators,andviceversa,and

9 ― supplierstosubmit,say,fast but inaccurateandslow but accurateversions.

10 Table 3 – MINEX II classes of participation 

Classof

Participation

AnnexH

Participation

agreement

ISO/I C7816

Card+Matcher

PC basedISO

CCTemplate

Matcher

PC basedINCITS

378:2004

Template

Generator

ClassA + + +

ClassB + + + +

11 TheseclassesofparticipationmayberevisedforPhaseII.

12 6.9. Three-way interoperability 

13 NISTanticipatesthatsomecardsembedfingerprintmatchersthatarenotaccompaniedbyanassociated

14 templategenerator(i.e.ClassA),andmaywellbeusedwithenrollmentandverificationtemplatescoming

15 fromtwodifferentsources.Thatiscard basedmatcher,M,willcompareareferencetemplateproducedby

16 XwithaverificationtemplatefromY.NISTintendstoevaluatethree wayinteroperabilityinPhase2ofthis

17 test,butmayinadditiondosoinPhase1.ThepossibleimplicationsforaccuracyarediscussedinAnnexB.

18 BothClassAandClassBsubmissionsmaybetestedinallcombinationsofM,XandY.

19 6.10. Metrics 

20 NISTintendstoreportfulldetectionerrortradeoff(D T)characteristicsforallimplementationstested.The

21 D Tisprimarymechanismfortransferringtheaccuracyresultsofevaluationsintothetechnologypolicy

22 arena(e.g.inordertoestablishsecurityrequirements).

23 Inaddition,inthefull sizePhase2trial,NISTintendstoreportperformanceinteroperabilitymatrices9

.Such

24 tableswillreportfalsenon matchratesatfixedfalsematchratesof0.0001astheprimaryfigureofmerit.

25 NISTmayreportothermetricsalso.

26 NISTwillmeasureandreportestimatesoftheelapsedtimesofatleastthe

27 ― templategenerationprocess,

28 ― on cardandoff cardtemplatecomparisons,and

29 ― thestorageofthereferencetemplateonthecard.

30 6.11. Participation 

31 Prospectiveparticipantsshouldreadthisdocumentthencompletetheapplicationform,AnnexH.



9

LikeTable8ofNISTInteragencyReport7296Performance and Interoperability of the INCITS 378 Template.

NIST GrotherandSalamon Page12of48

 


 




 

 

 


 



 


NISTMIN XMatch on card valuation–ConceptandAPI.

1 7. Profile of MINEX II templates 

2 7.1. Overview 

3 AlltemplategeneratorssubmittedundertheMIN XIIprogramshallproduceanINCITS378:2004template,as

4 definedinsection7.2.Thisisspecifiedbecauseavalidminutiaqualityisrequiredinthepreparationofthe

5 section7.3ISO CCtemplatessenttothematchers.

6 7.2. INCITS 378:2004 profile 

7 7.2.1. Record structure 

8 TemplategeneratorsshallproducerecordsconformanttoTable4.ThisisidenticaltotheOngoingMIN X

9 profile10exceptthat

10 ― theminutiaqualityfieldshallbemeaningfullypopulated11,

11 ― theIBIAvendorcodefieldshallbepopulated,

12 ― theversionnumberIDsshallbepopulated.

13 Table 4 – MINEX II profile of INCITS 378:2004 standard 

Sectiontitleand/orfieldname

(I378clausenumbersinparentheses)

ValuesAllowed InformativeRemarks

1. FormatIdentifier(6.4.1) 0x464D5200 i.e.ASCII"FMR\0"

2. VersionNumber(6.4.2) 0x20323000 i.e.ASCII"20\0".

3. RecordLength(6.4.3) 32≤L≤800 26recordheader+4viewheader+2

extendeddatalength+6K.MaxKis128

4. CB FFProductIdentifierOwner(6.4.4) >0 Twobyte,IBIAregistered,vendorID.

5. CB FFProductIdentifierType(6.4.4) >0 Twobyte,vendorassigned,versionnumber.

6. Capture quipmentCompliance(6.4.5) 0

7. Capture quipmentID(6.4.6) 0

8. SizeofScannedImageinxdirection(6.4.7) MIT Inheriteddirectlyfrominputdata

9. SizeofScannedImageinydirection(6.4.8) MIT

10. X(horizontal)resolution(6.4.9) 197

11. Y(vertical)resolution(6.4.10) 197

12. NumberofFingerViews(6.4.11) 1

13. ReservedByte(6.4.12) 0

14. FingerPosition(6.5.1.1) MIT Inheriteddirectlyfrominputdata(see9.4.2)

15. ViewNumber(6.5.1.2) 0

16. ImpressionType(6.5.1.3) 0or2 Inheriteddirectlyfrominputdata

17. FingerQuality(6.5.1.4) MIT Inheriteddirectlyfrominputdata

18. NumberofMinutiae(6.5.1.5) 0≤K≤128 Kminutiaedatablocks

19. MinutiaeType(6.5.2.1) 01b,10b,or00b

20. MinutiaePosition(6.5.2.2) MIT

21. MinutiaeAngle(6.5.2.3) MIT

22. MinutiaeQuality(6.5.2.4) 0,1≤Q≤100 0=unsupported

23. xtendedDataBlockLength(6.6.1.1) 0 Nobytesshallfollowthisfield.

MIT=mandatoryattimeofinstantiation



10TheOngoingMIN XprofileisthatgiveninTable11ofNISTSpecialPublication800 76 1. 11TheoperationalPIVprofilegivenTable3ofNISTSpecialPublication800 76 1requirestheminutiaqualityfieldtobe

suppliedperI378.Howeverallexistingminutiastandardsgivespoorguidanceonwhatqualitymeans.

NIST GrotherandSalamon Page13of48

 


 







 

 


 






 











 

 

NISTMIN XMatch on card valuation–ConceptandAPI.

1 7.2.2. Minutia quality values 

2 Theuseofaminutiaqualityvalueisnormativelyrequiredbyclause8.3.1ofISO/I C19794 2:2005forthe

3 preparationofISO CCtemplates,asdescribedlaterinsection10.4.3.

4 ForMIN XII,thetemplategeneratorshallgeneratequalityvaluesthatareindicativethataminutiaisatrue

5 minutia.Thatis,largervaluesshallindicatedecreasedlikelihoodthattheminutiaisafalseminutia.This

6 requirementisspecificallydistinctfromoneinwhichthequalityvaluewouldbeindicativeof,forexample,

7 thelocalnoiseintheoriginalimage.

8 MIN XIIIwillbeacooperativeprojecttodevelopminutiaqualityimplementations.

9 7.2.3. ID values 

10 TheIDvalueswillbeusedforinternalNISTlogging.Theversionnumbersshouldbedistinctbetweenany

11 versionswhichofferdifferentalgorithmicallyfunctionality.

12 7.3. ISO/IEC 19794-2:2005 compact card structure 

13 ThissectiondefinespreciselywhatconstitutesthedatatobesenttoPC basedandcard basedMOC

14 implementations.ItisincludedherebecauseISO/I C19794 2:2005anditsdraftcorrigendaandrevisions

15 definemultipletemplatescombining

16 ― threeencodings(record,card normal,card compact),

17 ― versionswithandwithoutheaders12,

18 ― variantsdifferingintheirminutiaplacementsemantics,

19 ― presenceofstandardizedextendeddata(zonalqualityetc),and

20 ― presenceofnon standard,proprietary,extendeddata.

21 TheMIN XIIevaluationwilluseISO CCtemplatesforwhich

22 ― therecordandviewheadersshallbeabsent,

23 ― standardizedextendeddatashallbeabsent,and

24 ― proprietaryextendeddatashallbeabsent.

25 NISTwillconverttheI378instancesofTable4toproduceTable5instancesofISO CC.Thisprocessis

26 describedinsection10.

27 Table 5 – MINEX II profile of ISO/IEC 19794-2:2005 standard 

1. Xcoordinate 8 [0,255] xpressedinunitsof0.1mm Viewdata

Sinstancesofthe

minutiaedataon

lines17
20shallbe

present

2. Ycoordinate 8 [0,255] xpressedinunitsof0.1mm

3. Minutiaetype 2

4. Minutiaeangle 6 [0,63] Resolutionis5.625degrees

28 MOCimplementationsshallaccepttemplatesintheTLVformatofTable6.

29 Table 6 – ISO/IEC 19794-2 minutiae template DO 

Tag L Value

‘7F2 ’ L1 Biometricdatatemplate

Tag L Value

‘81’ L2 Fingerminutiaedata

Field Size(bits) ValidValues

Xcoordinate 8 [0,255]



WorkingGroup3ofSC37discussedthisissueinitsJanuary2007meetinginNewZealand.

NIST GrotherandSalamon Page14of48

12

 


 







 

 




 


 
 



 



 


 

 

NISTMIN XMatch on card valuation–ConceptandAPI.

Ycoordinate 8 [0,255]

Minutiaetype 2

Minutiaeangle 6 [0,63]

S

instances

1 7.4. Non-presence of a header 

2 NISThasabandonedplanstorequiretheminutiaedatatobeprecededbyafourbyteviewheader.These

3 planswereadvancedinversionsofthisdocumentcirculatedbeforeMay262007.However,seealsosection

4 F.3foracommentregardingstandardization.

5 7.5. Minutia uniqueness 

6 Anon ISOrequirementisfortheminutiapointstobeunique.TemplategeneratorssubmittedinMIN XII

7 shalloutputunique(x,y,andtheta)tuplesandNISTwillimplementcheckstodetectdeviationsfromsuch

8 behavior.Thisrequirementisinstitutedbecausenon uniquenessimpedessomematchingalgorithms.

9 7.6. Failure to acquire 

10 TemplategeneratorsinMIN XevaluationsmustalwaysproduceaTable4template,evenifnominutiaeare

11 found.Suchatemplatewillhavelength26bytes,andthevalueinthe"numberofminutiae"fieldshallbe0.

12 NISTconsidersthisavalidtemplate.Itisusefulforcorrectaccountingoftemplategeneratorfailure(see

13 MIN XNISTIR7296 http://fingerprint.nist.gov/minex04/minex_report.pdfsection5.3).

14 8. MOC interface specification 

15 8.1. Overview 

16 Thefollowingsubsectionsdefinethemechanismbywhichallcardsshallbeaccessedforthistest.This

17 includesselectionoftheapplication,readinganduseoftheBiometricInformationTemplate(BIT),

18 installationofareferencetemplate,verification,recoveryofsimilarityscores,andretrievalofidentifiers.

19 Thetemplategenerationfunction,includinguseoftheBIT(s),shallbeconductedonPC classcomputers.

20 8.2. Approach to the use of ISO/IEC 7816 

21 ThefollowingsubsectionsdetailtheMIN XIIMOCinterface.Itwasdesignedwiththefollowingcriteriain

22 mind.

23 ― AdherencetotheprovisionsofISO/I C7816 4:2005,7816 11:2004and19794 2:2005.

24 ― WhenthebasestandardsprovideforoptionalcontentthisspecificationfollowsNISTSpecialPublication

25 800 73 1InterfacesforPersonalIdentityVerification.

26 ― Toonlydefinenewelementswhenextantstandardsaresilentonanecessaryfunctionality.

27 TheimpactofthesecondprovisionistoselectoddbyteINSvalues.

28 8.3. Establish Communications 

29 AnAnswer to Resetshallbeperformedtodetermine(T=0,T=1orT=CL).

30 8.4. Selection of the test application 

31 ThiscardshallbesuppliedwithadedicatedNISTMOCtestingapplication.Itshallbeinvokedoncebyusing

32 theS L CTcommandinTable7.TheresponseshallbeasinTable8.

33 Table 7 – Command APDU for selection of MOC application 

Command

Parameter

RequiredValue Meaning

CLA ‘00’

NIST GrotherandSalamon Page15of48

 





 


 








 


 





NISTMIN XMatch on card valuation–ConceptandAPI.

INS

P1 P2

‘A4’

‘040C’

S L CT

AIDfollows,1100b

Lcfield 16 LengthofAID

Datafield 'F04 495354204D4F4320545354205031' AID

InASCII,"≡NISTMOCTSTP1"

whereP1connotesPhase1

Lefield Absent

1

2 Table 8 – Response APDU from selection of MOC application 

ResponseParameter Meaning

Datafield mpty

SW1 SW2 SeeISO/I C7816 4:2005

3 8.5. Store enrollment template on the card 

4 TheAPDUforreplacingthetemplateonthecardisshowninTable9.ItusesthePUTDATAinstructionto

5 overwritetheexistingreferencetemplate.

6 Table 9 – Command APDU for storage of reference template 

Command

Parameter

RequiredValue Meaning

CLA

INS

P1 P2

‘00’

‘DB’

'3FFF'

PUTDATA

StoreanywhereinthecurrentDedicatedFile(ApplicationDF)

Lcfield Lengthofcommanddatafield

Datafield Table6 DataObjectinB R TLVformattobestored(tag'7F2 ')

Lefield mpty

7

8 Table 10 – Response APDU from storage of reference template 

ResponseParameter Meaning

Datafield mpty

SW1 SW2 SeeISO/I C7816 4:2005

9 Notethatfingerpositiondataisnotincluded,becausenostandardregulatesitstransmission.Inanycase,

10 NISTwillonlyconductcomparisonsofsame
fingertemplates.NISTwillnotwrite,norrequiresupportfor

11 writing,newBIT(s)toreflectanychangesinthefingerpositionvalue.

12 NISTconsidersthatthelackofastandardhereimpedesatleasttesting,andprobablyoperationalissuance

13 systems
seeAnnexF.

14 8.6. NIST read of the BIT 

15 NISTwillusethecommandofTable11toretrievetheBITgrouptemplateofTable13pertheresponseof

16 Table12.

17 Table 11 – Command APDU for retrieval of biometric information template 

Command

Parameter

Required

Value

Meaning

CLA

INS

P1 P2

‘00’

‘CB’

'3FFF'

G TDATA

RetrievefromanywhereinthecurrentDedicatedFile(ApplicationDF)

Lcfield '04'

Datafield '5C'

'02'

'7F61' DataObjectidentifiertoberetrieved(groupofBIT)

NIST GrotherandSalamon Page16of48

 


 


 






























 



 
 


NISTMIN XMatch on card valuation–ConceptandAPI.

Lefield ‘00’

1 Table 12 – Response APDU from retrieval of biometric information template 

ResponseParameter Meaning

Datafield BiometricInformationTemplate(seeTable13)

SW1 SW2 SeeISO/I C7816 4:2005

2 Table13containstwoBITs13.NISTshallapplythefirstBITtoenrollmenttemplates.NISTshallapplythe

3 secondBITtotheverificationtemplates.Ifonlyonebitispresent,NISTshallapplyittoboththeenrollment

4 andverificationtemplates.WhetherthereareoneortwoBITs,theyshallbegroupedtogetherasaBITgroup

5 template.NISTwillreadthegroupoftwoBITsfromeachsubmittedcard,andstoreit.NISTislikelyto

6 conductthisreadoperationonlyonce,butwillusetheBITstoparameterizealltemplateconversion

7 operationspriortosendingtemplatestothecardortothePC
basedsoftwarematcher.

8 AllinstancesofasubmittedcardmusthavethesameBITgroup.TheBIT(s)shallcontainthedataas

9 describedinTable13.TheBIT(s)mayalsocontainotherinformation(e.g.asallowedbythestandards),

10 whichNISTshallignore.

11 Table 13 - ISO/IEC 19794-2 Biometric Information Template 

Tag Len. Value NIST

‘7F61’ Var. BITgrouptemplate Requirements

Tag Len. Value

'02' 1 NumberofBITsinthegroup 2

‘7F60’ Var. BiometricInformationTemplate(BIT) Forenrollment

Tag Len. Value

‘A1’ Var. BiometricHeaderTemplate(BHT)conformingtoISO/I C

19785 3:2005

Tag Len. Value

'81' 1 08biometrictype(08=fingerprint)

'82' 1 XXbiometricsubtype(fingerposition)

Thesevaluesshallbefrom7816 11table(and

19785)andNOTfrom19794 2

SeeNOT 1below

‘87’ 2 CB FFBDBformatowner 0101i.e.

JTC1/SC37

‘88’ 2 CB FFBDBformattype 0005seesec.

8.6.1

'B1' Var. Biometricmatchingalgorithmparameters

ISO/I C19794 2Table14

Tag Len. Value

'81' 2 Min.andmax.numbersof

minutiae,seeISO/I C19794 2

(subclause8.3.3,Table10)

Seesec.0

'82' 1 Minutiaeorder,seeISO/I C19794

2(subclause8.3.4andTables11

and12)14

Native,seesec.

10.5

'83' 1 Featurehandlingindicator,see

ISO/I C19794 2(Table15)

SeeNOT 2below

andsec.10.6

‘7F60’ Var. BiometricInformationTemplate(BIT) Forverification



13InaccordancewiththesuggestioninAnnexDofISO/I C19794 2:2005,NISTseekstosupportasymmetricenrollment

andverificationtemplates.Thisallows,forexample,highermaximumnumbersofminutiaeinthereferencetemplate

thanintheverificationtemplate.However,NISTwillnotpasstheseparameterstothetemplategeneratorsothePC

basedAPIstillonlycontainsagenericcreate_template()functioncallwhichdoesnotdifferentiatebetweenenrollment

andverification(seesec.9.4.2).Instead,thiswilloccurduringapre matchpost processingofthetemplate. 14ThetextinthislineisacorrectedversionofthatinISO/I C19794 2:2005Table14second to lastlinewhichshould

referencesubclause"8.3.4"not"8.33".

NIST GrotherandSalamon Page17of48

 























 










 





 


NISTMIN XMatch on card valuation–ConceptandAPI.

Tag Len. Value

‘A1’ Var. BiometricHeaderTemplate(BHT)

Tag Len. Value

'81' 1 08biometrictype(08=fingerprint)

'82' 1 XXbiometricsubtype(fingerposition)

Thesevaluesshallbefrom7816 11table(and

19785)andNOTfrom19794 2

SeeNOT 1below

‘87’ 2 CB FFBDBformatowner 0101i.e.

JTC1/SC37

‘88’ 2 CB FFBDBformattype 0005seesec.

8.6.1

'B1' Var. Biometricmatchingalgorithmparameters

ISO/I C19794 2Table14

Tag Len. Value

'81' 2 Min.andmax.numbersof

minutiae,seeISO/I C19794 2

(subclause8.3.3,Table10)

Seesec.0

'82' 1 Minutiaeorder,seeISO/I C19794

2(subclause8.3.4andTables11

and12)

Native,seesec.

10.5

'83' 1 Featurehandlingindicator,see

ISO/I C19794 2(Table15)

SeeNOT 2below

andsec.10.6

1 NOT 1 NISTdoesnotintendtopassfingerpositioninformationtothecard.Therefore,NISTcannot

2 expectcorrectdatainthe'82'tag.NISTrequiresthetagtobepresent,perISO/I C19785 3:2007,butwill

3 nottestitsvalue.NISTwillneverupdatetheBIT,forexamplewhenthereferencedataischanged.

4 NOT 2 Thetag'83'isoptional.Ifpresent,thevalueshallbe00000000b.Itisincludedinthetable

5 above,toformallyindicatethatextendeddataisoutofscopeofthistest.

6 8.6.1. Variants of the ISO/IEC 19794-2 standard 

7 Clause9oftheISO/I C19794 2:2005standardgivesthe"formattype"codesforsixvariantswhichdifferin

8 theencoding(asinTable26)andplacementrequirementsonminutiae.Placementvariation,suchas

9 whetheraridgeendingisencodedastheridgeskeletonend pointorasthevalleybifurcation,remainsan

10 openissueinminutiaeinteroperability.Forthecurrenttest,NISTwillmaintainitsMIN Xrequirementofthe

11 latterdefinition.Thus,

12 ― cardsmustreturnavalueof0005forthe"formattype"intheBITtag'88',and

13 ― encodersshouldfollowtheISO/I C19794 2:2005clause6guidanceonplacement.

14 8.7. Verification 

15 8.7.1. APDU specifications 

16 TheverificationdataissentusingtheV RIFYcommandofTable14.

17 Table 14 – Command APDU for comparison of biometric templates 

CommandParameter Meaning

CLA

INS

P1 P2

‘00’

‘21’=V RIFY

‘0000’

Lcfield Lengthofcommanddatafield

Datafield ValueFieldofthetemplate,identicaltoTable6.

Lefield absent

18 TheoddINSvalueallowstheuseofP1 P2parameterswithavalueof00 00astheindicationofwhatistobe

19 verifiedisgivenbythetagofthedataobjectpresentedinthedatafieldofthecommand.

NIST GrotherandSalamon Page18of48

 


 










 








 


NISTMIN XMatch on card valuation–ConceptandAPI.

1 Table 15 – Response APDU from comparison of biometric templates 

ResponseParameter Meaning

Datafield mpty

SW1 SW2 '9000'(yes)or

'63CX'(register0)or

'6300'

2 NOT thatthisonlyreturnsthestatuscode.TherequiredsimilarityscoreisreturnedinaseparateG TDATA

3 command,seesection8.7.2.

4 8.7.2. Locking of the card 

5 NISTseekstoconductarbitrarycomparisonsonthecard.HoweverNISTwillrespect'63CX'countervalues

6 andwillalsoattempttoexecutehigh
scoringcomparisonswithsufficientfrequencytoensurethatlow

7 scoringverificationcomparisonsareinfrequentenoughtopreventcardlocking.NISTwilldiscontinuetesting

8 ofcardsforwhichthesemechanismsareinsufficienttopreventlocking.

9 PC
basedimplementationsofMOCalgorithmsshallneverlock.

10 8.7.3. Similarity scores 

11 NISTmustbeabletoreadasimilarityscorefromthecard.NISTwillnotevaluatecardsthatproduceonlya

12 verificationdecision.TheserequirementssupportcomputationofafullD Tcharacteristic,theprimary

13 outputofthistest.NISTconsidersmatchingalgorithmsthatproduceonlyasmallnumberofpossible

14 similarityvalues(naturallyorotherwise)tobeoperationallylessuseful.

15 Table17specifiesreturnofatwo
bytesimilarityscore.Nativematchingscoresoutsidetherange[0,65535]

16 shouldbeinternallyremappedbytheimplementation.

17 Table 16 – Command APDU for retrieval of verification similarity score 

CommandParameter Meaning

CLA

INS

P1 P2

‘00’

‘CB’=G TDATA

'3FFF' =RetrievefromanywhereinthecurrentDedicatedFile(ApplicationDF)

Lcfield '03'

Datafield '5C'

'01'

'C0'DataObjectidentifiertoberetrieved(twobytesimilarityscore)

Lefield '04'(2+2)lengthofB R TLVencodeddataobjecttoberetrieved

18

19 Table 17 – Response APDU for retrieval of verification similarity score 

ResponseParameter NISTrequiredvalues Meaning

Datafield 'C0' Tagofthescoredata

'02' Lengthofthescorevalue

xxxx Scorevalue

Big endianscorefromthe

lastcomparisonon

[0 65535]

SW1 SW2 SeeISO/I C7816 4

20

21 NOTE Using a proprietary tag ('C0') to retrieve the verificationsimilarityscoreisaguaranteethisinformation

22 willnotbeavailableforcardapplicationsinoperationalmodebecausetheinformationusesatagwhichhasa

23 meaningforthetestapplicationonly.

24 8.7.4. Prohibition of stateful behavior 

25 AlthoughNISTisinterestedintemplateupdateasapotentialmeansofimprovingoperationalperformance,it

26 isbeyondthescopeofthistest.Anycardthatattemptsupdateislikelytogiveanswersdifferentfromthose

27 onproducedintheStage2PCtesting,wheretemplateupdateisprohibitedby9.6.4.

NIST GrotherandSalamon Page19of48

 






 






 


NISTMIN XMatch on card valuation–ConceptandAPI.

1 8.8. Reading card identifier 

2 Table10ofISO/I C7816
6:2004providesastructureforcarddataunderconstructeddataelementtag'66'.

3 ThisstructuremustbereadableusingtheG TDATAAPDUofTable18.

4 Table 18 – Command APDU for retrieval of Card identifier 

CommandParameter Meaning

CLA

INS

P1 P2

'00'

'CB' =G TDATA

'3FFF' =RetrievefromanywhereinthecurrentDedicatedFile(ApplicationDF)

Lcfield '03' lengthofcommanddatafield

Datafield '5C'

'01'

'66'DataObjectidentifiertoberetrieved(CardData)

Le

5

6 Foradministrationpurposesandtoidentifythecardundertest,forexampleinMIN XIItestreports,NISTwill

7 usetheinformationcontainedintheresponsefieldofTable19whichshouldcontainadiscretionaryfield,tag

8 '73',containingthecardversioninformationintag'88'.

9 Table 19 – Response APDU for retrieval of Card identifier 

field '00'

ResponseParameter Meaning Minimalresponsevalue

Datafield 7306

8804<4byteCB FFID>

SW1 SW2 SeeISO/I C7816 4

10 8.9. Reading matcher identifier 

11 Table12ofISO/I C7816
6:2004providesastructureforapplicationrelateddataunderconstructeddata

12 elementtag'6 '.ThisstructuremustbereadableusingtheAPDUofTable20andTable21.NISTshall

13 includetheresultofthisG TDATAwheneveritidentifiesthealgorithm,forexampleinMIN XIItestreports.

14

15 Table 20 – Command APDU for retrieval of Matcher identifier 

CommandParameter Meaning

CLA

INS

P1 P2

'00'

'CB' =G TDATA

'3FFF' =RetrievefromanywhereinthecurrentDedicatedFile(ApplicationDF)

Lcfield '03' lengthofcommanddatafield

Datafield '5C'

'01'

'6 'DataObjectidentifiertoberetrieved(Applicationrelateddata)

Le

16

17 Theresponsefieldshouldcontainadiscretionaryfield,tag'73',containingthematcheridentifierintag'99'.

18 Table 21 – Response APDU for retrieval of Matcher identifier 

field '00'

ResponseParameter Meaning Minimalresponsevalue

Datafield 7306

9904<4byteCB FFID>

SW1 SW2 SeeISO/I C7816 4

NIST GrotherandSalamon Page20of48

 


 







 







 


 


 

 

 

NISTMIN XMatch on card valuation–ConceptandAPI.

1 9. PC-based API specification 

2 9.1. Overview 

3 ThissectiondescribestheMIN XIIAPI.ItappliestothePC basedStage2accuracytestoutlinedinsection

4 6.2.ThematerialdifferencesbetweentheMIN XIIAPIandthatspecifiedinOngoingMIN Xareasfollows.

5 ― TheINCITS378templateshallconformtosection7.2.

6 ― Thetemplategeneratorisrequiredtoreturnthecoordinatesofalogicalcenter,aboutwhichminutiae

7 pruningwillbeconducted.

8 ― ThematchersmustacceptISO CCinstances(notI378instances).

9 9.2. INCITS 378:2004 compliant templates 

10 Alltemplatescreatedshallconformtothespecificationof7.2.NISTwilltestconformanceofallgenerated

11 templatesusingourownopen sourcecode15.

12 Theseshallcontaintheimagequalityvalue(line17ofTable4)thatwasinputtotheSDKbyNIST,i.e.the

13 SDKisnottogeneratethisvalue.Thisvaluemaybeofusetotemplategenerators.Thevalueshallbethere

14 mappedNISTNFIQvaluegiveninTable22.

15 Table 22 – NFIQ Mappings 

 ncodedNFIQvaluestobepassedasinputstothetemplategenerator

NFIQ MIN X04 800 76 1 MIN XII

1 100 100 100

2 75 80 80

3 50 60 60

4 25 40 40

5 1 20 20

16 "C"macrosforfingerqualityaregiveninAnnex .

17 9.3. Submission 

18 ThosewishingtoparticipateinMIN XIItestingshallprovideNISTwiththosecomponentsidentifiedinthe

19 ParticipationClassesgiveninsection6.8.SoftwareshallbesubmittedasanSDK(SoftwareDevelopmentKit)

20 librarywhichcomplieswiththeAPI(ApplicationProgrammerInterface)specifiedinthisdocument.Cards

21 submittedtoNISTshallbeconformanttoISO/I C7816andsupportthebiometricfunctionalitydescribedin

22 section8.

23 9.4. Testing interface 

24 9.4.1. Requirement 

25 MIN XparticipantsshallsubmitanSDKwhichpresentsthe"C"prototypedinterfacegiveninthefollowing

26 subsections.InMIN XII,Phase1,thetemplategenerationfunctionisoptional.

27 9.4.2. Minutiae extraction 

28 NISTwillcreatetemplatesusingtheSDKfunctioncalldefinedinTable23.Thefunctionshallbecapableof

29 processingtheimagedataspecifiedinAnnexC.

30 Table 23 – MINEX create_template API Function 



15Seehttp://www.itl.nist.gov/iad/894.03/nigos/incits.html

NIST GrotherandSalamon Page21of48

 






 








NISTMIN XMatch on card valuation–ConceptandAPI.

Prototype INT32create_template(

constBYT *raw_image,

constBYT finger_quality,

constBYT finger_position,

constBYT impression_type,

constUINT16height,

constUINT16width,

UINT16*xcenter,

UINT16*ycenter,

BYT *INCITS_378_template);

Description ThisfunctiontakesarawinputimageandoutputsthecorrespondingI378conformanttemplate.The

memoryforthetemplateisallocatedbeforethecalli.e.create_template()doesnotallocatememoryfor

theresult.Thefunctionreturnseithersuccess(0)orfailure(non zero).Failureindicatesafailuretoenroll

theimageandwillneverthelessresultintheoutputofaI378templatewithzerominutia.Thiswillbeused

insubsequentcomparisons.

Anerrorshallresultinatemplatecontainingonlytherecordandfingerviewheaders.Thisnumberof

minutiaeshallbesetto0,andnominutiadatashallbepresent.Theresultingtemplateshallhavelength

of32bytes(26 byteRecordHeader+4 byteFingerViewheader+2bytesforthe xtendedDataBlock

lengthwhichshallbeset0x0000).AllotherfieldsintheRecordandFingerViewheadersshallbesetto

theirregularandaccuratevalues.

Input raw_image Theuncompressedrawimageusedfortemplatecreation.

Parameters finger_quality Thequalityofthefingerprintimage(e.g.QUAL_GOOD).

finger_position Thefingerpositioncode(e.g.FINGPOS_RI).

impression_type Theimpressiontypecode(e.g.IMPTYP _LP).

height Thenumberofpixelsindicatingtheheightoftheimage.

width Thenumberofpixelsindicatingthewidthoftheimage.

Output xcenter Horizontalandverticallocationsofacenterpointsuitableforpruningtobe

usedpersection10.4.3.Ifthisfunctionalityisnotsupported,thexcenter

shallbesettotheinputwidth(i.e.outsidetheboundsoftheimage).

Parameters ycenter

INCITS_378_template Theoutputtemplate,perTable4

Return

Value

Thisfunctionreturnszeroonsuccessoradocumentednon zeroerrorcodeotherwise.

1 9.4.3. Minutiae matching 

2 One
to
onecomparisonsrepresentativeofsingle
fingerverificationattemptswillbemadeusingthefunction

3 definedinTable24.

4 Table 24 – MINEX API match_templates function 

Prototype INT32match_templates(

constBYT *verification_template,

constUINT16verification_template_size,

constBYT *enrollment_template,

constUINT16enrollment_template_size,

UINT16*score);

Description ThisfunctioncomparestwoTable5ISO CCcomplianttemplatesandoutputsamatchscore.The

verification_templateshallbecomparedtotheenrollment_template(inthatorderwherethe

underlyingmatcherisorderdependent).

Thereturnedscoreisanintegerrepresentingthesimilarityoftheparentfingerprintimages.Itshould

notbeartificiallyquantized.NISTwillallocatememoryforthisparameterbeforethecall.Whenthe

functioniscalledwitheitherorbothtemplatescontainingzerominutiae(see7.6)thefunctionshall

assignthevalue0tothescore,thenreturnadocumentederrorcode(see9.6.3below).

Input

Parameters

verification_template ATable5templatefromcreate_template()asprocessedbyNIST

accordingtotheverificationBIT.

verification_template_size Thesize,inbytes,oftheinputverificationtemplate0≤N≤384

enrollment_template ATable5 templatefromcreate_template()asprocessedbyNIST

NIST GrotherandSalamon Page22of48

 

















 

 







NISTMIN XMatch on card valuation–ConceptandAPI.

accordingtotheenrollmentBIT.

enrollment_template_size Thesize,inbytes,oftheinputenrollmenttemplate0≤N≤384

Output

Parameters

score Asimilarityscoreresultingfromcomparisonofthetemplates,onthe

range[0,65535].

ReturnValue Thisfunctionreturnszeroonsuccess(i.e.avalidscoreisproduced)oradocumentednon zeroerror

codeonfailure.

1 9.4.4. Implementation identifiers 

2 TheimplementationshallsupportthefunctionofTable25toidentifyitself.

3 Table 25 – MINEX API get_pids function 

Prototype INT32get_pids(

UINT32*template_generator,

UINT32*template_matcher);

Description ThisfunctionretrievesCB FFPIDswhichidentifytheSDK’ssupportedcoretemplategeneratorand

templatematcher.BothPIDsshallbefour bytefieldsconformingtotheCB FFProductIdentifier(PID)

requirementsofclause6.4.4ofINCITS378:2004.Thesestatethat

― Thetwomostsignificantbytesofthefieldindicatethe(corporate)owner.Itisahexadecimal

integerassignedbytheIBIA(pertherequirementofclause6.5.12.1ofISO/I C19785 1:2006).

― Theleasttwosignificantbytesareanowner assignedversionnumber.

ThememoryforthetemplategeneratorandmatcherparameterswillbeallocatedbyNISTbeforethe

call.

IftheSDKdoesnotincludeatemplate_generator,thereturnedvalueshallbezero.

Output

Parameters

template_generator

template_matcher

APIDwhichidentifiestheSDK’sminutiaeextractor

APIDwhichidentifiestheSDK’smatcher.

ReturnValue Thisfunctionreturnszeroonsuccessoradocumentednon zeroerrorcodeonfailure.Inthelatter

case,bothoutputparametersshallbesetto0.

4 9.5. Software and Documentation 

5 9.5.1. SDK Library and Platform Requirements 

6 ParticipantsshallprovideNISTwithbinarycodeonly(i.e.nosourcecode)−supportingfilessuchasheader

7 (“.h”)filesnotwithstanding.Suchfilesshallnotcontainintellectualpropertyofthecompanynorany

8 materialthatisotherwiseproprietary.ItispreferredthattheSDKbesubmittedintheformofasinglestatic

9 libraryfile(ie.“.LIB”forWindowsor“.a”forLinux).However,dynamic/sharedlibraryfilesarepermitted.

10 Ifdynamic/sharedlibraryfilesaresubmitted,itispreferredthattheAPIinterfacespecifiedbythisdocument

11 beimplementedinasingle“core”libraryfilewiththebasefilename‘libminex’(forexample,‘libminex.dll’

12 forWindowsor‘libminex.so’forLinux).Additionaldynamic/sharedlibraryfilesmaybesubmittedthat

13 supportthis“core”libraryfile(i.e.the“core”libraryfilemayhavedependenciesimplementedinthese

14 otherlibraries).

15 9.5.2. Linking 

16 NISTwilllinktheprovidedlibraryfile(s)toaClanguagetestdriverapplication(developedbyNIST)using

17 ― Forwindows,version3.3.3oftheGCCcompilerwillbeusedunderCygwin;

18 ― ForRedHatLinux7.3platforms,version2.96ofGCCwillbeused.

19 AllGCCcompilersuselibc.Thelinkcommandmightbe"gcc–omintestmintest.c L.–lminex"

20 ParticipantsarerequiredtoprovidetheirlibraryinaformatthatislinkableusingGCCwiththeNISTtest

21 driver,whichiscompiledwithGCC.Allcompilationandtestingwillbeperformedonx86platformsrunning

22 eitherWindows2000orRedHatLinux7.3(dependentupontheoperatingsystemrequirementsoftheSDK).

23 Thus,participantsarestronglyadvisedtoverifylibrary levelcompatibilitywithGCC(onanequivalent

NIST GrotherandSalamon Page23of48

 





 




 

 

 




 




10

15

20

25

30

35

NISTMIN XMatch on card valuation–ConceptandAPI.

1 platform)priortosubmittingtheirsoftwaretoNISTtoavoidlinkageproblemslateron(e.g.symbolnameand

2 callingconventionmismatches,incorrectbinaryfileformats,etc.).

3 NOT  Dependenciesonexternaldynamic/sharedlibrariessuchascompiler specificdevelopment

4 environmentlibrariesarediscouraged.Ifabsolutelynecessary,externallibrariesmustbeprovidedtoNIST

5 uponpriorapprovalbytheTestLiaison.

6 9.5.3. Installation and Usage 

7 TheSDKmustinstalleasily(i.e.oneinstallationstepwithnoparticipantinteractionrequired)tobetested,

8 andshallbeexecutableonanynumberofmachineswithoutrequiringadditionalmachine specificlicense

9 controlproceduresoractivation.

TheSDK’susageshallbeunlimited.TheSDKshallneitherimplementnorenforceanyusagecontrolsorlimits

11 basedonlicenses,executiondate/time,numberofexecutions,presenceoftemporaryfiles,etc.

12 ItisrecommendedthattheSDKbeinstallableusingsimplefilecopymethods,andnotrequiretheuseofa

13 separateinstallationprogram.ContacttheTestLiaisonforpriorapprovalifaninstallationprogramis

14 absolutelynecessary.

9.5.4. Documentation 

16 ParticipantsshallprovidecompletedocumentationoftheSDKanddetailanyadditionalfunctionalityor

17 behaviorbeyondthatspecifiedhere.Thedocumentationmustdefineallerrorandwarningcodes(see9.6.3).

18 9.5.5. Modes of operation 

19 IndividualSDKsprovidedshallnotincludemultiple“modes”ofoperation,oralgorithmvariations.Noswitches

oroptionswillbetoleratedwithinonelibrary.Forexample,theuseoftwodifferent“coders”byaminutiae

21 extractormustbesplitacrosstwoseparateSDKlibraries,andtwoseparatesubmissions.

22 9.6. Runtime behavior 

23 9.6.1. Speed 

24 ThefollowinglimitsareinstitutedtoconstrainNIST'stotalMIN XIIcomputationalworkload.

― Themeantemplatematchoperationshallnotexceed10milliseconds.

26 ― Themeantemplatecreationoperationshallnotexceed1.2seconds(usinga2GHzPentiumIV).

27 9.6.2. Interactive behavior 

28 TheSDKwillbetestedinnon interactive“batch”mode(i.e.withoutterminalsupport).Thus,thesubmitted

29 libraryshallnotuseanyinteractivefunctionssuchasgraphicaluserinterface(GUI)calls,oranyothercalls

whichrequireterminalinteractione.g.readsfrom“standardinput”.

31 9.6.3. Error codes and status messages 

32 TheSDKwillbetestedinnon interactive“batch”mode(i.e.withoutterminalsupport).Thus,thesubmitted

33 libraryshallrunquietly,i.e.itshouldnotwritemessagesto"standarderror"andshallnotwriteto“standard

34 output”.Instead,theSDKshallconformtotheerrornotificationproceduresofAnnexD.

9.6.4. External communication 

36 ProcessesrunningonNISThostsshallnotwriteanydatatoexternalresource(e.g.server,file,connection,or

37 otherprocess)otherthanthoseexplicitlyallowedinthisdocument.

NIST GrotherandSalamon Page24of48

 


 


 





 





 





 













 


 












 





NISTMIN XMatch on card valuation–ConceptandAPI.

1 9.6.5. Stateful behavior 

2 Allcomponentsinthistestshallbestatelessandidempotent.Nocomponentofthetestispermittedto

3 maintainstateinformation.Thisappliestotemplategenerationandmatching,andtoon cardandoff card

4 activity.NISTwillinstituteappropriateteststodetectstatefulbehaviorintheactivitiesmentionedinthe

5 followingsubsections.Ifdetected,NISTwillceaseevaluationandinformtheprovider.

6 NOT  NISTisprohibitingtemplateadaptation,andwillaccordinglyimplementcheckstodetectanystateful

7 behaviorandside effects.HoweverNISTisinterestedintemplateupdateasapotentialmeansofimproving

8 operationalperformance,butitisbeyondthescopeofthisandforeseeabletestingefforts.

9 10. NIST conversion of I378 to ISO-CC templates 

10 10.1. Background 

11 NISTintendstomaintainitsuseoftheI378standardasaprimaryformatforoff cardstorageofminutia

12 templates.NISTrecognizestheadvantagesofISO CCforon cardstorageormatching.Althoughthetwo

13 kindsoftemplatesdiffer,theaccuracyimplicationsseemtobelimited seetheAnnexAsimulationofthe

14 impactonmatchingaccuracy.

15 10.2. Presence of BITs on card 

16 achsubmittedcardshallbepopulatedwithoneortwoBITspersection8.6.Theseshallbetreatedasread

17 onlydata.TheseshallbesuppliedinthestructuregiveninTable13whichleveragetheBITandBITgrouping

18 structuresofISO/I C7816 11:2004(Tables1and2).

19 TheBITsparameterizetheproductionoftemplatesthatareader,orothersystem,shouldsendtothe

20 requestingcard:ForareferencetemplateTR,averificationtemplateTV,andaPCorcard basedmatcher,

21 M,thetestwillcompareBIT processedversionsofthetemplatestoproduceasimilarityscore

22 s=M(BR(TR),BV(TV))

23 whereBRandBVdenotethefunctionsrepresentingtheBITparameterization.

24 OperationallytheBITparameters(e.g.maximumnumberofminutiae)mightbesentas inputstoatemplate

25 generator.NISTdoesnotintendtodothisbecausesuchspecializationwouldbecomputationallyprohibitive

26 inthecontextofaninteroperabilitytest16.Instead,NISTproposestostandardizetheminutiaetemplate

27 reductionprocessasfollows.

28 10.3. Use of BITs 

29 NISTwilltreaton cardandoff cardmatcherimplementationsidentically.ThismeansthattheBITsreadfrom

30 thecardwillbeusedtoparameterizeBOTHtheconversionoftemplatessenttothecardandtothePC based

31 matchoperation.

32 Theconversionoperationproceedswithapruningoperation(sec.10.4.3),asortingoperation(sec.10.5),and

33 are encoding(sec.AnnexA.1).NISTwillconductthisoperationusingitsownsoftwarewhich

34 ― existswithinalargerstandardbiometricdatainterchangesoftwaredistributionnamedBioMDI,

35 ― isentirelyopensource17ISO/I C9899:1999"C"code,

36 ― isavailablefordownloadandcooperativedevelopment18intheopen sourcemodel,and



16Forexample,ifatestusedTtemplates,NtemplategeneratorsandCcards,imposestherequirementtoexecute

O(TNC)image to templategenerations. 17Seethelicenseathttp://www.itl.nist.gov/iad/894.03/nigos/NIGOS_licdis_061906.pdf 18Thesoftwareisavailableathttp://www.itl.nist.gov/iad/894.03/nigosandmaintainedusingaPerforceversioncontrol

system,athttp://www.perforce.com/,forwhichclientsarefreelyavailable.Whileanightlyzip/tar archiveis

NIST GrotherandSalamon Page25of48

 


 

 

 













 


 
 









 





NISTMIN XMatch on card valuation–ConceptandAPI.

1 ― isunderformalversioncontrol19.

2 Figure 1 – Conversion of INCITS 378 to ISO-CC 

Input

Image

INCITS378

template

VendorX

generator

AngleQuantization8→6bits

(fmr2fmr)

(x,y)197→100 pixcm 1

(fmr2fmr)

ISO CC

template

PruneonQandPosition

(fmrprune)

Sort

(fmrsort)

NISTsuppliedcomponent

BITParameters

Vendorsuppliedcomponent

VendorYcard

B R TLV

VendorY

PCbased.soor.dll

3 TheitemsinparenthesesarethenamesofexecutablespresentinNIST'sBioMDIdistribution.

4 10.4. Number of minutiae 

5 10.4.1. Limits on number 

6 NIST'sconsidersthatitsroleisnottoimposealgorithmicconstraints.Howevertheminimumandmaximum

7 numbersofminutiaacardmayacceptareregulatedasfollows

8 ― Theone bytevalueimpliesarangeof[0,255],

9 ― Becausesometemplateswillnaturallycontain0minutia(seeFTAinsection7.6),minimumvalueswillbe

10 ignored,

11 ― NISTimposeda128minutiamaximuminallpriorMIN Xtrials.ThisisarguablytoohighgiventhatMIN X

12 04,whichusedfourlargeoperationalsingleindexfingerflat impressiondatasets,foundthattheleading

13 systemsproducedamedianof41minutiaefromeachimagewiththe5%and95%quantilesbeing24and

14 61respectively.

15 ― AT=0APDUcommandconstrainsthemaximumnumberofthree byteminutiato60.NotethatT=0is

16 notrequiredbyNIST.

17 ― InformativeAnnexD.1.1ofISO/I C19794 2recommendstheminimumnumberofminutiaeforenrollment

18 tobe16,andforverification,12.Italsorecommendsthemaximumnumberofminutiaeforenrollment

19 andverificationis60.NISTnotesthatthesearerecommendationsonly,butotherwisetakesno

20 immediatepositionontheappropriatenessofthesenumbersbeyondtheinformationpresentedin

21 AnnexA.

22 10.4.2. Effect of the BIT 

23 NISTwillsendsingle viewtemplatestothePC basedandcard basedmatchingimplementations.The

24 referenceandverificationtemplatesshallbeparameterizedbytheirrespectiveBITs,asfollows.If,

25 ― thevalueindicatedintheBITfortheminimumnumberofminutiaeis0≤N≤255,

26 ― thevalueindicatedintheBITforthemaximumnumberofminutiaeis0≤M≤255,

27 ― thenumberofminutiapresentina(generallythird party)verificationtemplateisK,then



produced,usersshouldsubscribetoNIST'sopen sourceserverbecauseitautomaticallysendsemailnotificationsofany

changestothesoftware.

19Usersneedtoregister http://www.itl.nist.gov/iad/894.03/nigos/NIGOS_User_Registration.pdfandmaythenaccessthe

codebranchesusingaclientsuchasP4Vathttp://www.perforce.com/perforce/products/p4v.html.

NIST GrotherandSalamon Page26of48

 

















 


 
 





NISTMIN XMatch on card valuation–ConceptandAPI.

1 ― thenumberofminutiaNISTwillsendtothecardisdenotedbySwhere

Mif K≥M

S = Kif K<M { Kif K<N

2 NotethattheBITparameterNisignored.Thisisnecessarybecausesomeinputtemplateswillinevitably

3 havezerominutiae.Thematchershallexecutesuccessfullywheneitherorbothoftheinputtemplates

4 containsfewerthanNminutiae20.

5 NISTwillrejectcardsforwhichN>M.

6 10.4.3. Pruning mechanism 

7 WhenaMOCimplementationindicatesthecapabilitytotakenomorethanMminutiae,NISTproposesto

8 followarefinedversionoftheguidancegiveninthelastparagraphofclause8.3.1ofISO/I C19794 2:2005:

Ifthenumberofminutiaeexceedsthemaximumnumberprocessiblebyacard,

truncationisnecessary.Thetruncationisa2stepprocess.Atfirst,fingerminutiae

ofpoorqualityareeliminated.Ifstilltoomanyminutiaearethere,thentruncation

shallbemadebypeelingoffminutiaefromtheconvexhulloftheminutiaesetand

beforesortingintotheorderrequiredbythecard. 9

10 SpecificallyNISTintendstoreplacetherequirementtousetheconvexhull,withamethodbasedonthe

11 distanceofaminutiafromacenter.ThisisbasedontheISO/I C19794 2subclause8.3.4guidanceforpolar

12 ordering.

13 ThusgivenaI378templatecontainingKminutiaeandaBITrequestfornomorethanMminutiaeoursoftware

14 willremoveK Mminutiaeasfollows.

15 Minutiaewiththelowestqualityvalueareremovedfirst.Iftwoormoreminutiahaveanequalqualityvalue,

16 thentheonewiththelargestvalueoftheintegerquantity

r

2 = (x–xc)2

+(y–yc)

2

17 isremoved.Finallyifthosevaluesaretied,thentheISO/I C19794 2:2005polarorderinginstructionto

18 prioritizesmallangleminutiaeisapplied.

19 NISTunderstandsthattheISO/I C19794 2:2005materialonpolarcoordinatesisintendedforsorting,not

20 pruning,butconsiderstheconvexhullapproachtobecomplex,andpotentiallyharmfuleffects.

21 10.4.4. Pruning center 

22 InMIN XII,allI378templategeneratorsmayadditionallyreportthecoordinatesofanappropriatecenter

23 aboutwhichpruningshouldbeconducted. arlierversionsofthistestspecificationestablishedtheminutia

24 means(center of mass)for(xc,yc),pertheISO/I C19794 2:2005sortingguidance.However,thismaybe

25 particularlyinappropriatewhenlargenumbersofminutiaarereportedinanoisypartoftheimage.

26 NISTwillconductpruningabout

27 ― thecentercoordinatesfromthetemplategenerator,ifsupplied,otherwise

28 ― thecenterofmass,pertheISOstandard.



AnunappealingalternativewouldbetofillwithN Krandomlygeneratedminutiae.

NIST GrotherandSalamon Page27of48

20
NISTMIN XMatch
 
 on card valuation–ConceptandAPI.

1 10.4.5. Pruning priority 

2 Itisclearthataqualityalgorithmproducingmanylevelsofqualitywillcausethepruningoperationtoprune

3 onr2

onlyoccasionally.Conversely,aqualityalgorithmproducingfewlevelsofqualitywillcauser2pruning

4 tobemoredominant.Animplementershouldnotsupplyqualityvaluesthataredependentsolelyofr2

5 becausethiscontradictsthetrue
minutiarequirementofsection7.2.2.

6 10.5. Sort order of minutiae 

7 10.5.1. Support for ordering 

8 Althoughtemplategeneratorsarelikelytoproducetemplateswhoseminutiaehaveanarbitraryorder,the

9 ISO
CCstandarddefinesseveralgeometricorderingsoftheminutia.Thex
yandy
xsortingmethodssupport

10 extensionofthespatialrangeofafingerprint(e.g.forrolledprints)inonedimension.Thepolarmethod

11 supportsacenter
firstsort.

12 CurrentlyNISTintendstosupportatleasttheunsorted,Cartesiany
x,Cartesianx
yandpolarsorting

13 methods,becausethestandarddefinestheseasoptions.NISTwillpublishopen
source"C"codeindue

14 course.NISTdoesnotintendtoacceptcommercialcodeforthispurpose,althoughwemayinstitutea

15 conformancetestforimplementationsthatdo.

16 However,NISTisawarethatcommercialreaderswillneedtoincludesuchsoftwareinadditiontothepruning

17 software.Thisaddscomplexityanda"degreeoffreedom"thatwouldbetterbehandledasanaturalproperty

18 ofthematchingalgorithm.AlthoughNISTnotesthe uropeanCitizenCardspecification,C N/TS15480
2,

19 requiresimplementationstoacceptarbitrarilysorteddata,NISTprefersnottoignoretheSC37/WG3intentto

20 allowsorting.NISTdoesconsiderthattheexactrequirementsofISO/I C19794
2clause8areunclear.

21 10.5.2. Modulo sorting for large images 

22 NotethatarchivalimageryusedinallplannedMIN Xevaluationsisatmost500pixelsinwidthandheight,

23 andisscannedat19.7pixelsmm
1

,andthereforeallpossibleminutiaecoordinatescanbeencodedin8bits

24 withoutmodulosorting(orremoval).

25 TheISO/I C19794
2:2005standardneedsmodification,seeAnnexF.1.

26 10.6. Ridge count, core and delta and zonal quality information 

27 TheISO/I C19794
2:2005standardallowstheBITtoindicatethe"extendeddata"definedinclause7.5of

28 thatstandard.HoweverinTable13,thebinaryvalue00000000bindicatesthatridgecount,coreanddelta

29 andzonalqualityinformationareoutofthescopeofthistest.Suppliersmustadheretothezero

30 specificationhere.

31 NISTisinterestedinpossibleperformanceimprovementassociatedwiththeuseofrichertemplates,butpast

32 experiencewithINCITS378extensions(MIN X04)hasnotsuggestedlargeimprovementsareavailable.

33 HoweverNISTwill,onrequestfromanyinterestedparty,considerconductingtestsoftemplatesthatinclude

34 extendeddata.Particularly,whatbenefitswouldzonalqualityallowbeyondthatassociatedwitha

35 (calibrated)minutiaqualityvalue.

36 11. References 

37 [1]C.Wilsonetal.,“BiometricDataSpecificationforPersonalIdentityVerification,”NISTSpecialPublication

38 800
76
1http://csrc.nist.gov/publications/nistpubs/800
76
1/SP800
76
1_012407.pdf

39 [2]P.Grotheretal.,“PerformanceandInteroperabilityoftheINCITS378Template,”NISTIR7296

40 http://fingerprint.nist.gov/minex04/minex_report.pdf

41 [3] .Tabassietal.“FingerPrintImageQuality,”NISTIR71512004(Gaithersburg,MD:NationalInstituteof

42 StandardsandTechnology,August2004)http://www.itl.nist.gov/iad/894.03/quality/reports/ir_7151.pdf

NIST GrotherandSalamon Page28of48
NISTMIN XMatch
 
 on card valuation–ConceptandAPI.

1 [4]AmericanNationalStandardforInformationTechnology–FingerMinutiaeFormatforDataInterchange,

2 ANSI/INCITS378
2004,www.incits.org

3

NIST GrotherandSalamon Page29of48

 


 

 





 





 













 

NISTMIN XMatch on card valuation–ConceptandAPI.

1 Annex A 

2 Comparison of the INCITS 378 and ISO/IEC 19794-2 standards 

3 CB FFFormatOwner=0101forISO/I CJTC1/SC37.

4 CB FFFormatType=0005forridgeendingsencodedasvalleybifurcationpoints,asinINCITS378.

5 TheINCITS378standard'srecordformatandtheISO/I C19794 2compactcardformatdiffersyntactically

6 andsemantically.Thesedifferencesarepresentedinthenexttwosubsections.Thereafterweaddressthe

7 implicationsfortranscodingbetweenthestandards,andtheMIN Xrequirements.

8 A.1 Syntactic differences 

9 TheINCITS378:2004andISO CCtemplatesdifferasfollows.InISO CC

10 ― the(x,y)coordinatesareencodedin8bitsasopposedto14bits,

11 ― thespatialresolutionisfixedat10pixelspermillimeterasopposedtovariableresolution,

12 ― theangleisencodedin6bitsasopposedto8bits,and

13 ― theminutiaqualityvalueisabsent.

14 ThesedifferencesaredepictedinTable26.Notethatridgecountandcoreanddeltainformationisnot

15 beingevaluatedinthistest,andthereforetheBITentrydefinedinISO/I C19794 2Table14,shallbesetto

16 0,andignored.

17 Table 26 – Minutia encodings of the ISO-CC and INCITS 378 

Byte1 Byte2 Byte3 Byte4 Byte5 Byte6

ISO/I C19794 2CompactCardFormat xcoord. ycoord. t angle

8 8 2 6

ISO/I C19794 2RecordFormatand

INCITS378

t xcoord. r ycoord angle quality

2 14 2 14 8 8

t=type r=reserved

18 A.2 Semantic differences 

19 Theabbreviated8bit(x,y)encodingsintheISO
CCstandardsupport"typical"single
fingerimagesby

20 specifyingahard
wiredresolutionof10pixelspermillimeter(ISO/I C19794
2,subclause8.2).Thisis

21 approximatelyhalfoftypicalenrollmentdatagatheredon500ppi(19.7pixelspermillimeter)optical

22 scanners.ThisissummarizedinTable27.Theeffectwouldbethatminutiacannotextendoveraregion

23 largerthan255/10=25.5mm.HowevertheISO
CCstandardprovidesforcoordinatewraparoundwherein

24 theminutiacoordinatesaresortedsuchthattheactualvaluemayextendbeyondtherangebyencodingitas

25 xmod256.Reconstructionoftheactualvalueispossiblebecausesortingisapplied.

26 Table 27 – Minutia location quantization of ISO-CC and INCITS 378 templates 

Standard Allowedvalues

(units)

Allowedvalues(mm) Allowedvalues(mm),

at500ppi

INCITS378:2004recordformat [0,16383] Dependsonthe

encodingresolution

[0,0.051,0.1015,

0.1523,...,831.6] ISO/I C19794 2recordformat

ISO/I C19794 2compactcard [0,255] [0,0.1,0.2...25.5] N/A

27 AsshowninTable28,thethreedifferentangularencodingssupportminutiaencodingsofvaryingprecision.

28 Whetherthisdifferencemateriallyaffectsperformanceisdependentonthesensitivityofthematching

29 algorithm,andonhowaccuratelytemplategeneratorsmeasuretheangle.

30 Table 28 – Minutia angle quantization of ISO-CC and INCITS 378 templates 

NIST GrotherandSalamon Page30of48

 








 







 







NISTMIN XMatch on card valuation–ConceptandAPI.

Standard Allowedvalues Quantization

(units) Degreesperunit Radiansperunit

INCITS378:2004record [0,179] 360/180=2 2pi/180=0.0349

ISO/I C19794 2record [0,255] 360/256=1.4063 2pi/256=0.0245

ISO/I C19794 2compactcard [0,63] 360/64=5.625 2pi/64=0.0982

1

2 A.3 Simulation protocol 

3 ToquantifytheeffectsoftheISO CCencodingvs.theINCITS378recordformat,NISTsimulatedthe

4 productionofISO CCtemplatesbyquantizingthecoordinatesandanglesinsetsofINCITS378templates

5 producedinNIST'sexistingMIN Xtesting.

6 Figure 2 - Use of INCITS 378 for simulation of ISO-CC accuracy 

 nrollment

Image

INCITS378

template

VendorX

generator

Angle

8→6bits

(x,y)

197→100

pixcm 1

INCITS378

template

VendorX

matcher

Verification

Image

INCITS378

template

VendorX

generator

Angle

8→6bits

(x,y)

197→100

pixcm 1

INCITS378

template

7 TheCcodefragmentstoeffectthesetransformationsareshowninTable29.Thiscodeispartofthe

8 "fmrisocompact"programdistributed21byNISTaspartofasuiteoflibrariesandapplicationsthatsupport

9 variousINCITSbiometricstandards.

10 Table 29 – Source code for conversion of INCITS 378 to ISO-CC 

Angularre
quantization

// The ISO minutia record has 6 bits for the angle, so 

// we have 64 possible values to represent 360 degrees. 

for (m = 0; m < mcount; m++) // for all minutiae 

{ 

 const int theta = 2 * (int)fmds[m]->angle; // 378 has 2 degrees 

 const double isotheta = round((64.0 / 360.0) * (double)theta); // CC has 5.625 deg 

 fmds[m]->angle = (unsigned char)round(((360.0 / 64.0) * isotheta) / 2.0); // Put back in 378 

} 

Spatialre
quantization

for (m = 0; m < mcount; m++) // for all minutiae 

{ 

 const double x = (double)fmds[m]->x_coord; // cast from unsigned short 

 const double y = (double)fmds[m]->y_coord; // cast from unsigned short 

 const double xmm = 10.0 * x / (double)xres; // millimeters, because INCITS 378 resolution 

 const double ymm = 10.0 * y / (double)yres; // values are in pixels per centimeter 

 const double xunits = xmm / 0.1; // units of 0.1 pix per mm which is the CC 

 const double yunits = ymm / 0.1; // card format's hardwired sampling freq 

 const unsigned short xcc = 

 (unsigned short)(0.5 + xunits); // round the value - this is what would be 

 const unsigned short ycc = // stored in "typical" say 500 dpi operation 

 (unsigned short)(0.5 + yunits); 

 fmds[m]->x_coord = (unsigned short)((double)xcc * (double)xres * 0.01); // Now put back 

 fmds[m]->y_coord = (unsigned short)((double)ycc * (double)yres * 0.01); // in 378 format 

} 



Thisisavailablefordownload;seehttp://www.itl.nist.gov/iad/894.03/nigos/incits.html

NIST GrotherandSalamon Page31of48

21

 



 



 



 



 



 






 
 
 
 



 
 
 
 



 
 
 
 



 
 
 
 



 
 
 
 











 




NISTMIN XMatch on card valuation–ConceptandAPI.

1 WetookfivevendorsandappliedtheirmatcherstoINCITS378templatesderivedfromtheoutputsofthat

2 vendor'stemplategenerator.Theyareappliednatively,thatistoenrollmentandverificationtemplates

3 fromthesamesupplier'sINCITS378generator.Thefivematchingalgorithms,identifiedinthefirstcolumns,

4 aresomeofthemoreaccurateonesassessedintheOngoingMIN Xevaluation.

5 AllresultsapplytosinglefingermatchingusingthePO BVA collectionofleftandrightindexfingers,asused

6 intheOngoingMIN Xevaluation.TheFNMRcomputationisconductedover15disjointsetseachcontaining

7 16000genuinescores.TheFMRcomputationislikewiseconductedover15disjointsetseachcontaining

8 16000impostorscores.

9 A.4 Results after re-quantization of angle and position 

10 Table30givesthechangeinFNMRwhenthematcheroperatingthresholdissettoachieveFMRvaluesof0.01

11 onINCITS378templatesandthenresettoachievethoseFMRsonISO
CCtemplates.Thisthresholding

12 strategyisrepresentativeofthesituationwherethresholdscanbesetfortheISO
CCtemplateindependently

13 ofanyINCITS378matchertrialorcalibration.

14 Table 30 – Relative accuracy of ISO-CC and INCITS 378 templates (Fixed FMR) 

BaseFMR BaseFNMR ChangeinFNMR

A1 0.01 0.0140 0.0005+/ 0.0006 p2e 03

A2 0.01 0.0158 0.0018+/ 0.0007 p3e 08

A3 0.01 0.0133 0.0007+/ 0.0007 p2e 03

A4 0.01 0.0183 0.0006+/ 0.0005 p6e 05

A5 0.01 0.0159 0.0008+/ 0.0005 p9e 05

15 Table31giveschangesinFMRandFNMRwhenthematcheroperatingthresholdissettoachieveFMRvalues

16 of0.01,ontheunalteredINCITS378templates.Thisthresholdingstrategyisrepresentativeofthesituation

17 whereaISO
CCtemplateissent,withtranscoding,toanINCITS378matcher.

18 Table 31 – Relative accuracy of ISO-CC and INCITS 378 templates (fixed t) 

ChangeinFMRandFNMRwhenISO CCencodingissynthesizedfrominstancesoftheINCITS378recordformat

"MIN:A"templates.

BaseFMR ChangeinFMR BaseFNMR ChangeinFNMR

A1 0.01 0.0013+/ 0.0008 p7e 06 0.0140 0.0008+/ 0.0008 p5e 04

A2 0.01 0.0008+/ 0.0011 p1e 02 0.0158 0.0020+/ 0.0007 p4e 09

A3 0.01 0.0006+/ 0.0008 p6e 03 0.0133 0.0007+/ 0.0006 p5e 04

A4 0.01 0.0004+/ 0.0006 p1e 02 0.0183 0.0007+/ 0.0007 p7e 04

A5 0.01 0.0008+/ 0.0009 p1e 03 0.0159 0.0010+/ 0.0008 p1e 04

19 ThuswhengoingfromINCITS378toISO CC

20 ― Table30showssmallbutstatisticallysignificantincreasesinFNMR.TheworstcaseisA2whoseFNMR

21 goesfrom0.0158to0.0176ataFMRof0.01correspondingtoabout11%moremissedmatches.

22 ― Atafixedthresholdforbothkindsoftemplate,Table31showssmallthatFMRisslightlybutsignificantly

23 lowerforISO CCthanforINCITS378,butthatFNMRisagainhigher.

24 Thepresenceofanalgorithm effect(someimplementationsaremoresensitivethanothers,viz.A2overA3,

25 meansthatvendorsshouldconsiderthisissuefortheirimplementations.

26 NOT  Thechangeinperformanceforlessaccuratematchersandtemplategeneratorshasnotbeenstudied.

27 A.5 Results after reduction in number of minutiae 

28 TheplotsofFigure3showtheeffectofapplythepruningoperationofsection10.4.3torawINCITS378(not

29 ISO CC)templates.Theeffectonaccuracyisshownforthesamefiveleadingmatcherprovidersasused

30 above.Thematchersareappliednativelyi.e.thematcherfromproviderXisappliedtocomparetemplates

31 fromX'sgenerator.Foreachmatcher,thethresholdissettothevaluethatgivesaFMRof0.001onthe

32 entireunprunedcorpus.Theerrorratesarethenrecomputedafterremovingzeroormoreminutiato

NIST GrotherandSalamon Page32of48

 














NISTMIN XMatch on card valuation–ConceptandAPI.

1 achieveamaximumofNineachtemplate.Thetopgraphshowstheeffectofretainingallminutiaeinthe

2 enrollmenttemplateandminutiaeintheverificationtemplate.Thelowergraphshowstheeffectofpruning

3 both.

4 Theconclusionsare

5 ― FNMRincreasesforallmatchersalgorithms,withapproximately60minutiabeingareasonably"lossless"

6 value.Notethatthe95%percentilesfornumberofminutiaeare60,65,60,64,and63.

7 ― FNMRhasincreasedbyanorderofmagnitude(from~2%to~20%)whenfewerthan20minutiaareused.

8 ― FMRvaluesalsochangesignificantly,beginningatthesame60minutiaebreakpoint,andsubstantially

9 belowabout20minutiae.Somesystemsimprove(declineinFMR)andsomedegrade(increaseinFMR).

10 NISTisconcernedthatanyincreaseinFMRassociatedwithtransactionsinvolvingsmallnumbersof

11 minutiaeisasecurityhazard.

12 Notshownhereisdistributionalinformationonthenumbersofminutiaeproducedbytemplategenerators.

13 NISThasobservedvariationinthenumbersfoundfromasingleimage.Alsonotshownareinteroperable

14 results(cross vendor)andNISTsuggeststhatanincorrectconclusionfromthegraphswouldbethattemplate

15 generatorsfindingmoreminutiaearebetterperforming.

16 A.6 Conclusions 

17 TheISO CCtemplatecanofferperformanceapproachingthatoftheINCITS378template.However,some

18 implementationsexhibitdegradedperformance.Thisstudy,however,onlyapproximatesactualISO CC

19 performancebecauseprovidersmaybeabletoimprovealgorithmicfunctionalityiftheyspecificallyknowthe

20 targetresultisISO CC.

21

NIST GrotherandSalamon Page33of48

 


 

FNMR

0.1

0.05

0.01

0.005

0.001

0.0005

FMR

102050100

FNMR

0.1

0.05

0.01

0.005

0.001

0.0005

FMR

NISTMIN XMatch on card valuation–ConceptandAPI.

1 Figure 3 – Effect of minutia pruning on FNMR (above) and FMR (below) 

Maximumnumberofminutiaeafterpolarpruningofjusttheverificationtemplate

Maximumnumberofminutiaeafterpolarpruningbothverificationandreferencetemplates

2

3

NIST GrotherandSalamon Page34of48

 


 













 

NISTMIN XMatch on card valuation–ConceptandAPI.

1 Annex B 

2 Three-way interoperability 

3 NISTanticipatesthatsomecardsembedfingerprintmatchersthatarenotaccompaniedbyanassociated

4 templategenerator,andmaywellbeusedwithenrollmentandverificationtemplatescomingfromtwo

5 differentsources.Thatiscard basedmatcher,M,willcompareareferencetemplateproducedbyXwitha

6 verificationtemplatefromY.NISTwillevaluatethree wayinteroperabilityinthistest.MIN Xparticipants

7 shouldbeawarethattheMIN X04measurementsofFigure4,showthree wayinteroperability(green)will

8 generallyofferpoorerperformance

9 ― thanintwo way(cyan)ornative(horizontalbar)cases,and

10 ― insituations(matchers1and4)inwhichtheproviderofamatchersuppliesatemplategeneratorthatis

11 lesseffectivethanitspeers.

12 Figure 4 – Native vs. Two-way vs. Three-way Interoperability 

Matcher1 Matcher2 Matcher3 Matcher4 Matcher5

Thenotationhere,MXY,denotesuseofmatchersupplierM,withtemplategeneratorsuppliersXandY.The

valuesplottedareFNMRvaluesatFMR=0.01forfiveleadingmatcherprovidersexecutingleftandright

single
fingermatchesofINCITS378templates.Thematchersarepairedwiththebestsevendifferent

templategeneratorsfoundinMIN X04.

3 NISTacknowledgesthatnotrequiringacard/matcherprovidertoteamwithatemplategeneratorprovideris

4 inconsistentwiththerequirementinsection6.6torequirepairingofcardandmatchercombinations.

5 Howeverthisseeminginconsistencyisundertakeninlightofthefollowing:

NativeMMM Twoway

MMXorMXM

SameTG

MXX

Threeway

MXY

1

1

1

NIST GrotherandSalamon Page35of48

 



 


NISTMIN XMatch on card valuation–ConceptandAPI.

1 ― Cardsandmatchingalgorithmsmaywellbeboundattimeofmanufacture;

2 ― CardsandreferencetemplatesareboundattimethecardissuanceorIDMSsoftwarewasshippedbyan

3 integrator;

4 ― Althoughsoftwarematcherimplementations(e.g.Javaapplets)exist(andareeligiblefortesting)and

5 thesecouldbeselectedduringintegrationorevenissuance,theyarereportedtorunsignificantlymore

6 slowly.

7 FurtherNISTismotivatedbyadesiretoimproveperformance,bothinthisevaluationandinfielded

8 operation.GiventhatNISThasdemonstratedthatsometemplategeneratorsarebetterthanothers,NIST

9 seekstomeasurecard matcher templategeneratorcompatibility.

NIST GrotherandSalamon Page36of48
NISTMIN XMatch
 
 on card valuation–ConceptandAPI.

1 Annex C 

2 Input fingerprint image specifications 

3 C.1 Format 

4 TheSDKmustbecapableofprocessingfingerprintimagessuppliedtotheSDKinuncompressedraw8
bit(one

5 byteperpixel)grayscaleformat. achimageshallappeartohavebeencapturedinanuprightpositionand

6 approximatelycenteredhorizontallyinthefieldofview.Theimagedatashallappeartobetheresultofa

7 scanningofaconventionalinkedimpressionofafingerprint.Figure1illustratestherecordingorderforthe

8 scannedimage.Theoriginistheupperleftcorneroftheimage.Thex
coordinate(horizontal)positionshall

9 increasepositivelyfromtheorigintotherightsideoftheimage.They
coordinate(vertical)positionshall

10 increasepositivelyfromtheorigintothebottomoftheimage.

11 Figure 5 – Fingerprint image raster scan order 

12 Raw8
bitgrayscaleimagesarecanonicallyencoded.Theminimumvaluethatwillbeassignedtoa"black"

13 pixeliszero.Themaximumvaluethatwillbeassignedtoa"white"pixelis255.Intermediategraylevelswill

14 haveassignedvaluesof1
254.Thepixelsarestoredlefttoright,toptobottom,withone8
bitbyteper

15 pixel.Thenumberofbytesinanimageisequaltoitsheightmultipliedbyitswidthasmeasuredinpixels;

16 thereisnoheader.TheimageheightandwidthinpixelswillbesuppliedtotheSDKassupplemental

17 information.

18 C.2 Resolution and dimensions 

19 Allimagesforthistestwillemploy500PPIresolution(horizontalandvertical).

20 Thedimensionsofthefingerprintimageswillvaryfrom150to812pixelsinwidth,and166to1000pixelsin

21 height.

22 Note–theSDKmustbecapableofprocessingimageswithanydimensionsinthesespecifiedrangeswithout

23 theuseofseparatelyinvokedcroppingorpaddingfacilities.Forexample,SDKswhichrequirecroppingof

24 largeimagesmustdosointernaltotheoperationofthecreate_template(seebelow)APIcall.

25 C.3 Sensor and impression types 

26 AllimagesusedfortestinginMIN XcomefromthePO BVAdatasetdescribedinNISTIR7296[2](see

27 AppendixB,Table23page47)andthushavebeenobtainedfromlive
scansensors(Smiths
HeimannACCO

28 1394andCrossMatch300A).AllimagestestedinMIN Xareplainimpressiontypeimages.

NIST GrotherandSalamon Page37of48
NISTMIN XMatch
 
 on card valuation–ConceptandAPI.

1 Annex D 

2 Error Codes and Handling 

3 achparticipantshallprovidetheirSDKwithtextdocumentationofall(non
zero)errororwarningreturn

4 codes(seesection9.5.4,Documentation).

5 Theapplicationshouldincludeerror/exceptionhandlingsothatinthecaseofafatalerror,thereturncodeis

6 stillprovidedtothecallingapplication.

7 AtminimumthereturncodesofTable32shallbeused.

8 Table 32 – MINEX API return codes 

Return

code

 xplanation

0 Success

1 Imagesizenotsupported

2 Failedtoextractminutiae–unspecifiederror

3 Failedtoextractminutiae–impressiontypenotsupported

4 Failedtomatchtemplates–nullprobeorgallerytemplate

5 Failedtomatchtemplates–unabletoparseprobetemplate

6 Failedtomatchtemplates–unabletoparsegallerytemplate

9 Allmessageswhichconveyerrors,warningsorotherinformationshallbesuppressed.

NIST GrotherandSalamon Page38of48

 


 

 








 


NISTMIN XMatch on card valuation–ConceptandAPI.

1 Annex E 

2 Predefined SDK Constants 

//Fingerqualityvalues

#defineQUAL_POOR20//NFIQvalue5

#defineQUAL_FAIR40//NFIQvalue4

#defineQUAL_GOOD60//NFIQvalue3

#defineQUAL_VGOOD80//NFIQvalue2

#defineQUAL_ XC LL NT100//NFIQvalue1

//Fingerpositioncodes

#defineFINGPOS_UK0x00//Unknownfinger

#defineFINGPOS_RT0x01//Rightthumb

#defineFINGPOS_RI0x02//Rightindexfinger

#defineFINGPOS_RM0x03//Rightmiddlefinger

#defineFINGPOS_RR0x04//Rightringfinger

#defineFINGPOS_RL0x05//Rightlittlefinger

#defineFINGPOS_LT0x06//Leftthumb

#defineFINGPOS_LI0x07//Leftindexfinger

#defineFINGPOS_LM0x08//Leftmiddlefinger

#defineFINGPOS_LR0x09//Leftringfinger

#defineFINGPOS_LL0x0A//Leftlittlefinger

//Impressiontypecodes

#defineIMPTYP _LP0x00//Live scanplain

#defineIMPTYP _NP0x02//Nonlive scanplain

7

8 Notethatthefingerpositioncodesdifferinthefingerprintstandards,andthesmart
cardstandards.

9 ForallinteractionswiththecardISO/I C7816
11:2004fingerpositioncodesshallbeused.Forall

10 interactionswithPC
basedimplementationsISO/I C17994
2:2005fingerpositionsshallbeused.NISTwill

11 transcodeanyvaluesusingtheTable34associationswheneverneeded.Thetablesummarizesthetwobase

12 standardsandisincludedhereforinformativepurposesonly.

13 Table 34 - ISO/IEC 19794-2 and ISO/IEC 7816-11 finger position codes 

FingerID

Biometricsubtype

ISO/I C19794 2:2005 ISO/I C7816 11:2004

Binaryvalue HexValue Binaryvalue HexValue

Noinformationgiven 00000b 00 00000b 00

rightthumb 00001b 01 00101b 05

rightindex 00010b 02 01001b 09

rightmiddle 00011b 03 01101b 0D

rightring 00100b 04 10001b 11

rightlittle 00101b 05 10101b 15

leftthumb 00110b 06 00110b 06

leftindex 00111b 07 01010b 0A

leftmiddle 01000b 08 01110b 0 

leftring 01001b 09 10010b 12

leftlittle 01010b 0A 10110b 16

NIST GrotherandSalamon Page39of48

3 E.1 Pre-defined values 

4 Thepre
definedvalues(constants)ofTable33areforuseinspecifyingparameterstotheMIN Xtesting

5 interface:

6 Table 33 – MINEX API predefined values 

 


 

 

 





 
 


 

 


 




















NISTMIN XMatch on card valuation–ConceptandAPI.

1 Annex F 

2 Ambiguities in the standards 

3 F.1 Compact card sorting 

4 ThelastlineofISO/I C19794 2:2005clause8.3.4"Thesameconstructionprinciplemaybeappliedalsofor

5 theYcoordinate"shouldbechangedto"Thesameconstructionprinciplemayalternativelybeappliedtothe

6 Ycoordinate.UsingthisconstructiononXandYtogetherisnotpossible."

7 Clause8.3.4isverylong.Toenableeasycitationofthestandard,itneedstobebrokenupintonamed(or

8 evenumnamed)subparagraphs.

9 ThetextinISO/I C19794 2:2005Table14second to lastlinereferencessubclause"8.33"whichshouldbe

10 "8.3.4".

11 F.2 Unique minutia 

12 Thereshouldbeanormativerequirementforminutia(x,y,theta)triplestobeunique.Theissueofrequiring

13 unique(x,y)valuesseemstobeinconflictwiththereportingoftrifurcationswhichwouldhavesame(x,y).

14 F.3 No support for placing reference data on the card 

15 ISO/I CFDIS19785 3:2007( )establishestheCB FFTLV encodedC BFFpatronformatforthetagassociated

16 withbiometricsubtypedata(inthiscasefingerposition).Thisvalueis'82'.NeitherISO/I C7816 11:2004,

17 norISO/I C19794 2:2005includenormativespecificationsforthislocation.However,thereisno

18 standardizedmechanismforfingerpositioninformationtobesenttothecardwhenstoringareference

19 template.Indeed,noneoftherelevantstandardsadvanceanormativeprescriptionforaISO/I C7816

20 4:2005commandforthispurpose.Yes,ISO/I C7816 11:2004includestheuseofaCHANG R F R NC DATA

21 commandasanexampleininformativeAnnexB,butthattextdoesnotadvanceamethodforpassingthe

22 biometricsubtypetothecard.

23 NISTseesthelackofastandardizedcommandasanimpedimenttoMIN XII(seediscussioninsection8.5).

24 NISTseesthelackofastandardizedmechanismfortransmissionofbiometricsubtypedatatothecardasan

25 inhibitortoward(future)multi fingerapplications.

26 NISTisinterestedinstandardizationofthetransmissionofreferencedatatothecard.

27 ArevisionofISO/I C19794 2mightusefullyincludedefinitiveproceduresforenrollingfingerprintminutiae

28 templatesonthecard.ItshouldrecommendCHANG R F R NC DATAorPUTDATAandparticularlyshould

29 establishtagsforfingerposition(biometricsubtype).NISTnotesthatthereisnosupportforunsegmented

30 fingerprints.

NIST GrotherandSalamon Page40of48

 


 

 

 




 

NISTMIN XMatch on card valuation–ConceptandAPI.

1 Annex G 

2 ISO/IEC 19794-2:2005 record profile 

3 Table 35 – MINEX II profile of ISO/IEC 19794-2:2005 standard 

FieldnameandISO/I C19794 2:2005

clausenumbersinparentheses

ValuesAllowed InformativeRemarks

5. FormatIdentifier(7.3.1) 0x464D5200 i.e.ASCII"FMR\0"

6. VersionNumber(7.3.2) 0x20323000 i.e.ASCII"20\0".

7. RecordLength(7.3.3) 32≤L≤800 26recordheader+4viewheader+2

extendeddatalength+6K.MaxKis128

8. Capture quipmentCertifications(7.3.4) 0

9. CaptureDeviceTypeID(7.3.5) 0

10. SizeofScannedImageinxdirection(7.3.6) MIT Inheriteddirectlyfrominputdata

11. SizeofScannedImageinydirection(7.3.7) MIT

12. X(horizontal)resolution(7.3.8) 197

13. Y(vertical)resolution(7.3.9) 197

14. NumberofFingerViews(7.3.10) 1

15. ReservedByte(7.3.11) 0

16. FingerPosition(7.4.1.1) MIT Inheriteddirectlyfrominputdata

17. ViewNumber(7.4.1.2) 0

18. ImpressionType(7.4.1.3) 0or2 Inheriteddirectlyfrominputdata

19. FingerQuality(7.4.1.4) MIT Inheriteddirectlyfrominputdata

20. NumberofMinutiae(7.4.1.5) 0≤K≤128 Kminutiaedatablocks

21. MinutiaeType(7.4.2.1) 01b,10b,or00b

22. MinutiaePosition(7.4.2.2) MIT

23. MinutiaeAngle(7.4.2.3) MIT

24. MinutiaeQuality(7.4.2.4) 0,1≤Q≤100 0=unsupported

25. xtendedDataBlockLength(7.5.1.1) >=0 ither0fornoextendeddata,orthelength

ofazonalqualityblock

26. xtendedDataAreaTypeCode(7.5.1.2) 0x0003 Optional,onlypresentif(7.5.1.1)is>0.

27. ZonalQ.CellWidthandHeight(7.5.4.1) 1≤NPIX≤W Optional,onlypresentif(7.5.1.1)is>0.

ZonalQ.CellWidthandHeight(7.5.4.1) 1≤NPIX≤H Optional,onlypresentif(7.5.1.1)is>0.

28. ZonalQ.CellQualityInfo.Depth(7.5.4.2) 1,2,4,8 Optional,onlypresentif(7.5.1.1)is>0.

Thisvalueshallnotbe0.

29. ZonalQ.CellQualityData(7.5.4.3) Optional,onlypresentif(7.5.1.1)is>0.

MIT=mandatoryattimeofinstantiation

4

5 Table 36 – ISO/IEC 19794-2 minutiae template DO 

Tag L Value

‘7F2 ’ L1 Biometricdatatemplate

Tag L Value

‘81’ L2 Fingerminutiaedata

Field Size(bits) ValidValues

Xcoordinate 8 [0,255]

Ycoordinate 8 [0,255]

Minutiaetype 2

Minutiaeangle 6 [0,63]

'94' L3 ZonalQuality

Data

5+var SeeTable37

S

instances

1

instance

NIST GrotherandSalamon Page41of48
NISTMIN XMatch
on
card valuation–ConceptandAPI.

1 wherethezonalqualityblockshallconformtoTable37.Thisdataisamodifiedversionofthatinsertedinto

2 ISO/I C19794
2:2005bythedraftTechnicalCorrigendum1,SC37N2119.

3 Table 37 – Zonal quality data 

FIeld Length

(bytes)

Values

Allowed

InformativeRemarks

1 HorizontalResolutionoftheQualityMap(8.4.1.1.2) 1 SeeNote1and xample1

2 VerticalResolutionoftheQualityMap(8.4.1.1.2) 1

3 QualityMapWidth(8.4.1.1.3) 1 #cellsinxhorizontaldirection

4 QualityMapHeight(8.4.1.1.3) 1 #cellsinyverticaldirection

5 CellQualityInformationDepth(8.4.1.1.4) 1 1,2,4,8 Not0.

6 CellQualityData(8.4.1.1.5) L Packedbits

4 NOT 1 ThefirstdraftTechnicalCorrigendum1,SC37N2119hasonefieldforcellqualityresolution,

5 i.e.itassumesthex
yresolutionsareequal.However,theISO
R Cstandardallowsdifferentcellresolutions

6 inxandy.Therefore,iftheISO
R CtoISO
CCtranscodingprocessistobecomeviableoperationally,then

7 cardzonalqualitydataneedstosupportanisotropicresolutions.NISTwillcommentontheupdateofN2119

8 (tobecirculatedforballotinthelatterhalfof2007).

9 XAMPL 1 IfthehorizontalcelldimensioninaISO
R Czonalqualityblock(clause7.5.4.1ofISO/I C

10 19794
2:2005)is20pixels,andthecorrespondinghorizontalresolutionis197pixelspercentimeter(clause

11 7.3.8ofISO/I C19794
2:2005),thenthevalueoftheentryonline1ofthistable(i.e.thenumberofcells

12 perdecimeter)willberound(10*197/20)=99,wheretheroundingoperatorisnowherestandardized.

NIST GrotherandSalamon Page42of48

 


 

 

 


 
 


 

 

 

 

 

 

 

 

 

 

NISTMIN XMatch on card valuation–ConceptandAPI.

1 Annex H 

2 Application to participate in MINEX II 

3 H.1 Who should participate 

4 ProvidersofISO/I C7816card basedMOCimplementationsusingISO/I C19794 2:2005minutia based

5 templatesareinvitedtoparticipateinMIN XII.Inaddition,companies,researchorganizations,or

6 universitiesthathavedevelopedmatureprototypesorwhoresearchfingerprintmatchingofinteroperable

7 templatesareinvitedtoparticipate.

8 Thefingerprinttemplategenerationandmatchingsoftwareneednotbe“operational,”noraproduction

9 system,norcommerciallyavailable.However,thesystemmust,ataminimum,beastableimplementation

10 capableofbeing“wrapped”(formatted)intheAPIspecificationthatNISThasspecifiedinsection9forthis

11 evaluation.

12 Anonymousparticipationwillnotbepermitted.ThismeansthatsignatoriestothisAgreementacknowledge

13 thattheyunderstandthattheresults(seesections6.8andAnnexH.7)oftheevaluationofthesoftware

14 and/orhardwarewillbepublishedwithattributiontotheirorganization(s).

15 H.2 How to participate 

16 H.2.1 Application package 

17 InordertorequestparticipationinMIN XII,prospectiveparticipantsmustassembleALLofthefollowing

18 itemsandsendtheentirepackagetoNISTattheaddressgiveninAnnexI.

19 ― Physical7816cardsforeachsubmission(seesection6.8andH.3.3).

20 ― AsignedandfullycompletedcopyofthisentireAnnexH,includingtheAgreement Application to 

21 Participate in MINEX II,formbelow.Thismustidentify,andincludesignaturesfrom,theResponsible

22 Parties.

23 Thepackagemayalsoinclude:

24 ― softwareforeachsubmission(seesection6.8andH.3.4).

25

26 H.2.2 Parties 

27 TheResponsiblePartyisanindividualwiththeauthoritytocommittheorganizationtothetermsinthis

28 document.

29 ThePointofContactisanindividualwithdetailedknowledgeofthesystemapplyingforparticipation.

30 H.3 NIST activity 

31 H.3.1 Initiation 

32 UponreceiptofthesignedAnnexHformbyNIST,theorganizationororganizations,ifteaming,shallbe

33 classifiedasa“Participant”.NISTmustreceivetheformduringthesubmissionperioddescribedintheMIN X

34 IICalendar.

35 H.3.2 Supplier validation 

36 RegisteredParticipantswillbeprovidedausernameandpasswordtoallowaccesstoasmallValidation

37 Datasetavailableonthewebsitehttp://fingerprint.nist.gov/minex/registered/.Priortosubmissionoftheir

38 SDK,theParticipantmusttoverifythattheirsoftwareexecutesonthevalidationdata,andproducescorrect

39 similarityscoresandtemplates.

NIST GrotherandSalamon Page43of48

 







 


 


 


 

 

 

NISTMIN XMatch on card valuation–ConceptandAPI.

1 H.3.3 Submission of hardware to NIST 

2 SuppliersshallsendfiveidenticalinstancesofthesmartcardtoNISTattheaddressgiveninAnnexI.

3 SupplierscommittoassistingNISTinresolvingdeviationsfromthespecificationsofthisdocument,errors,

4 defectsorinconsistencies.

5 H.3.4 Submission of software to NIST 

6 AftertheParticipanthasexecutedhissoftwareonthevalidationimagery,theparticipantsshallsendthe

7 softwareanditsvalidationoutputtoNIST.AllsubmittedmaterialshallbeencryptedusingGnuPG(gpg)by

8 downloadingtheMIN XTestLiaison'spublickey:http://fingerprint.nist.gov/minex/minex_pk.ascwhose

9 fingerprintis448F3828719DB6B0FDC53D 6715B6C72062A520A.

10 ― Importingitintoyourkeyringusing: 

11 ― UsingittoencryptyourSDK(withASCIIarmorifsubmittingviaemail):

12 Theresultshalleitherbe

13 ― emailedtominex@nist.govor

14 ― senttoNISTonCDmediatotheaddressgiveninAnnexI.

15

16 H.3.5 Acceptance testing 

17 CardssubmittedshallimplementtheAPDUspecificationsofsection8.

gpg importminex_pk.asc

gpg rminex aemysdk.zip

18 SoftwaresubmittedshallimplementtheMIN XIIAPISpecificationofsection9.

19 UponreceiptoftheSDKandvalidationoutput,NISTwillattempttoreproducetheoutputbyexecutingthe

20 SDKonthevalidationimagery,usingaNISTcomputer.Intheeventofdisagreementintheoutput,orother

21 difficulties,theParticipantwillbenotified.

22 Intheeventcardsorsoftwareisfoundtobenon functionalornon compliantwiththisdocument's

23 specifications,orwherethevalidationdatasetresultscannotbereplicatedbyNIST,Participantswillbe

24 notifiedwithadetaileddescriptionoftheproblem(s)andgivenareasonableopportunitytoresubmit(astime

25 allows)accordingtothediscretionoftheMIN XIILiaison.

26 H.3.6 Limits of testing 

27 NISTwillusetheParticipant'scardsandSDKsoftwareonlyforthetestingdescribedinthisdocument.The

28 providedhardwareandsoftwarewillalsobeusedtoresolveanyerrorsidentifiedsubsequenttothetestor

29 publicationofresults.

30 NISTagreesnottousetheParticipantssoftwareforpurposesotherthanindicatedherein,withoutexpress

31 permissionbytheParticipant.

32 H.4 Points of contact 

33 TheMIN XIILiaisonisthegovernmentpointofcontactforMIN XII.Allcorrespondenceshouldbedirected

34 tominex@nist.gov,whichwillbereceivedbytheMIN XIILiaisonandotherMIN XIIpersonnel.

35 ThesecorrespondencesmaybepostedontheFAQ(FrequentlyAskedQuestions)areaoftheMIN XIIwebsite

36 atthediscretionoftheMIN XIILiaison.Theidentityofthosepersonsororganizationswhose

37 correspondencesleadtoFAQpostingswillnotbemadepublicintheFAQ.

38 H.5 Access to MINEX II validation data 

39 TheMIN XIIValidationDataissuppliedtoParticipantstoassistinpreparingforMIN XII.

40 ThefingerprintsintheMIN XIIValidationDataarerepresentativeoftheMIN XIITestDataonlyintheir

41 format.Imagequality,collectiondeviceandothercharacteristicsarelikelytovarybetweentheValidation

42 andTestDatasets.

NIST GrotherandSalamon Page44of48

 


 

 

 


 





 

 

 

 

 

NISTMIN XMatch on card valuation–ConceptandAPI.

1 H.6 Access to MINEX II test data 

2 TheMIN XIITestDatasetsareprotectedunderthePrivacyAct(5U.S.C.552a),andwillbetreatedas

3 SensitivebutUnclassifiedand/orLaw nforcementSensitive.

4 MIN XIIParticipantsshallhavenoaccesstoMIN XIITestData,eitherbefore,duringorafterthetest.

5 InformationabouttheimagesdatahasbeenpreviouslypublishedinMIN X04report,NISTIR729622.

6 H.7 Reporting of results 

7 H.7.1 Reports 

8 TheGovernmentwillcombineappropriateresultsintooneormoreMIN XIIReports.Togetherthesewill

9 contain,ataminimum,descriptiveinformationconcerningMIN XII,descriptionsofeachexperiment,and

10 aggregatetestresults.NISTwillinclude

11 ― D Tperformancemetricsastheprimaryindicatorsofone to oneverificationaccuracy,

12 ― ISO/I C19795 4interoperabilitymatricesastheprimarymeasuresofinteroperability,and

13 ― enrollmentandverificationtimingstatistics.

14 NISTmaycomputeandreportotheraggregatestatistics.

15 NISTintendstoreleasePhase1resultstotheparticipantonly.

16 NISTintendstopublishPhase2resultsinoneormoreNISTInteragencyReports.

17 ThePhase2reportswill:

18 ― containthenamesofPhase1participants,

19 ― notcontaintheresultsfromPhase1participants'implementations,

20 ― containthenamesofPhase2participants,and

21 ― containtheresultsofallPhase2participants'implementationswhichwillassociatedwiththe

22 participantsnames.

23 H.7.2 Pre-publication review 

24 Participantswillhaveanopportunitytoreviewandcommentonthereports.Participants’commentswillbe

25 eitherincorporatedintothemainbodyofthereport(ifitisdecidedNISTreportedinerror)orpublishedas

26 anaddendum.Commentswillbeattributedtotheparticipant.

27 H.7.3 Citation of the report 

28 AfterthereleaseofthePhaseIIFinalReport,Participantsmaydecidetousetheresultsfortheirown

29 purposes.Suchresultsshallbeaccompaniedbythefollowingphrase:“ResultsshownfromtheMinutiae

30 Interoperability xchangeTest(MIN XII)donotconstituteendorsementofanyparticularsystembytheU.S.

31 Government.”SuchresultsshallalsobeaccompaniedbytheURLoftheMIN XIIReportontheMIN XII

32 website,http://fingerprint.nist.gov/minexII.

33 H.7.4 Rights and ownership of the data 

34 AnydataobtainedduringMIN X(exceptingthesubmittedSDKitself),aswellasanydocumentationrequired

35 bytheGovernmentfromtheparticipants,becomesthepropertyoftheGovernment.Participantswillnot

36 possessaproprietaryinterestinthedataand/orsubmitteddocumentation.

37 H.8 Return of the supplied materials 

38 H.8.1 Returning software to vendors 

39 NISTwillnotreturnanysuppliedsoftware,documentation,orothermaterialtovendors.



22MIN XReportNISTIR7296PDFishere:http://fingerprint.nist.gov/minex04/minex_report.pdf

NIST GrotherandSalamon Page45of48
NISTMIN XMatch
 
 on card valuation–ConceptandAPI.

1 H.8.2 Returning cards to vendors 

2 NISTwillnotreturncardstotheprovider.NISTwilldestroythecardswithinninetydaysofpublicationofthe

3 resultsforthatcardornotificationtothevendorthatthecardisinoperable.Thisrequirementisneeded

4 becausetemplatedataonthecardisprotectedandbecauseNISThasnomechanismtoassuredeletionof

5 templatesfromthecard.However,NISTtosupportdebuggingNISTmay,atitssolediscretion,returncards

6 duringtheinitialacceptancetestingphase.

7 H.9 Agreement to participate 

8 Withthesigningofthisform,ParticipantsattestthattheywillnotfileanyMIN XII
relatedclaimagainst

9 MIN XIISponsors,Supporters,staff,contractors,oragencyoftheU.S.Government,orotherwiseseek

10 compensationforanyequipment,materials,supplies,information,travel,laborand/orotherparticipant

11 providedservices.

12 TheGovernmentisnotboundorobligatedtofollowanyrecommendationsthatmaybesubmittedbythe

13 Participant.TheUnitedStatesGovernment,oranyindividualagency,isnotbound,norisitobligated,inany

14 waytogiveanyspecialconsiderationtoMIN XIIParticipantsonfuturecontracts,grantsorotheractivities.

15 Withthesigningofthisform,Participantsrealizethatanytestdetailsand/ormodificationsthatareprovided

16 intheMIN XIIwebsitesupersedetheinformationonthisform.

17 Withthesigningofthisform,ParticipantsrealizethattheycanwithdrawfromtheMIN XIIatanytimeprior

18 totheendofthePhase1submissionwindow,withouttheirparticipationandwithdrawalbeingdocumented

19 intheMIN XIIFinalReport.

ThisformshallbecompletedbyallsuppliersofISO/I C7816cardsandprovidersoffingerprinttechnologyelectingto

participateintheMIN XIItrials.Whenmorethanonesupplierispartofateamtoprovideanimplementation,a

ResponsiblePartyfromeachpartyshallcompleteanexecutedcopyofthisagreement.

Cardidentifier(identicaltovalue Fingerprintmatcheridentifier(identical Fingerprinttemplategenerator

identifier(identicaltothatreturnin returnedinsec.8.8).Requiredfor tovaluereturnedinsections8.9and

ClassA+B(sec.6.8)submissions. sec.9.4.4).RequiredonlyforClassB 9.4.4).RequiredforClassA+B(sec.

(se . c 6.8)submissions. 6.8)submissions.

HexVendorID HexVendorID(IBIAassigned) HexVendorID(IBIAassigned)

Hexvendorassignedversionno. Hexvendorassignedversionno. Hexvendorassignedversionno.

ResponsiblePartyforsupplierofsmartcard

Company/OrganizationName

Title FirstName MI LastName Suffix

StreetAddress

City State Zip Country

Phone Fax mail

Technicalpointofcontact Phone mail

ResponsiblePartyforsupplieroffingerprintmatchertechnology(i.e.anyalgorithmspresentonthecardorintheSDK

library).

Company/OrganizationName

NIST GrotherandSalamon Page46of48
NISTMIN XMatch
 
 on card valuation–ConceptandAPI.

Title FirstName MI LastName Suffix

StreetAddress

City State Zip Country

Phone Fax mail

Technicalpointofcontact Phone mail

ResponsiblePartyforsupplieroffingerprintminutiaetemplategeneratortechnology(i.e.anyalgorithmspresentinthe

SDKlibrary).

Company/OrganizationName

Title FirstName MI LastName Suffix

StreetAddress

City State Zip Country

Phone Fax mail

Technicalpointofcontact Phone mail

1

2 Withmysignature,Iagreethatthisdocumentisasufficientdescriptionofthetesttobeconducted.

3 Withmysignature,IherebyrequestconsiderationasaParticipantintheMinutiaInteroperability xchange

4 TestII(MIN XII),andIamauthorizingmycompanyororganizationtoparticipateinMIN XIIaccordingtothe

5 rulesandlimitationslistedinthisdocument.

6 Withmysignature,IalsostatethatIhavetheauthoritytoacceptthetermsstatedinthisdocument

7

8

9

10 ________________________________________________________________________________

11 SIGNATUR OFCARDSUPPLI RR SPONSIBL PARTY DAT 

12

13

14

15 ________________________________________________________________________________

16 SIGNATUR OFFIRSTFING RPRINTSOFTWAR SUPPLI RR SPONSIBL PARTY DAT 

17

18

19

20 ________________________________________________________________________________

21 SIGNATUR OFS CONDFING RPRINTSOFTWAR SUPPLI RR SPONSIBL PARTY DAT 

NIST GrotherandSalamon Page47of48

 


 

 




NISTMIN XMatch on card valuation–ConceptandAPI.

1 Annex I 

2 NIST mailing address 

MIN XIITestLiaison

NationalInstituteofStandardsandTechnology

InformationAccessDivision(894)

100BureauDrive,Stop8940

Gaithersburg,MD20899 8940

USA

6 IncaseswherethecourierneedsaphonenumberpleaseuseNISTS+H301ninesevenfivesixtwoninesix.

7

NIST GrotherandSalamon Page48of48

3 TheaddressgivenbelowshallbeusedforallmailorcourierdeliverytoNIST.ThisincludesdeliveryofMIN X

4 IIparticipationagreementsandallMIN XIIcardsandsoftware.

5