Based on the above 3 components mentioned above, the Enrollment Station is to do capture of the various multi-biometric templates and will interface will various biometric devices being supported. These data will be stored at a biometric database repository at the IDCube Management Server. The IDCube Server serves to receive client request from various biometric application such as security access, mobile biometric devices. It then sends these request to the Backend IDCube Matching engine for quick identification. It can also send to other 3rd party matching engines if the biometric technology is new or not supported
a) Enrollment Station Module
i) The Enrollment Station Module is a biometric enrollment application to enroll a user’s Face, Fingerprint, IRIS, etc. It can also incorporate various RF Cards to store the biometrics such as Mifare or Iclass or other Card formats.
ii) The module uses IDCube desktop to manage user profiles including the various biometric raw data and templates. It also interfaces to multiple hardware devices providing a consistent management user interface for common tasks such as user management and transaction reporting.
iii) IDCUBE Desktop will gather biometric samples, extract biometric template information from them, and send extracted template matching to IDLink’s Multi-Biometric Matching Engine. For example, IDCUBE Desktop will need to check for duplicates before allowing the enrollment process to succeed.
iv) The following standards are supported by us to interface with other Biometric systems that conform to the following standards:
a. BioAPI 2.0 (ISO/IEC 19784-1:2006) Framework and Biometric Service Provider (BSP) for face, fingerprint and iris identification engine
b. ISO/IEC 19794-2 (Information technology – Biometric data interchange formats – Part 2: Fingerprint minutiae data)
c. ISO/IEC 19794-4 (Information technology – Biometric data interchange formats – Part 4: Finger image data)
d. ISO/IEC 19794-5 (Information technology – Biometric data interchange formats – Part 5: Face image data)
e. ISO/IEC 19794-6 (Information technology – Biometric data interchange formats – Part 6: Iris image data)
f. ANSI/INCITS 378-2004 (Finger Minutiae Format for Data Interchange)(ANSI378)
g. ANSI/INCITS 381-2004 (American National Standard for Information Technology – Finger Image-Based Data Interchange Format)
h. ANSI/INCITS 385-2004 (American National Standard for Information Technology – Face Recognition Format for Data Interchange)
i. ANSI/INCITS 379-2004 (American National Standard for Information Technology – Iris Recognition Format for Data Interchange)
j. ANSI/NIST-ITL 1-2007 (Data Format for the Interchange of Fingerprint, Facial, & Other Biometric Information - Part 1)
v) The following Biometric sensors are supported by our IDCube Desktop Enrollment Module:
FINGERPRINT
• ARH AFS 510
• Atmel FingerChip
• BioLink U-Match MatchBook v.3.5
• Biometrika Fx2000 / Fx3000
• Biometrika HiScan
• Cross Match L SCAN Guardian
• Cross Match Verifier 300 / 310 / 320
• Dakty NAOS-A
• Dermalog ZF1
• Digent FD1000
• DigitalPersona U.are.U 2000
• DigitalPersona U.are.U 4000 / 4500
• Fujitsu MBF200
• Futronic FS50 / FS80 / FS82 / FS88 / FS90 / eFAM (FS84)
• Futronic FS60
• Green Bit DactyScan 26
• Hongda S680
• id3 Certis Image
• Identix DFR 2080 and DFR 2090
• Identix DFR 2100
• Intech SOP1
• Integrated Biometrics LES650
• Jstac Athena 210
• LighTuning LTT-C500
• Lumidigm Venus Series sensors
• NITGEN Fingkey Hamster / Fingkey Hamster II / Fingkey Mouse III / eNBioScan-F
• SecuGen Hamster III / Hamster Plus / Hamster IV
• Startek FM200
• Suprema BioMini / RealScan-10 / RealScan-D / RealScan-S / SFR300-S / SFU300
• Tacoma CMOS
• Testech Bio-i
• UPEK Eikon / Eikon To Go / EikonTouch 300 / 700 / TouchChip TCRU1C / TCRU2C
• VistaMT Multimodal Biometric Device(1)
• Zvetco Verifi P5000
• ZKSoftware ZK6000
FACIAL CAPTURE CAMERA
• Cisco 4000 series cameras;
• Mobotix DualNight M12 IP camera (Microsoft Windows only);
• PiXORD IP cameras (Microsoft Windows only);
• Prosilica GigE Vision camera (Microsoft Windows only);
• VistaFA 2 / VistaFA 2E face & iris cameras (Microsoft Windows only);
• VistaMT Multimodal Biometric Device (Microsoft Windows only);
• Any other webcam or camera that is accessible using: DirectShow interface for Microsoft Window
IRIS CAPTURE
• Cross Match I Scan 2
• VistaFA2 / VistaFA2E iris & face cameras
• VistaMT Multimodal Biometric Device
b) IDCube Server Management System
i) The IDCube Server Management Sytem is a repository for various biometric data collected during the enrollment process. It receives request from any client biometric application and send the relevant biometric templates for backend matching via the IDCube Multi-Biometric Matching Engine
ii) IDCUBE Server is designed from ground up to manage multiple biometrics and card-based identifications systems from within a single framework. Its core functionalities include handling of multiple devices, template and transaction management, and reporting from a PC or laptop computer.
iII) IDCUBE Server incorporates web services to facilitate integration with third party systems. This is in addition to the ability to import and export XML, CSV or Fixed Field format files.
iv) IDCUBE Server provides the following features including role-based functional access, consistent interface to a set of common functionalities like managing multiple biometric and card devices, standard reporting for audit trail and transactions, user profile grouping, web services external interface, file import/export as well as time attendance integration.
v) IDCUBE Server Database will be used to store the following data which consists of user profiles including user details, biometric data (both raw and templates) plus card information, transactions, audit trail, and device information.
c) IDCube Multi-biometric Matching Engine
i) The Multi-biometric Matching Engine is designed for high productivity AFIS with millions of fingerprints stored in the database.
ii) IDCube Matching Engine Cluster distributes identification tasks over computers connected to the network. The cluster can be scaled up anytime to meet changing requirements in increasing user amount or request environment. The cluster consists of a MegaMatcher Cluster Server and a number of MegaMatcher Cluster Nodes.
iii) IDCube Multi-Biometric Cluster Server accepts requests from IDCube Server Management system, manage cluster network, distributes tasks over Biometric Engine Cluster Nodes, collects results, reports them back to IDCube Server management System.
iv) Each Cluster Node matches up to 160,000 fingerprints per second (on Intel Core2 processor with 4 cores running at 2.66 GHz). The Cluster can be used for multi-biometric systems that use any combination of these biometric modalities: fingerprints, faces and/or irises.
v) A Cluster Node contains part of the main database, performs identification tasks in it and reports 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.
vi) To provide for fault tolerance, spare nodes can be enabled. A spare node waits until an operating node fails and is used to replace the failed one by copying the part of the database that was used in the failed node. If the failed node is restored, it becomes the spare node.
