Griaule Biometrics

In fact, the only difference between the both versions is the matching speed. While the Verification version does, at maximum, 100 matchings per second, the Identification version does up to 35.000 matchings per second.

They are useful in different scenarios. An example of these scenarios are given below.

Scenario of use for the Fingerprint Verification SDK

• Appropriate for 1:1 matching;
• It requires an id + the template for the matching;
• Fast processing, involves only one matching;
• The user should in general give an id (e-mail, login name, NINO, etc).

Example:

1. Imagine a login screen, asking the user to be identified;
2. At this screen the id should be given and then the fingerprint captured through the fingerprint reader (template format);
3. The program then searches (in the database, e.g.) the record registered under the given id;
4. The program retrieves the content of the template field of the retrieved record;
5. Now the program uses the Fingerprint Verification SDK to know if the captured template at login screen is the same as the retrieved from the record;
6. If the matching returns true, the user can access the system;
7. If the matching returns false, the access should be denied;
8. The process of identifying the user finishes.

Scenario of use for the Fingerprint Identification SDK

• Appropriate for 1:N matching;
• It requires only the fingerprint template for the matching;
• Processing time dependent on the number (N) of templates, involves N matchings;
• The user does not need to give an id (e-mail, login name, NINO, etc).

Example:

1. Imagine a login screen, asking the user to be identified;
2. At this screen the fingerprint should be captured through the fingerprint reader (template format);
3. The program starts the loop through all user records in the system;
4. For each user in the system, the program retrieves the template content;
5. The program uses the Fingerprint Identification SDK to know if the captured fingerprint template is the same as the one of the current user record;
6. If the matching returns true, stops the loop and the user can have access to the system;
7. If the matching returns false, does not do anything and keep on doing the loop;
8. In case the loop reaches the end of the user list and no positive matching was identified, the access to the system should be denied;
9. The process of identifying the user finishes.