21.02.2013 Views

Advances in Fingerprint Technology.pdf

Advances in Fingerprint Technology.pdf

Advances in Fingerprint Technology.pdf

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

the expected number of matches required to solve the identification problem<br />

<strong>in</strong>creases l<strong>in</strong>early with the database size. It is therefore desirable to f<strong>in</strong>d more<br />

efficient solutions to the identification problem.<br />

There have been two primary approaches to make the identification<br />

searches more efficient. In the first approach, the database is organized so that<br />

certa<strong>in</strong> matches can be ruled out based on the <strong>in</strong>formation extr<strong>in</strong>sic/<strong>in</strong>tr<strong>in</strong>sic<br />

to the f<strong>in</strong>gerpr<strong>in</strong>ts. When the number of necessary matches is reduced based<br />

on the <strong>in</strong>formation extr<strong>in</strong>sic to the f<strong>in</strong>gerpr<strong>in</strong>ts, the solution is commonly<br />

referred to as filter<strong>in</strong>g. For example, the database can be presegmented based<br />

on <strong>in</strong>formation about sex, race, age, and other bio-/geographical <strong>in</strong>formation<br />

related to the <strong>in</strong>dividual. In b<strong>in</strong>n<strong>in</strong>g, a f<strong>in</strong>gerpr<strong>in</strong>t’s <strong>in</strong>tr<strong>in</strong>sic <strong>in</strong>formation<br />

(e.g., f<strong>in</strong>gerpr<strong>in</strong>t class) is used to reduce the number of matches. 61<br />

The percentage of the total database to be scanned, on average, for each<br />

search is called the “penetration coefficient,” P, which can be def<strong>in</strong>ed as the<br />

ratio of the expected number of comparisons required for a s<strong>in</strong>gle <strong>in</strong>put<br />

image to the total number of pr<strong>in</strong>ts <strong>in</strong> the entire database. Based on published<br />

results, we believe that b<strong>in</strong>n<strong>in</strong>g can achieve a penetration coefficient of about<br />

50%. The second approach for mak<strong>in</strong>g the search more efficient is to reduce<br />

the effective time given for each match. Given a match<strong>in</strong>g algorithm, the<br />

effective time per match can be reduced by directly implement<strong>in</strong>g the entire<br />

algorithm or components of it <strong>in</strong> special hardware. The other method of<br />

reduc<strong>in</strong>g the effective time per match is by paralleliz<strong>in</strong>g the matches, that is,<br />

us<strong>in</strong>g multiple processors and assign<strong>in</strong>g a fraction of the matches to each<br />

processor. Some vendors have resorted to optical comput<strong>in</strong>g 41 to achieve a<br />

very high match<strong>in</strong>g throughput.<br />

Scalability of accuracy performance of a large-scale identification system<br />

is a more formidable challenge than its speed performance. If the accuracy<br />

performance associated with match<strong>in</strong>g each pair of f<strong>in</strong>gerpr<strong>in</strong>ts (e.g., verification<br />

accuracy) is characterized by false accept (FAR v) and false reject (FRR v)<br />

rates, the identification accuracy performance of the system with n records<br />

<strong>in</strong> the database (one per identity) can then be expressed as:<br />

FRRi = FRRv × FCR<br />

n P<br />

i ( v)<br />

×<br />

FAR = 1− 1−FAR<br />

(8.3)<br />

(8.4)<br />

under the underly<strong>in</strong>g assumptions that (1) the outcome of each match is an<br />

<strong>in</strong>dependent event, (2) all the records <strong>in</strong> the database are correctly classified,<br />

(3) FCR is the probability of falsely classify<strong>in</strong>g (b<strong>in</strong>n<strong>in</strong>g) the given f<strong>in</strong>gerpr<strong>in</strong>t<br />

<strong>in</strong>to a wrong b<strong>in</strong>, and (4) the misclassification and mismatch<strong>in</strong>g events are<br />

<strong>in</strong>dependent.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!