Biometric Subsystem Integration in SQL RDBMS

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Relational database management systems (RDBMS) are resource-intensive when processing biometric data, leading to delays in biometric analysis and matching requests, and existing systems do not effectively convert biometric data into templates for comparison or process it separately from demographic data.

Innovation Solution

Integration of a real-time biometric subsystem within the RDBMS using SQL extensions, which includes proprietary biometric management functions and a template data manager to process and convert biometric data into templates, allowing for separate processing from demographic data, enabling faster and more accurate queries with biometric constraints.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If biometric data is processed using traditional RDBMS, then data storage and management is achieved, but processing speed decreases and resource consumption increases

Engineering Contradiction:
Improvebiometric processing speedVSAvoidcomputing resource consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The system divides biometric data management into separate modules: a biometric data store for storing templates, a biometric management function for processing and converting data, and an RDBMS for demographic data. This segmentation allows each component to be optimized independently, with the biometric processing occurring separately from traditional database operations, thereby improving processing speed and reducing resource consumption on biometric analysis tasks.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If biometric data is stored and processed in RDBMS, then centralized management is achieved, but query accuracy and speed for biometric constraints deteriorates

Engineering Contradiction:
Improvecentralized data managementVSAvoidbiometric query accuracy
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The biometric management function acts as an intermediary layer between the RDBMS and biometric data. It receives biometric data, converts it into templates using proprietary algorithms, and stores them in the biometric data store. When queries are executed, this intermediary processes biometric constraints separately, ensuring accurate matching while maintaining centralized management through the integrated architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If biometric data is processed separately from demographic data, then processing speed improves, but system complexity increases

Engineering Contradiction:
Improvequery execution speedVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system merges the RDBMS with biometric processing capabilities by integrating the biometric management function and biometric data store into the overall system architecture. This combination allows biometric data to be processed separately for speed, while the integrated structure maintains ease of operation through unified access points and centralized management, effectively balancing complexity with performance.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9268904B1Systems and methods for biometric data management using relational database management systems (RDBMS)
Publication Date: 2016.02.23 IMAGEWARE SYSTEMS INC
  • US9268904B1 patent drawing
  • US9268904B1 patent drawing
  • US9268904B1 patent drawing

AI summary

A structured query language (SQL) relational database management system (SQL RDBMS) may integrate a biometric subsystem to process and manage biometric data separately from the demographic data stored in normalized SQL tables of the SQL RDBMS. The SQL RDBMS may be operatively connected to the biometric subsystem by means of SQL extensions. The SQL RDBMS may execute queries with demographic and/or biometric constraints, wherein the demographic data is retrieved directly from normalized SQL tables on the RDBMS, while the biometric data is retrieved in the form of scores or probabilities from the biometric subsystem. The SQL RDBMS may return a query result set containing demographic data associated with corresponding biometric data, allowing the authentication of biometric clients.