Method and Apparatus for Rolled Fingerprint Capture
Background of the Invention
Field of the Invention
The present invention is directed to the field of rolled fingerprint capture, and more specifically, to capturing and combining multiple fingerprint images to generate an overall rolled fingerprint image.
Related Art
A rolled fingerprint scanner is a device used to capture rolled fingerprint images. The scanner captures the image of a user's fingerprint as the user rolls a finger across an image capturing surface. Multiple fingerprint images may be captured by the scanner as the finger is rolled. These images may be combined to form a composite rolled fingerprint image. A computer system may be used to create the composite rolled fingerprint image. Fingerprint images captured by a digital camera are generally comprised of pixels. Combining the pixels of fingerprint images into a composite fingerprint image is commonly referred to as pixel "knitting."
The captured composite rolled fingerprint image may be used to identify the user. Fingerprint biometrics are largely regarded as an accurate method of identification and verification. A biometric is a unique, measurable characteristic or trait of a human being for automatically recognizing or verifying identity. See, e.g., Roethenbaugh, G. Ed., Biometrics Explained (International Computer Security Association: Carlisle, PA 1998), pages 1-34.
Capturing rolled fingerprints using a fingerprint scanner coupled to a computer may be accomplished in a number of ways. Many current technologies implement a guide to assist the user. These guides primarily come in two varieties. The first type includes a guide located on the fingerprint scanner itself. This type may include guides such as light emitting diodes (LEDs) that move
across the top and/or bottom of the scanner. The user is instructed to roll the finger at the same speed as the LEDs moving across the scanner. In doing so, the user inevitably goes too fast or too slow, resulting in poor quality images. The second type includes a guide located on a computer screen. Again, the user must match the speed of the guide, with the accompanying disadvantages. What is needed is a method and apparatus for capturing rolled fingerprint images without the requirement of a guide.
Current devices exist for collecting rolled fingerprint images. For instance, U.S. Patent No. 4,933,976 describes using the statistical variance between successive fingerprint image "slices" to knit together a composite fingerprint image. This patent also describes techniques for averaging successive slices into the composite image. These techniques have the disadvantage of less than desirable image contrast. What is needed is a method and apparatus for capturing rolled fingerprint images with improved contrast imaging.
Summary of the Invention
The present invention is directed to a method and apparatus for rolled fingerprint capture. The invention detects the start of a fingerprint roll. A plurality of fingerprint image frames are captured. A centroid window corresponding to each of the plurality of captured fingerprint image frames is determined. Pixels of each determined centroid window are knitted into a composite fingerprint image. The end of the fingerprint roll is detected.
In an embodiment, a pixel intensity difference count percentage value between a current fingerprint image frame and a previous fingerprint image frame is generated. Whether the generated pixel intensity difference count percentage value is greater than a start roll sensitivity threshold percentage value is determined.
Furthermore, in embodiments, a pixel window in a captured fingerprint image frame is determined. A leading edge column and a trailing edge column of a fingerprint image in the corresponding generated pixel window are found.
A centroid window in the captured fingerprint image frame bounded by the leading edge column found and the trailing edge column found is generated.
The present invention further provides a novel algorithm for knitting fingerprint images together. Instead of averaging successive pixels, the algorithm of the present invention compares an existing pixel value to a captured potential new pixel value. New pixel values are only knitted if they are darker than the existing pixel value. The resultant image of the present invention has a much higher contrast than images that have been averaged or smoothed by previous techniques. In an embodiment, the invention compares the intensity of each pixel of the determined centroid window to the intensity of a corresponding pixel of a composite fingerprint image. The pixel of the composite fingerprint image is replaced with the corresponding pixel of the determined centroid window if the pixel of the determined centroid window is darker than the corresponding pixel of the composite fingerprint image. Furthermore, existing fingerprint capturing devices require actuating a foot pedal to begin the capture process. The present invention requires no such activation. The algorithm of the present invention can be instantiated through a variety of software/hardware means (e.g. mouse click, voice command, etc.).
According to a further feature, the present invention provides a rolled fingerprint capture algorithm that can operate in either of two modes: guided and unguided. The present invention may provide the guided feature in order to support legacy systems; however, the preferred mode of operation is the unguided mode. Capturing rolled fingerprints without a guide has advantages. These advantages include decreased fingerprint scanner device complexity (no guide components required), and no need to train users to follow the speed of the guide.
Further embodiments, features, and advantages of the present inventions, as well as the structure and operation of the various embodiments of the present invention, are described in detail below with reference to the accompanying drawings.
Brief Description of the Figures
The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the present invention and, together with the description, further serve to explain the principles of the invention and to enable a person skilled in the pertinent art to make and use the invention.
In the drawings:
FIG. 1 illustrates an example high level block diagram of a preferred embodiment of the present invention.
FIG. 2A illustrates a detailed block diagram of an embodiment of a rolled fingerprint capture module of the present invention.
FIG. 2B illustrates a detailed block diagram of an embodiment of a fingerprint image format module.
FIGS.2C-2E illustrate example embodiments of a fingerprint roll detector module. FIGS. 3A-3G show flowcharts providing detailed operational steps of an example embodiment of the present invention.
FIG. 4 shows an example captured image frame. FIG. 5 shows an example captured fingerprint image frame with a fingerprint image present. FIG. 6 shows an example captured fingerprint image frame with a fingerprint image and a pixel window present.
FIG. 7A shows a more detailed example pixel window. FIG. 7B shows a histogram related to the example pixel window shown in FIG. 7A. FIG. 8 shows an example of pixel knitting for an example segment of a composite fingerprint image.
FIG. 9 shows an example of an overall rolled fingerprint image, displayed in a rolled fingerprint display panel.
FIG. 10 shows an example computer system for implementing the present invention
The present invention will now be described with reference to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Additionally, the left-most digit(s) of a reference number identifies the drawing in which the reference number first appears.
Detailed Description of the Preferred Embodiments
Overview and Terminology
The present invention is directed to a method and apparatus for rolled fingerprint capture. The invention detects the start and end of a fingeφrint roll. One or more fingeφrint image frames are captured. A centroid window corresponding to each of the captured fingeφrint image frames is determined. Pixels of each determined centroid window are knitted into a composite fingeφrint image. The composite fingeφrint image represents an image of a complete fingeφrint roll. To more clearly delineate the present invention, an effort is made throughout the specification to adhere to the following term definitions as consistently as possible.
"USB" port means a universal serial bus port.
The term "fingeφrint image frame" means the image data obtained in a single sample of a fingeφrint image area of a fingeφrint scanner, including fingeφrint image data. A fingeφrint image frame has a certain width and height in terms of image pixels, determined by the fingeφrint scanner and the application.
The terms "centroid" or "fingeφrint centroid" means the pixels of a fingeφrint image frame that comprise a fingeφrint.
The term "centroid window" means an area of pixels substantially surrounding and including a fingeφrint centroid. This area of pixels can be any shape, including but not limited to rectangular, square, or other shape.
Example Rolled Fingerprint Capture Environment
Structural implementations for rolled fingeφrint capture according to the present invention are described at a high-level and at a more detailed level. These structural implementations are described herein for illustrative puφoses, and are not limiting. In particular, rolled fingeφrint capture as described in this section can be achieved using any number of structural implementations, including hardware, firmware, software, or any combination thereof.
FIG. 1 illustrates an example high level block diagram of a preferred embodiment of the present invention. Rolled fingeφrint capture apparatus 100 includes a fingeφrint scanner 102, a computer system 104, and a display 106.
Fingeφrint scanner 102 captures a user' s fingeφrint. Fingeφrint scanner
102 may be any suitable type of fingeφrint scanner, known to persons skilled in the relevant art(s). For example, fingeφrint scanner 102 may be a Cross Match
Technologies Verifier Model 290 Fingeφrint Capture Device. Fingeφrint scanner 102 includes a fingeφrint image capturing area or surface, where a user may apply a finger, and roll the applied finger across the fingeφrint capturing area or surface. Fingerprint scanner 102 periodically samples the fingeφrint image capturing area, and outputs captured image data from the fingeφrint image capturing area. Fingeφrint scanner 102 is coupled to computer system 104. Fingeφrint scanner 102 may be coupled to computer system 104 in any number of ways. Some of the more common methods include coupling by a frame grabber, a USB port, and a parallel port. Other methods of coupling fingeφrint scanner 102 to computer system 104 will be known by persons skilled in the relevant art(s), and are within the scope of the present invention. Computer system 104 receives captured fingeφrint image data from fingeφrint scanner 102. Computer system 104 may provide a sampling signal to fingeφrint scanner 102 that causes fingeφrint scanner 102 to capture fingeφrint image frames. Computer system 104 combines the captured fingeφrint image data/frames into composite or overall fingeφrint images. Further details of
combining captured fingeφrint image frames into composite or overall fingeφrint images is provided below.
Computer system 104 may comprise a personal computer, a mainframe computer, one or more processors, specialized hardware, software, firmware, or any combination thereof, and/or any other device capable of processing the captured fingeφrint image data as described herein. Computer system 104 may comprise a hard drive, a floppy drive, memory, a keyboard, a computer mouse, and any additional peripherals known to person(s) skilled in the relevant art(s), as necessary. Computer system 104 allows a user to initiate and terminate a rolled fingeφrint capture session. Computer system 104 also allows a user to modify rolled fingeφrint capture session options and parameters, as further described below.
Computer system 104 may be optionally coupled to a communications interface signal 110. Computer system 104 may output fingeφrint image data, or any other related data, on optional communications interface signal 110.
Optional communications interface signal 110 may interface the data with a network, the Internet, or any other data communication medium known to persons skilled in the relevant art(s). Through this communication medium, the data may be routed to any fingeφrint image data receiving entity of interest, as would be known to persons skilled in the relevant art(s). For example, such entities may include the police and other law enforcement agencies. Computer system 104 may comprise a modem, or any other communications interface, as would be known to persons skilled in the relevant art(s), to transmit and receive data on optional communications interface signal 110. Display 106 is coupled to computer system 104. Computer system 104 outputs fingeφrint image data, including individual frames and composite rolled fingeφrint images, to display 106. Any related rolled fingeφrint capture session options, parameters, or outputs of interest, may be output to display 106. Display 106 displays the received fingeφrint image data and related rolled fingeφrint capture session options, parameters, and outputs. Display 106 may include a
computer monitor, or any other applicable display known to persons skilled in the relevant art(s) from the teachings herein.
Embodiments for computer system 104 are further described below with respect to FIG. 10. As shown in FIG. 1 , computer system 104 comprises a rolled fingeφrint capture module 108. Rolled fingeφrint capture module 108 detects the start and stop of fingeφrint rolls on fingeφrint scanner 102. Furthermore, rolled fingeφrint capture module 108 combines captured rolled fingeφrint image frames into composite rolled fingeφrint images. Further structural and operational detail of rolled fingeφrint capture module 108 is provided below.
Rolled fingeφrint capture module 108 may be implemented in hardware, firmware, software, or a combination thereof. Other structural embodiments for rolled fingeφrint capture module 108 will be apparent to persons skilled in the relevant art(s) based on the discussion contained herein. The present invention is described in terms of the exemplary environment shown in FIG. 1. However, the present invention can be used in any rolled fingeφrint capture environment where a fingeφrint scanner that captures rolled fingeφrint images is interfaced with a display that displays fingeφrint images. For instance, in an embodiment, fingeφrint scanner 102 and/or display 106 may comprise rolled fingeφrint capture module 108. In such an embodiment, fingeφrint scanner 102 may be coupled to display 106, and computer system 104 may not be necessary in part or in its entirety. Such embodiments are within the scope of the present invention.
Description in these terms is provided for convenience only. It is not intended that the invention be limited to application in this example environment.
In fact, after reading the following description, it will become apparent to a person skilled in the relevant art how to implement the invention in alternative environments known now or developed in the future.
Rolled Fingerprint Capture Module Embodiments
Implementations for a rolled fingeφrint capture module 108 are described at a high-level and at a more detailed level. These structural implementations are described herein for illustrative puφoses, and are not limiting. In particular, the rolled fingeφrint capture module 108 as described in this section can be achieved using any number of structural implementations, including hardware, firmware, software, or any combination thereof. The details of such structural implementations will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. FIG. 2A illustrates a more detailed block diagram of an embodiment of a rolled fingeφrint capture module 108 of the present invention. Rolled fingeφrint capture module 108 includes a fingeφrint frame capture module 202, a fingeφrint image format module 204, and a fingeφrint image display module 206. Fingeφrint frame capture module 202 receives a fingeφrint scanner data signal 208. Fingeφrint scanner data signal 208 comprises fingeφrint image frame data captured by fingeφrint scanner 102. In an embodiment, fingeφrint frame capture module 202 allocates memory to hold a fingeφrint frame, initiates transfer of the frame from the fingeφrint scanner 102, and arranges the pixels for subsequent analysis. Fingeφrint frame capture module 202 outputs a captured fingeφrint image frame data signal 210. Captured fingeφrint image frame data signal 210 comprises fingeφrint image frame data, preferably in the form of digitized image pixels. For instance, fingeφrint image frame data signal 210 may comprise a series of slices of fingeφrint image frame data, where each slice is a vertical line of image pixels.
Fingeφrint image format module 204 receives captured fingeφrint image frame data signal 210. Fingeφrint image format module 204 detects the start and stop of fingeφrint rolls using captured fingeφrint image frame data signal 210. Furthermore, fingeφrint image format module 204 combines captured rolled fingeφrint image frames into composite rolled fingeφrint images. Further
structural and operational embodiments of rolled fingeφrint capture module 108 are provided below. Fingeφrint image format module 204 outputs a composite fingeφrint image data signal 212. Composite fingeφrint image data signal 212 comprises fingeφrint image data, such as a single rolled fingeφrint image frame, or any combination of one or more rolled fingeφrint image frames, including a complete rolled fingeφrint image.
Fingeφrint image display module 206 receives composite fingeφrint image data signal 212. Fingeφrint image display module 206 provides any display formatting and any display drivers necessary for displaying fingeφrint images on display 106. In a preferred embodiment, fingeφrint image display module 206 formats the fingeφrint image pixels into a Windows Device Independent Bitmap (DIB). This is a preferred image format used by the Microsoft Windows Graphical Device Interface (GDI) Engine. Fingeφrint image display module 206 outputs a fingeφrint image display signal 214, preferably in DIB format.
FIG. 2B illustrates a more detailed block diagram of an embodiment of fingerprint image format module 204. Fingeφrint image format module 204 includes fingeφrint roll detector module 216, centroid window determiner module 218, and pixel knitting module 220. Fingeφrint roll detector module 216 detects when a fingeφrint roll has started, and detects when the fingeφrint roll has stopped. FIG. 2C shows an example embodiment of fingeφrint roll detector module 216. Fingeφrint roll detector module 216 includes a fingeφrint roll start detector module 222 and a fingeφrint roll stop detector module 224. Fingeφrint roll start detector module 222 detects the start of a fingeφrint roll. Fingeφrint roll stop detector module
224 detects the stop of a fingeφrint roll. In the example embodiment of FIG. 2C, fingeφrint roll start detector module 222 and fingeφrint roll stop detector module 224 do not contain overlapping structure. In other embodiments, fingeφrint roll start detector module 222 and fingeφrint roll stop detector module 224 share structure. In an alternative embodiment shown in FIG. 2D, fingeφrint roll start detector module 222 and fingeφrint roll stop detector module 224 contain
common structure. The common structure provides advantages, such as requiring a lesser amount of hardware, software, and/or firmware. In an example alternative embodiment shown in FIG. 2E, fingeφrint roll start detector module 222 and fingeφrint roll stop detector module 224 share a common frame difference detector module 226. Frame difference detector module 226 detects differences between consecutively captured fingeφrint image frames. Embodiments of fingeφrint roll start detector module 222, fingeφrint roll stop detector module 224, and frame difference detector module 226 are described in greater detail below. Referring back to FIG. 2B, centroid window determiner module 218 determines the portion of a captured fingeφrint image frame where the finger currently is located. This portion of a fingeφrint image frame is called a centroid window. Embodiments of this module are described in further detail below.
Pixel knitting module 220 knits together the relevant portions of centroid windows to create composite rolled fingeφrint images. Embodiments of this module are described in further detail below.
The embodiments described above are provided for puφoses of illustration. These embodiments are not intended to limit the invention. Alternate embodiments, differing slightly or substantially from those described herein, will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein.
Operation
Exemplary operational and/or structural implementations related to the structure(s), and/or embodiments described above are presented in this section
(and its subsections). These components and methods are presented herein for puφoses of illustration, and not limitation. The invention is not limited to the particular examples of components and methods described herein. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the
teachings contained herein. Such alternatives fall within the scope and spirit of the present invention.
FIG. 3A shows a flowchart providing detailed operational steps of an example embodiment of the present invention. The steps of FIG. 3 A may be implemented in hardware, firmware, software, or a combination thereof. For instance, the steps of FIG. 3 A may be implemented by fingeφrint image format module 204. Furthermore, the steps of FIG. 3 A do not necessarily have to occur in the order shown, as will be apparent to persons skilled in the relevant art(s) based on the teachings herein. Other structural embodiments will be apparent to persons skilled in the relevant art(s) based on the discussion contained herein.
These steps are described in detail below.
The process begins with step 302. In step 302, system variables are initialized. Control then passes to step 304.
In step 304, the start of a fingeφrint roll is detected. Control then passes to step 306.
In step 306, a plurality of fingeφrint image frames are captured. Control then passes to step 308.
In step 308, a centroid window corresponding to each of the plurality of captured fingeφrint image frames is determined. Control then passes to step 310. In step 310, pixels of the determined centroid windows are knitted into an overall fingeφrint image. Control then passes to step 312.
In step 312, the end of a fingeφrint roll is detected. The algorithm then ends.
More detailed structural and operational embodiments for implementing the steps of FIG. 3 A are described below. These embodiments are provided for puφoses of illustration, and are not intended to limit the invention. Alternate embodiments, differing slightly or substantially from those described herein, will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein.
System Variable Initialization
In step 302, variables used by the routine steps must be initialized before the process proceeds. In a preferred embodiment, the initialization phase resets at least the variables shown in Table 1 :
Table 1 : System Variables
Both Rolllnitialized and RollDetected are initially set to FALSE. When a roll is initialized, Rolllnitialized is set to TRUE. When a roll is detected, RollDetected is set to TRUE. When a roll is complete, both variables are set to FALSE.
StartRollSensitivity and StopRollSensitivity may be fixed or adjustable values. In an embodiment, the StartRollSensitivity and StopRollSensitivity variables may be configured from a user interface to control the sensitivity of the rolling process. In an embodiment, these variables can take values between 0 and
100 representing low sensitivity to high sensitivity. Other value ranges may be used, as would be recognized by persons skilled in the relevant art(s).
CurrentBits, PreviousBits, and ImageBits are comprised of arrays of pixels, with each pixel having a corresponding intensity. In a preferred embodiment, all pixel intensity values in CurrentBits, PreviousBits, and
ImageBits are set to 255 (base 10), which corresponds to white. Zero (0) corresponds to black. Pixel values in between 0 and 255 correspond to shades of gray, becoming lighter when approaching 255 from 0. This scheme may be chosen in keeping with the concept that a fingeφrint image contains black ridges against a white background. Other pixel intensity value ranges may be used, as would be recognized by persons skilled in the relevant art(s). Furthermore, the invention is fully applicable to the use of a color fingeφrint scanner, with colored pixel values, as would be recognized by persons skilled in the relevant art(s).
Detecting Start of Fingerprint Roll
In step 304, the start of a fingeφrint roll is detected. Before a rolled fingeφrint image can begin to be created, the system must detect that the user has placed a finger in or against the fingerprint image capturing area of fingeφrint scanner 102 (shown in FIG. 1), and is beginning to roll the finger.
In a preferred embodiment, a method for detecting a finger on fingeφrint scanner 102 is based on calculating a percentage intensity change from a previously captured fingeφrint scanner image (PreviousBits) to a currently captured fingeφrint scanner image (CurrentBits). Each pixel in CurrentBits may be compared to the corresponding, identically located pixel in PreviousBits. If the difference in the intensities of a compared pixel pair is greater than a predetermined threshold, that pixel pair is counted as being different. Once all pixels have been compared, the percentage of different pixels is calculated. In alternate embodiments, the number of different pixels may be calculated without determining a percentage. This calculated pixel difference percentage is used to determine when a roll has started and stopped. When the algorithm is initiated,
this calculated percentage will be relatively low since virtually no pixels will be different.
FIG. 4 shows an example captured image frame 402. Captured image frame 402 is substantially light or white, because no finger was present in the image capturing area of fingeφrint scanner 102 when the frame was captured.
Fingeφrint image frames captured when no finger is present will have an overall lighter intensity value relative to when a finger is present.
FIG. 5 shows an example captured fingeφrint image frame 502 with a fingeφrint image 504 present. Fingeφrint image 504 represents the portion of a finger in contact with the fingeφrint scanner image capturing area or surface.
Because a fingeφrint image 504 was captured, captured fingeφrint image frame 502 will have an overall darker intensity value relative to captured image frame 402 (shown in FIG. 4). Hence, an increase in the calculated pixel difference percentage will occur after placing a finger in the image capturing area of a fingeφrint scanner.
Once the calculated pixel difference percentage goes beyond a predetermined start roll sensitivity threshold value (StartRollSensitivity), the algorithm goes into rolling mode. As soon as the percentage goes below a predetermined stop roll sensitivity threshold value (StopRollSensitivity), the algorithm exits rolling mode (discussed in greater detail below). As discussed above, in alternate embodiments, the number of different pixels may be calculated, without determining a percentage, and this number may be compared to a predetermined stop roll sensitivity threshold value.
FIG.3B provides a flowchart illustrating example steps for implementing step 304.
In step 314, a pixel intensity difference percentage value between a current fingeφrint image frame and a previous fingeφrint image frame is generated. In an alternate embodiment, a pixel intensity difference count value between a current fingeφrint image frame and a previous fingeφrint image frame may be generated. Control then proceeds to step 316.
-16-
In step 316, whether the generated pixel intensity difference percentage value is greater than a start roll sensitivity threshold percentage value is determined. In the alternate embodiment stated in step 314 above, whether a generated pixel difference count value is greater than a start roll sensitivity threshold value may be determined.
FIG.3 C provides a flowchart illustrating example steps for implementing an embodiment of step 316.
In step 318, a current fingeφrint image frame is captured. Control then proceeds to step 320. In step 320, the intensity of each pixel of the current fingeφrint image frame is compared to the intensity of a corresponding pixel of a previously captured fingeφrint image frame to obtain a pixel intensity difference count value. In embodiments, compared pixels are found different if their respective pixel intensity values are not the same. In alternative embodiments, compared pixels may be found different if their intensity values differ by greater than a pixel intensity difference threshold. The pixel intensity difference threshold may be established as a system variable, and may be set to a fixed value, or may be adjustable by a user. Control then proceeds to step 322.
In step 322, a pixel intensity difference percentage value is calculated. In an alternate embodiment, a pixel difference count value may be calculated.
In the following example of a preferred embodiment, a finger detected function (FingerDetected) is presented. This function may be called to detect whether a finger is present on a fingeφrint scanner.
BOOL FingerDetected(void) { double dDiff; double dDiffThreshold; short nPixelThreshold; dDiffThreshold = ((100 - m nRollStartSensitivity) * 0.08 / 100); nPixelThreshold = 20;
// calculate percentage change from previous DIB dDiff = FrameDifference((LPBITMAPINFO)&m_bmihPrevious, (LPBITMAPINFO)&m_bmih,
nPixelThreshold) ; if (dDiff > dDiffThreshold)
{ return TRUE;
} else
{ return FALSE;
}
In this preferred embodiment, the finger detected function calls a frame difference function. The frame difference routine calculates the percentage difference between two frames. This difference is calculated down to the pixel level. Two pixels are considered to be different is their values are more than a certain value (nDiff) apart. In the following example of a preferred embodiment, a frame difference function (FrameDifference) is presented.
double FrameDifference(LPBITMAPINFO IpBMInfol, LPBITMAPINFO lpBMInfo2, short nDiff)
{ // this method compares two frames and returns the percentage of pixels
// that are different. Two pixels are different if they differ by // more than nDiff
LPBYTE lpBitsl
LPBYTE lpBits2 double dPercentage; long ISize; long ICount; short nBytesPerPixel;
// make sure that the bitmaps are the same size if (IpBMInfol ->bmiHeader.biBitCount != _pBMInfo2->bmiHeader.biBitCount ||
IpBMInfol ->bmiHeader.bi Width != lpBMInfo2->bmiHeader.bi Width || IpBMInfol ->bmiHeader.biHeight != lpBMInfo2->bmiHeader.biHeight)
{
// bitmaps are 100% different since they are not // the same size return 1.0; } lpBitsl = (LPBYTE)lpBMInfol + sizeof(BITMAPI FOHEADER) +
(8 == IpBMInfol ->bmiHeader.biBitCount ? 1024 : 0); lpBits2 = (LPBYTE)lpBMInfo2 + sizeof(BITMAPINFOHEADER) +
(8 == lpBMInfo2->bmiHeader.biBitCount ? 1024 : 0); nBytesPerPixel = IpBMInfol ->bmiHeader.biBitCount / 8;
if (IpBMInfol ->bmiHeader.biBitCount % 8)
{ nBytesPerPixel++;
} ISize = IpBMInfol ->bmiHeader.bi Width * IpBMInfol ->bmiHeader.biHeight nBytesPerPixel;
ICount = 0; for (long llndex = 0; llndex < ISize; llndex++)
{ if (abs(lpBitsl [llndex] - lpBits2[Hndex]) > nDiff)
{ lCount++;
} } dPercentage = ICount / (double)lSize; return dPercentage;
In embodiments, fingeφrint roll detector module 216 of FIG. 2B may comprise one or both of the FingerDetected and FrameDifference functions or hardware equivalents. Fingeφrint roll start detector module 222 of FIG.2C may comprise one or both of the FingerDetected and FrameDifference functions or hardware equivalents. Furthermore, when present, frame difference detector module 226 of FIG. 2E may comprise one or both of the FingerDetected and FrameDifference functions or hardware equivalents.
Capturing Fingerprint Image Frames
Returning to FIG. 3 A, in step 306, a plurality of fingeφrint image frames are captured. Fingeφrint image frames are captured from the fingeφrint image area of fingeφrint scanner 102. As discussed above, in an embodiment, a currently captured fingeφrint image frame is stored in CurrentBits, and a previously captured fingeφrint image frame is stored in PreviousBits. Portions of these arrays are combined in subsequent steps to form a composite fingeφrint image. Portions of one or both of the fingeφrint image frames that were used to
detect the start of a fingeφrint roll may also be used to form at least a portion of the composite fingeφrint image.
Determining a Centroid Window
In step 308, a centroid window corresponding to each of the plurality of captured fingeφrint image frames is determined. After the algorithm has detected that a fingeφrint roll has started, the task of combining pixels from captured fingeφrint image frames into a composite rolled fingeφrint image begins. However, all of the pixels in a particular frame are not necessarily read. Only those pixels inside a particular window, the "centroid window," are read. A centroid window comprises captured fingeφrint image pixels, substantially trimming off the non-relevant pixels of a captured fingeφrint image frame. By focusing only on the relevant portion of the captured frame, the processing of the captured frame can proceed much faster.
In an embodiment, to determine a centroid window, the leading and trailing edges of the fingeφrint image in a captured fingeφrint image frame are found. These edges are determined by sampling a thin strip of pixels in a pixel window across the center of a fingeφrint frame. FIG. 6 shows an example captured fingeφrint image frame 602 with a fingeφrint image 604 and a pixel window 606 present. Pixel window 606 is shown across the center of captured fingeφrint image frame 602. This generated pixel window is analyzed to determine the leading and trailing edges of fingeφrint image 604. A centroid window is then generated within the leading and trailing edges in fingeφrint image frame 602. An example centroid window 608 is shown in captured fingeφrint image frame 602. FIG. 7A shows a close-up view of an example pixel window 702. Pixel window 702 has a vertical pixel height often pixels. Pixels in pixel window 702 have two possible intensity values of 1 (light) or 0 (dark). These pixel height and intensity values for pixel window 702 are presented for illustrative puφoses, and do not limit the invention. A wide range of these attributes for example pixel
window 702 are possible, as would be known to persons skilled in the relevant art(s) from the teachings herein. For instance, in a fingeφrint image frame where an average fingeφrint ridge is five pixels high, a pixel window 702 of a height of twenty pixels be effectively used, fitting four fingeφrint ridges within the window on average.
Furthermore, in alternative embodiments, more than one pixel window 702 may be generated to determine a centroid window. For example, three pixel windows may be generated within the fingeφrint image frame, with pixel windows generated across the center, at or near the top, and at or near the bottom of the fingeφrint image frame. Generating more than one pixel window may provide advantages in locating a fingeφrint image within a fingeφrint image frame, particularly if the fingeφrint image is off-center.
A histogram is built from the generated pixel window. The histogram includes the total pixel intensity value for each column of pixels in pixel window 606. An example histogram 704 is shown graphically in FIG. 7B. Histogram
704 was built from pixel window 702 of FIG. 7A. Histogram 704 includes the total pixel intensity value for each column of pixels in example pixel window 702. For example, pixel column 706 of pixel window 702 has a total pixel intensity value of four, as indicated in histogram 704. Pixel columns 708 and 710 have respective total pixel intensity values of five and zero, as indicated in histogram 704.
To find the leading edge of a fingeφrint image, the algorithm scans the histogram in the direction opposite of the direction of the fingeφrint roll. The algorithm searches for a difference above a predetermined threshold between two adjacent columns. Where the total pixel intensity changes above the threshold value between columns, becoming darker, the leading edge is found. To find the trailing edge of the fingeφrint, the algorithm scans the histogram in the direction of the fingeφrint roll, in a similar fashion to finding the leading edge. The "x" coordinates of the leading and trailing edges of the histogram become the "x" coordinates of the leading and trailing edges of the centroid window.
In the example of FIGS. 7 A and 7B, the leading edge of a fingeφrint image may be found by scanning the histogram from right to left. When the predetermined threshold value is equal to four, for example, scanning the histogram will find a leading edge between pixel columns 708 and 710. In an embodiment, any column relative to a determined edge may be selected as a leading or trailing edge column. Additionally, for example, because column 708 is darker than column 710, column 708 may be chosen as the leading edge column.
FIG. 3D provides a flowchart illustrating example steps for implementing step 308 of FIG. 3A.
In step 324, a pixel window in a captured fingeφrint image frame is generated. Control then proceeds to step 326.
In step 326, a leading edge column and a trailing edge column of a fingeφrint image are found in the corresponding generated pixel window. Control then proceeds to step 328.
In step 328, a centroid window in the captured fingeφrint image frame bounded by the leading edge column found and the trailing edge column found is generated.
In a preferred embodiment, the window generated in step 328 is centered in an axis peφendicular to the direction that a finger is rolled. In such an embodiment, the generated window may include columns of a height of a predetermined number of pixels in the axis peφendicular to the direction that the finger is rolled. Furthermore, the generated window may have a length in an axis parallel to the direction that the finger is rolled equal to the number of pixels spanning the captured fingeφrint image frame along that axis.
FIG. 3 E provides a flowchart illustrating example steps for implementing step 326 of FIG. 3D.
In step 330, a histogram representative of the cumulative pixel intensity of pixels present in each column of the generated window is built. Control then proceeds to step 332.
In step 332, the histogram is scanned in the direction opposite of that in which the finger is rolled. The algorithm scans for a difference in the pixel intensities of adjacent columns of the generated window that is greater than a first fingeφrint edge. In an embodiment, the darker column of the adjacent columns is designated the leading edge column. In alternative embodiments, other columns, such as the other adjacent column, may be designated as the leading edge column. Control then proceeds to step 334.
In step 334, the histogram is scanned in the direction in which the finger is rolled for a difference in the pixel intensities of two adjacent columns that is greater than a second fingeφrint edge threshold. In an embodiment, the darker column of the adjacent columns is designated the trailing edge column. In alternative embodiments, other columns, such as the other adjacent column, may be designated as the trailing edge column.
In the following example of a preferred embodiment, a find centroid function (FindCentroid) is presented. The FindCentroid function may be called to determine a centroid window. The function builds a histogram from a generated pixel window in a captured fingeφrint image frame, and searches from left to right and then right to left through the histogram, looking for the edges of a fingeφrint.
BOOL FindCentroid(short * pnLeft, short * pnRight)
{
LPBITMAPINFO lpBMInfo;
LPBYTE lpCurrentBits; long * plHistogram; long llndex; short nBytesPerPixel; const short cnEdgeThreshold = 64; const short cnCushion = 20; short nLeft; short nRight; short nTop; short nBottom;
BOOL bFoundLeft = FALSE;
BOOL bFoundRight = FALSE: lpBMInfo = (LPBITMAI lpCurrentBits = (LPBYTE)lpBMInfo
(8 == lpBMInfo->bm_Header.biBitCount ? 1024 : 0);
nBytesPerPixel = lpBMInfo->bmiHeader.biBitCount / 8; if (lpBMInfo->bmiHeader.biBitCount % 8)
{ nBytesPerPixel++ ; }
// bounds check on acquisition parameters nTop = lpBMInfo->bmiHeader.biHeight / 2 - 10; nBottom = lpBMInfo->bmiHeader.biHeight / 2 + 10; if (nTop < 0) { nTop = 0;
} if (nBottom > lpBMInfo->bmiHeader.biHeight)
{ nBottom = lpBMInfo->bmiHeader.biHeight;
} nLeft = 0; nRight = lpBMInfo->bmiHeader.biWidth;
// build the histogram plHistogram = new long [lpBMInfo->bmiHeader.bi Width]; memset(plHistogram, 0, lpBMInfo->bmiHeader.biWidth * sizeof(long)); for (short nHeight = nTop; nHeight < nBottom; nHeight++)
{ for (short nWidth = nLeft; nWidth < nRight; nWidth++) { for (short nByte = 0; nByte < nBytesPerPixel; nByte++)
{ llndex = nHeight * lpBMInfo->bmiHeader.biWidth * nBytesPerPixel + nWidth * nBytesPerPixel + nByte; plHistogram[nWidth] = plHistogram[nWidth] + lpCurrentBitsfllndex];
} } } // find the left edge for (short nWidth = nLeft + 1 ; nWidth < nRight; n Width++)
{ if (abs(plHistogram [nWidth] - plHistogram[n Width - 1]) > cnEdgeThreshold)
{ *pnLeft = nWidth; bFoundLeft = TRUE; break; } } if (bFoundLeft)
{
// find the right edge for (short nWidth = nRight - 1 ; nWidth > *pnLeft; nWidth--)
{ if (abs(plHistogram[n Width] - plHistogram [nWidth - 1]) > cnEdgeThreshold)
*pnRight = nWidth; bFoundRight = TRUE; break;
} } }
// give the centroid some cushion *pnLeft -= cnCushion;
*pnRight += cnCushion; if(*pnLeft < 0)
{
*pnLeft = 0; } if (*pnRight > lpBMInfo->bmiHeader.bi Width)
{
*pnRight = lpBMInfo->bm_Header.biWidth;
} delete []plHistogram; return bFoundLeft && bFoundRight;
In an embodiment, centroid window determiner module 218 of FIG. 2B may implement the FindCentroid function or hardware equivalent.
Knitting Pixels
Returning to FIG. 3 A, in step 310, pixels of each determined centroid window are knitted into an overall fingeφrint image. Only pixels within the determined centroid window are considered for knitting. This has the advantage of increasing the speed of the knitting process. The centroid window provides an indication of where the finger is currently located on the fingeφrint scanner.
Therefore, it is not necessary to copy or knit pixels that are outside of this window.
In a preferred embodiment, the copying of pixels for knitting is a conditional copy based on the intensity, or darkness, of the pixel. In other words, the algorithm for copying pixels from the centroid window is not a blind copy. The algorithm compares each pixel of the ImageBits array with the corresponding pixel of the CurrentBits array. A pixel will only be copied from CurrentBits if the pixel is darker than the corresponding pixel of ImageBits. This rule prevents the image from becoming too blurry during the capture process. This entire process is referred to herein as "knitting."
FIG. 8 shows an example of pixel knitting for an example segment of a composite fingeφrint image. Segment 802 is a three pixel by three pixel segment of a current fingeφrint centroid (i.e., CurrentBits). Segment 804 is a three pixel by three pixel segment of a composite fingeφrint image (i.e., ImageBits). Segments 802 and 804 each include nine pixels. The intensity values of these pixels are shown. Each pixel of segment 802 is compared to the corresponding pixel of segment 804. The pixel of segment 804 is replaced by the corresponding pixel of segment 802 if the pixel of segment 802 has a darker intensity value (e.g. a lower intensity value). A resulting knitted composite fingeφrint image segment 806 is created.
For example, pixel 808 has an intensity value of 94. Pixel 808 is compared against pixel 810, which has an intensity value of 118. Because the intensity value of pixel 808 is darker than that of pixel 810 (i.e., 94 is a lower intensity value than 118), the intensity value of pixel 812 is set to the new pixel intensity value of pixel 808. Likewise, pixel 814 has an intensity value of 123. Pixel 814 is compared against pixel 816, which has an intensity value of 54. Because the intensity value of pixel 816 is darker than that of pixel 814 (i.e., 54 is a lower intensity value than 123), the intensity value of pixel 818 remains that of pixel 816.
FIG. 3F provides a flowchart illustrating example steps for implementing step 310 of FIG. 3 A.
In step 336, the intensity of each pixel of the determined centroid window is compared to the intensity of the corresponding pixel of an overall fingeφrint image. Control then proceeds to step 338.
In step 338, the pixel of the composite fingeφrint image is replaced with the corresponding pixel of the determined centroid window if the pixel of the determined centroid window is darker than the corresponding pixel of the composite fingeφrint image.
In the following example of a preferred embodiment, a pixel knitting function (CopyConditionalBits) is presented. The CopyConditionalBits function copies pixels from the determined centroid window (CurrentBits) into the overall image (ImageBits). The function does not blindly copy the pixels. Instead, the function will only copy a pixel if the new value is less than the previous value.
void ConditionalCopyBits(short nLeft, short nRight)
{ LPBITMAPINFO lpBMInfo;
LPBYTE lpCaptureBits; long llndex; short nBytesPerPixel; lpBMInfo = (LPBITMAPINFO)&m_bmih; lpCaptureBits = (LPBYTE)lpBMInfo + sizeof(BITMAPINFOHEADER) +
(8 == lpBMInfo->bmiHeader.biBitCount ? 1024 : 0); nBytesPerPixel = lpBMInfo->bmiHeader.biBitCount / 8; if (lpBMInfo->bmiHeader.biBitCount % 8) { nBytesPerPixel++; }
// copy pixels from capture window only if less than previous for (short nHeight = 0; nHeight < lpBMInfo->bmiHeader.biHeight; nHeight++) { for (short nWidth = nLeft; nWidth < nRight; nWidth++)
{ for (short nByte = 0; nByte < nBytesPerPixel; nByte++)
{ llndex = nHeight * lpBMInfo->bmiHeader.biWidth * nBytesPerPixel + nWidth * nBytesPerPixel + nByte;
// only copy if the new value is less than the previous if (mJpRollBits[Hndex] > lpCaptureBitsfllndex])
{ JpRollBitsfllndex] = lpCaptureBits[Hndex];
} } // end for }
In an embodiment of the present invention, pixel knitting module 220 of FIG. 2B may implement the CopyConditionalBits function or hardware equivalent.
Detecting End of Fingerprint Roll
Returning to FIG. 3 A, in step 312, the end of a fingeφrint roll is detected.
After a fingeφrint roll is complete, the user will remove their finger from the fingeφrint scanner image capturing area. The system detects that the user has removed their finger, and ends the rolled fingeφrint capturing algorithm. At this point, an overall rolled fingeφrint image has been generated. FIG. 9 shows an example of an overall rolled fingeφrint image 902, displayed in a rolled fingeφrint display panel 904. Overall rolled fingeφrint image 902 of FIG. 9 is a composite image, generated according to the present invention.
Returning to FIG. 3 A, step 312 operates substantially similar to step 304, where the start of a fingeφrint roll is detected. As discussed above, in a preferred embodiment, a method for detecting a finger on fingeφrint scanner 102 is based on a percentage change from a previously captured fingeφrint image (PreviousBits) to a currently captured fingeφrint image (CurrentBits). Each pixel in CurrentBits is compared against the corresponding, identically located pixel in PreviousBits. If the difference in the intensities of a compared pixel pair is greater than a predetermined threshold, that pixel pair is counted as being different. Once all pixels have been compared, the percentage of different pixels is calculated. In alternate embodiments, the number of different pixels is calculated without determining a percentage.
As discussed above, this calculated pixel difference percentage is used to determine when a roll has started and stopped. When the rolled fingeφrint
capture algorithm is operating, and a fingeφrint is being captured, this percentage will be relatively low because a relatively small number of pixels will be changing during the roll. However, when the user removes their finger from the scanner surface, the difference percentage will increase, as fingeφrint image data is no longer being captured.
As discussed above, as soon as the percentage goes below a predetermined stop roll sensitivity threshold value (StopRollSensitivity), the algorithm exits rolled fingeφrint capture mode.
FIG.3 G provides a flowchart illustrating example steps for implementing step 312 of FIG. 3 A.
In step 340, a pixel intensity difference percentage value between a current fingeφrint image frame and a previous fingeφrint image frame is generated. In an alternative embodiment, a pixel intensity difference count value between a current fϊngeφrint image frame and a previous fingeφrint image frame may be generated. Control then proceeds to step 342.
In step 342, whether the generated pixel intensity difference percentage value is less than a stop roll sensitivity threshold percentage value is determined.
In the alternate embodiment mentioned in step 340, whether a generated pixel intensity difference count value is greater than a stop roll sensitivity threshold value may be determined.
FIG. 3C provides a flowchart illustrating example steps for implementing an embodiment of step 340, and is described in more detail above in reference to step 304 of FIG. 3 A.
A finger detected function (FingerDetected) is presented above in reference to step 304 of FIG. 3 A. This function may be called to detect whether a finger is present on a fingeφrint scanner. Refer to the section above for a more detailed description of this function. Furthermore, a frame difference function (FrameDifference) is also presented above in reference to step 304 of FIG. 3 A. This function may be called to calculate the percentage difference between two frames. Refer to the section above for a more detailed description of this function.
In embodiments, fingeφrint roll stop detector module 224 of FIG.2C may comprise one or both of the FingerDetected and FrameDifference functions described above or hardware equivalents.
Rolled Fingerprint Display Panel
In an embodiment, rolled fingeφrint display panel 904 of FIG. 9 is an example display panel that allows a user to input rolled fingeφrint capture parameters, to begin a roll, and to view fingeφrint images, among other functions. Some of these functions may include: indicating when a finger is present on the fingeφrint scanner; permitting a user to select a roll speed for setting a fingeφrint image capturing area sampling interval; permitting a user to select a start sensitivity threshold value for detecting a start of a fingeφrint roll; permitting a user to select a stop sensitivity threshold value for detecting a stop of a fingeφrint roll; permitting a user to select a guided roll mode; permitting a user to activate a roll mode; permitting a user to freeze/unfreeze a rolled fingeφrint image; permitting a user to save an overall fingeφrint image; permitting a user to alter the video properties of the fingeφrint scanner; and permitting a user to exit the rolled fingeφrint capture algorithm.
Example Computer System
An example of a computer system 104 is shown in FIG. 10. The computer system 104 represents any single or multi -processor computer. Single-threaded and multi-threaded computers can be used. Unified or distributed memory systems can be used.
The computer system 104 includes one or more processors, such as processor 1004. One or more processors 1004 can execute software implementing the routine shown in FIG. 3 A as described above. Each processor
1004 is connected to a communication infrastructure 1002 (e.g., a communications bus, cross-bar, or network). Various software embodiments are
described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the relevant art how to implement the invention using other computer systems and/or computer architectures. Computer system 104 may include a graphics subsystem 1003 (optional).
Graphics subsystem 1003 can be any type of graphics system supporting computer graphics. Graphics subsystem 1003 can be implemented as one or more processor chips. The graphics subsystem 1003 can be included as a separate graphics engine or processor, or as part of processor 1004. Graphics data is output from the graphics subsystem 1003 to bus 1002. Display interface 1005 forwards graphics data from the bus 1002 for display on the display unit 106.
Computer system 104 also includes a main memory 1008, preferably random access memory (RAM), and can also include a secondary memory 1010. The secondary memory 1010 can include, for example, a hard disk drive 1012 and/or a removable storage drive 1014, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive 1014 reads from and/or writes to a removable storage unit 1018 in a well known manner. Removable storage unit 1018 represents a floppy disk, magnetic tape, optical disk, etc., which is read by and written to by removable storage drive 1014. As will be appreciated, the removable storage unit 1018 includes a computer usable storage medium having stored therein computer software and/or data.
In alternative embodiments, secondary memory 1010 may include other similar means for allowing computer programs or other instructions to be loaded into computer system 104. Such means can include, for example, a removable storage unit 1022 and an interface 1020. Examples can include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM, or PROM) and associated socket, and other removable storage units 1022 and interfaces 1020 which allow software and data to be transferred from the removable storage unit 1022 to computer system 104.
Computer system 104 can also include a communications interface 1024. Communications interface 1024 allows software and data to be transferred between computer system 104 and external devices via communications path 1026. Examples of communications interface 1024 can include a modem, a network interface (such as Ethernet card), a communications port, etc. Software and data transferred via communications interface 1024 are in the form of signals which can be electronic, electromagnetic, optical or other signals capable of being received by communications interface 1024, via communications path 1026. Note that communications interface 1024 provides a means by which computer system 104 can interface to a network such as the Internet.
Graphical user interface module 1030 transfers user inputs from peripheral devices 1032 to bus 1002. In an embodiment, one or more peripheral devices 1032 may be fingeφrint scanner 102. These peripheral devices 1032 also can be a mouse, keyboard, touch screen, microphone, joystick, stylus, light pen, voice recognition unit, or any other type of peripheral unit.
The present invention can be implemented using software running (that is, executing) in an environment similar to that described above with respect to FIG. 10. In this document, the term "computer program product" is used to generally refer to removable storage unit 1018, a hard disk installed in hard disk drive 1012, or a carrier wave or other signal carrying software over a communication path 1026 (wireless link or cable) to communication interface 1024. A computer useable medium can include magnetic media, optical media, or other recordable media, or media that transmits a carrier wave. These computer program products are means for providing software to computer system 104.
Computer programs (also called computer control logic) are stored in main memory 1008 and/or secondary memory 1010. Computer programs can also be received via communications interface 1024. Such computer programs, when executed, enable the computer system 104 to perform the features of the present invention as discussed herein. In particular, the computer programs, when executed, enable the processor 1004 to perform the features of the present
invention. Accordingly, such computer programs represent controllers of the computer system 104.
In an embodiment where the invention is implemented using software, the software may be stored in a computer program product and loaded into computer system 104 using removable storage drive 1014, hard drive 1012, or communications interface 1024. Alternatively, the computer program product may be downloaded to computer system 104 over communications path 1026. The control logic (software), when executed by the one or more processors 1004, causes the processor(s) 1004 to perform the functions of the invention as described herein.
In another embodiment, the invention is implemented primarily in firmware and/or hardware using, for example, hardware components such as application specific integrated circuits (ASICs). Implementation of a hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s).
Conclusion
While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the invention. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.