MegaMatcher Accelerator Standard - Fingerprint Edition

Solution for large-scale AFIS or multi-biometric systems

Click Here to download the full MegaMatcher SDK brochure as a .pdf document

MegaMatcher Standard Accelerator 3.0 is a solution for fast template matching on server-side part of a large-scale AFIS or multi-biometric system. The Extended versions of this product include server hardware and software for fast biometric template matching on server-side part of a large-scale AFIS or multi-modal system. The Standard version is intended to be run on a common PC/Server and does not include any hardware.

MegaMatcher Accelerator 3.0 Extended units and MegaMatcher Accelerator 3.0 Standard software can be purchased by new and existing MegaMatcher SDK, VeriFinger SDK and VeriEye SDK customers.

Advantages of MegaMatcher

• Available as ready-to-use biometric solution with server hardware
  or as biometric software for running on a common PC.
• Up to 200,000,000 irises or 100,000,000 fingerprints per second matching speed on a single unit.
• Fingerprint, iris and face modalities supported.
• Scalable cluster architecture.
• ISO & ANSI fingerprint template standards support.
• Suitable for duplicates search.

MegaMatcher Accelerator Standard Technology

• MegaMatcher Accelerator in high productivity biometric systems. MegaMatcher SDK and MegaMatcher Accelerator include cluster software that allows to scale up the AFIS or multi-biometric system to reach the required response time, database capacity and system robustness… Read more
• MegaMatcher Accelerator 3.0 Standard. Available in 3 versions with fast fingerprint, iris or fused iris-fingerprint matching engines. All versions include installation CD with Linux and biometric matching software. Read more
• Technical specifications.  The Standard version stores 3 million fingerprints or 5 million irises and matches 35 million fingerprints or 70 million irises per second.The Extended version stores 30 million fingerprints or 50 million irises and matches 100 million fingerprints or 200 million irises per second.  Read more
• Reliability and performance tests. Experiments with fingerprint, iris and mixed fingerprint-iris databases have been performed. Matching speeds and ROC charts are available. Read more
• System requirements for MegaMatcher Accelerator Standard... Read more
• Technical support. Free unlimited technical support is provided by Neurotechnology for MegaMatcher Accelerator. Read more
• Evaluation. Fulcrum Biometrics can provide access to MegaMatcher Accelerator Standard or Extended units running at remote locations for evaluation purposes. Please contact us for more information.
  

Back to top of this page

MegaMatcher and MegaMatcher Accelerator in High Productivity Systems

Different large-scale biometric projects may require specific system performance. These matching engines and architectures may be used depending on the required matching speed, database size and system availability:

• Single Matching Server;
• Cluster of PCs running MegaMatcher components;
• Single MegaMatcher Accelerator 3.0 Standard or Extended unit;
• Cluster of MegaMatcher Accelerator 3.0 Standard or Extended units.

The charts below compare the different architectures for high performance AFIS or multi-biometric systems.

It is possible to use more than one architecture within a large-scale biometric system to reach optimal system performance and/or availability. For example, MegaMatcher Accelerator 3.0 unit(s) can be used for candidates selection using irises or several fingerprints, and then the results can be validated on Matching Server or Cluster with other biometric modalities. Also, two or more Clusters Servers or MegaMatcher Accelerator 3.0 clusters can be connected together for high availability system.

Single Matching Server

The architecture with a single Matching Server is intended to be used in moderate size systems like local AFIS or multi-biometric system which do not have strict requirements on performance or availability. The Matching Server software is available in MegaMatcher 4.0 Standard and Extended SDKs, as well as in VeriFinger 6.3 Extended SDK, VeriLook 5.0 Extended SDK and VeriEye 2.3 Extended SDK.

A PC running Matching Server software accepts identification requests from client-side components for fingerprint, face and/or iris biometrics and returns back the identification results. Up to 160,000 fingerprints or 1,200,000 faces or 1,440,000 irises per second can be matched on single Matching Server (on Intel Core2 processor with 4 cores running at 2.66 GHz).

The Matching Server can be also used for multi-biometric systems that use any combination of these biometric modalities: fingerprints, faces and/or irises.

Cluster of PCs running MegaMatcher components

This architecture is designed for high productivity AFIS or multi-biometric system with millions of biometric templates stored in the database. The Cluster Server component is available in MegaMatcher Extended SDK.

Cluster Server distributes identification task over computers connected to the network. A biometric system based on Cluster Server software can be scaled up anytime to meet changing project requirements in increasing user amount or request environment. The cluster software consists of a Cluster Server and software for cluster nodes that run fingerprint, face and/or iris components.

The Cluster Server accepts requests from client side, manages cluster work, distributes tasks over cluster nodes, collects results, reports them back to client side. Also it communicates with the main database which stores the biometric data.

Each cluster node matches up to 160,000 fingerprints or 1,200,000 faces or 1,440,000 irises per second (on Intel Core2 processor with 4 cores running at 2.66 GHz). The Cluster Server can be also used for multi-biometric systems that use any combination of these biometric modalities: fingerprints, faces and/or irises.

A cluster node contains part of the main database, performs identification tasks in it and reports results to the Cluster Server. The node must have enough memory to store that database part, as all data is kept in memory during identification to achieve the best matching speed. A larger number of nodes results in faster matching, because each node operates on a smaller part of the database.

The cluster node uses database to store its database part and in order to perform relational queries, such as filter persons by gender, age, living place.

The amount of required cluster nodes is calculated is this way:

1. The whole database should fit into nodes memory (RAM). For example, if there are 10GB of biometric data and each node has 2GB of free memory available, at least 5 nodes should be used as otherwise the database will not fit into nodes memory and the cluster will not work.
2. The identification speed should satisfy project requirements. The speed requirements may be defined indirectly via identification request response time and/or peak hour request quantity with a given database.
   • Response time. For example, a database stores biometric data for 1 million people with 2 fingerprints for each of them, and the response time for an identification request should be 1 second. At least 13 cluster nodes should be used to provide the required response time.
   • Peak hour request quantity. For example, the project with the same database as above requires to process 5,000 identification requests at the peak hour. At least 18 cluster nodes should be used to provide the required peak hour availability.

Two methods of node fault tolerance are implemented in Cluster Server software:

1. Spare nodes (enabled by default). A spare node "waits" until an operating node fails and is used to replace the failed one by copying the part of database that was used in the failed node. If the failed node restored, it become the spare node.
2. Re-split tasks and database over existing nodes. If a node fails, the system finishes all tasks which are not related with the failed node, reinitializes nodes again by re-splitting the database over them and continues tasks passed into cluster. As a result the overall cluster performance decreases but the cluster continues to operate until the failed node is fixed or replaced.
   Note, that the database re-split is possible only if total amount of memory available in the remaining nodes is larger than the database size.

We recommend to leave at least 10%-20% free memory reserve when calculating the amount of used nodes in a cluster for both fault tolerance methods. The memory reserve would allow to avoid situations when the system can not continue work as it has not enough resourses.

Single MegaMatcher Accelerator 3.0 Standard or Extended unit

MegaMatcher Accelerator 3.0 is a solution for large-scale AFIS and multi-biometric projects and is available in two versions:

• MegaMatcher Accelerator 3.0 Standard is intended for biometric identification projects with up to several million people enrolled in database. This version includes ready-to-use server-side fingerprint and/or iris matching software for installation on a PC with Intel Core i7 processor and 12 GB of RAM. A single MegaMatcher Accelerator 3.0 Standard unit can store 3,000,000 fingerprints or 6,000,000 irises and matches 35,000,000 fingerprints or 70,000,000 irises per second. 
• MegaMatcher Accelerator 3.0 Extended is a solution for national-scale biometric identification projects with millions of people enrolled in database. This version includes ready-to-use HP Proliant server hardware with pre-installed OS and fingerprint and/or iris matching software. A single MegaMatcher Accelerator 3.0 Extended unit can store 30,000,000 fingerprints or 50,000,000 irises and matches 100,000,000 fingerprints or 200,000,000 irises per second.
  

A MegaMatcher Accelerator 3.0 unit accepts identification requests from PCs that run client-side software based on components for fingerprint, iris or face biometrics, performs identification and returns back the results.

MegaMatcher Accelerator can be also used as a part of scalable multi-biometric identification system that uses fingerprint, face and/or iris modalities. The fingerprints and/or irises would be matched using MegaMatcher Accelerator(s), whereas other modalities would be matched using Matching Server or Cluster Server software depending on project size and performance requirements. Also MegaMatcher Accelerator 3.0 software includes fingerprint, face and iris matching engines that may be used for results validation after fast fingerprint or iris matching inside the Accelerator unit instead of using MegaMatcher Server or Cluster.

Cluster of MegaMatcher Accelerator 3.0 Standard or Extended units

MegaMatcher Accelerator 3.0 Standard and Extended versions already include cluster software, thus multiple MegaMatcher Accelerator 3.0 Standard or Extended units can be connected via network to a cluster.

To create a cluster, one MegaMatcher Accelerator unit is assigned as a primary unit in the cluster while other MegaMatcher Accelerator units act as cluster nodes. Note that the primary unit of MegaMatcher Accelerator cluster will still perform fast fingerprint and/or iris matching while using only a small part of its resources for managing the cluster.

Each MegaMatcher Accelerator 3.0 Standard unit in the cluster matches 35 millions fingerprints or 70 millions irises per second, and each MegaMatcher Accelerator 3.0 Extended unit matches 100 millions fingerprints or 200 millions irises per second.

When started, the primary unit splits the whole biometric database, which is stored on its hard disk, and send parts of the database to all MegaMatcher Accelerators in the cluster. Later the primary unit waits for fingerprint and/or iris identification requests from client side, then distributes the identification request to the units of the cluster and returns the identification results to the client side.

The cluster of MegaMatcher Accelerators can be scaled up anytime to meet changing project requirements in increasing user amount or request environment. A larger number of MegaMatcher Accelerator units results in faster matching and higher number of requests processed, because each unit operates on a smaller part of the database.

For example, there is a database with 10 million people biometric data (4 fingerprints for each user, 40 million fingerprints in total). The amount of required MegaMatcher Accelerator units is calculated is this way:

1. The whole database should fit into memory of the MegaMatcher Accelerator units. A single MegaMatcher Accelerator 3.0 Extended unit stores 30 million fingerprints, thus 2 units required to store the sample 40 million fingerprints database.
2. The response time for an identification request should satisfy project requirements. For example, the project requires receive an answer to an identification request in 1 second. Single MegaMatcher Accelerator 3.0 Extended unit matches 29 million templates in 4-to-many mode, thus the two units will satisfy the project requirements for response time.
3. The peak hour request quantity should satisfy project requirements. For example, the project expects that there may be up to 30,000 identification requests per hour. Single MegaMatcher Accelerator 3.0 Extended unit matches 29 million templates in 4-to-many mode, thus it will be able to process 10,440 requests per hour with the sample 10 million template database. Therefore, a cluster of 3 MegaMatcher Accelerator 3.0 Extended units will be required to process the required number of identification requests with the sample database.

Fault tolerance for a cluster of MegaMatcher Accelerators can be provided using these methods:

1. Spare MegaMatcher Accelerator units. A spare MegaMatcher Accelerator 3.0 unit "waits" until an operating unit fails and is used replace the failed one. Switching time from "wait" state to "operating" state depends on time required to copy database part used by failed node into spare node. If the failed node restored, it become the spare node.
2. Spare cluster. Two clusters of MegaMatcher Accelerator 3.0 units can be used to provide higher availability and failover. The clusters should have the same database loaded into each of them. One of the clusters can be used as "spare" and wait, until the "active" one fails and replace it. Switching time is very small even in case of manual switch, as the spare cluster already contains the database.
3. Two parallel clusters. This method also requires to run two clusters of MegaMatcher Accelerator 3.0 units with the same database loaded into each of them. Both clusters can run in parallel and provide 2 times higher performance. If one cluster fails, the other one will continue operation and provide the nominal performance.

Note, that "spare cluster" and "two parallel clusters" methods may require additional software and hardware for building high-availability clusters.

Back to top of this page

MegaMatcher Standard Accelerator Versions

MegaMatcher Accelerator 3.0 Standard is a family of ready-to-use software products for fast fingerprint and iris matching on server-side part of an AFIS or multi-biometric system. These products are intended for large-scale biometric projects with up to several million people enrolled in database.

• These biometric matching engines can be used with MegaMatcher Accelerator 3.0 Standard:
  • Fast fingerprint and iris matching engines that can be used separately or together. See technical specifications for engines comparison and licensing model for engines availability.
  • Fingerprint, face and iris matching engines that can be used separately or together to validate matching results produced by the fast fingerprint and/or iris engines. 
• Includes an installation CD for a PC that meets system requirements.
  The installation CD includes:
  • Debian Linux OS;
  • MegaMatcher Accelerator 3.0 Standard software.
• Hardware is not included.
• Several PCs with the Standard Accelerator software can be combined to reach higher performance using the included cluster software.

Client communication module that allows sending a task to the MegaMatcher Accelerator, querying status of the task, getting the results and removing the task from it, is included with MegaMatcher 4.0 SDK, VeriFinger 6.3 SDK, VeriLook 5.0 SDK and VeriEye 2.3 SDK. This module hides all low level communications and provides high-level API for the developer.

Back to top of this page

Technical Specifications

Database storage capacities for single MegaMatcher Accelerator 3.0 unit are:

• 30,000,000 fingerprint records or 50,000,000 iris records for each MegaMatcher Accelerator 3.0 Extended unit.
• 3,000,000 fingerprint records or 5,000,000 iris records for each PC that runs MegaMatcher Accelerator 3.0 Standard software.

If a biometric template contains several fingerprint and/or iris records, the database storage capacity changes proprtionally. The table below shows storage capacities for some combinations of fingerprints and/or irises records; there are no limitations on the quantity of fingerprint or iris records in a template. Please contact us to help you determine how many MegaMatcher Accelerators would be required for a specific project.

The tables below show the performance of MegaMatcher Accelerator 3.0 fast fingerprint and iris matching engines performance on the specified hardware.

Back to top of this page

Reliability and Performance Test Results

MegaMatcher Accelerator 3.0 Extended was tested on the specified server hardware.

MegaMatcher Accelerator 3.0 Standard was tested on hardware with these specifications:

• Intel Core i7-920 processor, running at 2.66 GHz;
• 12 GB of RAM;
• ASUS P6T SE motherboard;
• 2 x 1TB SATA hard disk drives;
• RTL8111/8168B PCI Express Gigabit Ethernet network card;
• bootable CD-ROM compatible device.

These template databases were used for testing MegaMatcher Accelerator 3.0 template matching algorithm reliability: Database 1 is the SONATEQ Fingerprint Database SQ FDB1-75TS1 that contains 75,000 fingerprints collected with Cross Match Verifier 300 LC scanner. The database represents 1,500 unique persons with 10 fingerprints per person captured in 5 sessions. Neurotechnology proprietary format was used for fingerprint templates storage. The tests were performed with these biometric template types: 1 fingerprint record – using right hand index fingerprints; 2 fingerprint records – using right and left hands index fingerprints belonging to the same person; 4 fingerprint records – using right hands slap (index, middle, ring and little fingerprints) belonging to the same person; 10 fingerprint records – using all 10 fingerprints belonging to the same person. Database 2 was created by merging iris images from BATH, Casia3 and ND-IRIS-0405 Iris Image Dataset. The irises from those 3 datasets were combined to form 1,500 unique persons with left and right irises captured in 5 sessions. The tests were performed with these biometric template types: 1 iris record – using right eye iris image; 2 iris records – using both eyes iris images belonging to the same person. Database 3 is a combination of Database 1 and Database 2. The database represents 1,500 unique persons with 10 fingerprints and 2 iris images per persons, captured in 5 sessions. The tests were performed with these biometric template types: 1 fingerprint + 1 iris records belonging to the same person; 1 fingerprint + 2 iris records belonging to the same person; 2 fingerprints + 1 iris records belonging to the same person; 2 fingerprints + 2 iris records belonging to the same person; 4 fingerprints + 1 iris records belonging to the same person; 4 fingerprints + 2 iris records belonging to the same person.

Database 1 Click to zoom Database 2 Click to zoom Database 3 Click to zoom

Reliability testing results for the MegaMatcher Accelerator 3.0 fingerprint template matching algorithm are shown as a receiver operation characteristics (ROC) charts. Note, that all tests with Database 3, except 1 finger + 1 iris, produced 0% FRR for all FAR values.

The MegaMatcher Accelerator 3.0 template matching algorithm performance was tested with full database capacities for both Standard and Extended units as specified above. The table below shows the performance testing results:

Back to top of this page

MegaMatcher Accelerator Extended Requirements

MegaMatcher Extended Accelerator is provided on a pre-configured HP Proliant Server Platform.  All requirements are taken care of in the custom server implementation.  Customers simply take delivery of the server after purchasing it.

Back to top of this page

Technical Support for Extended Accelerator

Fulcrum Biometrics and Neurotechnology provide free and unlimited technical support for MegaMatcher Accelerator over phone or email. Technical support covers issue resolution, bug fixing and providing the required technical information.

Back to top of this page